jo,
i was inspired by a post you made about timeline/history of MuLab where you mentioned that you had a major redo of the architecture of the Undo/Redo system
would it be possible/easy to revert to a previous state of a project?
sometimes, i'm working on a song and find the route/path i'm in not really rewarding and would like to start again, from a few weeks or months back
of course, i don't make several/different saves of my project, so the only possibility i see to go back in time is to undo what i did
practically i can't press ctrl+Z 'indefinitely', so it would be much more practical if i could choose from a 'target list' that lists (at least dates) of previously saved iterations
would this be something that could be made to work?
(premise that no samples were destroyed/deleted in the process , or no audio streams were permanently altered in a destructive way of course)
FR: return to previous state of project // The Unlimited Undo Orchestra
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
I think you can easily get that by simply saving your project regularly using a different date appendixes:
MyProject-20250817.MuProject
MyProject-20250829.MuProject
MyProject-20250915.MuProject
MyProject-20251022.MuProject
MyProject-20251130.MuProject
...
MyProject-20250817.MuProject
MyProject-20250829.MuProject
MyProject-20250915.MuProject
MyProject-20251022.MuProject
MyProject-20251130.MuProject
...
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Maybe there could be an option to take a sequentially numbered backup every N-th history entry, with the history stored from the previous backup to that point along with the project? The problem generally comes in midst of a creative flow -- when you don't even think "I should take backups" -- you realise you had the idea a little while back and now it's ruined...
-
- KVRist
- Topic Starter
- 185 posts since 10 Dec, 2007 from A'pen
agree
i'm a little afraid of doing auto or manual save as - as i'm afraid these will create a lot of overhead on my system (of double samples/streams etc) whereas a list would be consequent (my naming is not always that) and easy (to choose from)
i'm a little afraid of doing auto or manual save as - as i'm afraid these will create a lot of overhead on my system (of double samples/streams etc) whereas a list would be consequent (my naming is not always that) and easy (to choose from)
