The bug is most likely in the plugin. If it sends param changes back to the host it will cause SONAR to dirty the document.

Understood, Noel.
I felt I should follow the appropriate procedure and log the "bug" anyway, just in case. I understand it will most likely be low-priority. 
 
I know the VSTi is pretty popular; it's a free but very good sounding Minimoog emulator.

I have a problem with the Asterik. If I have any automation in my project, it will "dirty the document" as soon as the automation engages. This causes problems for me with the "playlist" because I do a lot of automation in my tracks. When I have a large Playlist, the songs remain loaded after playing them thus stacking up song after song during a performance in the background "waiting for me to answer whether or not I want to save the changes." This bogs down the computer and time is of the essence in a live situation. I haven't changed the song, the program thinks I have because there's automation in it. I would love to see a fix to this.

@JCody find out what plugin does it then you can log the issue with them.

Bug resolved as "Third part issue; Will not fix" as expected.

This is the most annoying bug fix, ever.
 
I know it's not Cakewalk's fault... but is there any chance we can get an .INI setting to restore the old "save VST parameter change" behavior?

Have you found out which plugin is causing it?
I wouldn't regard it as a bug BTW, annoying for sure though.
 
EDIT - sorry forgot to read again...
 
"I'm pretty sure that MiniMogueVA" - well there you go.
Stop using it or demand an update (as you say it may not be supported). Cakewalk really can't be expected to fix or work around other people's code. They have enough of their own problems...

>> Cakewalk really can't be expected to [..] work around other people's code
 
Actually, they've done that quite a bit in the past. Of course I'm not holding my breath they'd do it in this instance.