# AU automations permanently disabled in Ableton Live

**URL:** <https://forum.juce.com/t/au-automations-permanently-disabled-in-ableton-live/61977>\
**Category:** General JUCE discussion\
**Created:** [June 25, 2024, 9:00am UTC](https://forum.juce.com/t/au-automations-permanently-disabled-in-ableton-live/61977 "2024-06-25T09:00:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgleo](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@cgleo](https://forum.juce.com/u/cgleo)\
**Post date:** [June 25, 2024, 9:00am UTC](https://forum.juce.com/t/au-automations-permanently-disabled-in-ableton-live/61977/1 "2024-06-25T09:00:34Z")

</div>

While porting an old plugin from JUCE 4.0.1 to JUCE 7.0.5, we encountered an issue, where Ableton Live (11 and 12 tested) disables automations when loading a project, that references the old plugin version with some automation, after installing the new version. It is not the usual disabled automation, with the re-enable button lighting up, but it is permanently disabled, with no way to re-enable it. Its fine with VST, only AU seems to trigger the problem. No changes to the plugin, other than adapting to the new JUCE version.

We started looking into the difference between the JUCE 4 and 7 AU wrapper, but its quite a lot. Does anyone have an idea, why this might be happening, and how to fix it?

---

<div class="post-metadata">

**Author:** ![anthony-nicholls](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/anthony-nicholls/32/1246_2.png) [@anthony-nicholls](https://forum.juce.com/u/anthony-nicholls)\
**Post date:** [June 25, 2024, 9:10am UTC](https://forum.juce.com/t/au-automations-permanently-disabled-in-ableton-live/61977/2 "2024-06-25T09:10:21Z")

</div>

My guess is that the IDs for the parameters have changed, try enabling `JUCE_FORCE_USE_LEGACY_PARAM_IDS` in the `juce_audio_plugin_client` module

From the description

> Enable this if you want to force JUCE to use a continuous parameter index to identify a parameter in a DAW (this was the default in old versions of JUCE). This index is usually used by the DAW to save automation data and enabling this may mess up user’s DAW projects.

 ![Screenshot 2024-06-25 at 10.06.26](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/2/5/25451bb6ef20492594dfdab44a6be13836c9a6ea.jpeg)

---

<div class="post-metadata">

**Author:** ![cgleo](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@cgleo](https://forum.juce.com/u/cgleo)\
**Post date:** [June 27, 2024, 10:30am UTC](https://forum.juce.com/t/au-automations-permanently-disabled-in-ableton-live/61977/4 "2024-06-27T10:30:23Z")

</div>

> [@anthony-nicholls](#):
>
> My guess is that the IDs for the parameters have changed, try enabling `JUCE_FORCE_USE_LEGACY_PARAM_IDS` in the `juce_audio_plugin_client` module

That solved it, thanks a lot!

It was working fine in Logic Pro X, so somehow Logic must be able to deal with the changed IDs.

---

<div class="post-metadata">

**Author:** ![HowardAntares](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/howardantares/32/4629_2.png) [@HowardAntares](https://forum.juce.com/u/HowardAntares)\
**Post date:** [June 27, 2024, 2:44pm UTC](https://forum.juce.com/t/au-automations-permanently-disabled-in-ableton-live/61977/5 "2024-06-27T14:44:00Z")

</div>

I seem to recall that Logic uses the index of the parameter, not its ID…?