Forums > Max For Live

max4live parameters automation delay problem.

July 1, 2014 | 5:59 am

Hi everyone!
I’ve got a problem I cannot solve by myself.
I create some devices for my externals expanders and machines drums, The goal was to trigger any midi CCs show and record them as parameters automation in the Live Timeline. After some feedback problems with the live.dial "set" message my devices seamed to work perfectly without delay or midi saturation, now my new problem is that all the automation of the MAX devices is shifted between 1 or 16! measures in the timeline after 8/9min in my set and this delay depends on where i start to play the track!!?
Visually the parameters dials moves in time but their message are outputted a long time after???
Please help me, I really don’t understand what happens and i cannot finish my track.
Thank you


July 2, 2014 | 8:24 am

Is your max device using transport timing? (something like [object 4n]) It could be that the object is waiting for a host sync that way?


July 2, 2014 | 11:10 am

Hi thank you to reply,
No transport timing in the devices.
Each device have JavaScript object and a parameter value filter in it to avoid midi buffer saturation.
Some dials are float range and each automation output a correlated float value between points, this causes two many and insignificant equals integers values midi events. I just send on integer change using a shadow value for each parameter. I think I will check this function because when I delete or simplify an envelope in a track the problem disappears. But it’s very weird! Midi CC events can be sent even after a stop :/ ??? …


Viewing 3 posts - 1 through 3 (of 3 total)