Discussion of v1.1.15’s changes to handling of rating field in ID3v2, [posts #6–13 split from final release thread] Options

[someone8]

Previously, I always used a rating scheme which also incorporates one decimal place (mostly .5). But after the recent rating tag change

■ ID3v2: “rating” tags now compatible with Windows Media Player (beta 2).

, my old habit can't be realized anymore, as only the number without the decimal places is saved (to assure WMP compatibility). However, if write a "6" (or any higher number) in the rating tag with foobar, it is saved but will never be compatible with WMP. So can the developers please enable the possibility to save floating numbers again, and only write WMP compatible rating tags, if the written rating is [1 2 3 4 5]? This would help me a lot, because I wouldn't have to modify my whole music library to use a custom rating tag or switching to a [1 2 3 ... 10] (from a [1.0 1.5 2.0 2.5 ... 5]) rating.

Thanks in advance!

[neothe0ne]

I think a nice compromise would be having an advanced option to toggle what the Rating tag is saved to. (So that we can turn off the WMP compatibility)

[shakey_snake]

I don't think foobar writing a POPM frame belonging to another software is a good idea. It would be better that foobar writes a POPM frame of its own.

Please stop.

You are entirely out of your league and don't even seem to understand grasp the basics of the situation, so please save us from your "fix suggestions". I'm sorry if this seems curt, but I am here in attempt to clarify what the changelog means, I don't need you getting 10 steps ahead of yourself.

This would prevent the situation I described above.

There are many ways to avoid the situation you've described above, one of which has already been implemented in component that I shared above. Why not explore your available options, first, before burdening us with your half-baked ideas?

Until this fix was made there was no way to get the mp3 tag to correctly work between programs. Now there is. Compatibility enhancement added. End of story.

I need to make one clarification related to my initial post. I incorrectly (but I think reasonably) assumed that because foobar can write a WMP POPM frame that it would also see existing frames and import them for ratings. foobar does NOT do this...

It can read a mp3's ratings (and add it to your user-specific statistics database), by using the "import statistics from file tags" feature found in the playback statistics menu.

I think a nice compromise would be having an advanced option to toggle what the Rating tag is saved to. (So that we can turn off the WMP compatibility)

If we added a new option every time one user didn't understand something...

This post has been edited by shakey_snake: Sep 15 2012, 23:26

[BenB]

Please stop.

You are entirely out of your league and don't even seem to understand grasp the basics of the situation, so please save us from your "fix suggestions". I'm sorry if this seems curt, but I am here in attempt to clarify what the changelog means, I don't need you getting 10 steps ahead of yourself.

There is no need for personal insults. You don't know me so please refrain from characterizing me or my abilities. I could say more in this regard but I'm not going to engage anyone in a dick-measuring contest. It's irrelevant and pointless. Again, there is no need to make this personal.

There are many ways to avoid the situation you've described above, one of which has already been implemented in component that I shared above. Why not explore your available options, first, before burdening us with your half-baked ideas?

I'm well aware of the various ways to get around the situation and I alluded to them in my previous posts. For the record, this change doesn't affect me. I never write ratings tags to files. I'm speaking up for those who can't or won't speak up for themselves. Now I have a question for you: Why doesn't development seek any input from foobar users before making changes which might negatively affect the users?

Until this fix was made there was no way to get the mp3 tag to correctly work between programs. Now there is. Compatibility enhancement added. End of story.

I wasn't aware there was a high demand for this change. I've not seen any recent posts in this regard. The change doesn't affect me as I've already stated. I'm a fan of compatibility between programs. I raised valid concerns in regard to how this change might affect users and suggested a remedy. Development can take them into consideration or ignore them. I stated my case.

It can read a mp3's ratings (and add it to your user-specific statistics database), by using the "import statistics from file tags" feature found in the playback statistics menu.

I didn't clarify myself enough. I meant it doesn't import those ratings automatically, forcing users to have to change ratings which aren't theirs. I took it for granted that others would take what I was saying in the context of a multi-user environment (indeed all of my comments were in that context), which I shouldn't have done.

If we added a new option every time one user didn't understand something...

Rather flippant remark (and a mischaracterization if you were referring to me).

I do request that this discussion be split into a separate thread, at least from my second post (with relevant references from earlier posts included, of course).

This post has been edited by BenB: Sep 16 2012, 01:38