Do you mean "Reverse Active Layer" from the Layer menu.

Filip, a month ago

Isn't pressing the UNDO button the same as "reverting to a previously saved baseline"?

outerspace-software.com...

michiel, a month ago

A baseline establishes a named design (show) to which you can return, or from which you can branch/fork for different alternatives. Undo doesn't do that.

colint, a month ago

Why not just save all files in a show folder. You can put the folder anywhere you want and pull it up anytime. You can also add into other shows you're working on if so desired.

Decentralized, a month ago

I googled on "VEGAS incremental save" and ended up in an "incremental save", "auto save" and even an "incremental auto save" rabbit hole of lengthy incomprehensible tutorial vids. Strangely enough, the VEGAS Pro 16 help document has no topics on "incremental", so I'm still puzzled by this concept.

Isn't it as simple as automatically saving your project under a new filename every time you manually hit save?

How do you turn this on in VEGAS?

michiel, a month ago

I read this :

Vegas 21 has a feature to do incremental saves, meaning it will create new save files every time you save

So it seems it's only since version 21, I wonder what it does when autosave is active.

vincent, a month ago

Thank you for your contributions and replies.

Yes, putting all show files in a folder is exactly what I do. In fact, the folder name is the show/project name and my show names are just 1.bt, 2.bt, etc within that folder as I go along developing the show.

"google.... Vegas.... incremental save".... rabbit hole..." I know what you mean Michiel! 😳😁 It's just that I find myself using incremental save as I go along developing a project in Vegas, firstly saving a baseline that I'm happy with, then incrementally saving as I make changes until I decide to save the next baseline. If I mess something up or later realise a change has had an unintended consequence I can go back to a known previous baseline and start from there again. It also allows me to more easily branch/fork a show for different variants.

"...automatically saving your project under a new name every time you manually hit save?" Yes, manually saving as you describe Michiel is exactly what I do at the moment. The "Incremental save" feature achieves that with fewer clicks and less risk of user error, hence the suggestion 😊

Incremental save doesn't need to be enabled as far as I'm aware. It's just under the "File" menu with "Save" and "Save as".

Autosave is something completely different for a different purpose. The concept of incremental autosave is beyond my comprehension! 😁

colint, a month ago

I suppose you end up with tons of files named like this:
MyTestProject_1.bt
MyTestProject_2.bt
MyTestProject_3.bt
MyTestProject_4.bt
MyTestProject_5.bt
MyTestProject_6.bt
MyTestProject_7.bt
MyTestProject_8.bt
MyTestProject_9.bt
MyTestProject_10.bt
MyTestProject_11.bt
MyTestProject_12.bt
MyTestProject_13.bt
MyTestProject_14.bt
MyTestProject_15.bt
MyTestProject_16.bt
MyTestProject_17.bt
MyTestProject_18.bt
...

Because the filenames are meaningless you have to open them all to find the one you are looking for?

Isn't is easier to save normally at crucial moments using a descriptive filename? Something like this:
MyTestProject_FunkyCamera.bt
MyTestProject_SpookyLighting.bt
MyTestProject_GoofyFont.bt
MyTestProject_TrendyColours.bt
MyTestProject_JumpingTexts.bt

michiel, a month ago

Yes, you _could_ end up with that! 😁

I end up with (in Vegas), for example

MyTestProject\FunkyCamera\1.veg
MyTestProject\FunkyCamera\1_(0001).veg
MyTestProject\FunkyCamera\1_(0002).veg
MyTestProject\FunkyCamera\1_(0003).veg
MyTestProject\FunkyCamera\2.veg
MyTestProject\FunkyCamera\2_(0001).veg
MyTestProject\FunkyCamera\2_(0002).veg
MyTestProject\FunkyCamera\3.veg
MyTestProject\SpookyLighting\1.veg
MyTestProject\SpookyLighting\1_(0001).veg
MyTestProject\SpookyLighting\2.veg
.
.
.
etc

I know what's in each because they are in the appropriately named project folder and I know which are the (happy) baselines and which are the (temperamental) incremental saves 😊

colint, a month ago

Colint, I've added your feature request as follows:

Incremental save: press <Alt> S to save the current show under a new unique name. For example, MyProject.bt is saved as MyProject_1.bt. And MyProject_1.bt is saved as MyProject_2.bt.

Thank you for your request!

michiel, a month ago

Wow! That's great! 😁 Thank you very much Michiel.

May I also request that if the destination file (MyProject_2.bt in your example) already exists, the destination file becomes MyProject_2_1.bt, etc to indicate a branch/fork has occurred at that point please? Thank you again.

Do you have a date when the change will be implemented?

colint, a month ago

Isn't it better to rename MyProject_2.bt to MyProject_3.bt?

michiel, a month ago

Ideally not. What if MyProject_3.bt already exists too? And MyProject_4.bt, MyProject_5.bt and MyProject_6.bt, etc as well? (i.e. the main development trunk).

Ideally the tree would look like:
MyProject.bt
MyProject_1.bt
MyProject_2.bt
MyProject_3.bt
MyProject_3_1.bt <- branch/fork occurs here because MyProject_4.bt already exists
MyProject_3_2.bt
MyProject_4.bt
MyProject_5.bt
^^ main trunk

colint, a month ago

(MyProject_4.bt already exists because you've back-tracked to re-use a previous version to create a different variant).

colint, a month ago

Branches? Forks? We have to prevent we end up building our own version control system. This is of course a solved problem, crucial for software development, and already perfectly implemented by apps like GitHub. A COMMIT TO GIT button will probably give you all the functionality you're asking for. But isn't that a bit over the top for an app that tries to stay short and simple?

michiel, a month ago

A tree with version numbers, MyProject_1_1_3_2_4_1_4.bt i prefer use save as and give an explicit name when i want to keep an intermediate step especially since in general these intermediate versions end up forgotten.

vincent, a month ago

michiel
Totally agree. There's no intention to burden and bloat BT with functionality that is perfectly implemented elsewhere. Of course not. BT is a great app as we all know and love. Just using appropriate terminology to illustrate an example with the aim of influencing the design of the new feature in the case where the destination file already exists. Rather than overwriting the existing file causing data loss, simply appending _1 until uniqueness occurs seems a straight forward solution that avoids data loss and brings the benefit of identifying it as a "branch" (i.e. an alternative from a common point) for free. That's all.

colint, a month ago

vincent
Also totally agree. To be honest, I rarely get past _3 (never more than _4!) before creating a new baseline using "Save as" with a meaningful name. Otherwise you end up with a long linear sequence _1, _2, ... _18, etc of unknown state and function which completely defeats the object of the exercise of course. Also the example of MyProject_1_1_3_2_4_1_4 is equally baffling and useless. That's certainly not the intention. Incremental saves are intended to simply be short, convenient sequences of stepping stones to the next baseline, that's all. They can be easily identified by their names and safely deleted afterwards.

colint, a month ago

Thank you for your replies and contributions. Great, responsive community 😊

colint, a month ago

Wow very complicated. Why would you save all your versions. The next version is the best and last.

Filip, a month ago

Incremental save is implemented in version 16.6.1:

outerspace-software.com...

michiel, a month ago

Great

Filip, a month ago

Thank you Michiel.

colint, a month ago

Previous articleNext articleCommunity home