Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Picard settings migrator #1352

Open
fooness opened this issue Mar 10, 2015 · 3 comments
Open

Picard settings migrator #1352

fooness opened this issue Mar 10, 2015 · 3 comments
Labels
feature features we would like to implement good first issue https://github.com/beetbox/beets/pull/5479

Comments

@fooness
Copy link

fooness commented Mar 10, 2015

Anyone knows an automatic and easy way for migrating MusicBrainz Picard settings (especially file naming, tagging and scripting) to Beets?

The settings I talk about above are named: file_naming_format, tagger_script, ignore_tags, windows_compatible_filenames, ascii_filenames, clear_existing_tags, id3v2_encoding.

I think(!) most other settings aren’t that important.

Here’s an example configuration of Picard: http://lpaste.net/124392

@sampsyo sampsyo added the needinfo We need more details or follow-up from the filer before this can be tagged "bug" or "feature." label Mar 12, 2015
@sampsyo
Copy link
Member

sampsyo commented Mar 12, 2015

There's no current automatic migrator. If you describe exactly how these could be mapped, though, maybe someone could be enticed to work on one!

@fooness
Copy link
Author

fooness commented Mar 12, 2015

At first, it seems Beets needs to have the ability to replace text and symbols in tags (also when using the autotagger). Like in the style of the 'replace' config option. Here's a great post about how this could be possible. #488 (comment)

I’m not sure if that’s already clear, but it’s important that you can use those replace-patterns just for one (or some) tag fields.

In my picard config e.g. I’m replacing 'remix' with 'Remix' in ONLY album- and title-tags:

$set(album,$rreplace(%album%,\\bremix,Remix))
$set(title,$rreplace(%title%,\\bremix,Remix))

But not just titlecasing it, also:

$set(album,$rreplace(%album%,\\bRe-mix,Remix))
$set(title,$rreplace(%title%,\\bRe-mix,Remix))

$set(album,$rreplace(%album%,\\bRMX,Remix))
$set(title,$rreplace(%title%,\\bRMX,Remix))

[…]

Also, I’m able to set how much characters the date should have (I want four characters to be displayed):

$set(date,$left(%date%,4))

Furthermore, Beets needs to support unsetting/ignoring/deleting of tags, as I don't want all those MusicBrainz tags in my audio files:

$set(artistsort,$unset(%artistsort%))
$set(albumartistsort,$unset(%albumartistsort%))
$set(arranger,$unset(%arranger%))
$set(asin,$unset(%asin%))
$set(barcode,$unset(%barcode%))
$set(catalognumber,$unset(%catalognumber%))
$set(composer,$unset(%composer%))
$set(conductor,$unset(%conductor%))
$set(discsubtitle,$unset(%discsubtitle%))
$set(djmixer,$unset(%djmixer%))
$set(engineer,$unset(%engineer%))
$set(isrc,$unset(%isrc%))
$set(label,$unset(%label%))
$set(language,$unset(%language%))
$set(license,$unset(%license%))
$set(lyricist,$unset(%lyricist%))
$set(media,$unset(%media%))
$set(mixer,$unset(%mixer%))
$set(originaldate,$unset(%originaldate%))
$set(performer,$unset(%performer%))
$set(producer,$unset(%producer%))
$set(releasecountry,$unset(%releasecountry%))
$set(releasestatus,$unset(%releasestatus%))
$set(remixer,$unset(%remixer%))
$set(script,$unset(%script%))
$set(_recordingcomment,$unset(%_recordingcomment%))
$set(_releasecomment,$unset(%_releasecomment%))

PS: Sorry but I don't know any Python and I also don't know what you mean with mapped …

@sampsyo
Copy link
Member

sampsyo commented Mar 12, 2015

Thanks for the extra background. I'll mark this a feature request in case anyone would like to implement a Picard-compatible parser.

@sampsyo sampsyo changed the title migrating MusicBrainz Picard settings to Beets Picard settings migrator Mar 12, 2015
@sampsyo sampsyo added feature features we would like to implement and removed needinfo We need more details or follow-up from the filer before this can be tagged "bug" or "feature." labels Mar 12, 2015
@brunal brunal added the good first issue https://github.com/beetbox/beets/pull/5479 label Apr 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature features we would like to implement good first issue https://github.com/beetbox/beets/pull/5479
Projects
None yet
Development

No branches or pull requests

3 participants