Bug report: MediaMonkey 5 star rating interpreted as 4 stars in MyTunes

[Bill F]

Hello,

I have a bug to report.  To manage and play my music, I am using MyTunes Pro (version 1.3 build 3219) on my Android phone, MediaMonkey (version 4.0.6.1501) on my PC, and PlayerPro (v4.22) on my phone as well.  I use MediaMonkey and PlayerPro to rate music and MyTunes Pro for its playlist management and replay gain abilities.  (All of these versions should be the latest versions of these apps at this time.)

While MyTunes Pro does a great job of recognizing ratings from both Winamp and MediaMonkey, it has a bug where a song rated 5 stars in MediaMonkey shows up as 4 stars in MyTunes Pro.  This affects songs rated 5 stars in both MediaMonkey as well as PlayerPro (using its MediaMonkey rating system).

I did some research and it looks like MediaMonkey might use 252 as its POPM rating for 5 stars .  I'm guessing that MyTunes Pro might expect a POPM rating of 255 for 5 stars.

MyTunes Pro does recognize all Winamp ratings correctly, however I switched to MediaMonkey from Winamp on my PC recently and really don't want to go back.

Thank you for making this great app.  On my phone, it works together with PlayerPro very well.  Aside from this rating glitch, I am very happy with it:  it has definitely been worth more than $3 to me. :)

Regards,

Bill

[whitestarlogic]

You're right - MyTunes expects a POPM value of 255 for 5 stars. I based the interpretation of those values on Windows Media Player, which uses 1, 64, 128, 196, and 255. I'm working on some bug fixes now and I can change it to recognize a wider range of values. Thanks!

The actual formula it uses is: stars = (popm + 1) / 64 + 1. That formula works with winamp and WMP

[Bill F]

Fantastic!

I guess it's a bit annoying how MediaMonkey chose to use 252 instead of 255 for 5 stars, even though it follows Winamp and WMP for 2, 3, and 4 stars.  In any case, I'm very much looking forward to the next release.

Many thanks!

Bill

[whitestarlogic]

The new release posted today should fix this issue.