Score2Rating 3.0 review

Score2Rating is a script that converts the scores of your tracks in amaroK to ratings using some pretty accurate intervals

License: GPL (GNU General Public License) File size: 1K Developer: Firetech

0

Score2Rating is a script that converts the scores of your tracks in amaroK to ratings using some pretty accurate intervals. In future versions of Score2Rating, the intervals might become changeable.

This is mostly usable to give you a starting point for using the new rating system in amaroK 1.4 (SVN).

NOTE!

It is recommended that you back up your database (the statistics table at least) before running this script. It should do no harm, but you can never be too safe.

Note that tracks with the same score can get different ratings, this is because amaroK rounds the score that is saved in the database.

An example: If the shown score is 95 (the limit between rating 4 and 5), the database can contain anything from 94.500 to 95.499. If the "real" score is below 95 (94.500-94.999), the track will get a rating of 4, if it's above 95 (95.000-95.499), the rating will be 5.

This will happen around all the rating limits (20, 60, 85 and 95).

It is recommended that you back up your database (the statistics table at least) before running this script. It should do no harm, but you can never be too safe...

Usage:

Just start it and then click configure, and it will do everything automagically!
It will tell you tell you (using a popup in the playlist window) when it's done.

Requirements:
Ruby 1.8 (not sure about the version, 1.6 _might_ work, I didn't test it.)
amaroK 1.4* (Currently only in SVN)

What's New in This Release:
I'm an idiot. I made the script WAY to advanced from the beginning. I can't believe I didn't come to think about this earlier. Anyhow. instead of running 4 dcop calls per track (and some more), this version runs a grand total of 9 dcop calls (one per rating) to Amarok and 10 to update and close the optional progress bar KDialog. It doesn't even care about the problemous file names. On my computer with my ~1000 track music collection, this is more than 500 times faster, seriously. It's all about SQL Magic!

(This new version is tested successfully with both MySQL and SQLite, but not PostgreSQL. If you've run it successfully with PgSQL, pop me a note, preferably via email.)