# New plugin automation examples

**URL:** <https://forum.juce.com/t/new-plugin-automation-examples/24796>\
**Category:** General JUCE discussion\
**Created:** [October 25, 2017, 1:49am UTC](https://forum.juce.com/t/new-plugin-automation-examples/24796 "2017-10-25T01:49:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lalala](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/lalala/32/8577_2.png) [@lalala](https://forum.juce.com/u/lalala)\
**Post date:** [October 25, 2017, 8:14am UTC](https://forum.juce.com/t/new-plugin-automation-examples/24796/3 "2017-10-25T08:14:28Z")

</div>

Redo never worked correctly with AudioProcessorValueTreeState, it’s a known bug :

> [@Redo issue with PluginStateValueTree. SetPropertyAction & excludeListener](https://forum.juce.com/t/redo-issue-with-pluginstatevaluetree-setpropertyaction-excludelistener/21388):
>
> AudioProcessorValueTreeState::Parameter::copyValueToValueTree() calls setPropertyExcludingListener(), giving this as listener to exclude. That creates a ValueTree SetPropertyAction() with that Parameter given as ‘excludeListener’. In consequence, when redo is called, SetPropertyAction::perform() will be called, but the parameter won’t be notified by the change. Note that it “sometimes” work in practice, because you often modify your parameter twice in a row (through a slider drag for instance…

---

_[View the full topic](https://forum.juce.com/t/new-plugin-automation-examples/24796)._