# ARA plugins and host automatable parameters

**URL:** <https://forum.juce.com/t/ara-plugins-and-host-automatable-parameters/60941>\
**Category:** General JUCE discussion\
**Created:** [April 18, 2024, 9:18am UTC](https://forum.juce.com/t/ara-plugins-and-host-automatable-parameters/60941 "2024-04-18T09:18:39Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![moritzsur](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@moritzsur](https://forum.juce.com/u/moritzsur)\
**Post date:** [March 11, 2025, 4:57pm UTC](https://forum.juce.com/t/ara-plugins-and-host-automatable-parameters/60941/16 "2025-03-11T16:57:42Z")

</div>

The main one is ProTools.

But I suspect that this will cause problems for most hosts that make good use of the partial consistency introduced with ARA 2.0.

After experiencing some of these problems myself I’m now storing this type of data in the audio modification (which is persistent). When getting or setting this type of data, I convert between playback sample positions and underlying audio modification sample positions.

---

_[View the full topic](https://forum.juce.com/t/ara-plugins-and-host-automatable-parameters/60941)._