-
Notifications
You must be signed in to change notification settings - Fork 21
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
MPC lsplaylists returns "wrong number of arguments for 'tagtypes'" error #48
Comments
Also, just checked, downgrading from 0.34-1 to 0.33-3 does in fact fix the issue, so there was probably a change in there relating to lsplaylists. |
These new versions tagtypes with arguments are not supported in MPD 0.19, which is the mega old version of the MPD protocol we support. The MPD documentation lacks any info on what version they are supported from, not that it matters really. Our implementation here is very outdated and we need someone to help with that. But for this particular issue we could apply some duct tape and just ignore the extra arguments to get things working again. PR welcome - we still don't have a maintainer but I'm happy to merge a fix. |
I've stubbed out |
With #50 merged, is this now resolved or do we also need to report support for a higher version of the MPD protocol? |
This specific issue is fixed, but I wouldn't yet advertise mpd-0.21 support. The warning printed by mpc will not prevent it from working. For 0.21 support, we still need some commands (mostly regarding 'partitions') and switch the parameters for search* and find* to the newer 'filter' format. I'm working on stubbing out the missing commands, and will tag bug#47 when i'm getting anywhere. |
That's good news because I agree we can't advertise support we don't have! I did some work on some of this before and had to make some core changes which I must have lying around somewhere. I'll dig those out and remind myself of the problem. But what you are doing sounds good, thanks! |
Since recently I can't use mpc to query my spotify playlists, because I get the following error:
I think it's somewhat connected to #47 because that started happening at around the same time as well.
The text was updated successfully, but these errors were encountered: