Forums > MaxMSP

Re-enable automation turning on randomly


August 24, 2013 | 4:11 pm

Hi,

This keeps happening in my patch for no apparent reason, it turns on the live automation re-enable button, when I automate a dial. There is nothing else controlling this dial. Its just a normal dial, controlling an lfo, but live just decides at random to deactivate it. I can see on the timeline where it happens and sometimes it does not happen, sometimes it does. Also I duplicated the device/track that its happening on, so could it be that the duplicate is somehow interfering with the original? Does anyone know why this might happen? It seems completely random in this case and possibly a rather large bug in the handling of automation.

August 25, 2013 | 6:01 am

After testing this extensively, it seems that max for live automation has a bug, where when two of the same devices are used in a liveset, the automated parameters become deactivated. This happens quite randomly throughout the timeline.

Is anyone looking into this? Its quite a fundamental problem for anyone creating a max for live device really.

Is it possible for someone else to test it? Put one device on a track, automate a dial for 4 bars, duplicate the whole track, press play on loop (within 5 or 6 cycles the parameter will become deactivated)

August 26, 2013 | 10:56 am

Any 1 ?

This even seems to be happening with the simple pitch drop max plugin released with max for live essentials, so it seems to me a problem with max itself rather than with any specific patch.

Granted I’m using live 9.1 but would be grateful if others could test it to prove this bug.

August 30, 2013 | 5:13 am

I have since found out from ableton that this is a bug that is not being prioritised/worked on.

Kind of brings into question the whole use of Max for live. Of course you want to automate devices. That’s the whole point of integrating live and max surely?

August 30, 2013 | 5:50 am

Ive found a solution. There is a setting for the live objects called "defer automation output"

This seems to fix the problem completely.

Thanks for all the help in figuring this out.

Now Im off to rename around 180 live objects with this setting. Manually….

August 30, 2013 | 6:23 am

hem, couldn’t you rename with a script to [thispatcher] or [universal] object or something ? :>

August 30, 2013 | 7:24 am

Unfortunately, it is a "hidden" attribute and cannot be changed dynamically.

I managed to change it in a text file, but I couldnt do this directly in maxforlive for some reason. I had to save it as a maxpat, open with textedit, change and then copy/paste from the maxpat into an amxd. Rigmorol, but got there in the end.

There are still errors with the automation issue above, but theyre slightly more bareable with defer automation output enabled.

March 25, 2014 | 12:26 pm

I was having this issue too, attempting to automate some faders of the Max4Live device – DMaX Dimmer Pack in Ableton Live 9.1. I opened the device in MAX and turned ON "defer automation output" for all the faders. Saved the patch. But, still get the Re-Enable automation kicking in when my custom automation comes to the play head, thus not playing my automation. Is there something I’m missing here?

March 25, 2014 | 2:25 pm

The only thing I can think of is that if youre already moving/automating those parameters with something and then you try and draw in some automation for them, you will get the re-enable automation coming on. Essentially, you cant move a dial, or fader twice, otherwise live cant tell what your trying to move, so it disables it. Might not be the answer youre looking for…

April 9, 2015 | 3:48 pm

i’m having some luck with setting the "update limit" to 50ms too.

April 10, 2015 | 1:55 pm

I wonder if the LOM (Live Object Model) permits, "repressing" the Re-enable Automation button automatically?

April 10, 2015 | 4:26 pm

Yes You Can!

Download the attached M4L Device.

Attachments:
  1. Screen-Shot-2015-04-10-at-4.25.47-PM

    Screen-Shot-2015-04-10-at-4.25.47-PM.png

  1. fgc.AutoReEnableAutomation.amxd.zip

mvf
April 13, 2015 | 1:49 am

I experienced the same bug and would be glad, if it was fixed.

Kind of brings into question the whole use of Max for live. Of course you want to automate devices. That’s the whole point of integrating live and max surely?

Yes!

Thank you NEWTFISH for your findings.
@furiousgreencloud: Pressing the button automatically is a kind of dirty option, but thanks for the device. I’ll give it a try!

April 13, 2015 | 2:35 am

Maybe we should do a ‘class action’ towards Ableton by sending multiple bug reports about this so that it becomes a priority ?


mvf
April 13, 2015 | 3:34 am

Edit 2: Hi Stephane. That’s a good idea. I just started to prepare a bug report, but I first couldn’t provoke the error in the manner, NEWTFISH did some time ago:

Put one device on a track, automate a dial for 4 bars, duplicate the whole track, press play on loop (within 5 or 6 cycles the parameter will become deactivated)

But suddenly it came up again. So my discovery is, that the bug occurs only with the 64 Bit Version of Live 9.
Please try the attached set.
I use OSX 10.8.5, Live 9.2b5 64 Bit (Beta) and Live 9.1.7 32 Bit. Max 6.1.9

June 1, 2015 | 12:52 pm

Working with Live 9.2b10 (32Bit) I’m experiencing the same problems. The problem persists even if I remove the MaxForLive objects. I filed a bug report as Beta tester and will post any responses here.

June 2, 2015 | 1:03 am

Ableton gave me the suggestion to disable control surfaces. This didn’t help, but disabling "remote" on my "Output IAC Driver (Using Mac)" did make the problem go away for me. My guess is using remote on the Output generates a data feedback loop, hence the automation override. Maybe this helps some of you guys.

July 30, 2015 | 3:37 pm

I have been having the same problem. I use Ableton 9.2 64bit.
It happens with both vst plugins and Ableton FX. It’s only recently started doing it so I don’t yet know if it does it with any of the M4L devices. However due to this problem I am unable to work in the arrangement view.
The same thing was happening in session view the other day, although it’s not happening at the moment.
Has anyone found a solution yet? It seems to be a very common problem. Anyone heard anything from tech support?

Sharon

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

Forums > MaxMSP