Hi all!
Yesterday I had the stupid idea of installing the scope SDK on my scope 5 production system (1x scope + 2x pulsar2). I switched all the drivers to the SDK drivers but the SDK didn´t start anyway.
After reinstalling the new v5 drivers using the automatic install function in the device manager, I had 3x Sonic Core Scope devices but not 1x Sonic Core Scope and 2x Sonic Core Pulsar2. Of course, scope 5 didn´t start anymore. After several tries I found the correct combination of card/driver and PCI slot.
-> Scope 5 is working.
BUT: Cubase SX says that "The ASIO Driver ASIO SCOPE could not be loaded"
Any ideas?
Scope SDK killed Scope 5
Re: Scope SDK killed Scope 5
After thousands of driver changes and reboots I resigned and turned the computer off. When I started it again a few minutes ago to do a backup and to reinstall windows, scope 5 started without any problems and cubase works too now...
I´ve got no idea, what the problem was.
I´ve got no idea, what the problem was.

- FrancisHarmany
- Posts: 1078
- Joined: Sun Jun 02, 2002 4:00 pm
- Location: Haarmania
Re: Scope SDK killed Scope 5
yeah. unplugging the computer and letting all the power drain out sometimes solves weird problems....
Re: Scope SDK killed Scope 5
some devices (may) need a so-called 'full power cycle', which means a restart isn't enough as power is kept on.
You have to turn the power switch.
Francis' idea is even better, as sometimes the big caps in the powersupply buffer enough current to 'fool' the system, so it's best to unplug the cord for a short while.
cheers, Tom
You have to turn the power switch.
Francis' idea is even better, as sometimes the big caps in the powersupply buffer enough current to 'fool' the system, so it's best to unplug the cord for a short while.
cheers, Tom
- siriusbliss
- Posts: 3118
- Joined: Fri Apr 06, 2001 4:00 pm
- Location: Cupertino, California US
- Contact:
Re: Scope SDK killed Scope 5
It requires a beer break between hard/full reboots before the system can totally configure itself properly.
Greg
Greg
Xite rig - ADK laptop - i7 975 3.33 GHz Quad w/HT 8meg cache /MDR3-4G/1066SODIMM / VD-GGTX280M nVidia GeForce GTX 280M w/1GB DDR3
Re: Scope SDK killed Scope 5

USB and MIDI are notorious for this too. That's why I have 2 hardware MIDI units chained together and hardware panic buttons. Sometimes you still have top unplug the cable physically.
What I love about my antique QX-1, Oberheim MC3000 and my first soundcard, the EgoSys WaMiRack, was they each had 8 x 8 MIDI and stuck notes were tracked down by knowing what sounds were on what cables and simply disconnecting them while still playing the parts.
Francis and Astro are right about the Caps too. The upper end i7's and some of the old Abit motherboards use the top shelf Japanese Capacitors that are known for zero leakage.
I have a sequenced power up/down regulator as I know all too well about fried hardware. Actually static electricity from my carpet caused a USB stick to knock out my network drivers on my NIC Card and I fried my antique 875 board. I couldn't believe it when the repair guy told me what happened. I have worn Moccasions ever since.
Re: Scope SDK killed Scope 5
But soundcard drivers are handled by the operating system, aren´t they? The new drivers should have been active even without rebooting my system.
Anyway, I´m glad that it is working again. I think I will install a second instance of windows for the SDK
Anyway, I´m glad that it is working again. I think I will install a second instance of windows for the SDK

- FrancisHarmany
- Posts: 1078
- Joined: Sun Jun 02, 2002 4:00 pm
- Location: Haarmania
Re: Scope SDK killed Scope 5
there is no should in the world of Windows 
