Re: Batch Renaming Bug...
 

I totally agree, and that's what I've been doing. I was just trying to illustrate a real world use case.

Re: Batch Renaming Bug...
 

Those use cases totally make sense. I was thinking of it just automatically do it. Some of the other respondents mentioned making a tick box or something.

I can understand batch naming filenames as a reasonable workflow and the current implementation as described above as "incomplete".

That makes sense, I can agree an option to rename filenames as clips, such as automatically when there is 1:1 clip and file association. My initial feedback on the topic was trying to ask about what to do when there were 2:3 or 3:2 files and clips, or whatever. I didn't think it was a bug, but as incomplete to user needs, I see that too.

Re: Batch Renaming Bug...
 

+1 on a tick box to name clips and disk file names.

Re: Batch Renaming Bug...
 

Yeah, it's totally simple to understand.

Two clips with different audio files can have the same name:

Batch rename would try to call the one audio file by one name then the other audio file by the same name.

Since that simple simple case would throw an "ERROR" and a partial job is not right. No one is answering my question of what it should do. Y'all just say "yeah but it should do it" without explaining the obvious trouble with deciding default behaviour.

How many warnings do I need and errors when I want batch rename to just work perfectly like it does now.... batch export is so, so simple.

Therefore,

Command+A
Command+Shift+K

is your friend.