View Issue Details

IDProjectCategoryView StatusLast Update
0003078MMW v4Playlist / Searchpublic2007-08-17 19:53
Reporterjiri Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Fixed in Version3.0 
Summary0003078: Add new filters/query types - those that were in MM 2.5
DescriptionIn MM 2.5 we had an option to filter Artist and Album nodes according to number of their tracks (e.g. show Albums with >= 8 tracks). In MM 3.0 we have much advanced filtering functionality, but these specific filters are missing because they aren't part of Advanced Queries - this should be implemented. Namely:

1. 'Artist Tracks' (number of tracks of given Artist)
2. 'Album Tracks' (number of tracks of given Album)
3. 'Artist Albums' (number of albums of given Artist)

Each should have standard operators (=, <, >, <=, >=).
Additional InformationTechnical note: Since SQL for these operation could be quite time consuming (and for some other reasons too) I added fields calculated by triggers to tables Artist and Albums: Artists.Tracks, Artists.Albums, Albums.Tracks in build 1037. Therefore a very simple and fast queries can be made.

Technical note 2: In memory comparisons will be quite problematic. E.g. this scenario: User has filter (Album with >5 tracks) and scans new tracks, while the first 5 tracks of album are scanned, they shouldn't be shown (e.g. when user is in Title node), but as soon as 6th track is scanned, suddently all the tracks of the album should be shown. I'm not sure if we can make anything better, but I'd suggest to ignore there operators for in-memory query handling and only support them for SQL queries - i.e. user would see correct result only after pressing F5 key, not on-line.
TagsNo tags attached.
Fixed in build1060

Relationships

has duplicate 0001986 closedjiri Advanced AutoPlaylists/Search: Ability to find tracks from 'full' albums 

Activities

jiri

2007-05-30 14:09

administrator   ~0009215

When this is finished, Rusty should review the wording and positions of the query operators.

rusty

2007-06-15 04:24

administrator   ~0009404

Last edited: 2007-06-15 09:44

Re-opening for cosmetic tweaks:

1. Grammar changes:
'Artist Tracks' --> '# Tracks by Artist'
'Album Tracks' --> '# Tracks in Album'
'Artist Albums' --> '# Albums by Artist'

2. Default operator changes:
In all cases the default operator should be '>='

3. Order in the query list:
These queries should appear after 'Tempo' and before 'Comment'

4. I also noticed a functional problem, but I'm not sure if it's fixable:
-If the user adds a criterion such as '# Tracks by Artist' >=5, then, when filtering is enabled, there are often situations where a given artist will only have 3 tracks displayed, the reason being that the criteria of '# Tracks by Artist' >=5 is examined independently of the other criteria. This shouldn't be done as it yields results that can be confusing. I think that users would expect is that these criteria are performed on the result set of criteria that preceded them. Let me know what you think.

jiri

2007-06-15 09:55

administrator   ~0009420

4.
 A. No, this isn't easily fixable, at least in a way that would work fast.
 B. Although I understand that it could be confusing sometimes the way it's currently implemented, I'm not sure if it's really better the other way. It's about how the condition is understood, I see it as looking for Artists that have >5 tracks in my Library, not Artists that have >5 tracks under given conditions.

The rest if for Ludek...

Ludek

2007-06-15 11:33

developer   ~0009423

1,2,3 - fixed in build 1042.

rusty

2007-06-18 16:11

administrator   ~0009484

Verified 1044.

jiri

2007-08-09 15:25

administrator   ~0010085

'# Albums by Artist' doesn't work well, the results are incorrect, as can be tested by using some mutli-artists album. It's caused by the fact that the query links over ArtistSongs table, while it should be over ArtistsAlbums table.

Ludek

2007-08-14 09:34

developer   ~0010127

I still hasn't been able to find out what Jiri means by "'# Albums by Artist' doesn't work well, the results are incorrect"

After a discussion with Jiri I found out that Jiri means that it should work like '# Albums by Album Artist' instead of '# Albums by Artist'.

So I fixed it in build 1060.
Note: The field may want to be renamed to '# Albums by Album Artist' now, but in most cases user can't notice a difference and the title would be too long.

rusty

2007-08-17 19:52

administrator   ~0010183

Verified 1060.