PlanetZ forums - scopeusers.com

I have this problem that suddenly both the ASIO and MIDI inputs/outputs of my Scope Professional card can't be recognized anymore by either Sonar 7 or Reason. I even went so far as to install WIndows XP from scratch, but that only helped a while and the problem is back in full effect.

Does anybody else recognize this problem? I have been looking whether there was any problem with the drivers,m but XP says they're okay.

Thanhks in advance...

Registry cleaners and 'system optimizers' are known for removing drivers from the registry...

valis wrote:Registry cleaners and 'system optimizers' are known for removing drivers from the registry...

I don't use those... and the drivers are not removed from the registry anyway. They seem to be in perfect working order when I inspect them in the Control Panel.

Things usually work fine with the default project. It goes wrong after I loaded a custom project, in which I re-wire the MIDI of Sonar to play a synth. I don't remove or add any I/O devices. But at times the default project won't work either.

I'm at a total loss here and my production rate has taken a nose-dive because of this. I am thinking about re-installing my Terratec, so I at least can get some work done.

the proper asio modules, with the proper number of channels, must be present in the project window BEFORE opening your asio app. when the app opens it checks to see what i/o is available and configures itself accordingly. for this reason, whenever the asio modules are changed(in size or type or because of loading a new project), the asio application(cubase or reason stand alone) MUST be closed FIRST, and the the change made, and then the asio host restarted.

just a guess, i hope this helped.

btw- the control panel is useless with scope.


if you are in XTC mode, use the I/O Enabler in the scope folder and start menu.....i'll bet it's set for no I/O somehow....

garyb wrote:the proper asio modules, with the proper number of channels, must be present in the project window BEFORE opening your asio app. when the app opens it checks to see what i/o is available and configures itself accordingly. for this reason, whenever the asio modules are changed(in size or type or because of loading a new project), the asio application(cubase or reason stand alone) MUST be closed FIRST, and the the change made, and then the asio host restarted.

I always do that. And as I said: it regularly doesn't work without any changes to the default project either.

if you are in XTC mode, use the I/O Enabler in the scope folder and start menu.....i'll bet it's set for no I/O somehow....

I don't use XTC, but thanks for the tip.

I would wonder if there's an electrical issue somewhere, or possibly an irq conflict that happens only infrequently.

After a long time of fiddling around I finally found the problem. I set Scope into bitrate slave mode to record the S/PDIF output of my Bass Pod Pro. because If I leave it at master mode, the recording will pop and crackle rhythmically, in stereo. As soon as I switch my Bass Pod off though, Scope won't load its drivers properly anymore... but the system doesn't give a warning either. So either I always have to keep the Bass Pod on, or I have to remember switching back to master mode. It's a pain, but it works.

Thanks for all your replies, folx.

well yes, you do need to have a clock source!