Hi Brian, no this is the wet/dry mix of Breverb that is automated.  It's on a vocal bus, and I turn the reverb off on a couple of lines in the chorus of my song and bring it back in through the end of the song.  If I stop the song anywhere short of the ending, it doesn't prompt me to save; only if I let it play all the way through does it ask me to save.  Mr. Garrigus, do you have any ideas?

Lynn, et al,
 
If the automation is on a synth, have you tried freezing the tracks?
 
Brian

As soon as Cakewalk lets me freeze a bus, I'll be glad to
 
Regards,
Dan

Lynn


Hi Brian, no this is the wet/dry mix of Breverb that is automated.  It's on a vocal bus, and I turn the reverb off on a couple of lines in the chorus of my song and bring it back in through the end of the song.  If I stop the song anywhere short of the ending, it doesn't prompt me to save; only if I let it play all the way through does it ask me to save.  Mr. Garrigus, do you have any ideas?

Seems to me this might be logical & intended.

If, as the song plays, the now time moves through an automated parameter change, a control somewhere will move sympathetically and Sonar will flag up "Project Change", even though when you stop, the control will move back to it's starting position.

If Cakewalk can confirm this, I suggest we put in a feature request to have it modified so that only manual changes are flagged up, not changes through automation.

As an aside, this 'save request' also happens after an export.  I think in this case it's because I've selected all the tracks before exporting - that's the only 'change' I can think of.

This has been happening since at least v8.5.3

Lynn, I've seen this before. It's a 3rd party plug you're using bringing it on and should have nothing to do with Sonar itself.

As you may or may not know, I beta test for a few plug companies. In my beta work, sometimes the beta plugs cause this * to show up and you don't even need to do anything new to the project. I can save it and re-open, and upon re-opening, there's that * again. If you try to open the project in Sonar's safe mode while doing a process of elimination on the plugs, you'll eventually find the one that is causing this. I've had this issue so many times, I can't even begin to tell you...and it IS frustrating. But it's NEVER in my experience, been Sonar's fault.

As soon as I got the final version of the plugs I was testing, the * went away. So try it and see which one may be causing you the problem. That's the only time I've encountered this problem religiously. Hope this helps...best of luck my friend. :)

-Danny

You are quite correct on the project change detecting by Sonar after an export.

I get that all the time, and just close the projects without saving, as I do not want to inadvertently ADD some change I accidentally may have introduced in doing the export.  (hitting some stray key without even knowing, etc.).  That is also my thinking whenever Sonar asks me for a save when I have not made any deliberate changes.  So, I NEVER save if I am not 100% sure I did something on purpose.  I would rather make sure to LOSE any change that I have no awareness of.

I suppose it boils down to philosophy applied to that situation, and different folks will have different approaches on dealing with this kind of situation.

Bob Bone

I've seen this behavior as well but never worried about it enough to track down the source of it. In one case, the asterisk appeared immediately after loading or saving the project. 

I assume it's due to a minor bug in a plugin. When you change a plugin's parameters, those settings only get saved when the project gets saved, so the plugin must notify SONAR to set its data-changed flag to make sure that happens. However, the plugin has to differentiate between parameter changes you made via the UI versus changes made via automation. I think sometimes the devs overlook that distinction in their code and accidentally set the change flag in response to MIDI data or automation.

Well, I'm just annoyed simply because whenever I open a project and hit play then try to exit Sonar, it asks if I want to save the changes... What changes?! It's the little things with Sonar that annoys the crap outta me.

Well, I'm just annoyed simply because whenever I open a project and hit play then try to exit Sonar, it asks if I want to save the changes... What changes?! It's the little things with Sonar that annoys the crap outta me.