gmane.comp.multimedia.id3v2

Beatport ID3v2.4 tag support

Peter Siciliano — 2012-09-24T22:24:52

Hello ID3 community,

Over the past year we at Beatport have been working to support as many ID3v2.4 frames as we could and populate them with accurate data.
We have updated our ingestion system for new files and retagged our old files to supply all frames and tags consistently.

I am excited to announce that as of today we are delivering all of our track MP3s and AIF with IDv2.4 tags containing the following frames:
UFIDBeatport ID
TSRCISRC (international standard recording code)
APIC $03Cover Art [Cover (front)]
APIC $11Beatport Waveform image (brightly colored fish)
TIT2Trackname (Mixname) [Original filename]
TPE1 Artist [Lead performer(s)/Soloist(s)]
TPE4 Remixer [Interpreted, remixed, or otherwise modified by]
TALBAlbum / Release [Album/Movie/Show title]
TPUBLabel [File owner/licensee]
TDRCYear (Published on Beatport)
TDORDate (Original release)
TDRLDate (Published on Beatport)
TFLTFile Type
TENCEncoded by
WOAFBeatport track detail page URL
WPUBBeatport label detail page URL
TCONGenre
T

Standards for remix types and multiple remixers

Evgueni Naverniouk — 2012-08-14T01:37:26

Dear ID3,

I'd like to properly tag remix artist and types and I'm wondering if anyone
has created a standard for this yet. I found the TPE4 field which is
helpful, but it's certainly not enough.

How should I deal with:

*1) Storing the "type" of remix.*

John Smith - Diddy (Abe Lincoln Remix)
John Smith - Diddy (Abe Lincoln Dub)
John Smith - Diddy (Abe Lincoln's Super Awesome 1929 Mix)

Where would the "Remix" vs "Dub" go? Ideally it would be something like
this:

%TPE1% = John Smith
%TIT2% = Diddy
%TPE4% = Abe Lincoln
%???% = Super Awesome 1929 Mix


*
2) Storing multiple mix artists?*

John Smith - Diddy (Abe Lincoln & Mr. Waldo Remix)

Where would Mr. Waldo go? I don't want to put him into %TPE4% because then
I won't be able to keep the artists separate, but I don't see a way to add
a second %TPE4% value. Ideally it would be something like this:

%TPE1% = John Smith
%TIT2% = Diddy
%TPE4% = Abe Lincoln
%TPE4% = Mr. Waldo
%???% = Remix


*
3) Collaborations*

John Smith vs. Abe Lincoln - Diddy (Mr. Waldo

Re: id3v2.4 and Windows Media Player (WMP)

Francois Chabloz — 2012-07-26T15:00:11

< at >Scott, very glad to see the 1.8 Beta support for writing 2.3! Thanks!

my 2cts in this post, hoping it'll help those like me who struggled with WMP and ID3 tags! 
http://backstage.official.fm/ruby/id3-windows-media-player-is-the-ie6-of-music-players/


Le 4 mai 2012 à 09:59, Francois Chabloz a écrit :

Re: id3v2.4 and Windows Media Player (WMP)

Francois Chabloz — 2012-05-04T07:59:58

Thanks Scott, i'll have a look. and thanks for the great lib!

Re: Contact information for Eric Kemp

Alan Dykes — 2012-05-04T04:32:14

Dan O'Neill <dano <at> id3.org> writes:

approached regarding the history of tagging is related to an NPE [1] type of 
issue. I figure that if someone here has prior art references, good! The story 
from Jud was a good read and therefore a nice outcome.Now back to our regularly 
scheduled program.Best to all,dano[1] http://en.wikipedia.org/wiki/Non-
practicing_entity


I don't know how to contact Eric but I do remember helping him (and not 
succeeding) try to figure it out on EFnet IRC when he came up with the idea of 
making a tag the size 128 bytes for it to not mess up the MP3 decoding.  I don't 
know how much help I'd be in any questioning but if its helpful, I can be 
contacted at dykesa at googlemail.com (gmail).

Alan

Re: id3v2.4 and Windows Media Player (WMP)

Peter Siciliano — 2012-05-04T01:37:23


