• SONAR
  • new in Manchester- 197 automation message
2016/01/25 14:18:48
nace
I just installed Manchester & tried the usual automation snapshot feature to insert a node ( rt. click on volume)
After the rt. click all boxes lit up & I received this message pop-up (for the first time ever btw)
"197 automation parameters were modified etc..."
Is this a new feature, if so how do turn it off?
2016/01/25 14:42:11
nace
edit-this problem also fixed
2016/01/25 15:49:38
azslow3
I confirm, Automation is broken in Manchester. Arming automation for any parameter arms ALL parameters.
 
I have also explicitly checked before upgrade, that is new in Manchester.
 
EDIT: disarming one parameter automation write throw CS API disarm only this parameter, disarming one parameter with mouse (for example for volume) does not work at all.
2016/01/25 17:26:27
kb420
Have you submitted a bug report,  or tried to contact Cakewalk about the problem?
 
Actually,  I don't seem to be able to recreate the problem on my system.
2016/01/25 17:27:34
Bristol_Jonesey
Confirmed.
 
Boston, we have a problem.
2016/01/25 19:12:57
gokidsmusic
Confirmed. Platinum - Manchester update.
 
It seems to be an "everything on the channel" selection.
Select a control for automation recording by right clicking the control, everything is selected.
Usually half the write button turns red, now the whole thing does, as if you pressed the write button.
 
In practice, I found that only a control that is adjusted gets an envelope created.
 
If I don't change anything, the "automation present" indication remains.  It doesn't matter if I deselect the write automation button on the channel or the clear automation button on the control bar.
Confirmed there are no envelopes created unless I move something.  
 
Starting and stopping playback with automation write disabled clears the "automation present" indication.
 
I rolled back to Lexington to see if the same thing was happening there, no issue that I could find.  I rolled forward to Manchester and will probably stay.
 
It's not a problem for me, as I typically (95% of the time) draw automation by hand and there seems to be nothing wrong with that operation.
 
Windows 10 64bit, AMD FX-9590, 16 Gb ram, AMD Radeon HD 7450, ASUS M5A99FXPro R2.0, 250Gb SSD sys. drive, 2- 1Tb Int, 2- 120Gb SSD Sample drives.
Sonar Platinum - Manchester
 
2016/01/25 19:17:37
skitch_84
Please submit a bug report so that they can get us a patch right away :)
2016/01/26 06:16:39
subtlearts
Hmm. This doesn't sound good. I'm in the middle of a project that I can't afford to jeopardize, so I'm wary about running the upgrade so I can test and confirm, but I'll be watching to see if there's a patch for this soon - seems like a matter of some urgency if automation is broken. Sounds like it's more a display issue than a functionality one, but still... 
2016/01/26 06:25:50
azslow3
This bug will affect you in two special cases (only):
1) you use control surface / mouse to arm automation for one parameter. In Manchester it will work like global arm automation. So in case during automation writing you touch some other parameter, it will be automated.
2) you use "Right click/Snapshot" (like in OP). Before it was just adding one automation point for this particular parameter, now it will do a snapshot for all parameters related to the strip.
 
The bug is not affecting other automation aspects. But that is not a display issue.
2016/01/26 06:29:17
subtlearts
Got it. Thanks for the clarification! I think that will not substantially affect my workflow, so I will proceed with the upgrade and roll back if I need to. 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account