After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 638966 - Score should also be influenced by play count
Score should also be influenced by play count
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: general
unspecified
Other Linux
: Normal enhancement
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2011-01-08 06:49 UTC by Christoph Wolk
Modified: 2020-03-17 08:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christoph Wolk 2011-01-08 06:49:14 UTC
Banshee automatically determining track score based on playing or skipping is a very good feature. I feel the current measure is not optimal, though.

Currently, the measure works out to the sum of play percentages divided by the number of total plays. This means that a song that the user has completely listened to once has the same score as a song the user has listened to completely ten times, and a higher score than a song the user has listened to fifty times but skipped once; however, the user clearly likes the latter two songs better.

One solution would be to divide by total number of plays + 1; this way each complete play (at least for quite some time) would raise the score.
Comment 1 André Klapper 2020-03-17 08:48:47 UTC
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.