# Jumpy/inconsistent parameter value changes when using ParameterAttachment on VST3

**URL:** <https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665>\
**Category:** Audio Plugins\
**Created:** [August 30, 2024, 3:32pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665 "2024-08-30T15:32:11Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![vladvoina](https://avatars.discourse-cdn.com/v4/letter/v/b5ac83/32.png) [@vladvoina](https://forum.juce.com/u/vladvoina)\
**Post date:** [August 30, 2024, 3:32pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/1 "2024-08-30T15:32:11Z")

</div>

I’ve been chasing a jumpy slider value [see video below]. I initially thought it’s performance related, but the root cause seems to the behaviour of `juce::ParameterAttachment` (specifically `juce::SliderParameterAttachment`).

[Jumpy Slider.mov.zip](https://forum.juce.com/uploads/short-url/Ns57EDF2a3PFDgPmrPVlkgnILe.zip) (75.1 KB)

When the slider is not connected to the APVTS (i.e. `juce::SliderParameterAttachment` is not created), the slider value moves smootly.

This issue reproduces on macOS, JUCE 8.0.1 VST3 in Ableton 10 and 12. It works OK in Standalone and AU.

It seems that sometimes on slider drags, `ParameterAttachment::parameterValueChanged` is called from both the message thread and audio thread. Based on the `newValue` I’m seeing in `parameterValueChanged` my suspicion is that the call from the audio thread is the one that is making the slider look jumpy. Is this expected? I would expect a call from the audio thread only on automation.

I was able to reproduce this message thread + audio thread callback on a basic AudioPlugin example, although the jumpiness is not that visible.

I’ve attached the CMake [AudioPlugin example](https://drive.google.com/file/d/1m9OKqG4qWzXWGLe3wMvCmE3xq5GLVRjD/view?usp=sharing) and [here’s a video of the stack traces](https://drive.google.com/file/d/1hgdp78QpTkND5A5a6bXidTPRVKRSx2RR/view).

Any idea what the issue is?

---

<div class="post-metadata">

**Author:** ![Flux](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/flux/32/18528_2.png) [@Flux](https://forum.juce.com/u/Flux)\
**Post date:** [September 1, 2024, 4:25pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/2 "2024-09-01T16:25:07Z")

</div>

I have exactly the same bug… Did you manage to fix it ?

---

<div class="post-metadata">

**Author:** ![vladvoina](https://avatars.discourse-cdn.com/v4/letter/v/b5ac83/32.png) [@vladvoina](https://forum.juce.com/u/vladvoina)\
**Post date:** [September 2, 2024, 6:35am UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/3 "2024-09-02T06:35:06Z")

</div>

No success. It’s actually worse than I thought as it’s also happening with `juce::ButtonParameterAttachment`. (again, only VST3 on Ableton - have not tested other DAWs)

1. Add a `juce::AudioParameterBool` to APVTS and initialise to `false`
2. Connect a `juce::ToggleButton` to the parameter above with `juce::ButtonParameterAttachment`
3. Set a breakpoint in `ParameterAttachment::parameterValueChanged`
4. Click on the button to toggle its state.
5. Breakpoint is triggered on message thread with a value of 1 (true) [see Image 1]
6. Breakpoint is triggered again audio thread with a value of 0 (false) [see Image 2]
7. Toggle’s state is still `false`
8. I click on the toggle again and turns on but breakpoint is not triggered

Very strange. I can repro this reliably in my plugin but not in the toy example. In the toy example only the `juce::SliderParameterAttachment` reproduces.

 ![Image 1](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/5/3/53b6095aa161e87f56df29f7372caca4ee7e4210.jpeg)

 ![Image 2](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/0/5/05ee7966884df8009d83ad311fcfe96fc6b7b461.jpeg)

---

<div class="post-metadata">

**Author:** ![yfede](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/yfede/32/506_2.png) [@yfede](https://forum.juce.com/u/yfede)\
**Post date:** [September 2, 2024, 8:34am UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/4 "2024-09-02T08:34:19Z")

</div>

when you set the value to the host via `setValueNotifyingHost()`, it’s possible that it results in a reaction from the host to the plug-in that is indistinguishable from a regular change to an automated parameter initiated by the host.

It would be very nice if `parameterValueChanged()` were called with a flag indicating whether the change was initiated by the host (for example a change in automation envelope), or if it was initiated by the plug-in UI (in which case it may probably be ignored by the plug-in UI because it’s already expected to represent the correct value)

---

<div class="post-metadata">

**Author:** ![Flux](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/flux/32/18528_2.png) [@Flux](https://forum.juce.com/u/Flux)\
**Post date:** [September 2, 2024, 9:24am UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/5 "2024-09-02T09:24:55Z")

</div>

It works well on Bitwig.

It’s weird because I’m pretty sure we use APVTS exactly as in the tutorial but the bug is obvious in the world’s most used DAW. I suppose JUCE team would have seen it by the time.

I remember the bug was in JUCE 7 as well.

Hope we find a solution someday !

---

<div class="post-metadata">

**Author:** ![ibisum](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ibisum/32/21288_2.png) [@ibisum](https://forum.juce.com/u/ibisum)\
**Post date:** [September 2, 2024, 10:28am UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/6 "2024-09-02T10:28:31Z")

</div>

I admit to being unsure about this - but shouldn’t this code:

` return juce::Decibels::toString(value, 1, -60.f, true); }`

Be:

` return juce::Decibels::toString(value, 2, -60.f, true); }`

… otherwise, you’re losing precision?

---

<div class="post-metadata">

**Author:** ![sudara](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sudara/32/8071_2.png) [@sudara](https://forum.juce.com/u/sudara)\
**Post date:** [September 2, 2024, 1:28pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/7 "2024-09-02T13:28:08Z")

</div>

I was also wondering if the value is percieved as different at the end of the audio callback — it should only be sending values that fail equality [since 2021ish](https://forum.juce.com/t/vst3-processparameterchanges/44396/2)?

Maybe worth sticking a breakpoint at that equality test in `processParameterChanges` — you may need to add the companion `withValueFromStringFunction` function so that normalization/denormalization produces the same value when translating back and forth?..

I’m naive as why this logic exists in the first place for VST, would love to understand if it’s spec-pleasing or “ensures audio callback always gets parameter changes in a timely way” or…

---

<div class="post-metadata">

**Author:** ![modosc](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/modosc/32/2308_2.png) [@modosc](https://forum.juce.com/u/modosc)\
**Post date:** [September 2, 2024, 7:40pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/8 "2024-09-02T19:40:01Z")

</div>

> [@yfede](#):
>
> when you set the value to the host via `setValueNotifyingHost()`, it’s possible that it results in a reaction from the host to the plug-in that is indistinguishable from a regular change to an automated parameter initiated by the host.
> 
> It would be very nice if `parameterValueChanged()` were called with a flag indicating whether the change was initiated by the host (for example a change in automation envelope), or if it was initiated by the plug-in UI (in which case it may probably be ignored by the plug-in UI because it’s already expected to represent the correct value)

i experienced this issue with ableton in an uncommon situation (a VST3 wrapper for an AUv3 plugin) and i had to do something like this in the VST3 to get it working (ymmv, this was essentially proxying changes from host ↔ vst3 ↔ auv3):

```cpp
// in processor
juce::ThreadLocalValue<bool> inAudioProcessorParameterChangedCallback;

void parameterChanged(const juce::String &parameterID, float newValue) {
  // we only want to listen for changes that come from the host so we can pass
  // them on. however - it's possible to end up here in the
  // audioProcessorParameterChanged callback when we call
  // setValueNotifyingHost(). the inAudioProcessorParameterChangedCallback flag
  // is an attempt to avoid this loop (change from slider in our editor ->
  // audioProcessorParameterChanged -> setValueNotifyingHost -> parameterChanged
  // -> setValue on on processor -> audioProcessorParameterChanged) see also the
  // similar "inParameterChangedCallback" code in the au wrappers
  if (inAudioProcessorParameterChangedCallback.get()) {
    inAudioProcessorParameterChangedCallback = false;
    return;
  }
  // otherwise this handles changes from host -> processor
}

void audioProcessorParameterChanged(
    juce::AudioProcessor *, int parameterIndex, float newValue) {
  if (getParameters()[parameterIndex] != nullptr) {
    inAudioProcessorParameterChangedCallback = true;
    getParameters()[parameterIndex]->setValueNotifyingHost(newValue);
  }
}

```

there is [code that does something like this already](https://github.com/search?q=repo%3Ajuce-framework%2FJUCE%20inParameterChangedCallback&type=code) but it may not be doing the right thing?

---

<div class="post-metadata">

**Author:** ![vladvoina](https://avatars.discourse-cdn.com/v4/letter/v/b5ac83/32.png) [@vladvoina](https://forum.juce.com/u/vladvoina)\
**Post date:** [September 4, 2024, 2:05pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/9 "2024-09-04T14:05:43Z")

</div>

It seems the jumpiness gets worse as the frame rate drops. I have been improving the frame rate of my plugin, which makes the VST3 jumpiness barely noticeable, but it’s still there. I’ll save myself the ParameterAttachment fork for now…

---

<div class="post-metadata">

**Author:** ![sudara](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sudara/32/8071_2.png) [@sudara](https://forum.juce.com/u/sudara)\
**Post date:** [April 5, 2025, 8:15pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/10 "2025-04-05T20:15:17Z")

</div>

I’m seeing behavior similar to this as well, VST3, Ableton 12, latest develop. In my case, a custom button component with a ParameterAttachment.

The short story is my ParameterAttachments are being called three times in VST3.

The first time is the expected stack trace with the expected value:

 ![CLion-EAP - 2025-04-05.45@2x](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/5/4/5428ef9308d3ae9c4e68c08e491fe29460bc8610.png)

The second time is through `JUCEVST3 EditController::audioProcessorParameterChanged` with the expected value:

 ![CLion-EAP - 2025-04-05.57@2x](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/7/2/72c04d67bedd2f3301f805b546055e3572f3d936.png)

And then the third time via AsyncUpdater — with the opposite value (which means that my button is impossible to toggle and my component breaks)

 ![CLion-EAP - 2025-04-05.09@2x](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/a/c/acbc29572cd26a1308a1c380879ce858cf5364e0.png)

I also found a workaround that I don’t understand at _all_:

I was calling `setEnabled()` within this attachment’s callback — if I instead put that call in a `juce::MessageManager::callAsync` — there’s no problem whatsoever and I only get a single call to my attachment instead of 3!

Maybe there’s a timing constraint or ordering issue with the additional VST3 parameter callbacks? Maybe @reuk has ideas…

---

<div class="post-metadata">

**Author:** ![JeffMcClintock](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jeffmcclintock/32/21430_2.png) [@JeffMcClintock](https://forum.juce.com/u/JeffMcClintock)\
**Post date:** [April 6, 2025, 10:33pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/11 "2025-04-06T22:33:15Z")

</div>

This is definitely a bug in Ableton Live ( I logged events from the DAW which confirmed that parameter updates are arriving out-of-order).

I reported it on March 14 2024. Ableton responded:

> Re: Ableton Support #2890650: Ableton Live VST3 plugin automation bug (jitter).
> 
> **QA Agent** (Ableton Support)
> 
> Apr 15, 2024, 06:00 PDT
> 
> Hello Jef,
> 
> we’re aware of this problem. It’s filed in our bugs backlog and there’s progress on this currently, but it’s not yet clear when a fix would be ready to ship.

---

<div class="post-metadata">

**Author:** ![sudara](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sudara/32/8071_2.png) [@sudara](https://forum.juce.com/u/sudara)\
**Post date:** [April 7, 2025, 10:05am UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/12 "2025-04-07T10:05:34Z")

</div>

Thanks Jeff, that’s helpful. I just heard this exact same thing from another Ableton source.

I guess that means there’s a big chunk of at least Ableton 12 versions that can be expected to work this way and will need to be mitigated (I haven’t tested Ableton 11).

It is interesting to me that the issue is only present when I call something synchronously on the message thread.

---

<div class="post-metadata">

**Author:** ![chkn](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/chkn/32/3862_2.png) [@chkn](https://forum.juce.com/u/chkn)\
**Post date:** [July 29, 2025, 11:47am UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/13 "2025-07-29T11:47:28Z")

</div>

Aha, this explains my trouble with my parameter link mechanism with Ableton and VST3.

Is there anything new from the Ableton side?

PS: I guess the behaviour is part of the VST3 specification where a plugin can multiple GUIs which are separated from the processor model, but makes no sense in terms of JUCE where GUI and Parameter access the same underlying parameter value.

---

<div class="post-metadata">

**Author:** ![JeffMcClintock](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jeffmcclintock/32/21430_2.png) [@JeffMcClintock](https://forum.juce.com/u/JeffMcClintock)\
**Post date:** [January 1, 2026, 11:25pm UTC](https://forum.juce.com/t/jumpy-inconsistent-parameter-value-changes-when-using-parameterattachment-on-vst3/62665/14 "2026-01-01T23:25:10Z")

</div>

Happy New Year!

**Ableton Live 12.3 Release Notes**

- The UI of VST3 plug-ins will now animate more smoothly when changing plug-in parameters.
