-
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 0.34 requires mpd 0.21 and displays a warning #47
Comments
On Tue, Dec 07, 2021 at 01:46:39PM -0800, klundry wrote:
Everything appears to be still working normally as far as I can tell
but mpc starting with v0.34 prints this warning with all output and I
`warning: MPD 0.21 required`
mopidy-mpd advertises 0.19 compatibility (c.f.
https://github.com/mopidy/mopidy-mpd/blob/1ab15a0c6b34a6cfb32674fa0b6f867decf6d8cf/mopidy_mpd/protocol/__init__.py#L24).
the warning was introduced a week ago in
MusicPlayerDaemon/mpc@ce1a004
the checks are gating send_tag_types_for_format() and
mpd_search_add_expression(). tagtypes is not supported, looking at
mopidy-mpd's readme; i'm not sure about search expressions, but probably
not supported either.
maybe someone has the time to implement those, otherwise i don't think
they'd be a showstopper (you can still use mpc, just that you might get
an error when sending tagtypes or using search expressions).
don't see any way to disable it. Also, the warning text is somehow
immune to tail/grep. It will print no matter what. Quite annoying.
it is probably printed to stderr. you can add 2>/dev/null to the mpc
call to hide all error and warning messages (but possibly even those
that you care about).
|
Thanks for the tip about stderr, I will try that. I'm only using pretty basic functions of mpc like playing playlists, querying the current song in some scripts. If I can just get rid of the warning text that will be good enough for me until the newer things get implemented. |
FWIW even though |
Experiencing the same issue with
System details:
Switched to the Iris web-based client for the time being, but I use I've not contributed to Mopidy or mopidy-mpd before, but would be happy to contribute a fix if someone can coach me through getting started. |
On Tue, Jul 05, 2022 at 09:10:20AM -0700, Josh Mock wrote:
Experiencing the same issue with `ncmpc` as of this morning. Error on startup:
```
Error: MPD version 0.19.0 is too old (0.21.0 needed)
this is still waiting on our support for search expressions (afaik,
that's the only 0.21 stuff we're still missing). I've started working on
that in PR#52, but i got distracted with other stuff. if someone wants
to pick that up, go for it! otherwise, it'll take me some time to finish
that.
the problem of right now is that the parser is way too complicated and
mopidy's api (and backends themselves) can't support the general form of
these expressions. it'd be best if we could at least handle simple
cases, and just fudge the results when encountering the other cases.
as long as it continues to be just a warning (and not an error that
exits the program), i'm inclined to say we just live with it.
|
In my case, |
Having this issue now :( |
Everything appears to be still working normally as far as I can tell but mpc starting with v0.34 prints this warning with all output and I don't see any way to disable it. Also, the warning text is somehow immune to tail/grep. It will print no matter what. Quite annoying.
warning: MPD 0.21 required
The text was updated successfully, but these errors were encountered: