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: original release date - broken or not? (Read 4410 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

original release date - broken or not?

I'm in the midst of the most ridiculous project I've ever taken on: detailed tagging of a collection I'm calling "Everything ever Recorded" (Not really, but it is ~1.2 million recordings from 1878-1978) Since the recording date is central to the collection, I'm wanting to tag everything with its original recording date (or whatever they're calling it this week). Because of the compatibility issues with id3 v2.4, I've been tagging everything v2.3 UTF-16. So far, so good. I was almost through 320,000 tracks when I noticed something that caused a mild psychotic break. Foobar apparently isn't saving original release date in the right frame. Everything I've read says that's TORY. Foobar seems to think it should be in: TXXX: ORIGINAL RELEASE DATE

My usual process is to use Picard to grab basic info (correct names, genre, grouping, release date and original release date, if available) then save as v2.3 UTF-16. Then I open the album in foobar for further cleanup/replaygain scan. I've verified that Picard is saving the origdate in the TORY frame, which is what foobar docs say it should be for v2.3:

Code: [Select]
ORIGINAL RELEASE DATE      TORY           Original release year

To speed editing, I added a line in Preferences - Advanced - Standard Fields: OriginalDate=ORIGINAL RELEASE DATE to move the tag out of the unknown tag pile at the bottom of Properties and into a better spot. Once I noticed the tag was being...evicted(?) from its frame on save, I removed that to see if it made a difference, but no change.

So, am I doing something wrong, is this another foobar quirk, or what? Here's metamp3 output of the tag Post-Picard and Post-Foobar, in case anyone's into that sort of thing.

Code: [Select]
TIT1: Classic Rock
TIT2: Armenia City in the Sky
TPE1: The Who
TRCK: 1/23
TALB: The Who Sell Out
TCON: Psychedelic
TDAT: 2006
TPE2: The Who
TORY: 1967
UFID: , 36 bytes
TYER: 1995
TPUB: MCA Records
TXXX: [BARCODE]: 008811126827
TXXX: [CATALOGNUMBER]: MCAD-11268
TXXX: [ALBUMARTISTSORT]: Who, The
TXXX: [ASIN]: B000002OX5


Lovely. I load it in Foobar, change 1967 to 1962 and save.

Code: [Select]
TIT1: Classic Rock
TIT2: Armenia City in the Sky
TPE1: The Who
TRCK: 1/23
TALB: The Who Sell Out
TCON: Psychedelic Rock
TPE2: The Who
TPUB: MCA Records
TYER: 1995
TXXX: [CATALOGNUMBER]: MCAD-11268
TXXX: [ALBUMARTISTSORT]: Who, The
TXXX: [ASIN]: B000002OX5
TXXX: [BARCODE]: 008811126827
TXXX: [original release date]: 1962

 

I also noticed that beside TORY, TDAT and UFID are gone too, but I can live with that, it's the date that bugs me.

Any ideas?  Thx in advance.

Kel

original release date - broken or not?

Reply #1 –
94 views and 0 answers? 

All I need to know is if this one tag (ORIGINAL RELEASE DATE) maps to the frame the tag mapping docs imply it should on id3v2.3. I'm pretty sure I've spent way more time scouring forums and docs than the creators did making them. If this is answered elsewhere, then it has eluded me. The Properties - Advanced - Display section appears to be completely undocumented online, and as far as tag mapping, all I found was a lot of this:

Mapping: "foobar2000 0.9 does not write ID3v2.3 tags; the ID3v2.3 Frame column indicates how foobar2000 reads this version"

FAQ: "ID3v2 writer compatibility mode...results in non-standard-compliant tags being written (ID3v2.3 instead of ID3v2.4..."

I won't even try to figure that one out. Instead, I post.    Any info/clarification would be much appreciated.

TIA
-Kel

original release date - broken or not?

Reply #2 –
If you use "ID3v2 writer compatibility mode..." than it will result in TXXX: [original release date], because as the wiki link sais:
Quote
Note that foobar2000 0.9 does not write ID3v2.3 tags; the ID3v2.3 Frame column indicates how foobar2000 reads this version of the standard.

If you use ID3v2.4 than it will be written in TDOR frame. TOYR is ORIGYEAR but foobar doesn't write that as the wiki shows

Maybe you'll find useful this foobar plugin: MusicBrainz Tagger
And this tagger: Mp3tag

original release date - broken or not?

Reply #3 –
Quote from: Kelani on
Mapping: "foobar2000 0.9 does not write ID3v2.3 tags; the ID3v2.3 Frame column indicates how foobar2000 reads this version"

FAQ: "ID3v2 writer compatibility mode...results in non-standard-compliant tags being written (ID3v2.3 instead of ID3v2.4..."

I won't even try to figure that one out. Instead, I post.    Any info/clarification would be much appreciated.
How about:
"foobar2000 0.9 does not write ID3v2.3 tags (although it may write something resembling id3v2.3 when compatibility mode is enabled)..."

Truth be told. Very few programs write actual, standard id3v2.3 tags, most use some collection of hacks to work around bugs and issues id3v2.4 already solves.


That said, I have no idea or recommendation for what you would want to use for your project, since I really have no idea why you'd be using mp3 for some sort of musical archive.
elevatorladylevitateme

original release date - broken or not?

Reply #4 –
@2E7AH:

Yeah, I wasn't using compatibility mode, just plain 2.3.  Even so, it still gets written to TXXX, so I guess that's unfortunately just how it is. The Wiki doublespeak definitely doesnt' help.

As for MusicBrainz Picard/Mp3tag, I do use those. (Currently helping develop the lastfmplus plugin, even.)  Picard's step #1, followed by foobar, then mp3tag.  The only reason I use mp3tag is to re-add those tags that foobar breaks. If that didn't happen, I probably wouldn't use mp3tag at all.

Quote from: shakey_snake on
How about:  "foobar2000 0.9 does not write ID3v2.3 tags (although it may write something resembling id3v2.3 when compatibility mode is enabled)..."
Truth be told. Very few programs write actual, standard id3v2.3 tags, most use some collection of hacks to work around bugs and issues id3v2.4 already solves.

Heh, what an appropriate statement. That should be in the wiki.

Quote from: shakey_snake on
That said, I have no idea or recommendation for what you would want to use for your project, since I really have no idea why you'd be using mp3 for some sort of musical archive.

Y'know, I wondered how many posts I'd go before I ran into a judgmental comment here. Pretty sure that's why I've been lurking since 2005.

let me clarify.

As stated in OP, the archive is ~1.2 million recordings from 1878-1968. (1978 was a typo) Most of my Post-1930 material is archived in FLAC, as is everything I've ever personally converted from 78 & reel. Personal favorites and rare items range from 24/96 to 24/192. That's about half the collection.  Before that? Lots of wax cylinders. I may lose my audio engineer card for saying it, but a lossy format ain't gonna make a damn bit of difference for those. Even if it did, almost all of the really vintage stuff, cylinders included, were previously archived to mp3 by various organizations, and most of said archives aren't exactly available to the public. So, I consider myself fortunate to have copies, period.

Of course, If I had the sources, the space (~3:00/track = 280TB. I'd have to mortgage something) and the time (~5 min. processing per track = 100k hours) then yeah, I'd *love* to have 24/192 copies of everything.

Thanks for the replies.

original release date - broken or not?

Reply #5 –
Quote from: Kelani on
Yeah, I wasn't using compatibility mode, just plain 2.3.  Even so, it still gets written to TXXX

I wouldn't say that. ORIGINAL RELEASE DATE is written in TDOR frame if compatibility mode isn't checked. Did you check on ID3v2 in "preffered writing scheme"?

Quote from: Kelani on
As for MusicBrainz Picard/Mp3tag, I do use those. (Currently helping develop the lastfmplus plugin, even.)

I was suggesting foobar plugin for MusicBrainz, I know that you use Picard

lastfmplus is nice plugin, only that it writes all tag values to COMMENT tag and however - I prefer AMG MOOD and THEME and discogs GENRE and STYLE
but don't get me wrong