# Popularimeter Tag Fails in 2.48c **URL:** \ **Category:** Fixed Bugs\ **Tags:** bug-fixed\ **Created:** [April 11, 2011, 8:50pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847 "2011-04-11T20:50:10Z")\ **Posts on this page:** 8\ **Page:** 3
**Author:** ![MrSinatra](https://community.mp3tag.de/user_avatar/community.mp3tag.de/mrsinatra/32/5574_2.png) [@MrSinatra](https://community.mp3tag.de/u/MrSinatra)\ **Post date:** [October 19, 2018, 6:43pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/41 "2018-10-19T18:43:19Z")
> [@Florian](#): > > I now think that adding those app-specific was a mistake — which is unfortunately not so easy to revert. My dream-solution is to remove the different app-specific `RATING MM` , `RATING WMP` , ... fields and to have Mp3tag show the raw data ( `POPULARIMETER` , `RATING` , `RATE` , ...). To ease displaying this data, instead of having dedicated fields I can imagine having a scripting function, e.g., `$rating(%field%)` that converts the raw value in a star-like representation. that sounds amazing, and i think is the best solution. to be clear, popularimeter [should] always show the raw data. then use scripts for different additional columns to convert that raw data to either a numerical value, or an actual star. so say 196 is the POPM value. in that case mp3tag would show: popularimeter = whatever txt string | 196 | # but another column via a script would map that as 4 while yet another column via a script would map that as ```auto **** ``` while yet another column via a script would map that as 80 why 80? b/c 80 is the value that 196 is translated into on a 0-100 scale, which is how ratings are stored in the MM database. (in other words, all ratings from any format or spec are translated into a 0-100 scale in the MM db) anyway, your proposal would be the ideal solution imo for mp3tag to follow!! **thank you Florian** for your very detailed explanation. i hope you have time to implement this. just FYI i am currently back at it, trying to nail down what values are written and read for MM for bombs and half stars. i don't anticipate being able to get them to make any more changes but from what i can gather there are some really strange things about how MM reads and interprets some values. however, whatever MM does, and will do going forward, i just want to know b/c it seems development has revived to some degree on winamp, and i am hopeful to get them to implement half stars, and to do it in such a way that is compatible with MM. (i know of no other app that writes values to POPM for bombs/half stars other than MM) the good news is that at this point, EVERY app i know of writes 1,64,128,196, and 255 for whole stars (for id3 / POPM). that really simplified things. ---
**Author:** ![MrSinatra](https://community.mp3tag.de/user_avatar/community.mp3tag.de/mrsinatra/32/5574_2.png) [@MrSinatra](https://community.mp3tag.de/u/MrSinatra)\ **Post date:** [November 11, 2018, 3:11pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/42 "2018-11-11T15:11:44Z")
Because I think the issue is similar in that it involves multiple columns and ratings, I wanted to be sure this was listed here in this thread, b/c it would make sense to fix all of this at once: [https://community.mp3tag.de/t/no-support-for-reading-windows-explorer-ratings-in-m4a-mp4/15671](https://community.mp3tag.de/t/no-support-for-reading-windows-explorer-ratings-in-m4a-mp4/15671) Thx. EDIT: I also want to add that all apps I know of, now write the same exact 5 POPM values for the 5 whole stars, which makes ratings handling easier, namely 1, 64, 128, 196, and 255. I got MM to conform to windows explorer's de facto standard. Not sure tho about reading ranges, half stars, etc. ---
**Author:** ![ZitoBandito](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/z/7feea3/32.png) [@ZitoBandito](https://community.mp3tag.de/u/ZitoBandito)\ **Post date:** [May 22, 2020, 5:27pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/43 "2020-05-22T17:27:19Z")
Hello there, I would like to chip in to this ancient thread because I just spend 3 hours pulling hear off my head over this topic and I thought it deserves a post at least. I'll reiterate the obvious - the lack of POPULARIMETER tag value when either any of the three player-specific tags are recognised and filled is incredibly confusing! Since the [Main Tags website](https://docs.mp3tag.de/mapping) states clearly that POPULARIMETER tag is a direct representation of POPM ID3 tag I thought that this is the only tag I need to display in Mp3tag to understand the format of my ratings. I was wrong - the tag ratings in my music collection were managed by both Music Bee and Dopamine and while the former uses its own Email subtag, the latter uses the subtag of WMP, making me run in circles for the outrageous amount of time and trying to solve the mystery of falsely-reported blank tags and contradictions among all those programs. From the user's perspective the behaviour of the tags superseding the others is simply unclear and undocumented. I know this is unlikely to change, given that it hasn't in the last 9 years, but there you go, I had to vent it somewhere... Thanks for reading! ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [April 15, 2021, 4:35pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/44 "2021-04-15T16:35:25Z")
This topic had its 10-year anniversary recently and I've (again) spent some time thinking about possible solutions. I've already explained that removing the app-specific fields won't happen because too many users adapted their workflows to those fields. There are even third-party apps that use those field names now, even for FLAC and other formats (this was never my intention and clearly a mistake). This is the explanation that I gave at the time: > [@Popularimeter Tag Fails in 2.48c](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/40): > > The main issue why this has not been addressed in the proposed way, i.e., having both POPULARIMETER with the raw data in Email|Rating|Playcounter and the different app-specific RATING MM, RATING WMP, ...) fields is the following: Displaying both fields, where in fact one of them is a derived field, i.e., would really break Mp3tag's way of showing what's in the file. You'd end up with a POPULARIMETER field (showing what's inside the tag) and a RATING MM field, which is then only a view on the ve… I've recently had another idea: since Mp3tag's options dialog now also has an advanced settings page, I could add a dedicated setting to disable the creation of those app-specific fields and display raw `POPULARIMETER` instead. > Prefer display of POPULARIMETER for ID3v2 rating over app-specific fields. Before I go into this direction, I wanted to ask y'all if there is still interest for any of that and if there are any objections/problems with this proposed approach, which I'm currently not seeing. ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [April 23, 2021, 12:31pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/45 "2021-04-23T12:31:08Z")
I've now added this option with [Mp3tag v3.06f](https://community.mp3tag.de/t/455) as a checkbox > Always display POPULARIMETER values for ID3v2 ratings at _Options → Tags → Advanced_ for those who prefer the raw POPULARIMETER field over the app-specific convenience fields. ---
**Author:** ![MrSinatra](https://community.mp3tag.de/user_avatar/community.mp3tag.de/mrsinatra/32/5574_2.png) [@MrSinatra](https://community.mp3tag.de/u/MrSinatra)\ **Post date:** [April 28, 2021, 9:26pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/46 "2021-04-28T21:26:37Z")
Thx Florian... I only am just now seeing this, it was in my junk folder unfortunately! 😖 I don't have f yet, will have to find it and try this out... I am confused tho... why is this exclusive? Meaning, why can't Mp3tag display both the raw popm values, and the 3 app specific ones simultaneously? In other words, if I have a raw popm column, and a winamp column, why can't a result populate in both at the same time? Thanks again for doing this... I have been considering redoing all my ratings, which is no small task, esp if I implement half stars. ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [May 3, 2021, 4:57pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/47 "2021-05-03T16:57:19Z")
> [@MrSinatra](#): > > why is this exclusive? Meaning, why can't Mp3tag display both the raw popm values, and the 3 app specific ones simultaneously? Each tag field in Mp3tag really represents a field in the file's tag. So adding something like you've proposed would require Mp3tag to observe each of the field changes and populate any of the changes to derived fields. This is something I won't implement in Mp3tag. ---
**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\ **Post date:** [June 2, 2021, 4:57pm UTC](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847/48 "2021-06-02T16:57:36Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. [Previous page](https://community.mp3tag.de/t/popularimeter-tag-fails-in-2-48c/11847.md?page=2)