PlanetZ forums - scopeusers.com

Hello community!!!
I'm currently use SCOPE 4.5 on the pulsar 2, win xp server pack 3 and the cubase 5.
my problem is that some time when I'm open a project and press play there is no sound and I'm mean that even the level meters dosen't work.
on my routing window I use the ASIO1-Fit Source/Dest 64 and I connect only 4 channels via the vst connection.
this problem occurs once in awhile and then I'm getting error and the cubase crashes, and there was a time when I got a blue screen.
I tried to reinstall the cubase and the scope and it didn't help.
is it the software, hardware??
pleaes can some one explain me what is wrong???
and what I can do about it???

thanks...

blue screens are usually hardware related.

it's impossible to say what the problem is from that description. is it possible that you're starting Cubase before the Scope project is fully loaded, or that you're opening different Scope projects when Cubase is open?

thanks for the repliy....

no man of course no. I always starting with loading the scope project first & when it's done I'm opening the cubase & than the project. so if I whant for exampele to load some cubase project with diffrent scope project, I first shutdown the cubase & just than switching the scope project.
the problem is that there is no sound from the cubase while the track is playing, but from the winamp for exampele there is.
seems to me like some asio issue,becuse the last time it gave me a runtime error.

there aren't any ASIO driver issues in v4 which would cause this.

it might be a hardware issue. do you have this patch?
http://sonic-core.net/downloads/asiosco ... _patch.zip

As general practice I would always close down Cubase and then change Scope project then re-open Cubase. This is because changing the ASIO I/O on a Scope project whilst Cubase is open can upset Cubase's visibility of the ASIO channels.

A workaround for this is to change the Cubase driver to multimedia then back again to Scope, but this is a workaround only and not guarenteed in all cases, so its still better IMHO to close Cubase then re-open after changing Scope project.

Other smaller changes to a Scope project like adding a device here or there whilst Cubase is open is normally ok, as long as you dont exceed Scope resources - as this again can shut down ASIO comms for some seconds or more and upset Cubase.

seems that the patch helped ( I knew about the patch, I gust forgot about it).
but I still think that I have problems with the hardwere becuse some times when I loading the windows and the scope is automatically
loading to it gets ane erorr and I reseve windows error about the scope.

if i saw a screenshot of the error message, i might be able to say what it means.

the error window is the regular with the "submit errors to Microsoft", like in the follow link:
http://www.techkranti.com/2009/10/fix-s ... in-xp.html

that's a totally worthless pursuit. there is absolutely nothing to be gained by sending a report to m$, nor will that report contain useful information.

are you saying the app just crashes with no error message? that would most likely be an IRQ shared with a USB controller.
what, exactly, were you doing when the crash occured? what operation led to the crash? "nothing" or "the usual" or "just normal things" isn't a helpful enough description...
how did you check for irq sharing? if it was the card's properties in the device manager, that "no conflicts" message is basically useless. go to start\programs\accessories\system tools\system information\hardware resources\conflicts/sharing and tell me what, exactly, is sharing an irq with the Scope card(s).
unless you disabled a few things, the csards are sharing irqs with something. that's just how a "modern"(less than 10 years old) computer is.

if it only happens during the program loading at boot, then there may be an issue with the program "timing out" because of another program loading at the same time which delays the Scope program's access to the system for too long. you can disable automatic startup for other apps that start at boot(one at a time), to find the one making trouble. you can also ignore the crash, if things work correctly whaen the program is restarted, or you could disable autostart for Scope.

the crash occured some times in the boot procees only.
of course up until now I didn't know what is IRQ ( but thanks to you now I know ) and I didn't know what to do.
I go to the system information and I made a pic for you to see, becuse I still don't know what to do.
I do have 1 usb ( of the wireless keybord and mouse ) that allways conected.
I can see that some things are use the same irq 19 with the scope.
can I some how make changes, so the scope will have his own irq?

thsoe things that are shared shouldn't be a problem, but if you have another slot, you should try moving the card to another slot and then check again.