Supercollider for Norns Best Practices

Thinking it would be useful to have a thread to collect advice, tips and tricks, or best practices for writing Supercollider code for Norns.

Or perhaps as a meta thread to link to specific answers in mega-threads.

3 Likes

As a first example, here’s @mimetaur’s “Norns Engine Development on MacOS” guide for running norns supercollider engines on MacOS for dev/testing

https://gist.github.com/mimetaur/18346a71f1444ec8bea98a0c3c6fa365

1 Like

And then a question:

What’s the better syntax? Is there any practical difference?

SynthDef(\MySynth, {| arg1, arg2 |
or
SynthDef(\MySynth, {arg arg1, arg2;

Throwing another option in the mix (my personal fave):
SynthDef(\MySynth, { SinOsc.ar(\arg1.ar(440), mul: \arg2.kr(0.5)); })
See this thread for why: https://scsynth.org/t/namedcontrol-a-better-way-to-write-synthdef-arguments/186

6 Likes

Much as I like supercollider it has too many syntax options!! I agree though. The named controls seem much better for a synthdef

2 Likes