There are a few ways to do it. The Naming Scheme in WaveLab is GREAT but I don’t use it for file version naming because then I would have double, triple, or quadruple the number of Naming Scheme and/or Render Presets.
One for each option, and then multiplied by each one to add V2, V3, V4, etc. Too many. It’s almost as if WaveLab needs an additional Naming Scheme suffix to add on to the main Naming Scheme.
For now, I use an app called A Better Finder Rename which is useful for many other things too.
I’ve made presets in the A Better Finder Rename to add _V2, _V3, _V4 to the end of a file name and then if I simply right click on a file or files in Path Finder (alternate/better Mac Finder app), I can apply that preset right to the file names without opening another app. It’s super fast.
I’ve found this to be the best and fastest option. I also have the V number in the folder name that the files live in but in some cases (especially during the approval process), it can be helpful to have the V number in the file name too.
Yeah, I mean the V1, V2, V3 thing is possible with the naming scheme now but to add on the V# in addition to your desired main naming scheme means you’ll have 4x the number of naming schemes if you take the time to program it up to version 4 which in my opinion is too many.
We almost need a Naming Scheme #2 field to add something on to the main Naming Scheme.
For me, it takes about 2 seconds to right click the file name(s) and have A Better Finder Rename add it so I haven’t really searched for another solution as it’s not really been in my way.
I think that with the way different people do versioning, the “filter” concept could get complex.
Maybe you’ve thought of that. But, off the top of my head and ITT, you’ve got
v1, v2, v3 as the last 2 characters
v1_, v1, v2_, v2, … as the last 2-3 characters (JP’s sentinel for with plugins or printed)
R01, R02, … as the last 3 characters for AES spec.
2-3 characters for versioning plus “final” and often “final-FINAL-ReallyFinal” for people who aren’t as…“obstinate” about naming as some of us.
ISO8601 datestamps (I use it because I’m a dork, but for project folders based on start date)
I’m not sure if this is actually a good idea or not…but it almost makes sense to me to have a second drop down to the right of “naming scheme” for versioning…that forces people to use a specific format.
So…just throwing it out there. I think I might end up preferring doing it manually unless you, PG, come up with a completely automatic versioning convention that actually captures everything I personally want…which is basically Justin’s version with the sentinel at the end…but I don’t care whether it’s v#, V#, R##, etc…
Right. Thanks to A Better Finder Rename, this hasn’t really been a pain point for me.
A bigger pain point or feature I’d be into is bulk Clip Replacement in the Montage. Something that can find new files that have _RX or [Instrumental] in the file name and replace them all at once instead of one by one.
Anyway, getting off topic. This would be a welcomed feature, it just wasn’t as high on my list as other things.
Everyone has to use a system that works for them, but we use date codes instead of “V1”, etc. Makes it far, far easier to cross-reference between client emails, file timestamps. our project management system, etc.
Also prevents a lot of files like “V3 FINAL”, “V4 NO REALLY FINAL”, “V5 I SWEAR THIS IS FINAL” lol.