Plogue sforzando is working good on Cakewalk Sonar (and CbB) but there is an issue.

Project status is always gone to "edited", when I just play project which contained sforzando. Like [Project.cwp*]
It's weird. What's this? Known issues?
I'm worried it affects auto backup. i.e. Getting wastefully/frequently backup with auto backup setting.
 
This issue is also happen with no CC control. I tested with simple MIDI clip, too.
If sforzando instrumemt is empty, its no problem.
If sforzando instrumemt is not empty, project status is gone to "edited" when just play it.
I checked with all sound fonts of all I have. TableWarp2 is no exception too.
 
Thanks,
HIBI

I think this is because the plugin is sending an "UpdateDisplay" message to the host and Cakewalk is responding by treating this as an edit change and dirtying the document. It happens by simply opening the plugin UI.
I'll look into it and see if we can avoid changing the project edited state when this happens.
 
 

Noel, thank you for replying.
 
As I thought, it affects auto backup?
Anyway, I hope that you can avoid changing the project edited state.

Same thing happens with Blue3 organ from gg-audio com.
Don't know why but I never thought to report it, I just got used to this inconvenience.
Hopefully, if the reason is same, that can be solved now.

I don't see any obvious problem with Blue 3. Nothing is dirties on playing a project. If you move any of the plugin controls it will dirty the project since you are changing the preset.
sforzando was sending an update message just on opening the UI which is a different matter.

Ah ok, changing the knobs dirties project. Thanks for clarification.
I have some CC data written in midi track, like CC# 11-Expression, and just by playing it back the project gets dirty. That's still annoying but at least now I understand where it comes from.

Just investigated these:
 
Chris: that sounds like a bug in the plugin. The plugin is calling back to the host with audioMasterAutomate in response to the host sending CC 11 data. That is not normal. It results in us thinking the plugin is changing its parameter state through its own UI.
 
HIBI: Sforzando is sending audioMasterUpdateDisplay in response to just opening its UI. That message is normally sent in response to a plugin changing its state. As a result Cakewalk thinks the project file has been modified.
 
I cannot fix this from the host side since it will make Cakewalk ignore legit changes from other plugins. Please contact the respective vendors and ask them to consider fixing these issues in the plugins.

Edit, select all, export is also setting the dirty bit.
If I recall correctly this was an old one that Splat quit doing.
 
I could be wrong again though.

Yes! Thanks for checking. I will forward it on the Blue3 beta forum. The dev is very responsive, he'll make it work right. Thanks!

Yes this has always happened in the past. For me I can save a project, export it and then when I go to close it it wants to save again. I'd say that half the time this will happen. I just re-save as no harm is done.