I've never tried this before but I've got 3 MIDI Media File sequences loaded and I just want them to play consecutively.
I've tried may different settings but playback always stops after the first sequence has played. Shouldn't "Next Beat" or "Next Bar" just link them up?
What's the secret formula? Or is this a bug?
Thanks!
Chaining midi file playbak (2064)
-
- KVRist
- 197 posts since 7 Dec, 2005
The way I would do this is as follows:
1. Get your midifiles so that each one is enabled in its own sub-session.
2. Create two MIDI Assignments. One to load 'next sub-session' and the other to the transport Play. Assign a midi loopback to each of those using the controllers or notes of your choice.
3. Create two Trigger events. Call the first 'Next Sub' or something that makes sense to you. Make the Event 'Transport Stop'and have the Action be the same as controller/note you assigned to the 'Next Sub-Session' Send to the appropriate Loopback
What this does is call the next sub-session when stop occurs (as it will at the end of each midi file)
Call the other Trigger Event 'Play Sub-Session' or something that makes sense to you. Make the Event 'Sub-Session Load' and have the Action be the same as the event you assigned to Transport Play. Send to the appropriate Loopback
What this does is issue a play command when the sub-session is loaded.
4. Make sure both Trigger Events are enabled for every sub-session except the last one which should only have the 'Play Sub-Session' trigger enabled.
For safety put a 10 ms or so delay on the Triggers.
It works! (as long as I didn't miss any steps that is)
PC
'
1. Get your midifiles so that each one is enabled in its own sub-session.
2. Create two MIDI Assignments. One to load 'next sub-session' and the other to the transport Play. Assign a midi loopback to each of those using the controllers or notes of your choice.
3. Create two Trigger events. Call the first 'Next Sub' or something that makes sense to you. Make the Event 'Transport Stop'and have the Action be the same as controller/note you assigned to the 'Next Sub-Session' Send to the appropriate Loopback
What this does is call the next sub-session when stop occurs (as it will at the end of each midi file)
Call the other Trigger Event 'Play Sub-Session' or something that makes sense to you. Make the Event 'Sub-Session Load' and have the Action be the same as the event you assigned to Transport Play. Send to the appropriate Loopback
What this does is issue a play command when the sub-session is loaded.
4. Make sure both Trigger Events are enabled for every sub-session except the last one which should only have the 'Play Sub-Session' trigger enabled.
For safety put a 10 ms or so delay on the Triggers.
It works! (as long as I didn't miss any steps that is)
PC
'