Jack Armitage

Multi-line commands work via ``` { ? #include ? using namespace std; ? for (int i = 0; i < 10; ++i) ? { ? cout

For this: ``` defineSD $ sdNamed "foooo" () $ do s

Thanks @vivid-synth I'm going to try the workaround and will post any results here...

My `startup.scd` looks a bit different to yours @vivid-synth, so I just tried running: ```supercollider SynthDef(\foo4, {|out=0| Out.ar(out, DC.ar(0)) }).add; ~dirt.soundLibrary.addSynth(\foo4); ``` After SuperDirt had launched, and got: ```supercollider ERROR:...

@telephon when I run your 2nd snippet above, the `~dirt.addModule('sound')..` works, but then I get the following when running `~dirt.soundLibrary.addEvent(\foo4, (argNames: [\out]));`: ```supercollider ERROR: Message 'addEvent' not understood. RECEIVER: Instance...

@telephone did you mean to write `addSynth` instead of `addEvent`? I tried this below now, no errors but I got `instrument not found: nil` from SuperDirt when playing from Tidal...

If I change my `startup.scd` to look more like @vivid-synth's, I get `instrument not found: nil` ```supercollider ( s.options.numBuffers = 1024 * 32; s.options.memSize = 8192 * 64; s.options.maxNodes =...

Usually when you use a wrong synth/sample name in SuperDirt you get the message ```supercollider no synth or sample named 'blahblahblah' could be found. instrument not found: nil ``` But...

Ok, so @telephon that seems to work, i.e I can add a synth from Vivid without using `send(s)`, but unfortunately now when I do `d1 $ sound "foo4"` or `d1...

Currently I am testing with ```supercollider ~dirt.soundLibrary.addSynth(\foo4, (instrument: \foo4, argNames: [\out, \freq, \note])); ``` And ```haskell :set -XDataKinds import Vivid let s' = sdNamed "foo4" (0::I "out") $ do {...