Agreed.
Speaking to what we are working on.
I am not going to hold back on sharing a ton of very useful data in an open format because others don't want to implement simple solutions to read the tags or want to fight to create a closed format just for the themselves (or to license).
Fortunately, my users are unique and need the info to do their jobs (not just because they want their iTunes library to look cool). 
Our users will adopt whatever tools and technologies keep up with the times and give them the value they need to grow and expand as Artists. 
On top of that, our industry is receptive (and responsive) to this and given the opportunity to work with an open format (not one developed by one of their competitors) I'm confident reading appropriate tags will be embraced and will likely add the custom tags we will be providing.

In time perhaps others will find value in them and choose the read them as well.
I'll provide the info to this group of course.

P.

Re: id3v2.4 and Windows Media Player (WMP)

Scott Wheeler — 2012-05-03T23:34:06


The current source on github (not released yet) can write 2.3.


TagLib was a Linux-only library for most of its lifetime and was originally designed as such.  What Windows did or didn't do was irrelevant.  That said, I see WMP as the Internet Explorer 6 of music players and cringe a bit seeing people tiptoe around its failure to implement a standard introduced 12 years ago.

-Scott

id3v2.4 and Windows Media Player (WMP)

Francois Chabloz — 2012-05-03T20:51:49

Hello all, 

I'm digging deep into id3 lately and can't make my mind about id3v2.4. Here's my understanding : 

- Windows Media Player 12 do not read 2.4.
- I'm not a fan of WMP12, but when targetting a large audience, WMP compatility is unfortunately required. (WMP12 comes out of the box with Win7)

Conclusion: read v2.4 (because there are few out there already) but write v2.3 only. - At least as long as WMP12 is in the picture.

Second conclusion : not writing v2.4 means not using the excellent taglib library. Or am i missing something? it's hard to believe that such a great lib is excluding - without optional settings - such a share of users (WMP users i mean).

I would greatly appreciate if anyone can confirm or correct this.

Thanks!
Francois Chabloz

Re: ID3 - Is this community still active?

Peter Siciliano — 2012-05-01T20:40:31

Excellent.
On it.
Thanks.
:-)
++
Peter Siciliano | CTO
Beatport | Play with music
-----------------------------------------------
2399 Blake Street Suite 170
Denver, Colorado USA 80205
tel:    +1.720.932.9103
fax:   +1.720.932.9104
direct:  +1.303.565.2690

On May 1, 2012, at 10:22 AM, Dan O'Neill wrote:

Re: ID3 - Is this community still active?

Dan O'Neill — 2012-05-01T16:22:21

Yes, there are people on this list. There is a github repository which will
accept pull requests for review and potential incorporation.

https://github.com/organizations/id3

I would really appreciate anyone and everyone's assistance in incorporating
changes into newer revisions of the standard.

Best,

Dan

On Tue, May 1, 2012 at 9:00 AM, Peter Siciliano <
peter.siciliano< at >beatport.com> wrote:

ID3 - Is this community still active?

Peter Siciliano — 2012-05-01T16:00:52

Hi ID3 Mailing list,

Is this community still active?

We are about to heavily utilize ID3v2.4 for a project currently in Alpha and would like to know if others still review and moderate this format.

I would also like to propose reviewing the v2.4 documentation to clean up some language now that time as dictated more clarity to some tag descriptions and irrelevance to others.

I will be pointing vendors and suppliers to this documentation in the coming months and would like it to be as simple as possible to understand how to use tags effectively.

++
Peter Siciliano | CTO
Beatport | Play with music
-----------------------------------------------
2399 Blake Street Suite 170
Denver, Colorado USA 80205
tel:    +1.720.932.9103
fax:   +1.720.932.9104
direct:  +1.303.565.2690

Re: id3v2 (the app): a question re: tag data formatting

Conrad J. Sabatier — 2012-04-21T11:51:59

On Sat, 21 Apr 2012 11:36:39 +0100
Josh Twigg <twigg321< at >gmail.com> wrote:


Ah, yes, of course!  Somehow I forgot about that.

I really do need to read the spec again more carefully.  :-)


Thanks!

Re: id3v2 (the app): a question re: tag data formatting

Josh Twigg — 2012-04-21T10:36:39

It is my understanding that if the frame has $00 before it then it implies
ascii, $01 then it is unicode. I suggest you give the specification a good
read.

Good luck with your program



On 21 April 2012 10:55, Conrad J. Sabatier <conrads< at >cox.net> wrote:

id3v2 (the app): a question re: tag data formatting

Conrad J. Sabatier — 2012-04-21T09:55:30

I've recently begun experimenting with doing a little coding in C to
manipulate ID3 tags, and have come across something that surprised me.

