Bug 199479 - dynamic playlist contributions from different filters are not forced to sum to 100%
Summary: dynamic playlist contributions from different filters are not forced to sum t...
Status: RESOLVED DUPLICATE of bug 177627
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.1.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-08 22:38 UTC by doc.evans
Modified: 2009-07-08 23:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description doc.evans 2009-07-08 22:38:19 UTC
Version:           2.1.1 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-13-generic

The interface for generating dynamic playlists is, frankly, incomprehensible.

It seems like a fundamental truism that, since the rubric for "Proportional bias" is "match a certain portion of the playlist to a value", then if one sets the slider for a filter to X%, then X% of the resulting playlist will be selected by that filter.

But that's not at all what happens. Each filter can be set to any value, so that the sum, instead of being 100% can be anything... and it's completely opaque what the final contribution of each filter will be to the playlist.

One can imagine several things that the underlying code *might* do if the sliders add up to something different than 100%, but the point is that:
  (a) there's no way to know which of those possibilities the code actually implements (and in fact, so far all my guesses have been wrong... I still haven't figured out what the code does, despite trying rather hard to deduce the underlying algorithm from the output playlists); 
  (b) it's simply completely unintuitive to have a total add up to anything other than 100%.
Comment 1 Mikko C. 2009-07-08 23:22:12 UTC

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