# \[F\] "MM Rating" field needs updating
**URL:** https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [June 23, 2009, 5:57pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493 "2009-06-23T17:57:36Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@Mizery\_Made](https://community.mp3tag.de/u/Mizery_Made)
#### Post date: [June 23, 2009, 5:57pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/1 "2009-06-23T17:57:36Z")
During the MediaMonkey 3.1 development cycle, some changes were made to MediaMonkey's Ratings values to fall more in line with WMP/Windows/etc. As a result, this feature in your program has been thrown off. Some ratings in MM appear lower in your program, while other MM ratings aren't shown under the MM Rating field, but rather as a normal POPM entry.
Seeing as 3.1 has been officially released and this change is now out in the wild, you might want to look into adjusting things within MP3Tag, if you plan to continue to support this feature. It doesn't contain information about what the values were changed to, but the relevant MediaMonkey bug entry for this change is [here](http://www.ventismedia.com/mantis/view.php?id=3143), I believe.
---
### Author:  [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [June 24, 2009, 8:05pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/2 "2009-06-24T20:05:50Z")
Interesting. I checked it, these should be the new values Florian:
252
242
196
186
128
118
64
54
23
13
0
---
### Author:  [@Mizery\_Made](https://community.mp3tag.de/u/Mizery_Made)
#### Post date: [June 24, 2009, 8:36pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/3 "2009-06-24T20:36:30Z")
Dano looks to be correct.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [June 26, 2009, 6:55am UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/4 "2009-06-26T06:55:13Z")
Thanks dano for the new values. I'll update them with the next build.
Kind regards,
Florian
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [June 29, 2009, 3:30pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/5 "2009-06-29T15:30:25Z")
> I'll update them with the next build.
Er, Florian, PLEASE do not break compatibility for people remaining on previous MM versions.
If Mp3tag is to accomodate MM's new back-incompatible ratings levels, it should be WITHOUT messing with the existing %rating mm%. E.g. should be by a new %rating mm 2%.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [June 30, 2009, 1:09pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/6 "2009-06-30T13:09:12Z")
Sorry, but I don't plan to maintain multiple versions of that field.
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [June 30, 2009, 2:43pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/7 "2009-06-30T14:43:10Z")
How then Florian will you avoid your proposed change messing up the majority of MM users - those on previous versions?
---
### Author:  [@Mizery\_Made](https://community.mp3tag.de/u/Mizery_Made)
#### Post date: [June 30, 2009, 3:54pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/8 "2009-06-30T15:54:12Z")
> [@chrisjj](#):
>
> How then Florian will you avoid your proposed change messing up the **majority** of MM users - those on previous versions?
Proof?
It's not like they would be unable to edit ratings anymore. They would be available just as they appeared before Florian implemented the MM Rating 'field,' as standard POPM entries. Florian doesn't _have_ to even offer this feature, but he chose to. 3.1 has been released and is the official version now, as a result, I feel if Florian wants to continue to support this field, it should reflect the current official build, not an outdated one that _some may_ continue to use.
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [June 30, 2009, 4:30pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/9 "2009-06-30T16:30:19Z")
> It's not like they would be unable to edit ratings anymore.
No-one suggested that.
> They would be available just as they appeared before Florian
> implemented the MM Rating 'field,'
That is no use or relevence to users of Rating MM.
> Florian doesn't _have_ to even offer this feature
He's not 'offering' it. It is a defined facility of Mp3tag. See [https://docs.mp3tag.de/mapping](https://docs.mp3tag.de/mapping) .
> I feel if Florian wants to continue to support this field, it should
> reflect the current official build
That would break compatibility with existing scripts. I.e. the same script on the same rating values would give different output.
I wonder if you'll be here proposing compatibility breakage _every_ time the MediaMonkey developers change their mind about their official ratings coding...
---
### Author:  [@Mizery\_Made](https://community.mp3tag.de/u/Mizery_Made)
#### Post date: [June 30, 2009, 4:52pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/10 "2009-06-30T16:52:41Z")
Yes, I'll be here proposing a change every time a change in MM's ratings values _make it into the official release_. It's not as if I was here months ago when the change was first implemented into the Betas, only when 3.1 went official and was released to the general public did I come here and suggest this change.
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [June 30, 2009, 5:13pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/11 "2009-06-30T17:13:45Z")
> It's not as if I was here months ago when the change was first implemented into the Betas,
Again, no-one suggested that.
> Yes, I'll be here proposing a change every time a change in MM's ratings values
> _make it into the official release_.
I am sad to see you MediaMonkey people are not satisfied to keep breakages of back-compatability to your own product.
---
### Author:  [@Mizery\_Made](https://community.mp3tag.de/u/Mizery_Made)
#### Post date: [June 30, 2009, 5:16pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/12 "2009-06-30T17:16:21Z")
If you have such a problem with MediaMonkey, perhaps it would just be easier for you to discontinue use of it?
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [June 30, 2009, 7:49pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/13 "2009-06-30T19:49:09Z")
You are wrong.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [July 12, 2009, 5:22pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/14 "2009-07-12T17:22:33Z")
I've updated the internal mapping to MediaMonkey 3.1 values with the current [Development Build](http://developer.mp3tag.de).
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:01pm UTC](https://community.mp3tag.de/t/f-mm-rating-field-needs-updating/8493/15 "2018-12-28T14:01:26Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.