Triggers a target Sequence, either by passing the triggering note or by a note sequence.
Property | Description |
Target Sequence | Select the Sequence to trigger. |
Triggering Mode | Selects whether to pass the triggering note on to the target Sequence or use the Event note sequence. |
Note Sequence | Specifies the notes to send, if Event is in note sequence mode. 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 sequence output by the specified number of semitones. |
You can target the parent Sequence but you should be careful. Trigger Sequence Events always wait for note-offs (to pass along to the target) so they will pile up in the work queue if note-offs aren't received, causing a gradual increase in CPU use as the queue grows longer and longer. You can see this in the Messages Dialog which displays the work count.
A re-triggering Event must have an on-delay value. Very short delays may lead to heavy CPU load and if a zero-delay re-trigger is found, a warning will be issued and the Event will be blocked.
Although you can send chords to the target Sequence, the Sequence will see each note of the chord as a separate event. So a PeerCtrl Event targeting a note parameter using 'Pass will see the chord as multiple triggerings and you won't hear the chord, even though the Event may be set to use all of the target machine's tracks on each triggering. If you want to hear the chord, you'll need to use "A" instead of "a" in the track list so that the Event will iterate over the tracks with each note. If you use "a", each note of the chord will be sent to the same target track. I know that sucks a bit and I'll try to improve it but it could prove to be too tricky.