# Possible Misinterpretation of the Popularimeter Tag in v2.54 **URL:** https://community.mp3tag.de/t/possible-misinterpretation-of-the-popularimeter-tag-in-v2-54/14296 **Category:** Fixed Bugs **Tags:** bug-fixed **Created:** [January 1, 2013, 4:31pm UTC](https://community.mp3tag.de/t/possible-misinterpretation-of-the-popularimeter-tag-in-v2-54/14296 "2013-01-01T16:31:36Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![Zamiel](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/z/ec9cab/32.png) [@Zamiel](https://community.mp3tag.de/u/Zamiel) #### Post date: [January 1, 2013, 4:31pm UTC](https://community.mp3tag.de/t/possible-misinterpretation-of-the-popularimeter-tag-in-v2-54/14296/1 "2013-01-01T16:31:36Z")
Hello devs. Thanks for all your work; Mp3tag is a great product! After playing around with a hex editor, I've found that this is how Mp3tag writes a "rating mm" tag, in hex: Value of 1 (emulating a "1 star rating") = 17 (23 in decimal) Value of 2 (emulating a "2 star rating") = 40 (64 in decimal) Value of 3 (emulating a "3 star rating") = 80 (128 in decimal) Value of 4 (emulating a "4 star rating") = C4 (196 in decimal) Value of 5 (emulating a "5 star rating") = FC (252 in decimal) This convention for 1 and 5 seem non-intuitive. For example, MusicBee uses the following convention, which seems more logically consistent: 1 = 01 (1 in decimal) 2 = 40 (64 in decimal) 3 = 80 (128 in decimal) 4 = C4 (196 in decimal) 5 = FF (255 in decimal) Is there some particular reason why Mp3tag is configured in this manner? --- _[View the full topic](https://community.mp3tag.de/t/possible-misinterpretation-of-the-popularimeter-tag-in-v2-54/14296)._