Posted
Hi,
I just lost my days work in a crash. I should have saved.
Would it be possible to implement a crash recovery feature to prevent this from happening? A few of the graphics programs I use have this implemented perfectly; I never lose anything despite the fact that they crash all of the time.
EDIT: I can see there is a backup system. It didn't save a backup for three hours which sort of defeats the point. Whats the skinny with this?
Here is what windows spit out.
Problem signature:
Problem Event Name: APPCRASH
Application Name: SynfirePro.exe
Application Version: 1.1.2.0
Application Timestamp: 4a5ce4b9
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 03d684bb
OS Version: 6.1.7137.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Sat, 2009-08-01 - 22:34 Permalink
An auto-save feature that makes a backup every 10 minutes would be great. Andre said we will probably be using folders (bundles) instead of flat files in the future anyway. That will simplify keeping track of backups and project snapshots and other nice things (bundled private devices!). The Mac supports bundles natively, but on Windows each document will then appear as a directory or zip.
Sun, 2009-12-06 - 09:40 Permalink
An auto-save feature that makes a backup every 10 minutes would be great. Andre said we will probably be using folders (bundles) instead of flat files in the future anyway. That will simplify keeping track of backups and project snapshots and other nice things (bundled private devices!). The Mac supports bundles natively, but on Windows each document will then appear as a directory or zip.
This approach should be rethought. It has been almost FIVE months. If this is not a simple problem, I would like to know why.
The backup system has ALWAYS failed me. Just now I lost an hours worth of work to a crash. The backups are always hours old. On this arrangement the most recent was two and a half hours old.
I don't care about any of that zips, snapshots or any of that in anyway. I would greatly appreciate a dead simple, reliable, 10 minute backup.
Thu, 2011-02-03 - 12:41 Permalink
Yes,
I agree. I am so used to working on projects where they back up all the time automatically that I plain forgot with Synfire. it locked up and didn't let me save and I lost all my work. Annoying as there was something pretty good there as well.
Is this going to appear soon? Why not have it autosave in the background when you stop playback? I can save in other applications when I am doing other things such as playback. if the conde wont allow that how about background save whilst editing not playback...
Anything would be good really...
Thu, 2011-02-03 - 14:26 Permalink
Why not have it autosave in the background when you stop playback?
This is our current approach and it seems to work well. The document and user interface however needs to be locked until the save is complete. During these few seconds, nothing must be touched or the document will become corrupted. We changed the internal document handling to enforce this.
Fri, 2011-02-04 - 00:13 Permalink
Why not add a option to have a big dumb pop up window come up and remind us to save at an interval as a stop gap until the next update?
Similarly an option to confirm canceling out of a phrase editor -- another swamp where endless work is lost due to a single accidental click.
I can't imagine that these can take long to implement. The neglect of these issues has literally cost me thousands of dollars in lost time and endless frustruation in the years that they have been ignored.
Fri, 2011-02-04 - 11:01 Permalink
macpro for me.
I have also found that the auto save option doesn't work.
If it freezes (which it has done a few times) then no saved document.
Fri, 2011-02-04 - 14:12 Permalink
@tokyorose:
Concerning the phrase editor, I would rather see those OK/Cancel buttons disappear altogether. Having a local undo stack per window is complicating things too much, with little or no extra benefit. My plan is to push all edits to the global undo stack exclusively. Closing an editor will then have no effect on the project anymore, unless one subsequently invokes undo. There will be no difference whether you invoke undo from the editor's menu or the arrangement's menu. They all refer to the same edit history.
As we are at it, what would you think about milestones? I could think of a feature that marks the current state of the project as a milestone, and later on one can return to that milestone in one big combined undo.
@sprekht:
The occiasional lockups happen on both Mac and PC.
@TWINSTATES:
The auto-backup feature does not yet exist. We will add it with the next update.
Sat, 2011-02-05 - 00:54 Permalink
I managed to eliminate the window-local undo stacks today. This means there will be no more confusion as to OK or Cancel with phrase and progression editors that were spawned off an arrangement window. The arrange window now keeps the undo stack for all of them. Opening or closing additional editors has no effect on the edit history anymore. They are just different views to the project (AR1151).