Original date field is not deleted if the tag is deleted externally. [#21759]

[Dynamic990]

Hi everyone,

I am currently using the latest build of the MMW beta version. For some time now I have noticed that the "Original Date" field is not emptied when the corresponding tag is deleted by an external tagger (e.g. MP3Tag) and the files are rescanned into the database again.

To replicate the problem, proceed as follows:

• There are .mp3 audio files in the database for which the "Original Date" field is filled and the corresponding tags are present.

• Delete the tags from the .mp3 files using an external tagger. In the case of the MP3tag software, the field is called "ORIGYEAR".

• Rescan the files in MMW.

• Check the files in MMW. The "Original Date" field is still filled and not emptied as one would expect. MMW even writes the corresponding tags back to the music files again.

This only affects the "Original Date" field. The "Date" field does not show this behaviour. Here the content is deleted correctly if you proceed as described above.

My files are tagged in ID3v2.4 format only and the relevant frame in this case is called TDOR I think.

Unfortunately, I can't say exactly when this problem started. However, I am thinking that this was not the case in earlier versions. But I'm not sure.

Best regards
Christian

[tmf]

Not sure this will help, but might if it's a mapping issue?

How to Configure which ID3 Tags are used for Year / Date in MMW: https://www.mediamonkey.com/support/kno ... year-date/

Haven't tried any of this myself, but I have had some problems with ID3 2.4 tags in the past. Went back to using only ID3 2.3 tags a long time ago. I also use the Original Date field in MMW, usually Year only though.

[Lowlander]

but might if it's a mapping issue

That may be the problem: https://www.mediamonkey.com/wiki/WebHel ... Properties

[Dynamic990]

Hi tmf, Hi Lowlander!

but might if it's a mapping issue

That was actually my first assumption. However, I am quiet sure that this is not the case here, as changes to the "Original Date" field (e.g. from 1983 to 1984) with my external tagger are correctly read by MMW when the music files are rescanned. Only the complete deletion of the tag with the external tagger is ignored by MMW during the rescan.

How to Configure which ID3 Tags are used for Year / Date in MMW: https://www.mediamonkey.com/support/kno ... year-date/

My MMW is set to use only ID3v2.4 tags and the [MP3Tagging] section in the MediaMonkey.ini file is set as follows:

Code: Select all

[MP3Tagging]
DisableFrames=TYER;TDAT;TORY
EnableFrames=TDRC;TDOR

MMW thus uses the ID3v2.4 standard-compliant TDRC frame for the "Date" and the TDOR frame for the "Original Date" data fields. You can check this by viewing the MP3 file with a HEX editor. The tagger "MP3Tag" that I use also uses these frames. The only difference is that the data fields are called "YEAR" and "ORIGYEAR" in MP3Tag.

but I have had some problems with ID3 2.4 tags in the past

With the above settings, I have never had any problems reading and writing ID3v2.4 tags in MMW or MP3Tag, except for the case mentioned here. All other programmes or apps that I use with my MP3 files can also handle ID3v2.4 tags without any problems.

I also use the Original Date field in MMW, usually Year only though.

Same here.

Best regards
Christian

[Lowlander]

That's about writing though. Changes can be seen as MediaMonkey reads multiple tags with priority. So if the priority tag is changed it's used, this doesn't mean that no other Original Date tags are present in the file.

[Dynamic990]

Hi Lowlander,

Changes can be seen as MediaMonkey reads multiple tags with priority. So if the priority tag is changed it's used, this doesn't mean that no other Original Date tags are present in the file.

And which tags would those be? As you can see from my last post, I have configured MMW to only use the two date frames TDRC and TDOR and ignore all others.

But fair enough, I did the following test:

First I have removed every date field that I could find from an album. When rescanning, the "Original Date" field remains filled. Then I even deleted all tags from that album. After a rescan, all data fields in the MMW database for this album were empty, only the "Original Date" field in remained filled. So in my humble opinion, MMW is clearly the culprit here.

And if you don't believe me, I can provide you with a sample file from the above tests via a support ticket where you can see that there are no tags left.

Best regards
Christian

[Dynamic990]

Hi Lowlander,

I can provide you with a sample file from the above tests via a support ticket where you can see that there are no tags left.

You can find the file mentioned in ticket #13690.

Best regards
Christian

[Lowlander]

This is a bug, tracking as: https://www.ventismedia.com/mantis/view.php?id=21759

[Ludek]

The issue is that for MP3 the 'Original date' is written as both
ID3FID_ORIGRELEASETIME
ID3FID_ORIGYEAR

And if the ID3FID_ORIGYEAR is removed in the MP3Tag then ID3FID_ORIGRELEASETIME still remains to read the value from..

So there is no issue, user needs to remove both ID3FID_ORIGRELEASETIME and ID3FID_ORIGYEAR to get it fully cleared..

[Dynamic990]

Hi Ludek,

So there is no issue.

Unfortunately, I have to disagree here. As I described in post #6, the Original Date information remains intact in the MMW database even if I remove all tags completely from the MP3 file, including the tag you mentioned for the ORIGRELEASETIME, and do a rescan of the file without any tags. You can also see in the sample file I provided via ticket #13690, that there are no tags left.

Just in case this is relevant and you missed it in post #4, I configured my MediaMonkey.ini as follows:

Code: Select all

[MP3Tagging]
DisableFrames=TYER;TDAT;TORY
EnableFrames=TDRC;TDOR

Best regards
Christian

[MiPi]

Hi, you are right, there was bug in this, should be fixed in all next builds.

[Dynamic990]

Hi MiPi,

ok thanks for the update.

Best regards
Christian