SuperCollider refuses booting after adding audio interface (Help!)

Questions
1

Hi all,

I’ve added a Focusrite 2i2 4th Gen to my setup (Win 10 x64-based) and SuperCollider now refuses booting.

I tried to test the options availabe to my knowledge but with no luck (so far). My software environment includes

  • Sonarworks Systemwide for sound calibration in the studio (but I already excluded it with, unfortunately, no benefits)
  • KoordASIO (a little ASIO implementation which was fundamental before buying the Focusrite interface, especially for selecting I/O devices and sharing the driver with multiple audio software)
  • The Focusrite driver

As I mentioned I tried excluding the Sonarworks software (nothing changed). Then I tried setting all the Input and Output devices to the same SR (nothing changed). KoordASIO is harmless as it just routes the audio to the correct output device.

Then I tried unplugging the interface, and SuperCollider booted again flawlessly. By plugging the interface again, and rebooting, the server respnds with:
-> localhost Booting server 'localhost' on address 127.0.0.1:57110. Server 'localhost' exited with exit code -1073741819.

Now, given that all the devices are matching in terms of SR, my thought was that SuperCollider was trying to boot to the wrong device. Therefore I tried to print all the devices to grab the correct one and pass it to the server as the target output device. I thus wrote the ServerOptions.devices command and the the console showed a very odd (to me) Interpreter has crashed or stopped forcefully. [Exit code: -1073741819], with the interpreter indeed crashing.

Obviously I can’t see the name of my interface nor change the output device (provided this is the problem) when it is plugged in. As these errors are quite obscure to me, and especially the crash of the interpreter is something I can’t really understand, I’m in a loop and can’t think of any solution.

Any help would be much appreciated. I already tried to consult the resources on the web and the forum, but I didn’t find any similar topic.

Thanks in advance!

2

Does the soundcard work ok with other audio software?

3

Yes. Tried it with Foobar, Ableton Live, REAPER, the browser with YouTube… everything works fine, both when sound is routed directly to the Focusrite driver as well as when it passes through KoordASIO first (with some extra latency, obviously, in this case)

4

Could you post the output of the following code in the Post window?

// ServerOptions.devices.do { |aDevice| aDevice.postln }
ServerOptions.inDevices.do { |aDevice| aDevice.postln }
ServerOptions.outDevices.do { |aDevice| aDevice.postln }
5

Sounds like something in our PortAudio usage is choking on some information received about the device.

Probably need to get a crash dump for the process (either server when booting, or sclang when probing ServerOptions.devices. I’m not using SC regularly in Windows and I’m afraid I’ve forgotten how to get a crash dump. There should be plenty of AI slop online about that, though.

hjh

6

Thanks both for your suggestions

@prko , both commands (out of curiosity I also tried the commented one, with the same result) return Interpreter has crashed or stopped forcefully. [Exit code: -1073741819]

@jamshark70 , I used Procdump to monitor sclang.exe during the execution of ServerOptions.devices. Here is the dump I got (attached from Google Drive): https://drive.google.com/file/d/1PKKjtXuBwqkuqE4kwHx4EGOxSZ4r1WIq/view?usp=sharing

7

Cool – I’m not able to analyze it myself but someone should be able to.

Maybe even better to log a bug report at github, with the core dump – a crash is by definition a bug.

hjh

8

UPDATE

Before starting this thread I downloaded SuperCollider V. 3.14 (the latest available for Windows) with the aim to update my V. 3.13 installation. However I got lost into testing and completely forgot that.

This morning I realised the softare was waiting for the update, so I did that and… everything started working seamlessly. I installed the new version on top of the old one, so nothing, concerning user preferences, should have been changed, according to my knowledge (in fact I found my settings for the theme and font).

All the commands you suggested work, I can list and select available devices, the server boots correctly and the interpreter does not crash anymore. So my setup now is SuperCollider leveraging KoordASIO, which in turn sets my built-in laptop mic as the source and Sonarworks Systemwide as the exit point, which finally outputs audio through the Focusrite interface.

I don’t really know why everything works now (and this is the part that scares me the most, to be honest). Likewise, I’m not sure whether this thread can be considered “solved” although my issue is in fact solved. Anyways, I deeply appreciate your help and efforts in assisting me with that.

1 Like
9

1/ Great! Happy that you got a good result in the end.

2/ It is possible to investigate this, by looking through the change history (git commit log) for changes in the parts of the codebase that read audio device names and properties. I don’t have the facts at hand just now, but it may well be a deliberate bug fix (and if so, it would be visible in the history).

hjh

1 Like