PlanetZ forums - scopeusers.com

Hallo and good morning,

@ripper:
Go to services ->Restart Audio Service and Windows Audio Endpoint Builder and check if it fixed the issue.
--> Done but unfortunately did not solve the issue.

@Gary:
did you change the ASIO driver while your audio app was open? the ASIO drivers need to be in place BEFORE opening your sequencer.
NO.

also, we cannot see which ASIO dest module you are using. the ASIO source and dest modules much match and both must be present.
Previous to this issue only the Asio source was in place (and during the re-installation/testmode activation), simply due to the rerason that I need (on this PC) only the play out path. Base on your recent post I added the Destination as well but it didn't help.

what do your sequencer's audio settings look like?
It's onyl a DJ Software called tractor pro by Native Instruments...

I had the same error, which was solved after restarting the sequencer once or twice.

When issues "like" this hapen to me I usually close the sequencer and the Scope software.
I then start Scope again and, after it's start up process is complete I start the sequencer again.
If it isn't solved yet I check the sample rate in both.

@Ripper & @DragonSF - thanks for the tips. Tried everything. Doesn't work

mcm060769 wrote:@Ripper & @DragonSF - thanks for the tips. Tried everything. Doesn't work

That's not coold %=$)#(" #"/» (Hehe, hope you find the gremling )

Hello guys,

I have the same problem since Win10 update, but I am not able to fix it with the testsigning tip, even as admin. Do I miss something?

Thank you!

Victor

Nevermind, it worked finally with GaryB tip from the Microsoft website

Thank you GaryB!

Hi Victor, not sure which "GaryB tip from the Microsoft website" you refer to. Assume it is...
Refering to....
Tried that way as well without any change. It does not work. Just to make clear, installation executed without any fault and the scope application worked after re-installation. The only problem is the Asio issue.

Does anybody have an additional idea ?

run the sequencer in win7 or win8 compatibility mode.

right click on the icon and choose "properties". click on the "compatibility" tab and then choose win7 or win8.

I tried Win7 and Win 8 compatibility mode. Indipendent from which I chose the system crashes with a blue screen saying SYSTEM_SERVICE_EXCEPTION - failure reason: scScope.sys

then there's something wrong in the computer's environment.
you are not the only person using that sequencer, but yours is the one that does not work.

blue screens usually indicate a hardware issue. the fact that the Scope driver is in the middle of the crash, doesn't mean that it's the cause of the crash.

Interesting that such a hardware issue become visible after a major windows update. Any sugestion how to go forward to isolate the reason ?

that's Live that doesn't work, correct?

no, i don't know where to start. what is sharing an IRQ with the card?

that's very strange that ASIO worked in the past with only a source module. it shouldn't...

No Gary, it is Tractor Scratch, a DJ audio application. Asio shouldn't work in the past....agree, interesting.
Here is the screen dump that might answer your question....

oh...
i don't know how well Tractor works with Scope. i'm pretty sure someone has used it.

the IRQ sharing looks ok.


have you tried other ASIO apps?

some apps these days try to set up the soundcard when they open. since a Scope card is NOT a windows soundcard(it's not controlled by the windows app. it's external hardware as far as windows is concerned), those apps will freeze or crash, since the card will not respond to the app's queries and will time out. if this is the case with Tractor, then it can probably only be fixed by NI.

a workaround might be either ASIO4all or using something that allows sharing of a non-multiclient ASIO driver with other apps like Reaper using ReaRoute. there was a post about a new app that made ASIO multiclient, so that way Tractor opens the virtual driver in the multiclient app instead of trying to open Scope directly.

Gary, before I go forward in that direction (Asio4All) I just recognized with winamp and foobar2000 that the standard "SoundCard" Driver doesn't work as well. I didn't use those in the past but this might be a benefitial information for us to go the right problem analysis path. However, it looks like the applications are not able to register/locate the driver. The error messages I saw are talking about missing objects, pointer errors etc.
Just to remember, the scope app works fine and all external audio interfaces like analog in/out seem to work.
In parallell I try to find an application that is lightweight (not a full live suite installation) providing a ASIO output....

the "soundcard" driver is a leftover from windows 98. it was to allow playback from a soundblaster card into Scope. ignore this. it's not supposed to work the way you tried to use it.

other windows apps will use the wave driver. of course, you must make the Scope "speakers" the default playback device in windows.

I guess used the wrong terms. I meant the wave driver.

For example if If try to set Sonic Core Loudspeaker as standard I can do this but sound is coming still from the previous selected output (Realtec on board sound).
Using the winamp preferences dialog -> Nullsoft WaveOut configuration the sonic core loudspeaker appears in the device selection dialog.
.....but as soon as I select the scope driver I get the following after pressing play:

Regarding Asio4all I'll come back in the following post...

After installing Asio4All this appeared in the tractor:
After selecting ASIO4ALL v2 I get the following...
No failure from Tractor any longer. As you can see, Realtect and Pulsar appear in the list. Same behaviour...Realtec works and pulsar not.

The scope application still works wonderfull but to exchange sound between windows apps and scope app/card doesn't. Neither via wave nor Asio.

Btw in case put the mouse over the yellow symbol I get the following help text:
Any suggestion ?