Batch Clip Rename not renaming audio files - just clips PT 2018-3

[MixerGuy]

Woah - hold on - just discovered a potentially huge issue...

Batch Clip Rename is not renaming audio files - just clips - in PT 2018-3. Mac. Sierra.

and AFAICS there is not an option / preference anywhere.... unless I have missed it.

I print mixes all in one PT mix rig, and this is a huge problem if I print stem mixes plus full mixes, all in one pass, then use Batch Clip Rename in PT to rename my mixes.... i DO want it to rename both clips and audio files.

as of right now - it is not renaming audio files. Just checked.

thoughts?

thanks.

[kkfaudio]

Yep, that’s how it works..
My process is batch rename the clips, and then select all of them and hit regular rename, and keep hitting “enter” to rename the actual file..

I’d love to see a preference to do the whole file...

[MixerGuy]

Originally Posted by kkfaudio

Yep, that’s how it works..
My process is batch rename the clips, and then select all of them and hit regular rename, and keep hitting “enter” to rename the actual file..

I’d love to see a preference to do the whole file...

That is completely crazy (and nuts) that it isn't a preference or a tick box to have it rename the actual audio files as well.





thanks .

[MixerGuy]

Does anyone else want this to be a preference or a tick box?

[Drew Mazurek]

The issue I see is that since sessions can share the same files, even across networked storage, one user changing file names could wreak havoc in a multi room facility with sound FX libraries etc.

[its2loud]

There’s an easy workaround if you’re delivering individual audio files. Just export the clips as .wavs and they’ll carry the name of the clip, not the actual file name.

[BScout]

That “issue” should be left to the user. (Like file naming in the first place) I too believe it should be an option and find that it being missing annoying. I understand they were really pitching this to game audio developers where there’s a workflow of clip rename and export but for a lot of us, this restriction slows down the effectiveness of this “time saver”. It also doesn’t help that advancing to the next clip with multi-clip/file rename has gotten slower — which has been the workaround to commit batch clip renames to file names.

I also understand that the lack is because of mixed highlighting/renaming could result in some clip renames and some file renames which could be confusing. Still find that Avid should trust the user.

As for networked/shared SFX libraries, I have no idea of a facility that has libraries like this for multiseats who do not enforce that a local copy/transfer path has to be used — for some very obvious reasons. It would be extremely short-sighted if such a facility exists.

[rpalagy]

Without a doubt we need a checkbox to allow us to rename actual files. Leave it up to the user.

[cwsand]

Originally Posted by rpalagy

Without a doubt we need a checkbox to allow us to rename actual files. Leave it up to the user.

I agree.

[BScout]

This really is one of the big annoyances.

I'll go through 300+files a week of renaming that I have to do the two steps of batch rename and then rename again just to make it transfer to the file name.

And the "committing" step is so slow because Pro Tools can't keep up with just hitting "Return" to go to the next file.