Page 1 of 1

Searching meta date ranges

Posted: 03 Aug 2012 00:14
by peterbonge
I'm trying to search MP3 files from a certain date range, without any success.

Searching for files older than a date/year is no problem:

prop:year: < 2000

But using a date range doesn't work. I've tried these variants:

prop:year: 1989 - 2000
prop:year: > 1989 AND < 2000
prop:year: > 1989 AND prop:year: < 2000

Isn't it possible or what I am doing wrong?
And why does the search need a space after "prop:year:" and the color filters not?

Re: Searching meta date ranges

Posted: 08 Aug 2012 13:56
by peterbonge
Really no one?

I've already noticed that I have to use "prop:#15:". With "prop:year:" the program searches for the track numbers of the songs...

But the problem with searching for date ranges remains.

Re: Searching meta date ranges

Posted: 09 Aug 2012 10:17
by admin
Confirmed and fixed. This should be in the Bugs section, it's a major search bug IMO. I'm surprised that it could survive that long. Thanks!

BTW, this is (will be) the correct syntax (both are equivalent):

Code: Select all

prop:year: > 1989 AND prop:year: < 2000
prop:year: > 1989 AND  < 2000

Re: Searching meta date ranges

Posted: 09 Aug 2012 10:39
by peterbonge
Thanks!

Will the boolean combination or the "year=track number" befixed? Or both?

Re: Searching meta date ranges

Posted: 09 Aug 2012 10:41
by admin
peterbonge wrote:Will the boolean combination or the "year=track number" befixed? Or both?
The "year=track number" thing could not be reproduced here (XP and Win7) for MP3s. Are you sure??

Re: Searching meta date ranges

Posted: 09 Aug 2012 10:45
by peterbonge
admin wrote:The "year=track number" thing could not be reproduced here (XP and Win7) for MP3s. Are you sure??
I'll check it again later today. I have no MP3s here at work...

Re: Searching meta date ranges

Posted: 10 Aug 2012 11:00
by peterbonge
peterbonge wrote:I'll check it again later today. I have no MP3s here at work...
I have checked it again and "year" is working fine. I don't know why I thought that it behaves like the track number.
And boolean searches are working fine now with the new beta.