hrm hmm. well there are the scripting docs, which come in two flavors (workshop-like, and reference-with-examples.) but these are focused on writing scripts / consuming the system API, not developing the system.
tbh i do not know the docs super well! and am not sure if we have something like a developer setup guide; if not we should make one? (how to ssh, run/restart stack, lua syntax cheatsheet?)
also the “norns study group” discord server is a good place to ask realtime questions if you are into that platform.
well in any case, the changes would be: (this stuff is found under
~/norns/lua/.. on your device):
add a “broadcast” or whatever option to this variable called
clock_table, after it is filled with midi ports.
[ norns/clock.lua at main · monome/norns · GitHub]
(and hey while you’re at it give it a better name like
in the midi out update function, test for that option and perform
:clock() on every connected device:
[ norns/clock.lua at main · monome/norns · GitHub ]
(while you’re at it you could refactor that guy for performance as the FIXME suggests! if you’re feeling ambitious.)
(note that this will only send to devices that you have selected in the midi ports menu, which i’d call a “feature”)
… and i kinda think that’s it? state persistence should continue to work. i don’t even think it would affect existing presets.
oh, these changes will take effect on restarting the
matron process or rebooting norns.
of course i can also just make these changes the next time i get a few minutes with the norns, it would be blind since i don’t happen to have appropriate hardware to test. so if it sounds fun then go for it by all means.
or of course someone else may come across this post in the meantime.