PlanetZ forums - scopeusers.com

WHAT UP WIT DAT?!

I think sth is occupying the asio driver already but i have nothing else set to use it, as far as i know. I've reinstalled scope. haven't tried reinstalling foobar yet. This has run on my system for the past couple months and every now and then i get this error and its because scope has failed and i just restart scope and it works, but not this time. please help.

...

yea i'm running windows......

sorry, couldn't resist, it's that 'every now and then' formula that probably triggered me
Hope you get it sorted out tho
maybe it's about priority settings in the system?
it just can't be Scope really

I'm pretty positive it is scope..

Ableton is saying the same thing.

try to replug the STDM cable/plugs...
or reload your ASIO modules in SFP and see what happens then

(Keep in mind you load SFP first...)

If you change the kind of Asio module, does something change? (Try for example to use the Asio2 module).

So the device can 'see' the scope driver just not access the resources (ie, its not the registry 'cleaning' issue)?

Have you looked in task manager to see if anything odd is running? Nothing that I'm aware of would be able to 'hang' onto the ASIO drivers on a soft reboot (bios on up) but when in doubt shut the box off for a few seconds and reboot (or even adjust card seating etc as recommended).

I've already shut it down (a few times) i've changed out the modules several times.

I just tried deleting it and reinstalling scope altogether. In all the confusion i deleted my allkeys file of course. So now i have to wait and see if they can send this file back to me. Its been one day and still no response......

So again, when you go into the soundcard selector for a given app do you still see Scope ASIO as a selection (since if you haven't checked apps might still be assigned to that but the registry entry might actually be gone?)

Also try running the ASIO2 32 Dest -64 modules (or whatever they're called, not at my DAW at the mo) and corresponding Source module, i see you are using the older ASIO1 for some reason (don't think it's that but no harm in trying). Perhaps try the ASIO2 32 Flt-64 one too.

i didn't know that ASIO2 meant upgraded ASIO driver.....

Why can't creamware just take the old ASIO1 out, and then replace it with the new one, to keep it less confusing. Thats the most retarded thing i've ever heard.

Omnicron wrote:i didn't know that ASIO2 meant upgraded ASIO driver.....

Why can't creamware just take the old ASIO1 out, and then replace it with the new one, to keep it less confusing.

Well probably because people with older DAWs would complain that there was only an ASIO2 driver!

ok.....

Anyway, does anyone know when i can expect a reply to my inquiry about my allkeys file? I can't do anything until i get that effin' thing!

If you haven't already, try emailing Ralf directly at the new address,
rb(at)soniccore.com

Don't forget it's Easter here in Europe though

fixed

Why doesn't he just get an e-mail that filters spam out?

so that the spam robots don't glean the address from the webpage and make the email useless because of the inevitable flood of junkmail and spoofed emails. please fix your post. Ralf already has too much spam to deal with, not to mention 100's of legitimate emails to sort through....

i do it so some spambot doesn't invade Ralf's email box, thus speeding up his ability to deal with requests for allkeys files.

[edit]garyb beat me[/edit]

Why doesn't he just get an e-mail that filters spam out?

Well i suppose people with hotmail accounts (like me) would get filtered out - i believe this has happened in the past, and generally you still have to go to a junk folder and delete spam, so it's still time consuming.

damn, you're cranky!
he has a spamfilter.
spamfilters often filter requests for allkeys files.....

Mr Arkadin wrote:

Omnicron wrote:i didn't know that ASIO2 meant upgraded ASIO driver.....

Why can't creamware just take the old ASIO1 out, and then replace it with the new one, to keep it less confusing.

Well probably because people with older DAWs would complain that there was only an ASIO2 driver!

Actually I believe it's because the ASIO1 drivers are there to meet the ASIO1 specification. ASIO2 drivers meet the ASIO2 spec as published by Steinberg.

Incidentally Omnicron, it's a really good idea to make backups of critical files (Cset.ini, Scope.rgy, Allkeys.skf) to prevent future issues. Did you get ASIO working or no?