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

Add a ~#playcount equalizer play order plugin. #1626

merged 2 commits into from Jul 12, 2016


None yet
4 participants

ZDBioHazard commented May 30, 2015

This shuffle play order plugin selects the next song weighted inversely by ~#playcount, attempting to equalize the ~#playcount of all songs in the playlist.

This might be useful when you have new songs that you aren't tired of yet; They will be played more often than songs you've had for a while and have heard many times.


This comment has been minimized.


declension commented Jun 3, 2015


Otherwise looks like an interesting idea, thanks.


This comment has been minimized.


pschwede commented Jan 29, 2016

When merging this to the trunk, it would make sense to rename the "Weighted" shuffle into something more concrete as well, e.g. "by rating".


This comment has been minimized.


CreamyCookie commented Jul 9, 2016

Any news on this @ZDBioHazard ? Sounds like an interesting idea!

@ZDBioHazard ZDBioHazard force-pushed the ZDBioHazard:plugin-playcounteq branch 2 times, most recently from 1ee0469 to 185ab5d Jul 12, 2016


This comment has been minimized.


ZDBioHazard commented Jul 12, 2016

Oh, sorry, I totally forgot this PR was still open.

I went ahead and reapplied this on master and cleaned it up a little bit. let me know if there is anything that still needs to be done. :)

@declension declension merged commit 7741ebe into quodlibet:master Jul 12, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed

This comment has been minimized.


declension commented Jul 12, 2016

Thanks @ZDBioHazard

@ZDBioHazard ZDBioHazard deleted the ZDBioHazard:plugin-playcounteq branch Nov 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment