schlam

When an automation lane is recorded, it is not recorded until it is moved even if the value has changed between when the both clips has been recorded.

-It seems that it is not possible to add breakpoint automation in the LOM...

-The only thing working was, each time the rec is 1 to :

- getting the values of all the parameters

- changing all the values with a random number

Then it's working when there are just few parameters but It's buggy with several hundreds of parameter... even retrigerring all the currents value when "Rec" is on doesn't work, 

...and it's not a very beautiful solution.

I really don't understand why this is not the default behaviour...

It's only working perfectly when you record the 1st clip of a new live.Set, not for the next one...strange..

lili.jpg

Something in Live makes me sick.
the picture below explains my problem

When an automation lane is recorded, it is not recorded until it is moved even if the value has changed between when the both clips has been recorded.
 Is there a way with M4L to avoid that ?

-It seems that it is not possible to add breakpoint automation in the LOM...
-The only thing working was, each time the rec is 1 to :

                                 - getting the values of all the parameters
                                 - changing all the values with a random number
                                 - retrigger all the values.

Then it's working when there are just few parameters but It's buggy with several hundreds of parameter... even retrigerring all the currents value when "Rec" is on doesn't work, 
...and it's not a very beautiful solution.

Any idea ?

 I really don't understand why this is not the default behaviour...
It's only working  perfectly when you record the 1st clip of a new live.Set, not for the next one...strange..


Hello
Something in Live makes me sick.
the picture below explains my problem

When an automation lane is recorded, it is not recorded until 

it is possible with M4L to correct this Live behaviour ?