arockmez

For some topics I've seen before, this bug is pretty common and has been around for ages:

When you use more than one instance of a M4L device and you automate some parameter in them, it gets deactivated randomly in one of the instances after a while. Watch this video I recorded to see the issue in action:

https://www.youtube.com/watch?v=sH6qtVqWLmA&feature=youtu.be

As you might think, this is really annoying when you are using M4L devices for live performing or even for producing.

Do some of you know some workaround that can be done in order to avoid this?

I already tried the M4L device that re-enable automations when they get deactivated. Even when it's useful it's not suitable for all kind of situations, specially when automations need to work in a sample by sample basis with more CPU-intensive processings.

When you use more than one instance of a M4L device and you automate some parameter in them, it gets deactivated randomly in one of the instances after a while. Watch this video I recorded to see the issue in action:
https://www.youtube.com/watch?v=sH6qtVqWLmA&feature=youtu.be

Do some of you know some workaround that can be done in order to avoid this?
I already tried the M4L device that re-enable automations when they get deactivated. Even when it's useful it's not suitable for all kind of situations, specially when automations need to work in a sample by sample basis with more CPU-intensive processings.


max-for-live-automation-bug

If the problem only happens with multiple instances of M4LDevices,

that means that there is a bug in either software, or the rule that

every instance of one plugin loaded in any daw should get own indentifier in order to

get unique address for storing and automating parameters is not respected.

Only solution I can think off is to make as many copies of M4L device as needed,

having different names ( like xxx1.amxd, xxx2.amxd, xxx3.amxd etc) and also check

that any value, send, receive etc named objects have unique address.

At least untill cycling and ableton solve the issue.

If the problem only happens with multiple instances of M4LDevices,
that means that there is a bug in either software, or the rule that
every instance of one plugin loaded in any daw  should get own indentifier in order to
get unique address for storing and automating parameters is not respected.
Only solution I can think off is to make as many  copies of M4L device as needed,
having different names ( like xxx1.amxd, xxx2.amxd, xxx3.amxd etc) and also check
that any value, send, receive etc named objects have unique address.
At least untill cycling and ableton solve the issue.


I tried duplicating the patch but it doesn't seem to solve the issue. Also I changed the name of the numbox in order to have 2 different parameter name to automate between the two patches but that isn't also solving the issue so it's really weird.

Maybe there's another thing that can identify the patch that I'm missing that can solve the issue along with duplicating the patch

Thank you very much for the answer.
I tried duplicating the patch but it doesn't seem to solve the issue. Also I changed the name of the numbox in order to have 2 different parameter name to automate between the two patches but that isn't also solving the issue so it's really weird.
Maybe there's another thing that can identify the patch that I'm missing that can solve the issue along with duplicating the patch


The problem may be caused by overloading the undo history. You could try increasing 'Update Limit' in the numbox inspector but it will of course affect the accuracy of automation.

Thank you Broc. Actually this also happens with built-in M4L devices, which is really annoying. I'll try what you say and post my results here!

Unfortunately update limit doesn't help :( it seems like it takes more time before it happens but it happens anyways. I tried with 10ms (10 times more than default). I also checked M4L built-in plugins and they have update limit set to 1ms

Unfortunately update limit doesn't help :(  it seems like it takes more time before it happens but it happens anyways. I tried with 10ms (10 times more than default). I also checked M4L built-in plugins and they have update limit set to 1ms


Anything else you know could do the trick, guys? Thanks!

Max for Live automation bug