Allow halve stars rating

Bug #973145 reported by Daniel Schürmann
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Mixxx
New
Wishlist
Unassigned

Bug Description

Whishlist:
Some mediaplayers like Clementine allow to rate halve stars. To display this rating correct in Mixxx, we schould allow handle halve stars.

An Ideal solution should be working without database schema upgrade and compatible to existing ratings and current Mixxx versions.

Also we should consider if we should allow rating halve stars within Mixxx.

Tags: metadata
Changed in mixxx:
importance: Undecided → Wishlist
Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

This was discussed when the rating system was introduced and we had decided that more than 6 (if you count 0 stars) levels of granularity is too many for DJing purposes. (In fact, some people think we shouldn't even have 5 stars since most DJs rate tracks as one of junk, warm-up, peak-time/floor-filler, cool down.)

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

No database schema change is needed since SQLite treats "INTEGER" as just a type hint. You can store a float in an INTEGER field.

We've hashed this to death on mixxx-devel :)
http://<email address hidden>/msg03273.html

I think stars are a common idiom but they fall short for some of the reasons Albert mentions in his post above. I think certain ways that people use them could be better served by crates.

If you try to use ratings to say "how much do I love this song" I've found that my ratings vary based on my mood, the day of the week, and the alignment of the cosmos :). Having 10 levels of granularity is just permitting myself to throw more noise into the rating system.

If you don't use them for rating how much you love the song but rather as a way to categorize tracks (e.g. warm-up, peak-time, must-play, etc.) then that's exactly what we made crates for. Though we fell short on our implementation of crates compared to Albert and my original vision for them. Crates are supposed to act like labels in GMail or tags in Delicious. We should finally finish the crate-delegate that shows you all the crates a track appears in so you can see those in the table view.

I think Google Music is a good model to follow. They have gotten the hint that humans are not very good at numerically quantifying a feeling like how good a track is (is this a 4.8 or a 4.9?) so their default rating system is just thumbs-up and thumbs-down or no rating. There is a Google Music "Lab" which you can turn on which enables the 5-star rating.

Revision history for this message
Kane Leja (wolfbiter) wrote :

I agree with all of the above, but can't both options (stars and thumbs) be provided? Granted rating music is more abstract than straight numbers, but I do think they serve a purpose orthogonal to thumbs in that they're useful to help quantify the overall musical quality of the song (e.g. mixing/mastering, rhythmic/harmonic complexity, etc).

"We should finally finish the crate-delegate that shows you all the crates a track appears in so you can see those in the table view."

+1 as a user: Tags would be sweet, and they're something I've always wanted in a music library.

p.s. Sorry for submitting the duplicate bug report... Next time I'll try to a better search before I post.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Here is the faq about integers in sqlite: http://www.sqlite.org/faq.html#q3

tags: added: metadata
Revision history for this message
naught101 (naught101) wrote :

FWIW, I think mix should *store* ratings as a float. Interfaces can chose what they want to do with that (e.g. you could have two skins that show it differently, and syncing to online services [ https://bugs.launchpad.net/mixxx/+bug/1741147 ] could round to what ever precision those services use).

Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6342

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.