starred/jellyfin

Fork 0

mirror of https://github.com/jellyfin/jellyfin.git synced 2026-01-23 23:20:51 +01:00

Music Star Rating #734

New issue

Closed

opened 2025-12-21 17:15:14 +01:00 by backuprepo · 5 comments

backuprepo commented

2025-12-21 17:15:14 +01:00

Owner

Originally created by @WisdomCode on GitHub (Jun 3, 2019).

Describe the feature you'd like
Beside the now common "favorit" button for organizing your favorite music, there is also the star rating, giving singular songs a number of stars between 1 and 5.
I would love to see support for this more sophisticated way of rating your music.
The stars can even be saved inside the mp3 file, so it would be nice to directly get them from there when scanning. For a supporting scanner, you may refer to banshee or ampache. For a working Tag editor fully supporting it, you may refer to eyed3. From their
Code, I concluded that this specific Tag is saved under the value 'POPM' (see Line 48). If you want help on this task, I'd be glad to help.

Originally created by @WisdomCode on GitHub (Jun 3, 2019). **Describe the feature you'd like** Beside the now common "favorit" button for organizing your favorite music, there is also the star rating, giving singular songs a number of stars between 1 and 5. I would love to see support for this more sophisticated way of rating your music. The stars can even be saved inside the mp3 file, so it would be nice to directly get them from there when scanning. For a supporting scanner, you may refer to banshee or ampache. For a working Tag editor fully supporting it, you may refer to eyed3. From their [Code](https://github.com/nicfit/eyeD3/blob/857a56d976bac05b65c3ce9f7323dbc215deb348/src/eyed3/id3/frames.py), I concluded that this specific Tag is saved under the value 'POPM' (see Line 48). If you want help on this task, I'd be glad to help.

backuprepo

2025-12-21 17:15:14 +01:00

closed this issue
added the
feature
label

backuprepo commented

2025-12-21 17:15:19 +01:00

Author

Owner

@ArnaudB88 commented on GitHub (Jun 8, 2019):

I would also love this feature. For me, it is a requirement to start using this system.

But I think saving the score should be done in the database so different users can rate different on one item.

@ArnaudB88 commented on GitHub (Jun 8, 2019): I would also love this feature. For me, it is a requirement to start using this system. But I think saving the score should be done in the database so different users can rate different on one item.

backuprepo commented

2025-12-21 17:15:21 +01:00

Author

Owner

@WisdomCode commented on GitHub (Jun 8, 2019):

This is actually also possible in the metadata. There can be multiple ratings, they are saved under a name, email or similar value. However, I can see that point, but for keeping those values for interoperability, some way for writing and reading those values (it may be an api or something, not necessarily a default option) would be really nice.

@WisdomCode commented on GitHub (Jun 8, 2019): This is actually also possible in the metadata. There can be multiple ratings, they are saved under a name, email or similar value. However, I can see that point, but for keeping those values for interoperability, some way for writing and reading those values (it may be an api or something, not necessarily a default option) would be really nice.

backuprepo commented

2025-12-21 17:15:23 +01:00

Author

Owner

@kyriakosbrastianos commented on GitHub (Jun 12, 2019):

Just use the vorbis comment way that are simply named "RATING" and a value from 1 to 5 or 1 to 10. This kind of tag names are also recognized from kodi and other players. I see no reason to add name, email and other no standard values and make it incompatible to be read from other players.

@kyriakosbrastianos commented on GitHub (Jun 12, 2019): Just use the vorbis comment way that are simply named "RATING" and a value from 1 to 5 or 1 to 10. This kind of tag names are also recognized from kodi and other players. I see no reason to add name, email and other no standard values and make it incompatible to be read from other players.

backuprepo commented

2025-12-21 17:15:25 +01:00

Author

Owner

@WisdomCode commented on GitHub (Jun 13, 2019):

The Popularity is a standard way to save the star rating, I know at least 3 player working with those and its part of the original definition of idv3. It allows for multiple ratings on one song, like @ArnaudB88 requests. For the exact usage of naming etc., you may refer to those players using it (banshee, ampache etc).
However, if this is a more popular way to save star rating, then this may be a better way to go. Maybe you could elaborate and explain in more detail how this works? Are these tag names recognized by emby already? What other players support it other than Kodi?

@WisdomCode commented on GitHub (Jun 13, 2019): The Popularity is a standard way to save the star rating, I know at least 3 player working with those and its part of the original definition of idv3. It allows for multiple ratings on one song, like @ArnaudB88 requests. For the exact usage of naming etc., you may refer to those players using it (banshee, ampache etc). However, if this is a more popular way to save star rating, then this may be a better way to go. Maybe you could elaborate and explain in more detail how this works? Are these tag names recognized by emby already? What other players support it other than Kodi?

backuprepo commented

2025-12-21 17:15:27 +01:00

Author

Owner

@jellyfin-bot commented on GitHub (Jul 29, 2019):

We are moving all feature and enhancement requests to our new Fider platform here. This new platform lets people vote on and better manage such requests.
This request now lives here.

@jellyfin-bot commented on GitHub (Jul 29, 2019): We are moving all feature and enhancement requests to our new Fider platform [here](https://features.jellyfin.org/). This new platform lets people vote on and better manage such requests. This request now lives [here](https://features.jellyfin.org/posts/9/music-star-rating).

backuprepo referenced this issue

2025-12-22 06:47:51 +01:00

[PR #734] [MERGED] Fix more analyzer warnings #8295

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#734

No description provided.

Rows
Columns