Soundly is an app with a sound library that you can browse through.
Whenever I launch that I get BSOD. It says that the error is scope.pci.sys. I get System Service Exception.
I assume its scanning inputs/outputs or something and then crashing on scope.
Luckily I don't use scope as my main soundcard. I run it through adat to another soundcard.
I have removed all software ins and outs from my scope project since I don't use them.
What can I do?
Ohhh the joys of scope drivers
Thanks
Last edited by the19thbear on Wed Apr 09, 2025 10:51 pm, edited 1 time in total.
There are a number of apps that query the drivers expecting responses that the drivers aren't coded for. Pretty much anything using portaudio past a certain date for instance, will crash Scope. Most of those queries are not in the Steinberg spec, and so weren't coded into the drivers. I do agree it needs to be addressed (I would love to be able to run V2 of VCVRack directly with Scope ASIO instead of hosting it in Bidule for instance).
There are ASIO wrappers that improve this, as you can then initialize the program to use the wrapper which will handle the calls. Rearoute was one I believe, and there was an open source one. Perhaps someone else can add to this?
I dont' see how a asio wrapper would help? I have no asio drivers in my project and therefore no asio drivers should be visible anywhere. The only things I have are hardware ins and outs (and some fx).
But I could be wrong
If an app attempts to access the ASIO drivers while scope is resident in memory. It still makes the API call even if you don’t have the driver‘s present in your project,
I also thought,- when I don´t have ASIO modules in a project and use SCOPE standalone,- there is no ASIO in the ballpark.
So, if it is,- like you explain above,- wouldn´t it be a better solution leaving SCOPE ASIO installation to be a user´s decision?
In other words,- WHY are we forced to install the SCOPE ASIO driver at all when using SCOPE standalone is the target ?
It used to be a separate installed app (would install and configure midi drivers too). I would gather from the number of questions we had about that back then (even though the installer later offered the option to launch the config app), it probably got integrated into the installer process to simplify support. Can't know that for sure.
We need fixed drivers, it's worth underscoring and getting Holger onto the case if this product is going to be relevant in the market. I think we would all like this, including him. I'm part of the holdup in terms of having the most aggregated info from the community on here and being responsible for it.
no. disable the driver, open the app, select the driver you want and then everything should be ok. if not, that's some bad programming on the app's part.
you do know that room eq is an exercise in futilty, right? the eq will only be correct in the exact spot that the measuring microphone sits. if your head isn't in that exact spot, there might as well be no room eq. room eq is fixed via acoustics, not electronics. i spent many months testing more than 20 years ago...room eq is not new. gone are the days of racks of White eqs....
garyb wrote: Tue Apr 15, 2025 6:19 am
no. disable the driver, open the app, select the driver you want and then everything should be ok. if not, that's some bad programming on the app's part.
you do know that room eq is an exercise in futilty, right? the eq will only be correct in the exact spot that the measuring microphone sits. if your head isn't in that exact spot, there might as well be no room eq. room eq is fixed via acoustics, not electronics. i spent many months testing more than 20 years ago...room eq is not new. gone are the days of racks of White eqs....
Just tried it Gary. Went to device manager and disabled the scope card. Opened the software that usually crashes. It didnt. I selected the soundcard I needed. I then closed it, enabled the scope card and opened the same software and got BSOD.
Many apps poll every driver present, even if it's not saved in their config/ini as the one to use / currently active. It is not necessary to do a full poll of features until it's selected, so populating a list/dropdown of drivers shouldn't cause the out of memory access error (BSOD). Yet many do, as its the default behavior for portaudio and the other major API's available for audio card i/o's.
Rearoute (from Reaper) and the multi-asio wrappers all work to fix this:
I am not sure any of those will prevent certain apps from still polling the Xite driver, but perhaps one is tolerant to enabling & disabling it in devices or etc, if done in the right order.
I actually can’t be bothered with this sadly. I will plug out the card until I get to a headspace where I focus on music only, and not work (where I need the app that crashes when using scope). Hope they fix it soon.
Cheers
I have several machines where--for various reasons--they are frozen into a configuration. Scope works with a certain bidule version and none past, and certain software doesn't even work as well on that version now. My Mac Pro 3,1 runs an ancient version of logic just fine, but it's sans any updates in this era except perhaps FullBucketAudio and etc.
I've got a bevy of silly little cheap things on my iPad and several other machines to distribute things to. Works for me.
Still, I have time in the next month to assemble the info from here and do some simple LLM processing. Dumping sql output into a vector db occurred to me too, but for fixing the ASIO driver and giving bugs to holger that's overkill. More soon.
