Bug 156585 - save ratings in music files instead of database
Summary: save ratings in music files instead of database
Status: RESOLVED DUPLICATE of bug 139597
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.8
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-24 19:47 UTC by Thomas Reitelbach
Modified: 2008-10-30 17:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Reitelbach 2008-01-24 19:47:47 UTC
Version:           1.4.8 (using 3.5.8 "release 33.2" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.7-default

I wish, Amarok could save song ratings inside the mp3/ogg files instead of the database.

This would make it possible to save ratings even if the database gets damaged or lost. Or I could share my ratings with other family members, which is impossible when they are only saved in the database.

Of course I know that there are problems: When I share my rated music file with someone else he probably would apply a completely different rating to this song. Maybe I like this song very much, but my friend doesn't. Do you see a solution?

Currently I have rated all my songs, which enables me to use smart playlists for parties where I only want to play songs with a higher rating than 3.5. Then I wanted to put my collection on a USB stick and use them at a party of a friend. But of course the rating information was missing and I was unable to use a cool smart playlist :-(

Now I save myself from this dilemma by typing the rating into the "comment" field of the files using some string like "rating=3.5" and such. But this is not very convenient and it forces me to sync my comments with the database manually (which is very hard work).

Any Ideas to solve this issue?
Comment 1 Tristan Miller 2008-10-30 16:00:49 UTC
This appears to be a duplicate of Bug 139597.
Comment 2 Mark Kretschmann 2008-10-30 17:37:25 UTC

*** This bug has been marked as a duplicate of bug 139597 ***