Automation Track / Curves Not Triggering Changes

[Spotto]

Hi folks,

WF 13.5.21 Win

I use automation quite a bit with various synth and other VSTs and have noticed that sometimes the automation fails to actually automate changes - ie, doesn't get parameters to follow the curve. If I just have the initial horizontal line there, I can slide it up and down using the mouse and it operates the parameter but the moment I add a node to automate a change, it stops changing and stays at the original setting even if I slide a section with the mouse. Just wondering whether anyone else has been experiencing this and whether there's a fix? Maybe I'm doing something wrong but.... I don't think so. Happy to be proved wrong!

Any thoughts and solutions gratefully received.

TIA

S

[dysjoint]

I can't really see an actual problem, just a weird behaviour when adjusting a curve (flat line) with one node. It's like Waveform holds both the initial value and the current value of the node and constantly flickers between them. Deleting the node returns the curve (flat line) to the inital value. Sometimes when holding the node and adjusting, if you move the mouse above or below the track boundary the value returns to the initial value. BUT....if I add a second node and use the automation curve for it's intended purpose then this behaviour stops and all is good. So, for me, no problem.

[Spotto]

I think I may have found the cause. Looks like something snapped when the CPU got overloaded at some point earlier in the composition / edit / mix. Then it saved with the glitch. I reckon this because, as a test, I copied the track into a new project and it works fine there so, the first project seems to have saved with the glitch on board and now won't let go. I do tend to go for quite intensive automation which can mean high CPU usage and potential for engine failure. The new test edit's fine. Looking like operator error but worth sharing.