PlanetZ forums - scopeusers.com

Had someone sucessfully run supercollider under Windows 10 64Bit? I even tried 32-bit version and compatibility mode. No dice

hi, this is a known bug of the PortAudio API used by supercollider and it doesn't work on windows 10 64 bits with asio drivers such as the scope one.

To workaround this problem i use the reaper rearoute driver in the middle.

First install reaper with the rearoute option enabled and remember that you need to install both reaper 64 bits version and 32 bit version to have rearoute available for 32 bit programs on 64 bits windows os.

Then follow these steps:

1. start reaper where you have asio scope as the audio driver
2. on windows 10 go to the following location: C:\Users\yourusername\AppData\Local\SuperCollider
3. create a file called startup.scd
4. edit that file with notepad or whatever you prefer
5. add the following lines
Server.local.options.device = "ReaRoute ASIO (x64)" ;

Server.local.options.sampleRate = 48000;

samplerate must match the one used by scope

save it

6. run supercollider and boot server

warning messages about scope asio and wasapi are nromal, but at the end it will boot with rearoute asio driver

7. inside reaper create a new track and set as input rearoute 1/2 and enable record

other startup parameters can be added, but this is the starting point.

tested on win 10 64 bits and supercollider 3.8 54 bits

hope that helps

voicemeeter is capable of this also.

garyb wrote:voicemeeter is capable of this also.

I installed voicemeeter and it works perfectly outside SC. But SC still crashes with the same error within sonicxite.sys.
My startup settings:

Server.local.options.device = "Voicemeeter Virtual ASIO" ;
Server.local.options.sampleRate = 44100;

The crash happens, even when Scope is not running. Only a switched off XITE get s the server booting. I think, SC server is dying at enumerating the devices, so whatever settings I use, they come too late.

I'm goind to recompile everything and see, where the culprit really is.

After 1 day of debugging, I found a solution to avoid the BSOD: put the ASIO driver's name on Port Audio's blacklist until S|C comes up with a Windows 10 driver.
Or rename the Xite driver to one in the Blacklist.

DragonSF wrote:After 1 day of debugging, I found a solution to avoid the BSOD: put the ASIO driver's name on Port Audio's blacklist until S|C comes up with a Windows 10 driver.
Or rename the Xite driver to one in the Blacklist.

this is also a portaudio bug, not just scope asio have problems with portaudio on 64 bits, also my stanton dj asio driver have problems with mixxxx on 64 bits and windows 10, while everything works on 32 bits.

All you have to do is to engage the asio driver before starting the buggy portaudio application and then use another driver.