Briefly, the code I've written so far just parses the ID3 tag and spits
out the raw data from each frame.  What's surprising to me is that the
actual data in many frames contains leading zeroes.  I'm just wondering
why this is.  I've used the id3v2 program to tag most of my files.

Can anyone offer any insight into this?  Is this an expected/required
behavior, or possibly a bug in the id3v2 implementation?

Thanks!

Support for ID3 v2.4

Pushkar Pradhan — 2012-03-15T02:22:21

Hello,
I was looking at id3v2 to generate ID3 v2.4 tags. I looked at the ldd
output and saw that it uses libid3-3.8.so which only produces ID3 v2.3 tags
and this library is not maintained anymore.
Any plans of supporting 2.4?
Does anyone know of a ID3 v2.4 library?

Re: Multiple Values proposal

Audio Ranger Development — 2012-03-07T08:30:48

Hi,

we had this exact discussion when talking about v 2.31 about a year ago:

 > > [Mathias Kunter]
 > > Multiple frames would also break backwards compatibility -
 > > "There may only be one text information frame of its kind
 > > in an tag." Well, breaking this rule won't make any existing
 > > parser fail, but many existing implementations would probably
 > > just use the last frame [...]
 > >
 > > Null-delimited frames seem to be the better choice for me,
 > > since they behave identically for current parsers, assuming
 > > that they read the frame data as simple null-terminated
 > > string.
 >
 > [Ben Allison]
 > Yeah, I agree with this. I mentioned multiple frames only
 > because that's how some other metadata formats handle this. I'm
 > not particularly partial to it and I agree that it conflicts
 > with the existing spec.


But we somehow never actually got to work on ID3 v 2.31. We still have 
that github repository at https://github.com/id3 and the collected ideas 
at https://github.com/id3/ID3v2.

Re: Multiple Values proposal

Paul Taylor — 2012-03-06T22:11:07

Hi Ben

Can you spell out the reasons because to my mind the null terminated 
values method supported by ID3v24 works perfectly well, and certainly 
uses alot less space than having to create a whole new frame for each 
value. If you introduced this new method then there would be two ways of 
doing the same thing in ID3v24  which is not good, unless you remove 
support for null terminated values thus making 2.4.1 incompatible with 2.4.

I would much prefer to just officially support null terminated values in 
ID3v231

Paul, Jaikoz, JThink

Multiple Values proposal

Ben Allison — 2012-03-06T22:00:44

I know we had this conversation a little while ago, but here's another
suggestion.  I'm not sure if we discussed this one or not.

Vorbis comments (as well as APEv2 and FLAC which uses a very similar
scheme) supports multiple values by having a key repeated more than once
in the tag.

Could we not do something similar with ID3v2?  If you want multiple
artists, for example, just create multiple TPE1 frames.

We could increment the versions to v2.31 and v2.41 to signify the change. 
The main questions are:
1) Would any major existing implementations completely fail or return a
parsing error when encountering duplicate frames
2) Would any major existing implementations do anything strange, like use
the last-encountered frame rather than the first-encountered frame, as the
value.

For a variety of reasons, this feels like a superior alternative to
NULL-delimited strings.

Thoughts?
-Ben Allison
Nullsoft, Inc.

Re: How about a new frame "Favorite song" or "Love it"

Quentin Sculo — 2012-01-16T17:17:24

I would suggest using FMPS_Rating and/or FMPS_Rating_User from the
FMPS standard instead :
http://www.freedesktop.org/wiki/Specifications/free-media-player-specs
POPM is id3v2-specific and use a very cumbersome 1-255 value range
that don't really map correctly to the values the apps actually use,
like 1-5 or 0-100

Quentin

Re: How about a new frame "Favorite song" or "Love it"

Peter Bennett — 2012-01-16T16:33:02

You are right, that looks like a better solution. Unfortunately I did
not build in support for that tag. An item for my to-do list..
Peter

On 1/14/2012 12:17 PM, Ben Bennett wrote:

Re: How about a new frame "Favorite song" or "Love it"

Ben Bennett — 2012-01-14T17:17:16

Why not just use the existing POPM tag?

http://www.id3.org/id3v2.3.0#head-2452ec9cf8b42c5c117b518b69e129ff67970852

-ben

On Sat, Jan 14, 2012 at 11:52:59AM -0500, Peter Bennett wrote: