![]() with values such as official, single and US). with values such as 81cba7a1-222e-4901-b5c8-134ddd4e85aa), but instead they are just like other tags (e.g. What is interesting about these 3 tags is that they aren't really identifiers like the other MusicBrainz tags (e.g. According to the source mentioned, they should be mapped to RELEASESTATUS, RELEASETYPE and RELEASECOUNTRY respectively. The tags are MUSICBRAINZ_ALBUMSTATUS, MUSICBRAINZ_ALBUMTYPE and MUSICBRAINZ_ALBUMRELEASECOUNTRY. ![]() I have checked all of MusicBrainz tags for ID3 and Vorbis and I have found out that 3 tags do not match the Vorbis mapping according to MusicBrainz documentation in Appendix B: Tag Mapping - MusicBrainz Picard v2.6 documentation. The second issue is regarding the tag mapping. Could you please take a look and check if it should be added as well? I had a suspicion that the duplicate ACOUSTID_ID was actually supposed to be the ACOUSTID_FINGERPRINT, however I probably didn't make myself clear enough when reporting it at the time. I have found my old report in Two issues with Extended Tags - #7 by Florian where I have encountered a bug with two ACOUSTID_ID fields where you have chosen to remove the duplicate one. ![]() According to your post in Add mappings for more MusicBrainz tags - #12 by Florian it should be present in Extended tags alongside ACOUSTID_ID, however only the latter one is there. The first one is regarding the tag ACOUSTID_FINGERPRINT. ![]() I have found some some minor issues in regards to MusicBrainz tags so I am letting you know. Thank you for your continuous work on Mp3Tag. Its usually best to merge duplicate entities (releases, release groups, recordings, etc.) instead of deleting them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |