Hi Steven, appreciate the support.
Unfortunately, patch35 didn't change the situation. Also, this seem to be the same patch files you had provided May 20, last year. I had tried this already.
Let me demonstrate again: I created a "test" rating tag from scratch and used it on a single file:
In "Case 1" I set a value by clicking 4 "test" stars in the track list.Result: "4" stars in the track list, numeric value "80" in the tag editor, "5" stars in the column browser (which is an error).
=> The column browser cannot display the value "80". It needs values between 0 and 5 to operate correctly.
In "Case 2" I set a value of "3" in the tag editor.Result: "3" stars in the track list, numeric value "3" in the tag editor (of course), "3" stars in the column browser
=> column browser works correctly this way, i.e. in numeric range 0 to 5.
As a sidenote: It is remarkable, that the rating field in the track list shows the correct number of stars in "0 to 5" and also in "0 to 100" range.
I use the custom rating tag that I created in my library to rate "danceability" like case 2. This way the column browser works properly.
However and as previously posted, it is not possible to create a library filter with that rating tag. Library rating filter needs the "100" value range.
So, in my opinion, it is the custom rating in the
column browser, that should be changed to operate on 0 to 100 range.
Everything else works fine and in good harmony.
Thanks,
Wolfgang
CASE 1:
CASE 2: