SuperCollider 3.10 with macOS Mojave


Before upgrading from High Sierra to macOS Mojave,
has anyone discovered specific issues with SC 3.10 on the latest macOS ?

Many thanks,


oh yes.
completely blank help browser. looks like some issue with QT in Mojave.
after reading the internets it was easily fixed by creating an Automator script that runs a shell script:

cd /Applications/SuperCollider/
./SuperCollider --disable-gpu

then i saved the Automator file as a standalone app to launch. help and tutorials galore!

ah. and people say in only happens on Xeon processors. i have the issue on a 2013 mac pro but not on my 2018 MBP.


Has someones tested on MacBook Pro (Late 2016) ?
Otherwise, I will wait.


I would consider holding off. I’ve had some very disruptive problems using SC on Mojave. The more restrictive microphone permissions have bit me a few times, and I see some very weird deep in the OS hangs when launching, I think due to application signing issues.

These may be caused and/or exaggerated by the fact that I’ve got like 15 different dev copies floating around on my machine :slight_smile: - and I think I’ve basically solved the above problems after fiddling with security preferences for a while, and manually signing my local builds. I’d love to hear other reports of people using SC on Mojave, to see if these are going to be common problems, or if it’s something particular to my environment.

all smooth on my mbp 15’ 2018 2.6 / 16 / mojave
including running TX_Modular from inside SC 3.10 which i believe is one rather demanding toolkit

‘trash can’ mac pro 2013 however has a pretty serious issue that i described a couple of posts back

Has anyone recently tested SC 3.10 with MacOS Mojave (MacBook Pro - Late 2016) ?
I would like to jump to new OS 10.14, if everything is now ok.


i’m running the latest release 3.10.1 on both MBP(2018) and ‘trashcan’ Mac pro (2013), all smooth and the bug with help files the 3.10 had on the mac pro was squashed!

I unfortunately experience quite a different situation here… see

I can’t get the .plot to work.

1 Like

Please try the signed 3.10.3 release:

Yes, I just did. Still no luck:

ERROR: Message ‘use’ not understood.
Instance of Function { (0x115e14978, gc=54, fmt=00, flg=00, set=02)
instance variables [2]
def : instance of FunctionDef in Method Plot:init
context : Frame (0x117c57578) of Plot:init
arg this =
arg this = nil
arg error =
arg this =
arg error =
arg this =
arg this = nil
arg selector = ‘use’
arg args = [*1]
arg this =
var fontName = nil
var gui = nil
var skin = nil
arg this =
var template = nil
arg this =
arg this =
arg arrays = [*6]
arg findSpecs = true
arg refresh = true
arg separately = true
arg minval = nil
arg maxval = nil
arg defaultRange = nil
arg this = [*6]
arg name = “Some data”
arg bounds = nil
arg discrete = false
arg numChannels = nil
arg minval = nil
arg maxval = nil
arg separately = true
var array = [*6]
var plotter =
arg this =
var res = nil
var func =
var code = “[5, 6, 7, 6.5, 4.5, 3.5].plo…”
var doc = nil
var ideClass =
arg this =
^^ The preceding error dump is for ERROR: Message ‘use’ not understood.

PS: Using either {}.plot or [5, 6, 7, 6.5, 4.5, 3.5].plot(“Some data”)

PPS: Ah, never mind. Something in my startup file breaks it.

OK! I did get those to plot, so if something still seems amiss after you update your startup file, let me know and I’ll check to see if I can reproduce. (BTW - Hi David!)

Works now. Thanks for the quick response.


Plot works ok with the new release, but I’ve just found a graphical/editing issue with Plotter in edit mode when your .specs or .domainSpecs is different.

a = (0…20).plot;

a.domainSpecs = \freq.asSpec; a.refresh;

a.editMode = true; // now edit the data by clicking into the plot.

I can not find an issue for this in Github and do not know if this is a known bug ?




    August 31

alt profcottle:
{}.plot or [5, 6, 7, 6.5, 4.5, 3.5].plot(“Some data”)

OK! I did get those to plot, so if something still seems amiss after you update your startup file, let me know and I’ll check to see if I can reproduce. (BTW - Hi David!)