In most cases, you'll want each voice to be exact copies of each other. <- send note and velocity to the outlet corresponding to voice numberĪt each outlet of (except the last) there should be a voice subpatch or abstraction that can be triggered on and off using note-on and note-off messages, respectively. <- create list of voice number, note, and velocity If there is no match, it sends the whole list out the last outlet (which we won't be using here). It's basically a way of assigning "tags" to messages and making sure they go where they are assigned.
So, if you have, and you send it a list where the first element is 2, then it will pass the rest of the list to the second outlet because 2 is the second argument here. For those of you not familiar, will take a list, match the first element of the list to one of its arguments, and send the rest of the list through the outlet that goes with that argument. When gets a note-off, it will automatically match it with its corresponding note-on and pass it out with the same voice number.īy ing the outputs, you can use to send the note number and velocity to the specified voice. When receives a new note-on, it will assign it a voice number and output the voice number, note number, and velocity out its outlets. The first argument is the maximum number of voices (or note-ons) that will keep track of. To start, accepts a MIDI-style message of note number and velocity in its left and right inlets, respectively.
I'll try to be thorough, which hopefully won't actually make it more confusing! It will probably be easier to follow along with this explanation if you open the attached patch. Hopefully this tutorial will clarify its usefulness.
However, the nuts and bolts of how to use it may not be immediately obvious, particularly given its sparse help patch. Luckily, the object can be used to take care of that for you. Keeping track of note-ons and note-offs for a polyphonic synth can be a pain.
0 kommentar(er)
