MinimServer Forum

Full Version: Displaying half-star ratings
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
(17-10-2023 20:02)simoncn Wrote: [ -> ]I am expecting this to be straightforward to implement. If there are no unexpected problems, it should be available within the next month or so.
That's great! It sounds like I have the perfect project in the wind down to Christmas. I'll keep an eye out for the change and pick all this up again then. I'll subscribe to this thread so if there are any bumps in the road I'd appreciate a heads up.

(17-10-2023 20:02)simoncn Wrote: [ -> ]I have been able to reproduce this problem and do some investigation. Unfortunately it will not be simple to fix. There are two separate issues. One of these is fairly easy to fix but the other will need a lot of careful thought to fix it in a way that doesn't cause problems for any existing user configurations.
I've since found customised icons, so I'll use these and then the stars in index values so don't waste any more time on this on my account. I'll likely be on Synology anyway.

(17-10-2023 20:02)simoncn Wrote: [ -> ]You could change the platform default charset (it's a Windows setting) but I don't recommend this because it could have unexpected side-effects and would only fix one of the two issues.
I had been trying to change the Java environment with '-Dfile.encoding=UTF-8'. I found a post that increased available memory size but I couldn't find the right location to place the options in Windows.
(17-10-2023 20:02)simoncn Wrote: [ -> ]I have been able to reproduce this problem and do some investigation. Unfortunately it will not be simple to fix. There are two separate issues. One of these is fairly easy to fix but the other will need a lot of careful thought to fix it in a way that doesn't cause problems for any existing user configurations.

I have been able to find a solution for this that adds support for UTF-8 in profile files while allowing existing profiles that use Windows-1252 to continue working.

(18-10-2023 08:40)DanielB Wrote: [ -> ]I had been trying to change the Java environment with '-Dfile.encoding=UTF-8'. I found a post that increased available memory size but I couldn't find the right location to place the options in Windows.

I suggest you hold off attempting to do this. It will not completely fix the problem and the results could be unpredictable.
(18-10-2023 17:25)simoncn Wrote: [ -> ]I have been able to find a solution for this that adds support for UTF-8 in profile files while allowing existing profiles that use Windows-1252 to continue working.
My friend said the support here would be great. He wasn't wrong!

(18-10-2023 17:25)simoncn Wrote: [ -> ]
(18-10-2023 08:40)DanielB Wrote: [ -> ]I had been trying to change the Java environment with '-Dfile.encoding=UTF-8'. I found a post that increased available memory size but I couldn't find the right location to place the options in Windows.
I suggest you hold off attempting to do this. It will not completely fix the problem and the results could be unpredictable.
Happy to leave well alone Smile
Support for mapping the Rating tag to upnp:rating is now available in MinimServer update 241. This update also fixes the problem with some Unicode characters in property values not being handled correctly on Windows.
(31-10-2023 11:47)simoncn Wrote: [ -> ]Support for mapping the Rating tag to upnp:rating is now available in MinimServer update 241. This update also fixes the problem with some Unicode characters in property values not being handled correctly on Windows.
Thank you it works, but I didn't expect it to.

I tried FLAC with values 20, 40, 60, 80, 100 and MP3 with 1-255 and thought MinimServer would map them to 1-5 (because of below) but it didn't.

(03-02-2023 23:15)simoncn Wrote: [ -> ]The mapping from POPM to RATING is fixed and cannot be changed. It is designed to handle different schemes for how the 1-255 range is used by different tagging programs and produce a reasonable 1-5 value.
Should I be seeing mapping?
MediaMonkey stores 1-5 in MP3 and 20,40,60,80,100 in FLAC and I see those values in MinimServer if I index rating.

foobar stores 1-5 in POPM and 6-255 in TXXX.rating in MP3 and 20,40,60,80,100 in FLAC, and I see those values again.

I can work either way, I'm just confused because of the previous discussion in the posts.
Please see Note 1 in this section for a description of how the mapping works. It is only performed for POP/POPM frames in ID3v2 tags when no TXX/TXXX:RATING frame is present. Other tagging formats (such as in FLAC files) use a RATING tag and there is no mapping for this.
(31-10-2023 18:53)simoncn Wrote: [ -> ]Please see Note 1 in this section for a description of how the mapping works. It is only performed for POP/POPM frames in ID3v2 tags when no TXX/TXXX:RATING frame is present. Other tagging formats (such as in FLAC files) use a RATING tag and there is no mapping for this.
That makes sense.

So if we're dealing with the standards (ignoring half-stars etc) then the logic to map to 5 stars from various sources would be (MP3 and FLAC):
1 and 20: 1 Star
2,64 and 40: 2 Stars
3,128 and 60: 3 Stars
4,196 and 80: 4 Stars
5,255 and 100: 5 Stars

Taking into account an already converted MP3 rating (by MinimServer) as well as the raw values.

Thank you so much.
It is a bit more complex than this because different tagging programs (MediaMonkey, WinAmp, Windows Media Player and JRiver) use different POPM numbers to represent the various star ratings. See this post for how MinimServer is mapping these values.
I was recommended BubbleUPnP and it's far superior to the MediaMonkey app so I was hoping that the developer would be able to add ratings.
My lookup rules was an attempt at the logic they could implement to map ratings to stars without worrying about the format (MP3/FLAC). Whilst they could use the Jriver mapping, MinimServer sends 1-5 so this wouldn't work.

Maybe MinimServer should send the raw number to the control point instead of the mapped value and use the mapped value for use within MinimServer?
The mapping happens before anything is sent to the control point. From that point on, the POPM value (if there was one) is no longer available.

What is the problem with letting MinimServer do the mapping from POPM (if applicable) and using only mapped values (1 to 5) in your tag update file?

BubbleUPnP is a control point, not a tagging program.
Pages: 1 2 3 4
Reference URL's