I have enough problems with crashes (I use lots of vsts and my WKP is very large) that I am always making backups. Usually after every edit.
It would be nice to keep the same name for the most current workspace, and save the backups under another name. When I do 'save as', then I start working on the wkp with the new name, so the current wkp has a different name all the time.
Better still would be to automate this somewhat, so I wouldn't have to rename all these (hopefully unnecessary) backups. Obviously I don't want a true autosave in live use (until someday when saving can run very low priority in a background thread) but a 'manual autosave', where usine would save a copy of my workspace with an incremeted number into an automatically created folder with a keyclick would be extremely helpful.
So MyWorkspace_backup01.wkp would be saved in a folder called MyWorkspace_backups
thx
-e
Save a copy AS
-
woodslanding
- Member
- Posts: 1327
- Contact:
Yes, I can ad +1 to this or any other backup possibilities. I have internal messages in complex polyphony subpatch very often while editing. the problem is that:
1. sometimes there is nothing could help under crash folder.
2. or saved workspace/patch had some not visible errors [modules parameters are changed for unknown reason] , but I didn't know before saved.
1. sometimes there is nothing could help under crash folder.
2. or saved workspace/patch had some not visible errors [modules parameters are changed for unknown reason] , but I didn't know before saved.
You're right, the backup and more generally the idea of "workspace history" is important.
Actually before a save, a wkp (or patch) is renamed into "*.wkp-old". So you can retrieve the older version.
I can extend this idea to have a longer list of backups like "*.wkp-old1", "*.wkp-old2", etc.
I'm more looking into this direction.
Actually before a save, a wkp (or patch) is renamed into "*.wkp-old". So you can retrieve the older version.
I can extend this idea to have a longer list of backups like "*.wkp-old1", "*.wkp-old2", etc.
I'm more looking into this direction.
Olivier Sens
www.brainmodular.com
www.brainmodular.com
-
woodslanding
- Member
- Posts: 1327
- Contact:
I do spend a lot of time renaming the backups, so I would prefer them in a folder.... but others might disagree.
I am also always saving versions of my wkp, and only the most recent one before closing shows up in the history list the next time.... I'd like if they were all there...
I am also always saving versions of my wkp, and only the most recent one before closing shows up in the history list the next time.... I'd like if they were all there...
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
-
woodslanding
- Member
- Posts: 1327
- Contact:
And the advantage of a 'save a copy' command over any autosave method is this:
I can name each of my backups so I can revert to the appropriate one when something goes wrong. I name every time I save, "fixedBugX", "TriedFeatureY", "fixedBugZ"
oops, fixing bug Z broke feature Y. Now I know which version to revert to.....
I can name each of my backups so I can revert to the appropriate one when something goes wrong. I name every time I save, "fixedBugX", "TriedFeatureY", "fixedBugZ"
oops, fixing bug Z broke feature Y. Now I know which version to revert to.....
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Who is online
Users browsing this forum: No registered users and 73 guests
