• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Autosave in Background

RobWJ

New member
Any chance to get this Feature?
It is 8 Years old
haha


I hope you all supported it already.

Does the autosave in S1v7 gets more annoying than before?
For now I deactivated it, because it also change window focus and this is fatal for my workflow.

How are you all dealing with this?

Or did I miss some other settings?

Or should I bother support with this?
 
Background saving is not as straightforward as it might seem to some. Saving a song file involves capturing the entire song state, including plug-in data, mixer settings, arrangement data etc. Any changes made during the saving process could result in inconsistencies or even corrupt the saved file. Without having spoken with Studio One's CTO about this topic, I assume that this complexity is one of the reasons why Studio One, like many DAWs, uses a modal save process to ensure the integrity of stored song data.

How are you all dealing with this?
I save manually. I've never had the need for a background save. If the song save takes too long, you can always turn on the "Use cached plug-in data on save" option (Options -> Locations), but this only works properly if the plug-ins also report their state changes to the host correctly. This option can massively improve the save times, as a large part of the save time is taken up by querying the states of all 3rd party plug-ins in the song.

Or should I bother support with this?
What would be the benefit?
 
Last edited:
  • Like
Reactions: AAV
......How are you all dealing with this?
Actually. I don't ever autosave. Ever. Any time I make saves that are impactful in that they are a logistical juncture with the song, I save as and add a suffix to the filename that displays some meaningful identifier towards that save. Such as:
songname_1d initial tracks.song, or
songname_2c Jens vox.song, or
songname-2m mix ref.song, etc.

MMV but I think too much is placed on autosave that doesn't leave any real breadcrumbs (traceability) anyway. What if the mix starts really going sour because of working on a tune too many hours late into the evening? Is autosave going to get you to some known safe place? Well..... maybe, or likely not. Maybe you go back to some prior save and miss some important milestones you needed, or are now stuck with or still having to fix.

As Lukas points out, the delay with autosave, there's a lot of information being stored. Undersandable. It's just not for me, delay or not. By avoiding it altogether, there's no down time, just progress. I'd say I understand if others need it, which is typically my position, but in the case of autosave, I dont understand its benefit. Just a thought in getting passed it.
 
Last edited:
For me it amounts to about a second of a little blue line flashing across my screen. I hardly even see it and it doesn't effect my workflow at all. I was going to disable it at first but now I'm glad I didn't. It saved my projects more than once.

:) John B
 
Back
Top