-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error when selectign a genre #542
Comments
See my reply in #541 |
$ mpd --version |
This version was released on 22-Feb-2019, maybe you can update MPD an check again? |
I'm on raspberrypi and this is the latest I can get. I'll see if I can compile later version myself. Thanks! |
Which OS are you using on the Pi? Did you succeed buliding MPD yourself? |
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" I haven't had the time to try building MPD. I'll update here when I give it a go |
If this doesn't work with a newer version of MPD, please open an issue. |
I finally had some tinkering time and upgraded MPD to 0.23.13 and I still see the samme issue. Same goes for genres and albums pi@raspberrypi:~ $ mpd --version Database plugins: Storage plugins: Decoders plugins: Filters: Tag plugins: Output plugins: Encoder plugins: Input plugins: Playlist plugins: Protocols: Other features: |
Hey there, I tried to reproduce the error on the same MPD version (0.23.13) but could not reproduce it. Could you post the relevant part from your I noticed that you have no After enabling it (with Also, your MPD installation is pretty sparse (by design?). Maybe there's an option missing? For reference, this is my
|
The app is able to get the list of all genres but when I try to open any of them I get the following error
An error occurred
{
"headers": {
"normalizedNames": {},
"lazyUpdate": null
},
"status": 500,
"statusText": "OK",
"url": "http://pi:8080/api/genre?genre=Adult%20Alternative%20Pop",
"ok": false,
"name": "HttpErrorResponse",
"message": "Http failure response for http://pi:8080/api/genre?genre=Adult%20Alternative%20Pop: 500 OK",
"error": {
"message": "[2@0] {list} Unknown filter type"
}
}
The text was updated successfully, but these errors were encountered: