The Peer Note Event is used to send a sequence of notes to a machine. The note input/output tracking and management code really fried my brain so I hope you appreciate how good it is.
Property | Description |
Target Machine | Selects the machine to manipulate. Most other controls are disabled if no machine has been selected. |
Track(s) | Specifies which tracks values will be sent to. See Common Peer Properties. |
Note Param | Selects the parameter which will receive note data. Magic will try to assign this automatically when a machine is selected but it may not always find the parameter you want. |
Velocity Param | Selects the parameter to receive the note velocity data. The velocity of the triggering note will be scaled and clamped according to the Event velocity settings before being transmitted to the target parameter. Magic will attempt to automatically assign this parameter when a machine is selected but might not always find the right parameter. |
Cut Mode | See Note Cut Modes. |
Note Sequence | Specifies the notes to send. The sequence is defined as a comma separated list of tokens which can define single notes, chords, arpeggios and rests. For full details see the Note Sequence reference |
Repeat | If checked, the note sequence will begin again when the last note has been sent. If not, the Event will stop sending notes when the sequence finish. |
Transpose | Transposes the note output by the specified number of semitones. |
Extra Param 1-2 | Selects a parameter on the target machine to manipulate. If you change the target machine, Magic will attempt to preserve parameter assignments. See Parmeter Remapping.. |
On Value 1-2 | Specifies the value to be sent to the corresponding parameter when the Event is triggered by a note-on. See the Peer/MIDI Value reference for details. |
Off Value 1-2 | Specifies the value to be sent when the trigger note-off is received. Disabled if the Note-Off is set to "Ignore". See the Peer/MIDI Value reference for details. |
When handling note parameters, Magic keeps track of which Event is currently using each track on a target machine, so several Events can send notes to the same machine. If the target machine has sufficient tracks to play all the notes then the Events will not clash. If there aren't enough tracks, an Event will re-use the oldest target track it currently owns, cutting its own notes rather than those generated by another Event. If the Event doesn't own any of the target tracks, it will steal the oldest track from a different Event. Peer Ctrl Events use the same rules when targeting note parameters.
Note that for Peer Note events, the track list merely specifies a pool of available tracks. If the Event outputs only a single note then only a single track from the pool will be used. If an extra parameter targets a track parameter, values will be sent to the same tracks as the note output.
Internally Magic treats a machine's global parameters as something like a unique track, so new notes will always steal the global voice.