Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[LeoH]

When using the Search Bar using text entry, I notice that I can type, for instance: "Rubinstein Nocturnes" (the " " are just to highlight the search string) and get a list of Chopin's Nocturnes played by Arthur Rubinstein.  One can even type: "rub noc" and achieve the same result (very nice feature, btw). Of course, any sufficiently unique combination works for any choice of artist, composer, album name or track title.  Likewise, just typing "256" returns bitrates >= 256kbps, etc.  There seems to be much common sense in the parsing but after considerable exploration, I have a few questions concerning open text searching:

(1) What fields (and in what order) does MC execute the search? 
(2) Are there standard fields that are ignored?
(3) Also, custom user fields are definitely not in the search path, correct?

Many thanks,
Leo

[MrC]

This is how I believe it works.

Prior to MC17, fields that had the "Default search field" option set were searched.  With MC17, almost all stock fields are searched.  I'm not clear on which ones are not.  Order is not clear to me.

Custom fields are searched if you make them so.  Set "Default search field".

See:  http://wiki.jriver.com/index.php/File_Properties_%28tags%29

[Matt]

I think MrC answered the questions.

But I can't help but make a little sales pitch for the search box.  There is a lot of code behind that little box.

The ordering of results should be by relevance, which includes the quality of the match, the fields that match, and the number of files in the match set.

An example of a neat suggestion is searching for "jewel christmas".  It will return Jewel's Christmas album first even though the album doesn't have Jewel or Christmas in the album name.

Another neat example is that single letters often give pretty good suggestions.  For example, I have a lot of Bob Dylan.  If I type 'b', it's the first suggestion.

You can also use the search box like a pane.  For example, in an image view, start typing 'keywords'.  Then pick 'See All Values For Library Field > Keywords' from the list of suggestions.  Then you'll get a full list of keywords, just like if you had a pane view.

You can even search for program commands, like 'Pause' or 'Options...'.

[MrC]

You can even search for program commands, like 'Pause' or 'Options...'.

I didn't know about this one!  Neat.

Give "Pause" a try... no workie.  Options worked.

[Matt]

I didn't know about this one!  Neat.

Give "Pause" a try... no workie.  Options worked.

Pause works for me.  Hit down, then enter after typing 'Pause'.  And of course you need to be playing to be able to pause.

[MrC]

Hah, this is funny.  I was playing something... but didn't realize it was not in MC!

Works fine - sorry for the (now paused) noise.

[Matt]

Hah, this is funny.  I was playing something... but didn't realize it was not in MC!

Works fine - sorry for the (now paused) noise.

Maybe in version 18

[LeoH]

Matt and MrC,

Many thanks for the clarification, all is well. 

With a large and complex library, the Search Bar is much appreciated, it provides great facility.