New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ratings are not stored in tags (tested with mp3 and FLAC) #1461
Comments
Comment #1 originally posted by reiter.christoph on 2014-08-31T20:30:35.000Z: I can't reproduce. but I see some possible errors if the rating is set to the default rating... what do you have set as default? |
Comment #2 originally posted by joschuaga@yahoo.de on 2014-09-01T20:33:50.000Z: I have set the default (2 stars = 0.5) as the default rating. Could it have to do with using "Banshee" as the email, which really isn't an email? Maybe you could try to change your "email" and then rate something unrated and see if it really has been set. |
Comment #3 originally posted by joschuaga@yahoo.de on 2014-09-09T12:37:37.000Z: Christoph - Could you find anything? Slightly related: Is it possible to "import" or use the Ratings & Playcounts that were made by Banshee? For example I have FLAC file that has been rated the best rating and a playcount of 1. This is what it looks like if I use pprint of mutagenx: FLAC, 82.40 seconds, 44100 Hz (audio/x-flac) but these are not shown in Quod Libet. |
I'm having the same issue. QL doesn't store ratings / playcounts, neither in MP3s, nor in FLACs. My rating scale is set to 5, default rating to 0. The Email field is set to a non-standard address, but it doesn't seem to work with a proper email address either. Ratings / playcounts from banshee are displayed in the QL tag editor, but, as far as I remember, they are not picked up as such in QL. |
@lazka In my original bug report I didn't realize that I have to execute Force Write on each song for which the ratings should be stored. If I use the plugin this way, the ratings seem to be stored. So the question is: Is there a way to run a plugin whenever ratings or playcount change (I need both)? And slightly related: Can a plugin be executed whenever albums are added? I'd like to automatically add ReplayGain tags to any new albums. |
@CreamyCookie we talked about this ages ago actually. Short version: currently: no, but it's definitely a feature I'd like (especially when combined with the work in the watched-library branch (see #1315) On further digging, see #275 for that exact use case. |
Okay, this is weird. When I rate a song (The ratings and playcounts are one of the most important metadata for me. I use them for making playlists, which I then export to my USB stick.) |
Yes.. some time ago QL didn't have an "unset" state for ratings and used the default instead. |
Interesting. So, as a temporary fix, could I set the default value to something like 0.3141592653589794 in the settings, and force write my whole library, so it will also store ratings of 0.5 in the tags? Edit: Sadly that doesn't work, because after editing the config file, Quodlibet resets the default to 0.25. :( @lazka What would it take to fix this bug? Could I just replace:
with
|
Any feedback on this? |
I've added some API in ca53d77 for this |
Thanks! |
Fixes #1461: Store ratings in the tags, even if they're the default value.
Original issue 1461 created by joschuaga@yahoo.de on 2014-08-30T14:19:07.000Z:
The plugin "Force Write" and "saving rating and play count" are enabled. I use "Banshee" as the email, because I hoped that I could get my old ratings (made by Banshee) this way, but it doesn't seem to work.
- What did you try to do?
I rated something and then checked with mutagenx if the tags for rating are correctly set.
- What did you expect to happen?
I expect it to set the rating tag.
- What did happen instead?
It didn't set the rating tag. (On one mp3 file the rating and the play count was set, but it was 0 instead of the expected 255, because I voted it 4 of 4 stars.)
- Which version of Quod Libet?
3.2.1
- Which operating system including version (Ubuntu 14.04, Win7, Debian
sid)?
Ubuntu 14.04 / 64bit
The text was updated successfully, but these errors were encountered: