MIDI Map treated differently than Key Map
Posted: Sat Jan 05, 2008 4:51 am
Hello,
What I am about to describe occurs with Live 6 and 7, on Macs and PCs, using any MIDI interface (I've tried 5).
Short version: When Session clips and Arrangement markers are mapped to the same MIDI note, the clip triggering does not behave properly.
... but if they are mapped to the same ASCII key, no problem.
Picture this project:
Session View: One track, 3 clips.
Clip 1 has follow action to Clip 2, Clip 2 follows to Clip 3, Clip 3 has no follow action.
Key map: Clip 1 = "1", Clip 2 = "2", Clip 3 = "3"
MIDI Map: Clip 1 = C3, Clip 2 = D3, Clip 3 = E3 (any MIDI channel)
Arrangement View: 3 Arrangement markers
Key map: Marker 1 = "1", Marker 2 = "2", Marker 3 = "3"
MIDI Map: Marker 1 = C3, Marker 2 = D3, Marker 3 = E3 (same MIDI channel as the Clip MIDI Maps)
(If it's easier to see this in real life, especially you Ableton folk, I can give a link to this project)
Trigger the clips and markers simultaneously with Key mapping. No problem: Hitting "1", "2" or "3" jumps to that marker and plays that clip.
Now, do the same with your MIDI controller. With the transport stopped, C3 can trigger Clip 1 and Marker 1.
Now, with the transport stopped, try hitting D3. Arrangement jumps to Marker 2, but in Session View, Clip 2 is triggered *momentarily* then jumps to Clip 3 - right follow action, wrong time (i.e. too soon).
Apparently if Session View clips (or scenes) have the same MIDI mapping as Arrangement View markers, Live does not play the mapped clip / scene properly.
- This does not occur with Key mapping.
- This does not occur if the transport is running - only when stopped.
I would like I would call the present MIDI Map behavior a "bug", and would like it to function the same as ASCII Key mapping.
Tried to make this short, but concise. If I can illustrate it better, let me know.
Thank you!
What I am about to describe occurs with Live 6 and 7, on Macs and PCs, using any MIDI interface (I've tried 5).
Short version: When Session clips and Arrangement markers are mapped to the same MIDI note, the clip triggering does not behave properly.
... but if they are mapped to the same ASCII key, no problem.
Picture this project:
Session View: One track, 3 clips.
Clip 1 has follow action to Clip 2, Clip 2 follows to Clip 3, Clip 3 has no follow action.
Key map: Clip 1 = "1", Clip 2 = "2", Clip 3 = "3"
MIDI Map: Clip 1 = C3, Clip 2 = D3, Clip 3 = E3 (any MIDI channel)
Arrangement View: 3 Arrangement markers
Key map: Marker 1 = "1", Marker 2 = "2", Marker 3 = "3"
MIDI Map: Marker 1 = C3, Marker 2 = D3, Marker 3 = E3 (same MIDI channel as the Clip MIDI Maps)
(If it's easier to see this in real life, especially you Ableton folk, I can give a link to this project)
Trigger the clips and markers simultaneously with Key mapping. No problem: Hitting "1", "2" or "3" jumps to that marker and plays that clip.
Now, do the same with your MIDI controller. With the transport stopped, C3 can trigger Clip 1 and Marker 1.
Now, with the transport stopped, try hitting D3. Arrangement jumps to Marker 2, but in Session View, Clip 2 is triggered *momentarily* then jumps to Clip 3 - right follow action, wrong time (i.e. too soon).
Apparently if Session View clips (or scenes) have the same MIDI mapping as Arrangement View markers, Live does not play the mapped clip / scene properly.
- This does not occur with Key mapping.
- This does not occur if the transport is running - only when stopped.
I would like I would call the present MIDI Map behavior a "bug", and would like it to function the same as ASCII Key mapping.
Tried to make this short, but concise. If I can illustrate it better, let me know.
Thank you!