Auto-Save poorly implemented

Author
jkoseattle
Max Output Level: -79 dBFS
  • Total Posts : 556
  • Joined: 2004/10/21 16:29:48
  • Status: offline
2014/05/03 18:44:50 (permalink)

Auto-Save poorly implemented

Auto-Save is impossible to set properly.
 
I have a complex project which takes 10-15 seconds to save. I have Auto-Save on for safety. I set it for every few minutes, but soon discovered that if I am doing nothing, say playing back, for over the length of time between saves, then every time I go to make some edit, Sonar sees the time span has elapsed so it Auto-Saves again, wasting another 10-15 seconds. Then I listen to the piece again, make a single change, and it happens again.
 
So I switched to auto-save every 100 edits. What I discovered was that if you select say, 50 tiny clips and copy-paste them, that counts as 50 edits. Do it twice and Auto-Save is engaged. I was doing a lot of that kind of editing and again waiting out the 10-15 second save. Really annoying.
 
I guess I have switch back and forth depending on what I'm doing at the time. Wish that was unnecessary. Auto-Save should be MUCH smarter.

Sonar Version: Platinum  
Audio Interface: M-Audio Delta
Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
Soft Synths: EastWest PLAY Symphonic Orchestra
MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
Check out my work here
#1

25 Replies Related Threads

    chuckebaby
    Max Output Level: 0 dBFS
    • Total Posts : 13146
    • Joined: 2011/01/04 14:55:28
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 21:31:38 (permalink)
    I have never relied on automation to save something that is of importance to me.
    in other words, use the key command CNTR+S for saving.
     
    it becomes a force of habit after a while, you work a little bit, you save, you work a little bit, you save.

    Windows 8.1 X64 Sonar Platinum x64
    Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
    Focusrite Saffire 18I8 - Mackie Control
       
    #2
    rbowser
    Max Output Level: -10 dBFS
    • Total Posts : 6518
    • Joined: 2005/07/31 14:32:34
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 21:58:56 (permalink)
    chuckebaby...use the key command CNTR+S for saving...

    Big +1 to that reply.  I save several times every minute, basically every time I do an edit.  I do it without thinking, but I'M in control of it, not some funky auto-save thing which can get in your way - as per your experience, jko.
     
    Randy B.
     

    Sonar X3e Studio
    Roland A-800 MIDI keyboard controller
    Alesis i|O2 interface
    Gigabyte Technology-AMD Phenom II @ 3 GHz
    8 Gb RAM 6 Core Windows 7 Home Premium x64
    with dual monitors
    #3
    mixmkr
    Max Output Level: -43.5 dBFS
    • Total Posts : 3169
    • Joined: 2007/03/05 22:23:43
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 22:07:14 (permalink)
    +2...  My hand can do Ctrl + S like playing a C chord on the guitar.  Easy peasy.  When I have talent over, basically after every take, I play a *C chord* on Sonar.  Ctrl + Z is pretty close to the same thing physically... , but big difference.  So watch out for that.
      However, I use that a lot too.

    some tunes: --->        www.masonharwoodproject.bandcamp.com 
    StudioCat i7 4770k 3.5gHz, 16 RAM,  Sonar Platinum, CD Arch 5.2, Steinberg UR-44
    videos--->https://www.youtube.com/user/mixmkr
     
    #4
    Anderton
    Max Output Level: 0 dBFS
    • Total Posts : 14070
    • Joined: 2003/11/06 14:02:03
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 22:10:14 (permalink)
    chuckebaby
    I have never relied on automation to save something that is of importance to me.
    in other words, use the key command CNTR+S for saving.
     
    it becomes a force of habit after a while, you work a little bit, you save, you work a little bit, you save.




    Another +1. I have auto-save engaged for "x" number of minutes just in case I get so wrapped up I forget to hit ctrl+S. Also, I do my own versioning. Every now and then I'll save as projectname2, projectname 3, etc. That way if I did some horrible keyboard shortcut faux pas that nuked the entire second half of the song or whatever, I can go back to a previous version.
     
    Auto-save is your "court of last resort" in case you haven't implemented your own saving regimen that's optimized for how you work, because it will in fact save something that would hopefully be of use.

    The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
    #5
    gswitz
    Max Output Level: -18.5 dBFS
    • Total Posts : 5694
    • Joined: 2007/06/16 07:17:14
    • Location: Richmond Virginia USA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 22:18:52 (permalink)
    I find autosave works fine for really very large projects that have no midi.
     
    When you include a lot of midi, the save time moves way up. There are times that I then need to change the settings.
     
    You can do it by time or by change count. I also keep 10 versions of the files, but it has almost never mattered. I just figure if it ever helps me, it was worth having.

    StudioCat > I use Windows 10 and Sonar Platinum. I have a touch screen.
    I make some videos. This one shows how to do a physical loopback on the RME UCX to get many more equalizer nodes.
    #6
    mmorgan
    Max Output Level: -77 dBFS
    • Total Posts : 676
    • Joined: 2013/02/19 23:39:05
    • Location: Bellingham, WA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 23:12:56 (permalink)
    Save early save often...that is my mantra in every computer related task I do. And I do it with <Ctrl><s>.
     
    Simples.
     
    Regards.


    Mike

    Win8(64), Sonar X3e(64) w/ RME Fireface UFX.
    #7
    Kev999
    Max Output Level: -36 dBFS
    • Total Posts : 3922
    • Joined: 2007/05/01 14:22:54
    • Location: Victoria, Australia
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/03 23:22:18 (permalink)
    rbowser
    chuckebaby...use the key command CNTR+S for saving...

    Big +1 to that reply.  I save several times every minute, basically every time I do an edit.  I do it without thinking, but I'M in control of it, not some funky auto-save thing which can get in your way - as per your experience, jko.
     



    Same here. Whenever I am doing mouse edits, my left hand hovers near the keyboard, poised ready to hit Ctrl-S.
     
    AutoSave has never really caused any problems for me, but if it started getting in the way then I would probably disable it.

    SonarPlatinum(22.11.0.111)|Mixbus32C(4.3.19)|DigitalPerformer(9.5.1)|Reaper(5.77)
    FractalDesign:DefineR5|i7-6850k@4.1GHz|16GB@2666MHz-DDR4|MSI:GamingProCarbonX99a|Matrox:M9148(x2)|UAD2solo(6.5.2)|W7Ult-x64-SP1
    Audient:iD22+ASP800|KRK:VXT6|+various-outboard-gear|+guitars&basses, etc.
    Having fun at work lately
    #8
    jkoseattle
    Max Output Level: -79 dBFS
    • Total Posts : 556
    • Joined: 2004/10/21 16:29:48
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/04 01:13:09 (permalink)
    Yeah, I've always  the same way with Ctrl-S, it's almost like I put a period at the end of something I like. Ctrl-S is my way of saying Yesss!! to myself. It's a habit I'll probably never lose, so maybe the auto-save is unnecessary. 

    Sonar Version: Platinum  
    Audio Interface: M-Audio Delta
    Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
    Soft Synths: EastWest PLAY Symphonic Orchestra
    MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
    Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
    Check out my work here
    #9
    Steve_Karl
    Max Output Level: -50 dBFS
    • Total Posts : 2534
    • Joined: 2003/11/06 20:53:26
    • Location: Pittsburgh, PA USA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 05:00:31 (permalink)
    Yes. Auto save has never been great because it interrupts work flow when the project is large.
    It's a great idea, but I think it would need to be re coded from scratch to really get it right.
    Ideally it should run as a subtle and unnoticeable background operation that can't be seen and doesn't stop us from doing what we're doing.
    I have to have it disabled because I can't stand the interruption in my work flow.
    CTRL+S as often as possible is the safest way.

    As for version numbers as in songname_001, songname_002 etc.
    "Blender" (3d software) has a great feature that ups the version number by one ... 003, 004 etc.
    When saving ... hitting the "+" on the numbers pad changes the 004 to a 005 and on up ever new save.
    It's a very slick time saver.

    Steve Karl
    https://soundcloud.com/steve_karl
    SPLAT 2017.01
    #10
    Grem
    Max Output Level: -19.5 dBFS
    • Total Posts : 5562
    • Joined: 2005/06/28 09:26:32
    • Location: Baton Rouge Area
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 07:19:43 (permalink)
    I use auto save. I have it set ofr every 20 changes. Never had a problem. Even if you hit Ctrl+s, it's still gonna take the same amount of time to save, no matter how you save.
     
    I also use my own version system. Just in case.
     
    And even though I use auto save, I still use Ctrl+s almost after every edit!!
     
    We maybe a little paranoid. I wonder what made us that way!!

    Grem

    Michael
     
    Music PC
    i7 2600K; 64gb Ram; 3 256gb SSD, System, Samples, Audio; 1TB & 2TB Project Storage; 2TB system BkUp; RME FireFace 400; Win 10 Pro 64; CWbBL 64, 
    Home PC
    AMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 
    Surface Pro 3
    Win 10  i7 8gb RAM; CWbBL 64
    #11
    Steve_Karl
    Max Output Level: -50 dBFS
    • Total Posts : 2534
    • Joined: 2003/11/06 20:53:26
    • Location: Pittsburgh, PA USA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 07:28:28 (permalink)
    Grem
     Even if you hit Ctrl+s, it's still gonna take the same amount of time to save, no matter how you save.


    Yes. The difference being I know when that's gonna happen.



    Steve Karl
    https://soundcloud.com/steve_karl
    SPLAT 2017.01
    #12
    Splat
    Max Output Level: 0 dBFS
    • Total Posts : 8672
    • Joined: 2010/12/29 15:28:29
    • Location: Mars.
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 08:30:43 (permalink)
    +1 for Ctrl S. I also use 'save as' every time something substantial is completed (the revised filename documents what happened ).

    Sell by date at 9000 posts. Do not feed.
    @48/24 & 128 buffers latency is 367 with offset of 38.

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
    #13
    DeeringAmps
    Max Output Level: -49 dBFS
    • Total Posts : 2614
    • Joined: 2005/10/03 10:29:25
    • Location: Seattle area
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 08:50:10 (permalink)
    I find Ctrl+S cumbersome.
    I set the ` key (backtick; whatever it is with the tilde, right below the escape key) to "save" in keyboard shortcuts.
    and Ctrl+` for "save as"
    Quicker, cleaner, leaner, meaner; for me.
    I still miss the "save" icon on the toolbar, just me.
    I don't use "auto-save".
    Long time user, just getting used to "versioning".
     
    Tom
    post edited by DeeringAmps - 2014/05/07 09:34:40

    Tom Deering
    Tascam FW-1884 User Resources Page
    Firewire "Legacy" Tutorial, Service Manual, Schematic, and Service Bulletins

    Win10x64
    StudioCat Pro Studio Coffee Lake 8086k 32gb RAM

    RME UFX (Audio)
    Tascam FW-1884 (Control) in Win 10x64 Pro
    #14
    sharke
    Max Output Level: 0 dBFS
    • Total Posts : 13933
    • Joined: 2012/08/03 00:13:00
    • Location: NYC
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 10:14:52 (permalink)
    And back things up with Gobbler too. It gives you a revision history. Not as finely grained as autosave or CTRL-S'ing yourself, but at least if things truly screw up you can go back to a version from a little earlier in the day. 

    James
    Windows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
    #15
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 14:23:08 (permalink)
    There are a couple of points regarding the above posts.
     
    Firstly, autosave only ever kicks in when the transport isn't running. It won't try and save when you're playing back or recording.
     
    Secondly, I'm curious as to why a project takes 15 seconds to save. The vast majority of mine save almost instantly, and this includes projects with 50+ tracks, 15+ vsti's, V-Vocal clips, 100+ Fx plugs etc. The only project which does take longer is my orchestral template, but this is a monstro project containing 135 tracks of Midi, audio, drum maps & multiple instruments loaded form EWQLSO platinum.
     
    So... you need to work out why it's taking so long to save - maybe an idea of system specs would help as well as an idea of what your project contains.
     
    FWIW, I'm in the Ctrl + S camp. 
     
     

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #16
    Steve_Karl
    Max Output Level: -50 dBFS
    • Total Posts : 2534
    • Joined: 2003/11/06 20:53:26
    • Location: Pittsburgh, PA USA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 15:16:01 (permalink)
    Bristol_Jonesey
    There are a couple of points regarding the above posts.
     
    Firstly, autosave only ever kicks in when the transport isn't running.


    Correct. It always does it when we're into really concentrating on editing.
    That's why it's a PIA and I have it turned off.

    Steve Karl
    https://soundcloud.com/steve_karl
    SPLAT 2017.01
    #17
    mettelus
    Max Output Level: -22 dBFS
    • Total Posts : 5321
    • Joined: 2005/08/05 03:19:25
    • Location: Maryland, USA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/07 19:02:37 (permalink)
    Another ctrl-s fan. Whenever something big is performed you can strategically choose when. I also happen not to rely on undo, so when a big change goes awry I simply close and reopen the project and know where it was.

    ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
    #18
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/08 05:56:49 (permalink)
    If it's a lengthy editing session, I always start by doing a 'save as' with a different name but within the same project folder so I always have something to return to.

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #19
    Grem
    Max Output Level: -19.5 dBFS
    • Total Posts : 5562
    • Joined: 2005/06/28 09:26:32
    • Location: Baton Rouge Area
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/08 08:37:49 (permalink)
    Bristol_Jonesey
    If it's a lengthy editing session, I always start by doing a 'save as' with a different name but within the same project folder so I always have something to return to.




    Yes, I always do this when an idea strikes me that I know will lead me down a very different path. Thankfully we can have the names very long!!

    Grem

    Michael
     
    Music PC
    i7 2600K; 64gb Ram; 3 256gb SSD, System, Samples, Audio; 1TB & 2TB Project Storage; 2TB system BkUp; RME FireFace 400; Win 10 Pro 64; CWbBL 64, 
    Home PC
    AMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 
    Surface Pro 3
    Win 10  i7 8gb RAM; CWbBL 64
    #20
    rbowser
    Max Output Level: -10 dBFS
    • Total Posts : 6518
    • Joined: 2005/07/31 14:32:34
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/08 09:31:12 (permalink)
    mettelus...I also happen not to rely on undo, so when a big change goes awry I simply close and reopen the project and know where it was.



    Interesting, Mettelus - Do you work that because you don't trust undo?  Using Ctrl+S is so ingrained in me I'm barely conscious of using it, do an edit - pinky, ring finger, - -But I'm also a constant Ctrl+Z guy, relying on instantly jumping back to before an edit or two or however many I want, without having to open History - and I sure don't want to close and re-open.  Why don't you use Ctrl+Z?
     
    Randy B.

    Sonar X3e Studio
    Roland A-800 MIDI keyboard controller
    Alesis i|O2 interface
    Gigabyte Technology-AMD Phenom II @ 3 GHz
    8 Gb RAM 6 Core Windows 7 Home Premium x64
    with dual monitors
    #21
    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/08 11:09:06 (permalink)
    I never want a program deciding when i should save. Just 'Keybind the letter 'S' and hit it often. 
     
    Cj

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #22
    yoursong
    Max Output Level: -89 dBFS
    • Total Posts : 61
    • Joined: 2008/03/11 12:20:55
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/08 21:48:18 (permalink)
    Absolutely it's best practice to manually save frequently, but we all forget once in awhile or get carried away in a hot session ... so I also use Auto Save in addition to 'trying to remember' to save after every few edits.  Auto Save has saved me several times after crashes and file corruptions. I really can't do without it.  Which is why I agree with the OP, that Auto Save could use improvement.
     
    I have it set for 15 changes. It only takes 1 or 2 seconds to save most projects.  But when Auto Save keeps kicking off all the time during heavy editing ... it does interrupt my workflow and often blows up the key strokes or mouse strokes that I was launching into. After an hour of it, just seems like Auto Save is kind of fighting me. But still, got to have it. Love it / Hate it.

    Sonar user for 15 years ... Currently Sonar X3 Producer, Win 7 Pro / 64 Bit, EastWest VSTi's
    #23
    riojazz
    Max Output Level: -64 dBFS
    • Total Posts : 1337
    • Joined: 2004/02/26 13:23:02
    • Location: Mid-Hudson Valley, NY
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/08 22:01:11 (permalink)
    Tom Deering said, "I still miss the "save" icon on the toolbar, just me."
     
    - Me, too.
     

    Software: Cakewalk by Bandlab; Adobe Audition; Band-in-A-Box audiophile; Izotope Ozone; Encore; Melodyne; Win 10 Pro, 64-bit.

    Hardware: Focusrite Scarlett 18i20 2nd; Roland Integra-7; TCE Finalizer; Presonus Central Station, Behringer X-Touch.  Home built i7 with 16 GB RAM, SSDs.
    #24
    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/09 11:57:51 (permalink)
    riojazz
    Tom Deering said, "I still miss the "save" icon on the toolbar, just me."
     
    - Me, too.
     


    Just key-bind a single key on your QWERTY Keyboard. Like an 'S'

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #25
    mettelus
    Max Output Level: -22 dBFS
    • Total Posts : 5321
    • Joined: 2005/08/05 03:19:25
    • Location: Maryland, USA
    • Status: offline
    Re: Auto-Save poorly implemented 2014/05/09 12:03:18 (permalink)
    rbowser
    Interesting, Mettelus - Do you work that because you don't trust undo?  Using Ctrl+S is so ingrained in me I'm barely conscious of using it, do an edit - pinky, ring finger, - -But I'm also a constant Ctrl+Z guy, relying on instantly jumping back to before an edit or two or however many I want, without having to open History - and I sure don't want to close and re-open.  Why don't you use Ctrl+Z?

    My aversion to undo is not specific to Cakewalk in any way... I need to make sure that is clear. That function is application dependent, and I have run into software with terribly scripted undo functionality over the years. The ones which have burned me have also trained me to rarely use this feature in any program.
     
    I did not mean to imply that it doesn't work... it is just a feature I never rely on. If I save something, close and reopen, that functionality is more universal to any application.

    ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
    #26
    Jump to:
    © 2025 APG vNext Commercial Version 5.1