PlanetZ forums - scopeusers.com

Hello,

I just noticed a little problem, maybe a bug:

Audio streams, routed directly from sequencer to scope platform, then back to sequencer results in a 6db boost!

All mastered tracks played back via asio from my sequencer are clipping 6db!
I hope there is an easy explanation for that...I didnt find anything in the manual.

thanks
Thomas

Off the top of my head i can only think that you need to check your Pan Laws on Cubase and on the SCOPE mixer - that's if we're talking about stereo signals.

thanks mr arkadin, there´s something wierd going on...here some screenshots: (see attachment)

I found that the 6db boost only occurs, when I use the mysterious 2 supposed-to-be-16bit-channels, which neundo shows me as the first 2 output options...with the others everything shows normal! (I ignored that thing, as it made no difference, and seemed not really to output only 16bit - I thought it was some kind of graphical error...)

That thing is really weird, since I use the 24bit source and the 24bit destination Adio modules in SFP.

Ok, the quick workaround would be, not to use the first 2 channels, but that´s not a clean soulution, I´d prefer it worked better.

any ideas?

Tom

Huh, weird. i would maybe try re-initialising the In/Outs in Nuendo to see if it comes up as 16 bit again - i never got anything like that in the same menu in SX. Looks more like Nuendo is doing something weird than SCOPE. Also it's showing 1 as 1L and 2 as 1R which is also a bit odd ass they should be stereo pairs. BTW i assume that project is just for test purposes?

yes this looks weird, Im just about checking this issue with other applications able to use asio, maybe soundforge can, but I´m not sure...

Yes well this was a standard project, but I used it to test this stuff

tom

i was just wondering why you would go ASIO out to ASIO in - just seems a bit odd to me.

no thats just a test arrangement

habits like these make me really think I should try to reinstall scope...

Does knowone know about this behaviour?

t

i would try a 'soft' re-install of SCOPE first ('hard' being completely deleting everything and starting from scratch). If you haven't done it in a while then maybe a Spring clean is in order. i would also re-install Nuendo and re-initialise the Output configuration as something is definitely up there - 1 and 2 should have their own stereo pairs.

it's just a cubase bug.

oh, thanks gary for that info, but how to cope with? any workarounds except not to use channel 1&2? do you know if the shown 16bit channels really only transmit 16 bit, so do they somehow truncate?

salutes
Tom

Use either "ASIO1... "- or "ASIO2... "-drivers (I prefere ASIO1), not "ASIO... "-drivers.

For Cubase, use "... -FLT 64 " (float, 64 channels maximum). Try again.

Cubase really wants to put out a 32-bit float format, so be kind to it.

Using the FLT-drivers will result in a propper 32-bit float to 32-bit integer conversion.

@voidar

same there, the first two channels show 16 bit something, the others only FLT...which might be ok - I dont know what reinitialize really means, except deleting the audio IOs in the vst connections manager, and reloading them.

I already tried to reinstall scope, I will try to do next with steinberg, see where it gets me

tom

Then it is as garyb said, a Cubase bug. Delete the bus-setup.

But you should really use the FLT-drivers ..

i deleted the bus setup, except if there is a bus setup file somewhere or a reinitialize button, bot else I did it already, I completely cleaned out my vst connections, and reloaded the stuff...ok, when I got time, I will reinstall nuendo

thanks
tom

it's an error in the reporting, not function.

Did you try cubase->devices->device setup->vst inputs (and outputs) -> reset

or did you just delete the vst outs and inns in VSt connections? cos that wouldnt make any difference.....

Endre

endre, you did it!

I just deleted vst outs and ins in vst connections manager---resetting it where you told specifically, brought everything back to normal!!!

thanks a million!...

Tom

Good!. Glad I could help

Endre

Also try, as others have suggested, using ASIO2 Dest-64 and ASIO2-32 Source64 (or ASIO2 Flt-Source 64) modules as well in future projects.