Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Strange TDRC-handling in foobar2000 0.9.6.9 (Read 5237 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Strange TDRC-handling in foobar2000 0.9.6.9

I'm using text tools to tag some files in Foobar2000 on Fedora linux 12 through Wine.

Everything seems to work fine, the files get their dates in foobar2000's view, but when I try to look at them in Quod Libet (a program that supports id3 v2.4 quite well), the date information isn't shown.

Apparently it is because foobar2000 uses a "TXXX (User defined text information)" frame to store the recording date, instead of just TDRC.

It is also discussed in quod libets bug list, with an explanation on why quod libet will not support the as far as I can tell non-standard TXXX:TDRC format foobar2000 uses in the near future:
http://code.google.com/p/quodlibet/issues/detail?id=48

This issue seems to be discussed here too:
http://www.hydrogenaudio.org/forums/index....530&hl=tdrc

This page in the wiki describes how foobar2000 supposedly maps tags:
http://wiki.hydrogenaudio.org/index.php?ti...ID3_Tag_Mapping


I have used the tool mutagen-inspect to verify that foobar2000 indeed do use the TXXX:TDRC-frame.

Any suggestions on how to deal with this are welcome, also if you need files for debugging.

Best regards, Bernt

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #1
Since I've seen no reply, I wonder: Is this the right place to post bugs?

Cheers

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #2
it's fine here with ID3v2.4


what kind of date format do you have?

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #3
ISO-date format: 1933-02-27

Moderation:Removed unnecessary full quote of the preceding post.

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #4
Well OK - that's the problem
I just now read your linked thread, so you probably know that only year is acceptable

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #5
Actually, full timestamps are acceptable in the TDRC frame.

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #6
you mean for reading?

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #7
What I was trying to say in the original post is that foobar2000 isn't id3v2.4 compliant, which is a problem for me since I'm using foobar2000 to tag files I'm using in Quod Libet, which is a id3v2.4 compliant music player.

Foobar2000 stores the ISO-dates as a TXXX TDRC-header instead of just TDRC-header.


Strange TDRC-handling in foobar2000 0.9.6.9

Reply #8
I'm using text tools to tag some files in Foobar2000 on Fedora linux 12 through Wine.

Everything seems to work fine, the files get their dates in foobar2000's view, but when I try to look at them in Quod Libet (a program that supports id3 v2.4 quite well), the date information isn't shown.



It is also discussed in quod libets bug list, with an explanation on why quod libet will not support the as far as I can tell non-standard TXXX:TDRC format foobar2000 uses in the near future:
http://code.google.com/p/quodlibet/issues/detail?id=48

So, Quod Libet doesn't read TXXX tags it doesn't write. That's not a fb2k problem. Why do you think that bug report is marked as a "Defect"?



Apparently it is because foobar2000 uses a "TXXX (User defined text information)" frame to store the recording date, instead of just TDRC.
...

This page in the wiki describes how foobar2000 supposedly maps tags:
http://wiki.hydrogenaudio.org/index.php?ti...ID3_Tag_Mapping


I have used the tool mutagen-inspect to verify that foobar2000 indeed do use the TXXX:TDRC-frame.
Correct, as the id3 tag mapping wiki pages says, foobar2000 does not write to the TDRC frame. foobar2000 doesn't write to all id3 frames. When it is requested to store data that doesn't match up with a frame it writes to, it stores that data in TXXX or WXXX.

This does not make fb2k "non-compliant" with the id3v2.4 standard. It just means the tag writer only writes a subset of the id3v2.4 standard.
Trolling isn't really the most efficient way to encourage someone to add a feature.
elevatorladylevitateme

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #9
I'm using text tools to tag some files in Foobar2000 on Fedora linux 12 through Wine.

Everything seems to work fine, the files get their dates in foobar2000's view, but when I try to look at them in Quod Libet (a program that supports id3 v2.4 quite well), the date information isn't shown.



It is also discussed in quod libets bug list, with an explanation on why quod libet will not support the as far as I can tell non-standard TXXX:TDRC format foobar2000 uses in the near future:
http://code.google.com/p/quodlibet/issues/detail?id=48

So, Quod Libet doesn't read TXXX tags it doesn't write. That's not a fb2k problem. Why do you think that bug report is marked as a "Defect"?

Well: Quod Libet reads the TDRC tag. Which I assume is the correct place to store the recording time, is it not? Have I misunderstood how it is supposed to work according to the id3v2.4 spec?

Apparently it is because foobar2000 uses a "TXXX (User defined text information)" frame to store the recording date, instead of just TDRC.
...

This page in the wiki describes how foobar2000 supposedly maps tags:
http://wiki.hydrogenaudio.org/index.php?ti...ID3_Tag_Mapping


I have used the tool mutagen-inspect to verify that foobar2000 indeed do use the TXXX:TDRC-frame.
Correct, as the id3 tag mapping wiki pages says, foobar2000 does not write to the TDRC frame. foobar2000 doesn't write to all id3 frames. When it is requested to store data that doesn't match up with a frame it writes to, it stores that data in TXXX or WXXX.

This does not make fb2k "non-compliant" with the id3v2.4 standard. It just means the tag writer only writes a subset of the id3v2.4 standard.
Trolling isn't really the most efficient way to encourage someone to add a feature.


My intention was definitely not to troll, sorry if I have offended anybody. True, fb2k isn't non-compliant, but at least I would be helped if it would store the recording date differently.

If there is any way I can help out, please let me know.

Best regards,
Bernt

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #10
Sorry for the resurrection.

I have a similar problem. My rockboxed iPod 5.5G doesn't display YYYY-MM-DD style date information tagged with foobar2000 because Rockbox only reads TDRC frame (as of r27134). Of course, there are some workarounds:
  • [easy]
    Mp3tag's Convert Action (Guess Values "%_date%": %year%). (as a side-effect, Mp3tag deletes TXXX:date frame and writes 2 TDRC frames. 2nd one is the date (mm/dd/yyyy) I use the function. Is this Mp3tag's bug?)
  • [messy]
    patch rockbox/apps/metadata/id3tags.c
    Code: [Select]
    --- id3tags.c.orig	2010-06-26 06:40:20.807557309 +0900
    +++ id3tags.c 2010-06-26 06:47:51.851542797 +0900
    @@ -309,6 +309,9 @@
            if (!strcasecmp(tag, "ALBUM ARTIST")) {
                strlcpy(tag, value, value_len);
                entry->albumartist = tag;
    +        } else if (!strcasecmp(tag, "DATE")) {
    +            strlcpy(tag, value, value_len);
    +            entry->year_string = tag;
     #if CONFIG_CODEC == SWCODEC
            } else {
                value_len = parse_replaygain(tag, value, entry, tag,
But now that foo_musicbrainz has become a popular component, I think it's nice to have a option about TDRC frame under Advanced > Tagging > MP3.

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #11
Just to clarify, the behavior I'm seeing with v1.1.2 is four-digit date = TDRC, anything else = TXXX:DATE.  Which isn't what I expected after looking at the ID3 Tag Mapping page (it only shows TDRC).  Of course, TXXX:DATE is fine if the value entered doesn't meet the required format (say, "196?" or something), but I would like it if foobar could use TDRC for at least yyyy-MM and yyyy-MM-dd formats.

id3v2.4.0 links, for reference:
http://www.id3.org/id3v2.4.0-frames
http://www.id3.org/id3v2.4.0-structure

Strange TDRC-handling in foobar2000 0.9.6.9

Reply #12
This is still a problem with foobar2000 1.1.7.

Really annoying bug! I wish foobar2000 would be standards compliant on this field.