ID3v2.4

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: ID3v2.4

Re: ID3v2.4

by jiri » Thu Jun 09, 2016 9:19 am

Yes, will be in MM5.

Jiri

Re: ID3v2.4

by denbartman » Thu Jun 09, 2016 8:46 am

Hi,

Any confirmation if writing ID3v2.4 tags will be implemented in version 5?

I mainly use MM for tagging my files that get read by KODI. Now multiple genres are not split in Kodi. With v2.4 tags this would be resolved.

Even more important is that my car audio system can read v2.4 tags And they seem to be the only way to be able to get de mulitple artists and Mutiple genres processed correctly.

Really hope this will make it in version5.

Greetz...

Re: ID3v2.4

by wwootton1 » Tue Dec 08, 2015 9:28 pm

Just a bump hoping to keep this out there till it gets resolved.

Re: ID3v2.4

by wwootton1 » Fri Oct 30, 2015 6:20 pm

nohitter151 wrote:
mwcem wrote:
nohitter151 wrote:Many mp3 players don't read ID3v2.4 tags, but pretty much everything can understand ID3v2.3.
This may have been true in 2008, but today, seven years later, no modern player has troubles with ID3v2.4. Maybe some outdated ones still ignore that format, but that's why the are outdated. No modern player to my knowledge has any troubles with that format, on the contrary. Most of them are able to read more exotic stuff like itunes-tags and others as well.

The decission - though on purpose - not to support the ID3v2.4 standard, keeps MM in its outdates place. A modern software should offer tagging on a most broad scale and diversity. See "Mp3Tag" or "Helium Music Manager" for example.
People still use those old players though.

As long as we agree...let them select older tag formats instead of forcing everyone to live in the past with them.

Re: ID3v2.4

by nohitter151 » Fri Oct 30, 2015 5:06 pm

mwcem wrote:
nohitter151 wrote:Many mp3 players don't read ID3v2.4 tags, but pretty much everything can understand ID3v2.3.
This may have been true in 2008, but today, seven years later, no modern player has troubles with ID3v2.4. Maybe some outdated ones still ignore that format, but that's why the are outdated. No modern player to my knowledge has any troubles with that format, on the contrary. Most of them are able to read more exotic stuff like itunes-tags and others as well.

The decission - though on purpose - not to support the ID3v2.4 standard, keeps MM in its outdates place. A modern software should offer tagging on a most broad scale and diversity. See "Mp3Tag" or "Helium Music Manager" for example.
People still use those old players though.

Re: ID3v2.4

by wwootton1 » Fri Oct 30, 2015 8:34 am

jiri wrote:I agree that ID3v2.4 should be at least an option for people who prefer it. Sorry for this taking so long, it somehow slipped through, we'll look into it soon and try to get it into 5.0.

Jiri

Good news. At this point. I'd love to see full support for id3v2.4, conversion and clean tags tools. Needs to come soon though.

Re: ID3v2.4

by mwcem » Fri Oct 30, 2015 2:43 am

nohitter151 wrote:Many mp3 players don't read ID3v2.4 tags, but pretty much everything can understand ID3v2.3.
This may have been true in 2008, but today, seven years later, no modern player has troubles with ID3v2.4. Maybe some outdated ones still ignore that format, but that's why the are outdated. No modern player to my knowledge has any troubles with that format, on the contrary. Most of them are able to read more exotic stuff like itunes-tags and others as well.

The decission - though on purpose - not to support the ID3v2.4 standard, keeps MM in its outdates place. A modern software should offer tagging on a most broad scale and diversity. See "Mp3Tag" or "Helium Music Manager" for example.

Re: ID3v2.4

by jiri » Fri Oct 30, 2015 2:35 am

I agree that ID3v2.4 should be at least an option for people who prefer it. Sorry for this taking so long, it somehow slipped through, we'll look into it soon and try to get it into 5.0.

Jiri

Re: ID3v2.4

by wwootton1 » Thu Oct 29, 2015 11:49 pm

I'd prefer v2.4 tags but would settle for the option to write a custom separator in artist tag. Just as it is capable in other multi field tags. I've read the devs remarks regarding both options over the years. I've been a gold member since MM 3 and holding out since then. Researching and putting together other options to maintain my growing library.

If they wont implement these features then atleast make the interface reflect how the tag is actually being written. And document it or put a note near the field in options. Seems like that would have saved people many hours of frustration and research.

Re: ID3v2.4

by nohitter151 » Thu Oct 29, 2015 8:22 am

mwcem wrote:Just think of it - I started this thread in 2008 and still no progress! :cry:
The ID3v2.4 is still regarded as too - what exactly? Exotic? New? Strange? Unusual??

Well, seems that MM will stay behind forever...
MM reads ID3v2.4 tags but doesn't write them. Many mp3 players don't read ID3v2.4 tags, but pretty much everything can understand ID3v2.3. It may be an intentional decision by the devs.

Re: ID3v2.4

by mwcem » Thu Oct 29, 2015 2:22 am

Just think of it - I started this thread in 2008 and still no progress! :cry:
The ID3v2.4 is still regarded as too - what exactly? Exotic? New? Strange? Unusual??

Well, seems that MM will stay behind forever...

Re: Id3v2.4 option

by wwootton1 » Wed Oct 28, 2015 2:04 pm

Juat realized I didn't post this in the Windows section somehow. Now I don't know how to change the location of the post. Sorry.

Id3v2.4 option

by wwootton1 » Wed Oct 28, 2015 1:52 pm

I know this has been discussed for years. Would like to just bring it up again. Everything I use has the capability to read v2.4 tags. I would love tge ability to atleast select the option to write only these tags. It's the only thing that has me contemplating moving from MM again.

Re: ID3v2.4

by mwcem » Thu Oct 23, 2014 1:52 am

I guess still no progress here, right?

Re: ID3v2.4

by MitchMitchel23 » Wed Aug 20, 2014 2:15 pm

Sorry, but I have expressed myself wrong.

XBMC reads ID3v2.3 and ID3v2.4. But if a tag has multiple entrys e.g. ARTIST='Alison Krauss; John Waite' they are only correctly stored in the database if ID3v2.4 is used.

Read this in a xbmc-forum. Can't find the thread at the moment.

Top