Date tag should be date tag?year tag?

Tags: #<Tag:0x00007f6d42ca9610> #<Tag:0x00007f6d42ca9548> #<Tag:0x00007f6d42ca9480> #<Tag:0x00007f6d42ca93b8>

The date tag in MusicBrainz should be a date(YYYY-MM-DD), but in a more general case, like ID3v1, it simply means year(YYYY). So the problem came when I edited and save the music tag using MusicBrainz online database, the date tag will be a date, which my phone and other device couldn’t recognized. My phone regards the date tag in MusicBrainz as the value of year.

I don’t know the standards and I don’t konw which one is right. But this small thing confused me a lot.

Please see Appendix B: Tag Mapping — MusicBrainz Picard v2.7.1 documentation for how the date tag gets stored.

For ID3v2.3 there are two separate tags, one that holds the year (TYER), and one that holds month + day (TDAT). So probably your phone is just reading the TYER field.

For ID3v1 it would indeed only be a year, but I doubt your phone uses this, or if it does only as a fallback in case the ID3v2 tag has no data.

But even if you have ID3v2.4, which has a single field for the whole date, it can still be that a player decides to only display the year.


Thank you!! I fell much better when I try to get a closer look in these tags. To be honest, they are awfully complex to be truly understood.

“Standards” means everyone reads it in their own way. Issues like this are down to different players reading different standards. My Android devices also get fussy about track numbers on multi-CD releases.

When I am going to copy music to my phone, I fix stuff like this by copying files to separate folder first.
I can then hit them with MP3TAG to bulk adjust misbehaving tags.

That way I have correct files in my library, but tweaked files compliant to the various apps on those devices.

1 Like

For many years, a lot of music players (on phones etc. and Windows) only recognised id3v2.3 tags.

These days recognition of ID3v2.4 tags is better, so it is more likely that your phone will recognise the full date if you use v2.4 rather than v2.3.