This kind of thing is usually very simple to add to any existing script. If you scroll all the way to the bottom of rebound in the maiden editor, you can see that there is a play_notes function which sends notes out in various ways:
engine.hz(MusicUtil.note_num_to_freq(n))
m:send({type='note_on', note=n})
if params:get("ii") == 2 then
crow.ii.jf.play_note((n - 60) / 12, 5)
end
You could add crow CV / trigger output here:
crow.output[1].volts = (n - 60) / 12
crow.output[2](pulse(0.02, 5))
If you want gate output instead of a 20ms trigger, you could modify this to just set crow.output[2].volts = 5 here (at the spot where the midi note_on is sent) and also modify the spot a few lines up where midi note_off is sent to set crow.output[2].volts = 0. This general pattern should be possible to adapt to pretty much any other script you come across that is sending midi note on/off messages.
To me this is a massive strength of Norns: the ability to tweak a script to do what you want like this, even making temporary changes to suit a particular patch or get the behavior you want, rather than thinking of any given change to a script as a permanent feature. Maybe tomorrow you want to use an AD envelope instead of a square pulse, or send x and y position of the selected ball out of crow as voltage outputs, or pretty much anything you can imagine the script doing ā lots of interesting possibilities are achievable with only very small modifications to scripts.
It would seem so, yes: https://github.com/nf/rebound/pull/3
