Cakewalk auto-saving too often

[Michael Fogarty]

yes, its amazing isn't it. I set mine to time instead of amount of changes as I sometimes will track an event in event list and move it from 25 -70 one increment at at a time. Adds up quickly.

 

edit: sorry, read the whole thread and it seems you may have other issues. Don't know how to delete a post.

Edited October 21, 2021 by Michael Fogarty

[jono grant]

On 2/16/2021 at 6:24 PM, Noel Borthwick said:

If you have a plugin in your project that has a lot of parameters and its notifying every parameter as a change it could add up quickly.
What happens if you set the number of changes to 0 to make it only respect the number of minutes?
 

There are many people having this issue. Noel says it's caused by a plugin with a lot of parameter changes. This is happening even without plugins. Something is wrong. I'm having this issue with one midi file and no plugins. Also, it would be great if CW didn't count plugin parameter changes as a file change. It doesn't make sense. If that is indeed the issue, perhaps there's some way to not have CW count plugin changes in the autosave function and only count actual changes to the file that the user makes. Very frustrating.

JG

[jono grant]

It's also worth noting that any time I have a crash in CW, it is at the exact same time as an autosave occurs. 100% of the time. I've raised this issue for years and years. CW autosave is messed up. It doesn't respect anything you have set in the preferences as far as zero changes, or setting a time limit. It simply doesn't work. I wish CW would look at these issues that have been present for ages.

JG

[reginaldStjohn]

Submit a support ticket and send them your project. Maybe they can reproduce it.

[Michael Fogarty]

On 2/21/2022 at 5:01 AM, jono grant said:

It's also worth noting that any time I have a crash in CW, it is at the exact same time as an autosave occurs. 100% of the time. I've raised this issue for years and years. CW autosave is messed up. It doesn't respect anything you have set in the preferences as far as zero changes, or setting a time limit. It simply doesn't work. I wish CW would look at these issues that have been present for ages.

JG

I have noticed this as well, that it "often happens" at this time. But it is usually if I have a pretty CPU intensive song loaded with heavy VST activity. I did take off the "autosave" and one time when I desperately needed it, it wasn't there and I lost work. I do it by minutes, not by changes. It seems to work better I assume because less calculations. I set it for 15 minutes.

 

[msmcleod]

On 2/20/2022 at 7:57 PM, jono grant said:

There are many people having this issue. Noel says it's caused by a plugin with a lot of parameter changes. This is happening even without plugins. Something is wrong. I'm having this issue with one midi file and no plugins. Also, it would be great if CW didn't count plugin parameter changes as a file change. It doesn't make sense. If that is indeed the issue, perhaps there's some way to not have CW count plugin changes in the autosave function and only count actual changes to the file that the user makes. Very frustrating.

JG

If you're working in the PRV, this can generate a lot of changes as IIRC a lot of operations are done on an individual note by note basis  ( as opposed to the clips view, where operations are done on a clip by clip basis ).

The best thing to do when you're still at the stage of editing events/clips is to set your auto-save to be time based.

[jono grant]

On 2/22/2022 at 4:51 AM, msmcleod said:

If you're working in the PRV, this can generate a lot of changes as IIRC a lot of operations are done on an individual note by note basis  ( as opposed to the clips view, where operations are done on a clip by clip basis ).

The best thing to do when you're still at the stage of editing events/clips is to set your auto-save to be time based.

I set it to 10 minute autosave only. There is no value set for amount of changes. Yet, it saves all the time! This is on files that have a fair bit going on, but still, why is it saving so much if set to 10 minutes?

Also, if I ever crash, it is always at the same time as an autosave... 

[Amberwolf]

Necrotopic REVIVE! 

 

Is there any way to "block" a plugin (VST) from sending parameter changes, to prevent the autosave triggering?  

Note that I'm still using an ancient SONAR (happens even in in 6, 7, etc) , so no answer from devs is expected, but anyone with insight is welcome to respond with useful feedback. 😉  I know it's a plugin issue, not cakewalk/etc.

 

I use Acmebargig's Shred, and any project with it in there, *even if it's disabled in the bin*, will instantly dirty the project when I save the project.  I can let the project just sit there, and eventually it will autosave on it's own long before the timed autosave. It's even worse if I am doing anything, especially play/stop/play/rewind/stop/click in timeline/play/stop/etc--it may autosave everytime I hit stop, and sometimes do it several times in a row before I can even do the next thing, with my finger already pressing the next editing key. 

There is no automation feeding Shred, and it doesnt' matter if it's UI is open, minimized, or closed.  Or if the track's automation read RD button is disabled or not.  Or bus vs track vs clip fx bin. Just having Shred in the project causes it.

I use autosave at every 100 changes, 10 minutes, which I've found is a reasonable balance between annoyance of autosave at the wrong moment and data loss.  I also frequently SaveAs with a new filename using my own versioning system with tiny notes in the filename, but the autosave is "just in case" and sometimes is useful for recovering from a stupid or a plugin hang or crash with minimal editing loss. 

Upping the changes number to something ridiculous slows the process down, but doesn't stop it, and then it doesn't autosave for my real changes after I delete the plugin. 

 

Oddly, it does not *appear* to autosave more often if there are multiple copies of the plugin in different track bins (using different heads/chains), which seems wierd...but it happens so often anyway, it's not easy to tell if this is really true. 

 

AFAICR its' the only plugin I use that does this...but it's annoying enough that whenever possible I bounce the clips used with it and delete it from the project.  However, there are many projects I can't do that for a long time because I'm working a lot directly with the source clips that feed it, tweaking them (or the shred setup itself) for the "right sound". 

 

I have other amp sims, but this one has a bunch of presets that are already close enough to what I want that I use it a lot. 

Edited December 23, 2024 by Amberwolf

[SirWillyDS12]

1 hour ago, Amberwolf said:

Necrotopic REVIVE! 

 

Is there any way to "block" a plugin (VST) from sending parameter changes, to prevent the autosave triggering?  

 

Not that I know of but being able to block a VST is a great idea... I have a few that constantly "Dirty" a project... I shut off "number of edits" for Auto Save and only use after so many minutes because of the nasty VST's that cause the problem...

[57Gregy]

I have autosave turned off and try to remember to Ctrl-S often while working on a song.

[呂聖斐]

Read all the replies...It seems new Cakewalk didn't solve this problem, right?

[Noel Borthwick]

You are reading an ancient thread! There is no problem to solve unless you have a project that exhibits the problem. 
Also note that CbB is not being maintained other than for the most essential issues. If you have a problem in Sonar submit a ticket with a repro project in the Sonar forum.