OK, maybe this is a bit of a niche feature, but I’m going for it anyway.
Renoise is a crazy cool sound engine, and lately I’ve been trying to use it a backend to Tidal Cycles.
It kind of works, but I faced one major block. In renoise, like in MIDI, there is one event to trigger a note (note_on), and one event to release a note (note_off). From the point of view of a keyboard player, it makes sense: when you press a key to play a note, you don’t necessarily know for how long you will play it.
Things are a bit different in Tidal (and maybe other live coding environments). There, the note’s length is known from the start, so the event triggering the note contains the note’s duration, so the note_off event is moot. It may look like a minor difference, but it has quite a few implications (for example in Tidal each note is independant and “stateless”, which is not the case with note_on/off).
Anyway, here is the idea:
/renoise/trigger/note(instrument, track, note, velocity, duration)
That OSC endpoint would trigger a note like
note_on, and attach a scheduled
note_off event to that specific note.
I’ve tried to do it in lua, but I had some ugly lags. I guess there is a reason for
/renoise/trigger/note_(on|off) to be hardcoded in renoise …