-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
music_assistant.search seems to prioritize collaborations above the individual artist #3459
Comments
This is not a core issue with MA but rather a problem with the plex provider or plex itself. Unfortunately there is no dedicated plex dev so this may take some time to get looked at. |
Oh, interesting, I am not sure I understand, because when I search in Plex with exactly the same input any collabs are not even showing in the first results, as I expect. So, I am not sure but I think there is something specific about how MA searches in Plex that is different. |
You misunderstand what Marcel said (emphasis added)
|
sorry, wanted to just make sure I was clear on what I was seeing in Plex. |
What version of Music Assistant has the issue?
2.4.0b12
What version of the Home Assistant Integration have you got installed?
n/a (built-in)
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
If you use
music_assistant.search
to search for an artist such as 'Joe Cocker' the results prioritize collaborations instead of the individual artist.How to reproduce
music_assistant.search
with an artist in your library. For example, I called:limit: 1
you can confirm that indeed the artist itself is returned as well:Music Providers
plex
Player Providers
slimproto
Full log output
music_assistant.log
Additional information
No response
What version of Home Assistant Core are your running
2025.1.0
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)
The text was updated successfully, but these errors were encountered: