Boot fail - win 10 x64

[gl33mer]

At some point a few weeks back Supercollider stopped working properly on my machine. I haven't managed to solve the issue. This is the issue (closed due to a patch I haven't tried applying) and has to do with Boost.

Since, Sonicpi has also failed to boot.

I install the latest sonic pi (2.11 - msi and protable) they just fail on startup.

I've trying clear the event log as suggested in that issue thread mentioned above.

Easy solve?

[gl33mer]

@llloret Thank you.

@samaaron This is a bit deeper than my normal depth but it seems that issue relates (If I understood correctly) to the event log size maxing out. Mine also seems to have a limit of 20mb but is currently only ~3mb (I think). I also seem to have quite a few events with id 6005. But then again I've never used boost, etc.

[gl33mer]

I would assume not many people encounter this one.

:-(

May end up ordering a raspbPI

[samaaron]

Cc @bagong

[bagong]

@samaaron, I am following. The tragic thing is that we haven't had a case yet that allowed to reproduce the problem. It's either there on a certain system, or not... Once someobdy turns up who says: I had it, but after I did this and that it disappeared (or the other way round), we are back in the game. But worse: SC has moved on to boost 1.63 now, where the code in question is different, so even less chance that we find out what triggers this problem in certain environments. To Sonic Pi users who bump into this: the same thing has been observed with vanilla SuperCollider, but it is exceedingly rare. If somebody feels up to trying a current pre-release SuperCollider build on their machine, we could try to see a) if the problem disappears with the boost update, or b) if a different version reveals a bit more about the reasons behind the problem. And more generally: the first thing is always to delete the system log and reboot the machine. If somebody is willing to invest some time, I am happy to take her hand in trying to go through the steps. But no promise, unfortunately, that we can easily solve the problem.

[samaaron]

@bagong - thanks for this - is the sc with boost 1.63 released at this point it still in dev?

[bagong]

Still in dev, and not clear yet when we will release. Some push for a quick release, others are sceptical...

[samaaron]

@gl33mer - could you try booting a vanilla version of supercollider? If that doesn't work - perhaps @bagong could let you have a pre-release of the new win supercollider to try out?

[llloret]

As @bagong said, the trouble is finding his to reproduce it.

I agree that next step would be to test the 1.63, when possible.

[gl33mer]

@samaaron which version are you referring to as vanilla, 64bit 3.8 (no supernova)?

@bagong ty. I should erase the system log before trying? (you mean the event log? more instructions welcome.)

@bagong I'm willing to invest time in solving this. Will do my best to follow your instructions.

[gl33mer]

hmm...

[gl33mer]

# Starting SuperCollider 2017-05-11 08:10:36
SC FFT global init: cosTable initialised.
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed

Event log was cleared before attempting to boot sonic-pi.

current version still not working.

[gl33mer]

This from Stackoverflow -

"It's a bit weird, but here boost relies on Windows Event Logger. And if there is no event with ID = 6005. It throws an exception.... ...The solution was just to add the event 6005 and all work again fine."

I did have more than one 6005 event before I erased the eventlog completely and a 6005 event has to be created.

This method using PowerShell for adding an event with id 6005 worked for me (eventcreate.exe can only create an event with id 0-1000 and LogEvent.exe that is mentioned elsewhere can't be found)

Sonic-Pi just booted.

I shall update.

[gl33mer]

Rebooted computer. Sonic Pi still boots.

[gl33mer]

After System event log has been erased - add a event with id 6005 like this: In powershell:

$evt=new-object System.Diagnostics.Eventlog(“System”)
$evt.Source=”EventLog”
$evtNumber=6005
$evtDescription=”For SC boot”
$infoevent=[System.Diagnostics.EventLogEntryType]::Information
$evt.WriteEntry($evtDescription,$infoevent,$evtNumber)

now SonicPi should boot.

[gl33mer]

Is this closing?

[gl33mer]

@samaaron Sonic-Pi has been stable with no problems since the above fix. (Sonic Pi 2.11.1) Not sure if this issue should be closed or kept open (for upstream Boost fix, etc.?). Thanks.

[llloret]

I think it should be kept open until either it is fixed in boost, or we find a way to make it work without manual interventions.

[Rainer]

Hello everyone,

I had the same boot problem until 15 minutes ago. After installing SuperCollider separately, one of it's logfiles told me that it had a problem with my Focusrite Scarlett Solo Device. I deactivated the device, restarted Sonic Pi, and voilà: I am a happy listener to the db_haus drum sample now. ;-)

Hope this helps anyone!

Kind regards,

Rainer

[gl33mer]

Hey @Rainer

Sonic Pi is working consistently for you now?

I'm also using a Focusrite interface (2i2) . Disconnecting it got SonicPi running. But only once and then it's back to splash screen and crash.

This still in the SonicPi (scsynth) logs:

# Starting SuperCollider 2017-09-15 09:12:04
SC FFT global init: cosTable initialised.
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed

[gl33mer]

This isn't a workable solution for me because I need the audio device for inputs/outputs etc.

I couldn't get it to work consistently and couldn't actually hear any sound off the on board audio.

[gl33mer]

I'm looking into possible upgrade on the Focusrite drivers.

[gl33mer]

No luck with updated drivers.

[samaaron]

Closing this here as it appears to be a duplicate of #959

Please update to v3.1 and see if that fixes your issues and if not, please do continue the conversation over at #959