-
Notifications
You must be signed in to change notification settings - Fork 686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search not working properly in Sonata #1
Comments
The search support is Mopidy isn't done yet, so much improvement can be achieved in Mopidy alone. The Sonata issue is though probably out of our hands, and we need to find some workaround and/or ask the Sonata maintainers to reconsider their assumptions on regarding how the MPD server works. |
When I try to search (in the "database", the any field) it does not return any results. |
This has been reported upstream in Sonata's bug tracker at https://developer.berlios.de/feature/?func=detailfeature&feature_id=5038&group_id=7323 |
I'm writing about this issue in the docs, and I've referred to the Sonata bug report. Thus, there's no reason to keep this bug open any longer. We can't do anything in Mopidy to solve it. |
Using mpd clients like Sonata, GMPC, ncmpd, and possibly others with Mopidy, the search function does not give good results (if any). This is caused by the implementation of the mpd search in MPD clients.
For instance in Sonata, the client make an mpd search request on the two first letter of the search terms and filter the resulting data to list only relevant result. Since spotify only returns about 100 results in search request, the client is unlikely to successfully filter the search results.
This is not a Mopidy bug but I hope that making it an issue will help people realize what is wrong with their settings.
The text was updated successfully, but these errors were encountered: