I would like to remove the automatic renaming that shotgun does when we use "save as", unless there is a specific need I want my students to keep the same name and just let shotgun keep track of the versions. The automatic "1" that shotgun adds just confuses them and we end up with lots of differently named files unintentionally. Where can I change the logic for this?
6 comments
-
Benoit Leveau If you want to keep the same name, then you should use "Version Up" instead of "Save As".
But I completelty agree...Last time I saw the "1" been added, II thought it was a bug and started to search for the cause...
Benoit
-
Alan Dann Hi Guys,
There is a setting you can change for this...
In the tk-multi-workfiles app configuration for the engine you are using in the various environment .yml's, look for the saveas_prefer_version_up setting and change it to True.
Now when you run Shotgun Save-As you'll find it prompts to version-up the file rather than incrementing the numerical suffix.
Is that what you were after?
Thanks
Alan
-
Benoit Leveau Hi Alan,
It sounds exactly like it! I completely forgot about that option... I think the renaming is especially confusing when you have a suffix that uses numbers, like "shot10_comp_testh264.v002.nk" for instance and you open the save as dialog and it shows up as shot10_comp_testh265....
Thanks,
Benoit
-
Steven Quinones Great tip. Thanks!
-
Steven Quinones I tried this:
saveas_prefer_version_up:
type: bool
description: Control how the save-as command determines the inital name to be used. If
set to True then the name from the current scene will be used and the version
incremented. If False then a new unique name will be used and the version
reset
default_value: TrueBut I get the same behavior. Shotgun reports in active apps I'm using:
Manage your Work files
Version: v0.4.6
I'm editing:
Z:\software\shotgun\studio\install\apps\app_store\tk-multi-workfiles\v0.4.6\info.yml
Am I in the correct place?
-
Alan Dann Hi Steven,
Sorry, I should have been more specific!
You should be editing your environment configuration file(s). Typically these can be found in your configuration root, for example the environment used when working on a Task for a Shot can be found here:
<project/pipeline configuration root>/config/env/shot_step.yml
Then within that environment file, look for:
engines:
...
tk-maya:
apps:
...
tk-multi-workfiles:
...
saveas_prefer_version_up: False <------ Change this
Does that make sense?
Thanks
Alan