Inconsistent rating tag format

[nintendoeats]

I've read everything I can find about the Rating tag, but what I see in practice is very inconsistent. Basically, I'm trying to use both Foobar and MM which would be fine except that MM is not using a consistent format for ratings.

For some files, it uses 1-5
For some files it uses 0-100
For some cases it writes both? I have many files where the rating field is now "4, 80".

IThe last case is the one that is really driving me crazy. At first I thought this was due to files with a mix of id3v1 and id3v2, but stripping the id3v1 from all my files did not change this behaviour. Even files from the same album (so ripped at the same time to the same format) will behave differently.

My only remaining thought is that it has gone weird because I was producing rating tags in another program using the 0-100 format. However, even if I delete the existing tags and tell MM to rewrite it's tags...it will still randomly write both.

Does anybody have any idea why it would do this?

[Lowlander]

What file type(s) are you using and which Build (Help > About) of MediaMonkey?

[nintendoeats]

What file type(s) are you using and which Build (Help > About) of MediaMonkey?

It's a mix of FLAC and MP3. In the examples I've tried, it only seems to do the multi value tag on MP3s, but I wouldn't entirely commit to that.

I can't access my computer to check ATM, but I downloaded and installed MM 3 days ago.

[nintendoeats]

The version is 2024.1.0.3113 (Portable Mode). This is running in Linux under Proton. It is the standard unregistered edition (I am currently evaluating MM).

[Lowlander]

Different file types have different tagging standards, this may be where the discrepancy comes from.

[nintendoeats]

Yeah, I know there are different standards. If it was just MP3 is one and FLAC is the other I could work with that, but these multivalued tags are really a sticking point. And again, I'm seeing files of the same format, ripped the same way, and even from the same album being tagged differently. I feel like it has to be something to do with MM behaving differently if a tag already exists.

[MiPi]

For MP3 MM writes rating only to standard POPM ID3 field, for FLAC to standard RATING field, both have range 0-100.
I do not understand, where should be that 1-5 value from, MM does not write it to these formats, maybe the other app?
Could you please create user ticket and share some samples? Ideally some before and after example, where such multiple rating values happened. Thanks.

[nintendoeats]

Yes, I will see about doing this after work.

[nintendoeats]

In going to make samples, I think I've concluded that this is not really an MM problem, but more to do with how Foobar displays the ratings field (or rather "fields" since there is more than one). I've never known Foobar to ever display tags as anything other than the raw data, but I guess I had never encountered the messed-up-ness of ratings tags before.

I verified what tags are actually set using ExifTool.

The gist of it is that if you load an untagged MP3 into MM and assign 3 stars (which edits the POPM flag), it will appear in Foobar as 3. If you do the same with the FLAC Ratings field, it will appear in Foobar as 60.

The hybrid case was what happened when a RATING field was added by Foobar, and MediaMonkey also added a POPM field.

So this is a config problem I need to figure out in Foobar, and not a MediaMonkey issue.

[MiPi]

Thanks for the info, I thought it will be something like this.