We understand that some users want to have absolutely full control over the structure of tags and so we plan to make this more configurable in some of the next versions. This would include a choice of ID3v2 version, a better control over fields stored in tags (e.g. Rating store/don't store), etc.

Jiri

> I f I give you ID3v2.4 tags, I don't think it is appropriate
> (or even nice) for you to revert my tags to v2.3 when I make a change

Agreed 100%. Is this now fixed?

[quote="studley"]If I give you ID3v2.4 tags, I don't think it is appropriate (or even nice) for you to revert my tags to v2.3 when I make a change to the information using MM. I shouldn't have to be concerned that by changing the rating of a song (and saving it to the tag), that it is going to make fundamental changes to my file.

I understand your decision to [b][i]default[/i][/b] to v2.3 tags for compatibility (although I wish I could persuade you to push v2.4). I might even encourage you to make it the default. I do believe, however, that you should be able to write ID3v2.4. You do not seem to be having a problem reading it. I'm not sure why you are shying away from complete support of ID3v2.4.

Even if you do not wish to make v2.4 an option, yet... [b]if you receive a file in ID3v2.4 you should write it back out the same way[/b] (or at least give me a strong warning that you are about to change my file in a way that I am not expecting).

Keep up the good work and thanks for a terrific product.

David[/quote]

Can we revisit this conversation again now that Version 3 is out the door?

Sincerely, David

Hey everyone in this thread. I just wanted to say that I've recently came across a bug with reading 2.4 tags - ARTWORK. It just doesn't work. But 2.3 works just fine. I assume other aspects of 2.4 tags are being faulty in MM from what I've read in this thread.

My other taggers and players (mainly MP3Tag & iTunes) were reading my 2.4 tags great. But MM is still king of features and I don't want to lose that. So, I've made reference to fixing this problem in another thread and hope MM will soon handle 2.4 correctly. We can only expect so much at times so 2.3 might need to hang around a little while longer. Cheers.

[quote="jiri"]How exactly does MM mess up the tag? MM currently saves ID3v2.3, because from compatibility point of view it seems to be the best solution...

Jiri[/quote]

I've been going round in circles and I'm not sure it is a MM problem, I will let you know if I find anything specific, but I need to say one thing...

If I give you ID3v2.4 tags, I don't think it is appropriate (or even nice) for you to revert my tags to v2.3 when I make a change to the information using MM. I shouldn't have to be concerned that by changing the rating of a song (and saving it to the tag), that it is going to make fundamental changes to my file.

I understand your decision to [b][i]default[/i][/b] to v2.3 tags for compatibility (although I wish I could persuade you to push v2.4). I might even encourage you to make it the default. I do believe, however, that you should be able to write ID3v2.4. You do not seem to be having a problem reading it. I'm not sure why you are shying away from complete support of ID3v2.4.

Even if you do not wish to make v2.4 an option, yet... [b]if you receive a file in ID3v2.4 you should write it back out the same way[/b] (or at least give me a strong warning that you are about to change my file in a way that I am not expecting).

Keep up the good work and thanks for a terrific product.

David

I tested it again now with B4 and the problem is still there... First I have the song in a separate folder to hear and classify them. While listening to the song, I edit the ID3 Tags and delete the fields "Album" and "Album Artist". Then move the song to my archive via rightclicking on the song and select "Send to \ Folder (Move)". After the song is moved I check the properties and the deleted fields are filled again... If I delete the fields again, then this is stored and I can move the song to whereever I want to. The fields stay empty then...

It was nearly every song that I added in the last time. I think, that this has something to do with the database. I think, that in the database the old tag was saved and when I moved the song to another directory, the tag was taken from the database. After editing the tag again it stays... It is only for new songs I add. When I move a song now into another directory, the tag stays as I saved it the last time. I don't have a sample file at the moment...

PoooMukkel,

Can you send me a sample file for which Album/Album Artist doesn't delete?

Thx.

-Rusty

Maybe I have the same problem... Let me explain...

When I edit the IDTags and save them, after moving the song in another directory the Tag changed. I deleted "Album" and "Album Artist" and after moving the song the info is back. I have to delete the fields again.

How exactly does MM mess up the tag? MM currently saves ID3v2.3, because from compatibility point of view it seems to be the best solution...

Jiri

MM3 is still not saving tags as v2.4. It seems to be reading them correctly, but if I make a change to the properties (and allow it to save to tags) it reverts the tags to v2.3 and messes them up.

Please let me know if I am doing something wrong or if there is a setting to forces the writing of v2.4 tags.

Thanks,
David