Rename Collision - Upon an Occurrence

MusicBrainz Picard
, , , ,
1

I’m not sure what happens currently if there is file name collision resulting from the renaming pattern, if the files are renamed on save and they’re moved to a “central repo” where it’s likely that there will be collision with existing same-name files.

Is it possible to request Picard examine the files-- as queued for renaming-- for highest bitrate, etc, so if impossible to avoid collision, an evaluation would mean only the best version of the file is kept.

Ideas?
e.g. maybe an extension/ plugin exists?

thank you!

PS. learning python, so perhaps-- and assuming your plugin system is python based-- have you a recommended …
[ EDIT - nix that. no one likes a guy in a support forum who asks too many questions]

Cheers! thank you

2

I think the standard file clash rule is a (1)(2)etc added to the newest files.

As to writing plugins, the best way is find a plugin that does something similar and start hacking around with the code. (Plugins — MusicBrainz Picard v2.12 documentation)

Install a plugin, then go look into your %AppData%\MusicBrainz\Picard\plugins folder and you’ll find a zip you can hack around with.

There are also userscripts around that rename files with [bitrate] in the filename. That should also help.

What I can’t answer is if you can ask “If duplicate filename, then rename”

1 Like