PlanetZ forums - scopeusers.com

Hello everyone, I have the following problem with cubase 5.5.1 and asio scope in XTC mode

My system is based on 1 Luna + 2 pulsar 1 cards scope 4

On my previous system based on Pentium 4 2.6 ghz and 1 Gb of ram and win xp home sp3 with scope 4 I never had any problems.

My new system is a dual core E7400 2.8 ghz 4 GB of RAM and motherboard asrock with the same configuration (the 3 cards and win xp home sp3).

When I select the inputs and outputs of Luna card from vst connection system crashes causing an error in asioscop.dll

Ok, from the scope routing windows I delete the connection between the Luna inputs and the mixer and i save the project as default.

Now I can select the output Luna card from vst connection without a crash but if i select also input Luna card it goes back to crash

I have also tryed to delete connection between the Luna output and mixer but without success.

I have installed the asio patch but the result does not change

Any suggestion?

Best regards

So under which of the following 3 scenarios does the problem occur :

1) In Scope alone when no Cubase running,
2) Using Cubase in XTC
3) Using Cubase after opening Scope in normal (non XTC ) mode.

Hi, the problem is only using Cubase in XTC mode

Well, mentioned here is an asioscop patch for Cubase

http://forums.planetz.com/viewtopic.php ... t=ASIOSCOP

I believe this may be it :
But Ive no idea if I ever used it ( I jumped from Cubase SL to Cubase 5 and never ran Cubase 4 so may not have needed it ) or no idea if it will fix your problem. If you decide to use it, do as the other topic suggested and back up your current one first.

Hi Dante, i have also tried this file but no success

you have Scope CLOSED in xtc mode, no?

garyb wrote:you have Scope CLOSED in xtc mode, no?

yes it is closed

Im running a similar system Cubase 5.5.0, Scope 5.0, Pulsar 2, Luna 2, Luna 2. Dont seem to have a problem ... am able to select all the Pulsar and Luna inputs after selecting the outputs :
Clutching at straws here, but did you try this after installing 5.0 but before installing 5.1 ? GaryB unless youve got any ideas do you think its re-install stuff time ?

you have scope 5, i have scope 4.
So i must update my scope

Yeah but that's not neccessarily your problem I believe Scope 4 should work. If you upgrade to Scope 5 and reinstall your cubase there's a chance the problem will go away though...

well, running the Scope and Cubase installers may correct a possibly corrupt file(just install over the top of the old installations), after you'll probably need to run the patch again. other than that, you got me...

have you checked for irq sharing with the card?

it is a fresh installation (WIndows, cubase and scope).
Yes the IRQ are correct not shared any card have your IRQ

I don't understand because on my old pc it is all ok and in this new i have this problem. Maybe the problem is the dual core?

Well got me stumped. You could try working in normal Scope (non XTC) mode - get used to it, and hope to find a fix later.

That way you could upgrade to 5.0 and if that didnt fix it, at least you could continue in Scope mode & be content with a bit less latency.

hi, i have solved
I remember once I had the same problem that i had solved as in image:

The problem is back
updated to Scope 5 all problem solved