Re: Multiple Artist Indexing Probs with WMP10

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Mike Williams [MVP] (mikew_at_Nospam.mvps.org)
Date: 01/03/05


Date: Tue, 04 Jan 2005 10:43:17 +1100
To: fabiospark <fabiospark@discussions.microsoft.com>

fabiospark wrote:
> Please check this:
>
> I put three different names in Contributing artist field separated by a
> semicolon (;) "First name; Second name; Third name"
> Ok, now I can see three nodes in the Contributing artist tree on the left
> pane. Clever, I say.
> If I create an autoplaylist with just one name - whichever - I can find
> those tracks.
> Now I want to create a playlist to find all the tracks with the first two
> names I put in the field so I do:
>
> "Field Contributing artist contains: "First name"
> "Field Contributing artist contains: "Second name"
>
> How many tracks I will find? No one!
Same result for me. Fails for both "contains" and "is".

That's kind of consistent with the bug in having multiple search clauses
on different fields looking for the same name. Item #34 here:
http://msmvps.com/thinice/articles/16084.aspx

I'm starting to see why delaying WinFS integration in Longhorn is a good
thing since WMP library features represent similar features to what
would be found generically in the Windows file-system in the future.

> Then I try putting "First name/ Second name/ third name" instead of using (;).
> Now I can see just the node "First name/ Second name/ Third name" in the
> tree but when I create the autoplaylist like the one above I can find the
> tracks.
>
> Does anybody know a way to save the clever behaviour of the tree using (;)
> but without having to loose the autoplaylist retrieving feature?

The closest you might get it to do the query as

Music in my Library
  Containing Artist1
+
Music in my Library
  Containing Artist2

That gets you the union of the entries, not the desired intersection.
Intersecting filter cases don't appear to have been tested.



Relevant Pages

  • Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2
    ... no-one apparently tested all the features together ... I pulled again on July 20 and all the bsg code was in mainline. ... The initial bsg submit went via the block git tree ... ... window git trees) and nothing else. ...
    (Linux-Kernel)
  • Re: RFD: Kernel release numbering
    ... practice, is to put "more intrusive" features into -mm first, and only ... -mm would be the 'feature tree'. ... SUSE LINUX Products GmbH - A Novell Business ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: My thoughts on the "new development model"
    ... |>of the features they need. ... | could have a permanent 4-digit kernel version. ... The current high-speed development model could be reused as ... but usable tree instead of a flat out unstable tree (as ...
    (Linux-Kernel)
  • Re: Yo Snarl!
    ... > Methinks a '47 offset top triple tree would've been a better/closer ... > Another thing to consider, while yer in there, is that th' new style ... I can do the holes and locate them relative to one another no ... problem but the other features are hard to get exact. ...
    (rec.motorcycles.harley)