ASIO2 Direct Monitoring Scope PCI v5.1 Win 7 x64 NOT WORKING

[DrhiQ]

In Cubase 5.52 32bit ASIO2 Direct Monitoring Scope PCI v5.1 Win 7 x64 ( and Win 7 x86) gives no sound at all!!!

On Win XP x86 with same Cubase & Scope versions and projects (and all older versions) ASIO2 Direct Monitoring is working properly.

This function is essential for me, becouse my Scope system ( Scope 15 dsp & Pulsar II) serves as main 36 chn. in & 36chn. out interface in my hybrid (analog & digital) pro recording studio.

I am not complaining about old and persisting bugs ( wrong frequencies in EQs at 96kHz, phase problems, MIDI timing problems....), but this is lack of functionality in the driver. And this was paid driver update !!!

Please SonicCore make this as a high priority problem to fix.

MFG
Milan Prokop

[w_ellis]

Hi Milan,

Worth noting that this forum isn't an official support forum, so there may not be anyone from Sonic Core listening. I'd recommend forwarding your bug report with as much detail as possible to support@soniccore.de. Also following up with a phone call can be a good idea.

Thanks,
Will

[garyb]

direct monitoring?
are you using xtc mode?
if not, this seems to be a non sequitor. direct monitoring is not needed when the Scope mixer IS direct monitoring. or maybe i misunderstand....

[milanlkc]

direct monitoring?
are you using xtc mode?
if not, this seems to be a non sequitor. direct monitoring is not needed when the Scope mixer IS direct monitoring. or maybe i misunderstand....

If you do not need direct monitoring, how to use amplitube or any similar program?????
This post looks like a bad joke.

[DrhiQ]

Hi Milan,

Worth noting that this forum isn't an official support forum, so there may not be anyone from Sonic Core listening. I'd recommend forwarding your bug report with as much detail as possible to support@soniccore.de. Also following up with a phone call can be a good idea.

Thanks,
Will

Hi Will,

Yes I now that. I've sent an email to support@soniccore.de. Reason for posting here and at XITEd.org is to inform other Scope platform users in hope thet this problem is going to gain on priority.

Thanks,
Milan

[DrhiQ]

direct monitoring?
are you using xtc mode?
if not, this seems to be a non sequitor. direct monitoring is not needed when the Scope mixer IS direct monitoring. or maybe i misunderstand....

No XTC, never used.
Yes Direct Monitoring IS needed when the Scope system is just a part of a system in studio with large analog recording/mixing desk, 6 monitoring paths for artists, racks full of anal. & dig. outboard...

[DrhiQ]

direct monitoring?
are you using xtc mode?
if not, this seems to be a non sequitor. direct monitoring is not needed when the Scope mixer IS direct monitoring. or maybe i misunderstand....

If you do not need direct monitoring, how to use amplitube or any similar program?????
This post looks like a bad joke.

Hi milanlkc,

Actualy you can't use dir. monitoring if you want to hear the effect of ampltube or any other
native plugin in realtime. Instead you have to use lowest latency (buffers) settings possible for your system...

Thanks,
Milan

[milanlkc]

Hi DrhiQ

This is very familiar to me.
I am in love almost 10 years with SC (32 i/o), but with the new configuration Intel i5 750 and SC 5.1 x64 and all the settings as recommended on the website of SC, I am a dead man
There is a catch

[garyb]

how can amplitube do any faster than asio latency in realtime? impossible. cpu processing time is cpu processing time.

direct monitoring is NOT neeeded when monitoring is through Scope and NOT though the sequencer, but however it works for you is fine for me.

[the19thbear]

i cant see why you need direct monitoring in cubase/reaper etc when you have scope..


The way i do it is this:
adat source to scope mixer, send to headphonemix via aux. have a stereotrack coming from the asio daw (reaper/cubase etc) into the same mixer and send to headphones via aux as well.
that way they can hear palcyback and them selves.

maybe i dont understand your problem...

[DrhiQ]

i cant see why you need direct monitoring in cubase/reaper etc when you have scope..


The way i do it is this:
adat source to scope mixer, send to headphonemix via aux. have a stereotrack coming from the asio daw (reaper/cubase etc) into the same mixer and send to headphones via aux as well.
that way they can hear palcyback and them selves.

maybe i dont understand your problem...

how can amplitube do any faster than asio latency in realtime? impossible. cpu processing time is cpu processing time.

direct monitoring is NOT neeeded when monitoring is through Scope and NOT though the sequencer, but however it works for you is fine for me.

Hi the19thbear & garyb,

Thank you for trying to be helpfull, but your way is too slow and unreliable when I'm doing a 30 channels recording session with let say ten musicians in three different rooms, providing six different monitor mixes to them.

My "old school" workflow : Cubase monitoring is set to tape machine style and direct monitoring is on. All 30 channels are sent through the Sope to a 36 ( 72) chn. inline analog desk. Control Room mix ( what I hear), all 6 monitor mixes , talkback, and speaker selection are done on the desk. IMPORTANT is that I can freely Solo or AFL whatever and whenever I want wothout affecting the monitor mixes. Scope window is hiden ( not needed) most of the time. Track rec. arming, transport control operating, punchin' in & out, signal level checking and quick editing is all done in Cubase and is allready enough time-consuming for a Houston remote ctrl., keyboard and mouse.

I'm using this workflow and dir. monitoring function in ASIO2 Scope driver since around 2004. on WinXP with great sucsess and I would like to continue using it on Win7 x64.

Thanks
Milan

[the19thbear]

yeah... if you need to do everything in cubase with a control surface... then its a bummer!

Might not be a solution for you, but i have thought about buying a RME raydat pcie card (there is a version that has 32 adat channels i think, and you can link more if you want). its very cheap and can go to low latency settings..
i'm doubting the future of SC and when my scope cards die, i will get this solution in stead.
I dont doubt the future and stability of RME - so maybe you should sell your scope card and get that instead..just a thought..

in a perfect world scope would work with direct monitoring and you shouldnt have any problems

[garyb]

if you are bringing out all those tracks to a hardware mixer, there's no need for direct monitoring, nor for monitor mixes to be done in Cubase. you can still arm Cubase tracks with the controller. you don't need to solo tracks in Cubase. you are making a big redunant loop, but as i said before, i'm not here to tell you how to best use your gear.

six different monitor mixes?! does anything actually get recorded, or do you spend all your time holding the divas' hands? can you actually make money like that?