We’re working on improving search so that it’s able to handle spelling errors (Mahler vs Malher) but it wasn’t something that was ready for inclusion as part of this release. For the moment, you’re only going to see results that actually include the word “Malher”.
As Brian mentioned above, there are lots more improvements to come, and spelling corrections are absolutely part of the roadmap – you can expect this query to hit as expected once that functionality is implemented.
Mike, the problem here is that you keep touting big improvements to search, then we try one simple thing (for me, the first search I tried for “Handel” returned Mozart), and it is really odd. And disappointing.
Why not do all these fixes and improvements you are talking about, and then roll it into your product and crow about it? Instead of the half-baked version you seem to keep giving us?
Zenit already explained it to you here:
This is a result of pre-880 data mappings that are cached on your machine and not the new search. I’m going to give you the benefit of the doubt and guess that you missed that post.
No, I saw the post, but so what? The fact was still that our experience with the “new search” touted in the release notes was odd and disconcerting. The reassurance that such things maybe won’t happen any more at some undisclosed and unknowable point in the future doesn’t really help much with that first impression.
Or am I wrong again? Will some flag pop up when the old outdated set of aliases are finally cleared out, so that the user can know what to think about it?
While the new search is certainly much better, there are still some gross errors. For example a search for “Beethoven Symphony 3” doesn’t find the composition:
And a search for “Mozart Piano Sonata 3” returns the right sonata but by the wrong composer.
@zenit - what is the best way to communicate these issues to you? Do you want them raised individually, or put in the general build 880 thread, or should there be one thread just for build 882 search issues?
Thanks for asking, and thanks for posting. It’s good to keep all these examples here within this thread.
First and foremost, thanks for all the continuing work you have put into the search feature. Is it perfect? No. But it does a pretty damn good job, especially compared to other products out there.
Oddities in non-classical searches in Tidal…
The original album “What’s Going On” does not appear in the discography of Marvin Gaye… but it does show up if you search on the title.
A search on Gladys Knight will result in her solo albums and some with The Pips, but not all. A search on Gladys Knight & The Pips will return all of them. BTW, Tidal treats them both as one entity.
I know it’s irritating when people say it works ok for me, but I have Qobuz and I’ve got five versions of “What’s Going On” in Marvin Gaye’s discography.
Interesting… I only have 61 main albums for Marvin Gaye in Tidal. Is your total of 129 main albums just in Tidal, or does it include other sources?
Qobuz and mine
Searching for “trip to the moon” or “trip to the moon acen” does not return Acen’s - Trip to the Moon Pt.2.
Only the exact track title “Trip to the Moon Pt.2” yields a hit. I’m guessing the “Pt.2” in the track name is confusing the search engine.
Do you use qobuz or tidal, or do you have that music locally? If you’re not seeing something similar to this, there might be some issue.
I have both Qobuz and Tidal but do not have the track locally.
The search now appears to be working however. I take it, something has been altered at your end as this search has not worked using the Android client when I tried earlier today and a couple of weeks ago?
Try having O’Neill for a surname. VB must have a lot to answer for in Ireland 
There have definitely been some changes in the recent weeks, but there were none in the past few days that should have affected this specific query. Could it be your android app was not yet updated?
