bitflipper
Slugbaby
I've had this happen before.
For me, (after a crash) if I try to re-open the project from the "recently opened projects" list under FILE, i get the not-updated project. However, if I select OPEN and go to the project file itself, it opens the most-recently saved version (can be validated by finding the 'modified date' field).
Seems to be related to the link in the dropdown not getting a chance to update itself due to the crash.
^^^This. Updating the Recent Files entry in the registry is apparently one of the last things SONAR does before it shuts down. Consequently, if you crash while working on a new project it won't show up on the list, even though it's intact on disk. I don't use versioning, but I would imagine the same principle applies.
These message are key above. If you're clicking 'save' every few seconds, those saves are committed to disk and you should be able to retrieve them. Versioning or using 'save as' is fine, but using 'save' is just as reliable.
As above, the latest version may not be listed in Sonar's drop down box after abnormal app termination, so you may have to open the latest version manually by checking the 'modified' file date and time.
The only exceptions to this I can think of are if Sonar crashes while you're clicking save, if you're clicking save while audio is still currently rendering or if Sonar has become unstable to the point where a "save" operation isn't completing and a few seconds later, you realize the app has crashed. But whether you're using "save as" or "save" in those circumstances, I think you'd still have issues.