Keep losing work (solved!)
Posted: Mon Jul 12, 2021 10:44 am
I keep hitting a problem where plugins crash and I have no route back to an earlier state. Things came to a head yesterday where a Synthmaster 2 crash took out all 6 instances and a later crash took out all 6 Atom 2 instances. In the Synthmaster case the annoyance was that I could not remember which presets I had been using for each track but I had an earlier export from which I managed to get this information. In the Atom 2 case however I lost a few hours of work as I had not been exporting (my fault).
I expect plugins to crash every now and then, that’s no fault of MTS and business as usual, but unless I constantly export my project then I have no way back to the data I was working on. The autosave is great when everything is working but when a plugin crashes then I cannot see any way of getting back to what I was working on 5 minutes ago as the autosave also saves the fact that the plugins all need to be reloaded. I had hoped that quickly shutting down the app would avoid an autosave but I assume a save occurs when you background the process.
Is there a way around this other than constantly exporting the project, or saving the individual state of each plugin manually? I would not mind the need to regularly save as I certainly accept that the onus is on me to do so but I need 6 taps each time I want to export a known good state which means it does not get done very often compared to apps with a save button on the main screen.
Are any of these feasible, or are there some better existing options?
* Maintain a selectable rotating list of autosaves (for me, the ideal solution)
* The plugin Reload dialog that appears after a crash offers the alternative option of reloading an earlier saved state *for that plugin*. The current behaviour is to reload it to its default state, thus losing presets and any user data which might have been created inside the plugin.
* Reduce the number of taps (ideally to 1 or 2) to export/save a project after it has been exported the first time.
Thanks.
I expect plugins to crash every now and then, that’s no fault of MTS and business as usual, but unless I constantly export my project then I have no way back to the data I was working on. The autosave is great when everything is working but when a plugin crashes then I cannot see any way of getting back to what I was working on 5 minutes ago as the autosave also saves the fact that the plugins all need to be reloaded. I had hoped that quickly shutting down the app would avoid an autosave but I assume a save occurs when you background the process.
Is there a way around this other than constantly exporting the project, or saving the individual state of each plugin manually? I would not mind the need to regularly save as I certainly accept that the onus is on me to do so but I need 6 taps each time I want to export a known good state which means it does not get done very often compared to apps with a save button on the main screen.
Are any of these feasible, or are there some better existing options?
* Maintain a selectable rotating list of autosaves (for me, the ideal solution)
* The plugin Reload dialog that appears after a crash offers the alternative option of reloading an earlier saved state *for that plugin*. The current behaviour is to reload it to its default state, thus losing presets and any user data which might have been created inside the plugin.
* Reduce the number of taps (ideally to 1 or 2) to export/save a project after it has been exported the first time.
Thanks.