# Final Cut - Automation Bug **URL:** \ **Category:** Audio Plugins\ **Created:** [November 6, 2017, 11:15am UTC](https://forum.juce.com/t/final-cut-automation-bug/25010 "2017-11-06T11:15:13Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![daniel](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daniel/32/790_2.png) [@daniel](https://forum.juce.com/u/daniel)\ **Post date:** [November 9, 2017, 1:43pm UTC](https://forum.juce.com/t/final-cut-automation-bug/25010/8 "2017-11-09T13:43:05Z")
After a lot of testing and digging, I am convinced, that it is bad to save automated parameters in the getStateInformation() / setStateInformation(): 1. Parameters are stored by the host outside the private stateInformation chunk. That is, because a parameter is only valid for a given timepoint 2. The host will set the parameter outside of each processBlock call, so setting a value yourself is counter productive 3. At least in final cut setting a value during playback will move the whole graph to fit the value at that time point. This is the reason, why the graph jumps, if you press play hovering a position with a different value). 4. Because the state might reflect a different snapshot, it must not restore automated parameters. So not setting a value from setStateInformation avoids that problem in FCPX. Maybe it does as well for other hosts… Can anybody please help me think, are there any reasons or situations, when one _should_ set parameters from setStateInformation? @fabian? --- _[View the full topic](https://forum.juce.com/t/final-cut-automation-bug/25010)._