This is a bug or ableotn 8.x work on this way?
Posted: Sun May 10, 2009 9:09 pm
PLEASE READ ALL:
ROBERT HENKE INFORM THIS CHANGE ON ABLETON 6 !!!:
Dear Users,
in the new beta version ( Live 606b1 ) we changed the behaviour of the MIDI feedback for clips lauched in session view. Let me first explain the problem and later tell you how you can solve it in this beta.
The Problem:
When a clip is launched via MIDI it sends back messages that can be used e.g. for to drive a status LED on a hardware controler. A note with velocity of 126 indicates that a clip is launched, a note with velocity 127 indicates it starts playing and veloctiy 0 means it stopped. So far so cool. But unfortunately if you launch a second clip in the same track while the first one is playing the order of execusion in Live leads to a very confusing output: first the new clip is launched, and afterwards the old clip is stopped, means the last MIDI info you get is the Note Off from the old clip. This behaviour makes it very hard to derive usefull information for display purposes.
One workaround (which I used for the MonodeckII control) is to delay all Note On messages a bit so they certainly will arrive after the Note Off. This is relatively easy to do in MAX but tricky elsewise.
The Solution
We decided to change this behaviour for the current beta. We now send the Note Off first and then the other feedback data. But this change is very tricky, it might break things on places which we do not expect. Therefore we decided to make it optional for this beta. You need to turn it on explicitely if you want it.
You need to create a textfile called Options.txt and place it in the .../Preferences/Ableton/Live606b1 folder. This file needs to contain this line of text:
-_SwitchOrderOfSuccessiveClipStartStop
If there is allready an Options.txt file simply add this line.
As we said before, we are not 100% sure if this is working under all circumstances correctly. This mean we would appriciate if a lot of you try it out. Even if you are not using the feedback yourself. It should in no case cause other oddities, like changing how follow actions work or looping. If you experience problems try removing the options entry to figure out if this is the cause.
Thanx for the support.
Robert Henke
Ableton
*******************************************************************************************************
Under version 6 the midi feedback order is changed with Options.txt
Under version 7 this change is permanent
Now under version 8 , ableton decide back to old way , Ableton rocllback this change anounced by MR Henke.
After 2 days broken my head jijij i found a workaround for make work midi feedback with my software MIDI controller with this new/older way of send MIDI feedback.
I just want now if this change is permanente now or is a mistake?
I really think this have relation with the APC 40
Really be usefull listen some officially repply, this new change requiere a lot of work under my software and really no want change all and see in 8.0.3 again other change in MIDI FEEDBACK.
Best regards.
ROBERT HENKE INFORM THIS CHANGE ON ABLETON 6 !!!:
Dear Users,
in the new beta version ( Live 606b1 ) we changed the behaviour of the MIDI feedback for clips lauched in session view. Let me first explain the problem and later tell you how you can solve it in this beta.
The Problem:
When a clip is launched via MIDI it sends back messages that can be used e.g. for to drive a status LED on a hardware controler. A note with velocity of 126 indicates that a clip is launched, a note with velocity 127 indicates it starts playing and veloctiy 0 means it stopped. So far so cool. But unfortunately if you launch a second clip in the same track while the first one is playing the order of execusion in Live leads to a very confusing output: first the new clip is launched, and afterwards the old clip is stopped, means the last MIDI info you get is the Note Off from the old clip. This behaviour makes it very hard to derive usefull information for display purposes.
One workaround (which I used for the MonodeckII control) is to delay all Note On messages a bit so they certainly will arrive after the Note Off. This is relatively easy to do in MAX but tricky elsewise.
The Solution
We decided to change this behaviour for the current beta. We now send the Note Off first and then the other feedback data. But this change is very tricky, it might break things on places which we do not expect. Therefore we decided to make it optional for this beta. You need to turn it on explicitely if you want it.
You need to create a textfile called Options.txt and place it in the .../Preferences/Ableton/Live606b1 folder. This file needs to contain this line of text:
-_SwitchOrderOfSuccessiveClipStartStop
If there is allready an Options.txt file simply add this line.
As we said before, we are not 100% sure if this is working under all circumstances correctly. This mean we would appriciate if a lot of you try it out. Even if you are not using the feedback yourself. It should in no case cause other oddities, like changing how follow actions work or looping. If you experience problems try removing the options entry to figure out if this is the cause.
Thanx for the support.
Robert Henke
Ableton
*******************************************************************************************************
Under version 6 the midi feedback order is changed with Options.txt
Under version 7 this change is permanent
Now under version 8 , ableton decide back to old way , Ableton rocllback this change anounced by MR Henke.
After 2 days broken my head jijij i found a workaround for make work midi feedback with my software MIDI controller with this new/older way of send MIDI feedback.
I just want now if this change is permanente now or is a mistake?
I really think this have relation with the APC 40
Really be usefull listen some officially repply, this new change requiere a lot of work under my software and really no want change all and see in 8.0.3 again other change in MIDI FEEDBACK.
Best regards.