# AudioProcessorValueTreeState & UndoManager usage

**URL:** <https://forum.juce.com/t/audioprocessorvaluetreestate-undomanager-usage/16179>\
**Category:** Audio Plugins\
**Created:** [December 9, 2015, 1:23pm UTC](https://forum.juce.com/t/audioprocessorvaluetreestate-undomanager-usage/16179 "2015-12-09T13:23:39Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [May 9, 2018, 6:44am UTC](https://forum.juce.com/t/audioprocessorvaluetreestate-undomanager-usage/16179/25 "2018-05-09T06:44:38Z")

</div>

[https://github.com/WeAreROLI/JUCE/commit/2e51654958df26d9c374e961758180cc842e0dfa](https://github.com/WeAreROLI/JUCE/commit/2e51654958df26d9c374e961758180cc842e0dfa)

This commit should address the issues using an UndoManager with an AudioProcessorValueTreeState.

- An undoable action is no longer pushed onto the stack when the plug-in is loaded
- Redoing actions works correctly
- New transactions are started when you interact with an attachment

Since this alters the behaviour of the UndoManager this is technically a _breaking change_, but I doubt anyone was relying upon the old way of doing things.

---

_[View the full topic](https://forum.juce.com/t/audioprocessorvaluetreestate-undomanager-usage/16179)._