I have duplicate date (duplicate “YEAR” tag) on most of my audio file, in mp3tag it looks like :
2024\\2024-11-06 or 1996\\1996-06-17
When doing alt§t it show that there is two YEAR tags, so I have try action like tell to mp3tag to erase the first 4 characters, hopping it will erase the first 2024 and keep the 2024-11-06 after that, but it will erase in booth tag, and end with a date like “-11-06”
I want to get rid of the first tag, the year only, the first one, to end with “2024-11-06” only and have only one YEAR tag, not two
If I make an action “delete duplicate field”, it works, but, by default it choose to keep the first tag, and erase all the other tags (so, it erases the 2nd one, the good complete one)
So I end with “2024” only, wich you guess it, I don’t want. I want to erase the first one, and keep the complete 2nd one instead
I dunno how to do this, there is no option to chose wich one to keep and how to make it erase the bad one, and keep the good one
Please note that the data in YEAR is supposed to be a 4-digit number according to the ID3 standard.
If you want to have a field with more detailed date information, then use e.g. RELEASETIME.
To separate the data try an action of the type "Guess value"
Source string: $meta_sep(year,==)
To delete the first YEAR tag field:
Guessing pattern: %dummy%==%year%
To split the information to put more standard compliant data in each field:
Guessing pattern: %year%==%releasetime%
which will put the first tag field into YEAR and the second (longer) into RELEASETIME
With the above instructions from @ohrenkino you take your two separate YEAR field contents:
2024
and
2024-11-06
and "combine" them with a separator ==
This results in one value with the content
2024==2024-11-06
Then you choose your Guessing pattern. With %dummy%==%year%
you are sending the value on the left side of == to "nowhere" (=dummy) and keep only the value on the right side of == in the field YEAR.
Or with the Guessing pattern %year%==%releasetime%
you are keeping the value on the left side of == in the field YEAR and the value on the right side of == in the field RELEASETIME.
Oh, thx to all of you for the answers, I learn a few things there!
I doesn’t know it wasn’t standard to have the full date associated with the “YEAR” tag, I get it
So it brings me to some other questions to determinate how I will deal with this :
-what is the correct standardized tag for full date? Is it “DATE” or..?
-if there isn’t normalized standard, what are the con of having it like this? I use almost only .flac and I haven’t have problem to have the full release date in the “YEAR” tag for years, only thing is that .mp3 doesn’t retain the full tag and they cut it to 4 digits, so they use the standardized year only (it wasn’t a bug but a feature)
-I like to have the full date, so if I use antoher tag (which one?), will foobar or else will show me the full date?
I mean, for most albums the year only could be ok. But it’s really more important with single tracks, like in electronic music / techno or else, when you have a full library of thousand of single tracks, you want to know which track is a release from the beginning of the years, which is from summer etc…And I don’t want to have 2 different standards for all my music
So, except if it’s really a problem, it seem that keeping the full date in the YEAR tag is the best option there for me? I mean, doing it this way, the full date show in Traktor or Serato without any modification. I’m not sure Traktor will show me the full date with another tag used for it (that been said, I can test)
You are mixing up various areas with your questions.
There are standards. Those for FLAC and those for mp3. They are not identical.
You can fill in your date wherever you want.
As suggested the field YEAR for 4-digits and RELEASETIME for 10-characters for MP3.
The interaction with software such as Traktor or Serato is a completely different situation.
They don't always adhere to standards.
The only thing that really helps is to try it out and test it yourself.
The easiest way is to fill a sample audio track in the respective software with a date, save it and look in Mp3tag in Alt+T to see in which field your date was saved. Use this field to exchange content between different software programmes.
Yep, as I say in my case it’s a double “YEAR” tag there, the first one is the year only, the 2nd one is the full date
Probably done this way to insure compatibility in case the full date will pose a problem with a flac player or else
Never happen, once to me btw
And yes a bunch of questions there. But I think my best option is to keep the full date in the YEAR tag, this way I’m sure it will show on my smartphone or in foobar or in Traktor, now that you give me hint how to obtain what I want and erase the first YEAR tag to only keep the 2nd same tag
Once again thank you all for the information, regards
All other questions in respect to 3rd party programs (players) can only be answered by their support or by your own tests.
But as soon as you know what your player likes, then MP3tag can probably help you to get the data into the correct format and field.
Yep, I just test it with foobar and it doesn’t show by default, so I will not use it because it will be a lot of unneeded pain to have to configure every music players in every computer or smartphone to understand it correctly (if not impossible to doing it most of the time)
Foobar for desktop can be configured to show just about any tag anywhere you want it. Not the case for Foobar Mobile.
Most players only support the four digit YEAR tag. If you choose to include more details like month, day, and even time - some players will ignore them, others will possibly show nothing. Only you can know what will happen by testing in your environment. But for the widest compatibility at home and on mobile devices it is a good rule of thumb to keep it at the 4 digits. Other than a few desktop players, the extra information besides year is often ignored either way.
I know but I have several computers, sometime format them or else, I don’t want to have to spend hours to set up foobar everytime, I want something standard that work now or in 10 years
It’s like to put the synced lyrics into the “unsynced lyrics” tag even if a “synced lyrics” tab exist : it’s stupid but that’s how everyone is doing it (even mp3tag), so… that’s teh way
