yevster wrote:Autosave is probably the most frustrating non-bug behavior in Studio One. It feels like every time I want to play up to a certain point, autosave starts just when I want to stop playback. I feel at that moment lurched out of whatever creative zone I might be in, turning into a hostage to my DAW's whim to do what it needs to do.
I'm not sure why saving takes so much longer with StudioOne than with any other DAW, but if that's how it must be, couldn't it be done in the background rather than modally? And failing that, couldn't autosave just not happen during playback? I know disabling autosave is a workaround, but that can lead to a whole other brand of frustration.

Texas Willie wrote:Well, I am going to chime in with my two cents worth
After years of using 3D Architectural software and having system crashes destroy hours of valuable production (even with an Autosave feature), I just got in the habit of hitting Ctrl S every time I made a change to ANYTHING.
As a result of that 'behavior modification' in my work habits, losing work or having my creative juices interrupted is just not an issue.
I have S1's autosave turned off and just use the very quick method of hitting Cntrl S while I am working/playing.
It seems these days, that everyone wants everything done for them, without having to put forth ANY effort or have any responsibility for their own work......Just Sayin'
TW

Texas Willie wrote:Well, I am going to chime in with my two cents worth
After years of using 3D Architectural software and having system crashes destroy hours of valuable production (even with an Autosave feature), I just got in the habit of hitting Ctrl S every time I made a change to ANYTHING.
As a result of that 'behavior modification' in my work habits, losing work or having my creative juices interrupted is just not an issue.
I have S1's autosave turned off and just use the very quick method of hitting Cntrl S while I am working/playing.
It seems these days, that everyone wants everything done for them, without having to put forth ANY effort or have any responsibility for their own work......Just Sayin'
TW

Lokeyfly wrote:Certainly not my intent to polarize us folks here as we all want a better DAW as S1 develops. It’s another point of view, that’s all. Hope it’s interpreted that way.
I agree with Texas Willy on this and I'll (hear me out) explain what at least works for my file management. Perhaps it will work for you or you'll respond with “Blah blah, it's 2013 already”.
Autosave - First and foremost, I don't ever autosave, especially with a DAW (I can feel the blood bubbling already). The reason being 2013 or not, I am trying to get as much lean CPU power and resources as possible. However efficient my computer is (and it seems to be, so far), I don't need the computer auto saving, reading available sectors, then writing to them when I'm running 15 mostly stereo audio tracks, running multiple percussion samples from all different velocities from independent drum multi samples, using FX bussed convolution reverb. Does the computer crash, no it doesn't. Do I have to convert instrument files to Audio? Hardly ever, unless I wish to create volume or pans via automation lanes. Just simply stressing a point that when hard disk recording is going on, who needs drive(s) working additionally to save (reading & writing), when heads are accessing many, many sectors for data, reading and writing already? I’d say there’s just a little more horsepower (did I say that?) if you do not autosave.
Rename - As the song develops I'll use a number or letter suffix (songname_1, _1a, _2a, _2b, etc.). Sometime after the suffix, even add a description of what occurred. For example Songname_2b nice mix, or 'songname_1d added Angies vocals'. Maybe no description after the suffix at all. Have to keep inspiration moving, right? This only takes a second, or two, and it’s on your terms, not the computer’s automatic scrub your balls for you terms.
Autosave is not going to manage your files that way. On the contrary, some parts of the song reach certain milestones, or developments that occur. Sure most of the time, I just hit Control S as Texas Willy does as well. I just don't rely on it too much just in case I’m overwriting an already corrupt file that won't soon after reopen. You do that once in your life and promise that will never happen again. I may never revisit an old file. Ah, but if there was a great mix, and the song morphed into something other than great, you can go back and rekindle a great feel, or mix, knowing how the song developed via descriptive file names along the way.
Look this works for me, and I fully understand that some really feel they need the autosave function on period. Thankfully S1 keeps folders with wav files all tidy, so the only thing that is updating is the song files info, not reconstructing the waves over and over. Have a look at Reason to really scream at that bit of wasteful file management. One song file, all waves embedded. Though you can autosave, but hold on to how large each file save is. Ouch!
Described is a file management process. You may not agree with it. Just know some of us couldn’t care less about autosave.
Thanks for hearing my point, and hope the described process provokes only some consideration.
I’d autosave with a text editor, AutoCad, Inventor or some less resource demanding program. Not a DAW. Just me.

yevster wrote:I'm not sure why saving takes so much longer with StudioOne than with any other DAW