Julian Rohrhuber
Julian Rohrhuber
There are two issues: 1. you need to register the SynthDef name in supercollider. This you can do by writing: `~dirt.addSynth(\foooo)` 2. you need to keep with the channel mapping...
ok, I don't know how vivid works: all you need is a synth that has a control name called `out`. If `addSynth` is not understood, then could you please also...
It's in `DirtSoundLibrary` the `1.0-dev` branch: https://github.com/musikinformatik/SuperDirt/blob/1.0-dev/classes/DirtSoundLibrary.sc#L50
Yes, we currently assume that your SynthDef is registered in the SynthDescLibrary, so that we know which arguments it takes. What you can do is just modify your default sound...
Can you describe? Did they post any error message? Have you tried adding a `postln` to see if the function is called?
maybe you could instead try the code I suggested above?
1. yes, I meant `addSynth`, not `addEvent` (sorry!) 2. I forgot that you need to add the synthdef name (`instrument:`) explictly 3. no need to `add` a `SynthDef` as you...
So the corrected code, to be added to the startup file *after* the `SuperDirt` init, would be: ```supercollider ( ~dirt.addModule('sound', { |dirtEvent| if(~diversion.value.isNil) { if(~buffer.notNil) { // argumets could be...
> but unfortunately now when I do d1 $ sound "foo4" or d1 $ sound "foo4*4" # note "0 1 2 3" I just get lots of little clicks instead...
>[ "/s_new", "foo4", -1, 1, 1064, "out", "freq" ], That is wrong. OK, I see (sorry, I don't currently have a tidal that works so I can't test). You could...