up to you.
here’s a dumb random sequence in SC
Engine_Boink : CroneEngine {
var <sequence;
*new { arg context, doneCallback;
^super.new(context, doneCallback);
}
alloc {
sequence = Routine { inf.do {
{ SinOsc.ar((10 + 50.rand).midicps) * 0.25 * EnvGen.ar(Env.perc, doneAction:2) }.play;
(0.1 + 0.5.rand).wait;
} }.play;
}
free {
sequence.stop;
}
}
but my 2c is that unless you are specifically interested in doing stuff mostly in SC, or are adapting existing SC code, it is a more natural fit to do sequencing / control stuff on the lua side for norns. that way your sequencing logic module can be more reusable and more easily integrated with controllers and stuff.
yes
yes. (i’d consider this an “advanced technique” though.)
it depends. sc3-plugins are installed already. quarks/extensions that need qt3 or another graphics layer will not work. quarks/extensions that need compiled UGen extensions will not work unless they provide arm64 binaries or you compile them. simple extension classes are fine. (norns engines are extension classes.)
in general i guess i am wary of the Quarks system, but i do love extension classes.
yes you should be able to access The Interweb from SC on norns. (send OSC with NetAddr, use String.systemCmd to curl or whatever, &c.) things like WebView will not work because nope, no graphix again. dunno about Link support; i think that is a compiled UGen so you may have to build it for arm64.
sounds like two questions. yes SC can acccess the filesystem directly with File or whatever. yes SC can talk to scripts, via polls and commands. (polls do not have to be periodic, it is just our word for the mechanism by which engines can generate events to be handled in lua.)
