A node to send an event (or data) first to one destination, then to the next (and the next, and the next…)
Working with MIDI as means of controlling other software is near impossible without this function as you often need to trigger an off-signal before triggering an on-signal from the same event source, and it will surely be beneficial in other scenarios as well.
A node to send an event (or data) first to one destination, then to the next (and the next, and the next…)
Do you mean like this? — where each time you sent an event to the Increment/Toggle port, the output would be routed to the next output port on Select Output?
Working with MIDI as means of controlling other software is near impossible without this function as you often need to trigger an off-signal before triggering an on-signal from the same event source
Do you mean like in the attached composition? As the mouse moves across the virtual piano keys, the composition sends a MIDI note-on upon hovering over each key and a note-off upon leaving it. It was not exactly straightforward to do, so it would help to have something analogous to Track Single Note but for output. (You give it a note number, and when that note number changes, it automatically outputs 2 events: Note Off for the prior note, and Note On for the new note.)
and it will surely be beneficial in other scenarios as well.
Any thoughts on what those other scenarios would be?
hover-piano.vuo (8.19 KB)
It might be my earlier experience with NI Reaktor that really wants an order module. This is what I ended up doing:
It works, but it is a bit more cluttery, and doesn’t really convey the ordering of events in a straightforward manner. The order module from Reaktor has one input and three outputs. It executes the full node path for the first output, before triggering the next one and so on. The most appealing thing about it is that it is very neat, and you know exactly what is going to happen. I have in the same composition that the picture is from a bunch of the Count Within Range nodes, Select Input nodes and a lot of extra conditionals that wouldn’t be needed if there was an order module.
I guess the main difference would be to be able to tell Vuo to first do this, then this, and finally this - instead of do this this and this.
It might be my earlier experience with NI Reaktor that really wants an order module.
Aha, your request makes more sense to me after reading https://www.native-instruments.com/en/support/knowledge-base/show/24/how-to-build-a-sequencer-in-reaktor-to-send-midi-notes-to-an-external-sound-generator/ . Thanks for elaborating.
Opened for voting.
