-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
import using pre-existing musicbrainz tags #1919
Comments
Yes, beets uses the existing metadata, including IDs in the files' tags. You can also use |
Good. What made me wonder is that the process for importing already picard-tagged folders with multiple CD (cd1, cd2 or disc1, disc2) seem way more complicated than I would expect. Lots of questions gets asked, while since the ID are already there I would expect no questions.. |
Beets still needs a way to decide which songs are part of each album (described in the autotagging guide). If something specific seems wrong, could you provide an example (along with what you expected to happen)? |
this is it. As each file is tagged with the musicbrainz release id/release group id, why does beets need to decide anything? |
Did you mean to paste example output here? Beets' importer balances the signal from the ID with other signals, like the track titles. If they don't line up perfectly, it asks you questions. |
OK, import log following.. |
Before pasting the log, let me ask one more question. |
Please search the docs for |
will do right away |
ok, seen that: |
The FAQ will help with that. |
And here is the log. With per_disc_numbering it's tidier, still my guess is that the questions do not come from a real difference but from different defaults from picard.
|
it seems beets is complaing about "(tracks)", because it manages the tracks in multiple cds in a different way. Is that correct? |
Yep. Looks like beets is tagging this automatically, without user intervention, except for the duplicate detector (which is not related to metadata matches). Is there still a problem? |
That's just indicating that the tracks' tags don't have a disc number, but beets wants to add one. |
I think we are mostly fine. Poker Face (#4) -> Poker Face (#2-4) (id) How can that be? |
That's indicating that there's an ID mismatch. Maybe you can dig in a little further and investigate why (which IDs didn't match). |
What else can I do for investigating? |
Gees, there it is. A different recording ID.. |
Amazing. In Picard the two files are exactly the same. Looks like it botches writing the tag in the file.. |
That'd do it, certainly! |
OK, got the multidisc configuration right. One last thing, is there a way for disc numbers to go from 1 to 9 instead of 01 to 09? |
One hacky way is to use the |
Or adapt this example from the inline plugin page :
Right? I have been meaning for more than a year to adopt beets for managing my music library. Now that I started really doing it, it's performing the way I hoped. Thanks a real lot. |
Yep! Glad things are working for you. |
My audio files are pre-tagged using Picard.
When importing these files, does beets take into consideration the pre-existing musicbrainz metadata?
Basically I find musicbrainz very useful for managing the initial matching in a gui oriented way, but once the relationship is established i prefer the batch oriented beets way.
The text was updated successfully, but these errors were encountered: