My music collection (almost completely in flac) is stored on a QNAP together with asset upnp (Version: R2024-09-23 [Linux-x64]) as music server for different devices via local network (e.g. Volumio; Apple)
Maintenance of my cllection (tagging, rating) is done via network by media monkey („MM“) on a pc.
With regards to star rating (1-5) by trying out I’ve learned, MM stores the star rating for flacs in the tag „rating“ (each star counts 20; thus up to 100 for five stars; half-stars also excist, counting 10). Generally I use full stars for rating, but also 0,5 and 1,5 stars for special purposes. Using mp3tag I can see those numbers in the tag „rating“, also via windows file properties / id tags.
As asset offers this, I want to browse my collection also via rating. As far as I can see, asset reads the rating values, but interprets it differently.
Looking for a workaround I created a separate asset instance with a small music collection. There I added in „User Rename List (Display / Tag Mapping)“:
rating:=20:=1
rating:=40:=2
rating:=60:=3
rating:=80:=4
rating:=100:=5
In my testing instance this works well up to two stars. Titles rated with 0,5 / 1 star can be browsed in Rating „*“; 1,5 / 2 stars in „**“. But Titles with three or more stars are only shown under „*&above“ and also under „Not rated“ but not under the correct number of stars.
Could you please explain, how asset interprets the numbers stored in the rating tag (in my case 10 up to 100) with regards to the stars rating 1-5 and give me a hint for the mapping above mentioned.
Maintenance of my cllection (tagging, rating) is done via network by media monkey („MM“) on a pc.
With regards to star rating (1-5) by trying out I’ve learned, MM stores the star rating for flacs in the tag „rating“ (each star counts 20; thus up to 100 for five stars; half-stars also excist, counting 10). Generally I use full stars for rating, but also 0,5 and 1,5 stars for special purposes. Using mp3tag I can see those numbers in the tag „rating“, also via windows file properties / id tags.
As asset offers this, I want to browse my collection also via rating. As far as I can see, asset reads the rating values, but interprets it differently.
Looking for a workaround I created a separate asset instance with a small music collection. There I added in „User Rename List (Display / Tag Mapping)“:
rating:=20:=1
rating:=40:=2
rating:=60:=3
rating:=80:=4
rating:=100:=5
In my testing instance this works well up to two stars. Titles rated with 0,5 / 1 star can be browsed in Rating „*“; 1,5 / 2 stars in „**“. But Titles with three or more stars are only shown under „*&above“ and also under „Not rated“ but not under the correct number of stars.
Could you please explain, how asset interprets the numbers stored in the rating tag (in my case 10 up to 100) with regards to the stars rating 1-5 and give me a hint for the mapping above mentioned.
Comment