-
Notifications
You must be signed in to change notification settings - Fork 457
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
meta_mpd.py loses stable connection with MPD #997
Comments
Can you please try the |
To reproduce this issue, I've installed Mopidy and as a front end I've installed Iris. I must admit that this was my first Iris installation. Thanks for this great project, it looks great on the desktop as well as on the mobile! I was so excited about Iris that I didn't continue to install the Mopidy-MPD extension, but took a look at Mopidy's excellent HTTP JSON-RPC API, which exposes the Mopidy core API. So I've decided to create meta_mopidy.py, which I guess is more stable, since it doesn't need the additional MPD layer. Overall the script is more simple than the The script works well, there are two issues:
I would appreciate if you could test the new script. It's really just a drop in replacement for |
@badaix thanks heaps for the effort here. I've been running your updated I did have to install a few additional dependencies but it was all pretty self explanatory; thanks for pointing them out in the script. |
@jaedb Nice, sounds like the issue in |
Cool, I'll update and test too. One thing I've noticed is that if Mopidy provides a foreign artwork URL, the For example, this track from Youtube:
|
The |
We've actually hit a very similar problem in Mopidy-MPD and didn't yet resolve it. We should probably "fix" Mopidy-Local to provide absolute image URLs but it's not as simple as it sounds. |
Update: I've installed Mopidy on my server and running |
I've just updated to the latest version and images are working 👌 on Mopidy-Youtube now too. I'm going to give the parameters configuration a whirl now to use a network-known hostname. This will make sure that Mopidy-Local images are accessible within the local domain. This should solve the issue where |
Fixed in snapcast v0.27.0 |
Describe the bug
Initial startup works fine and track information (and artwork 🤩) is beautifully plucked from MPD and added to the stream metadata. I can see the
meta_mpd.py
is interacting well with the Mopidy Docker instance.However after ~10 minutes, track metadata is no longer being updated from the MPD/Mopidy connection.
Control commands still appear to work, but the result of the command is not reflected in the stream. Again, it seems information is not being fed BACK to Snapserver. Here is a sample command being sent to the Snapserver API:
Steps to Reproduce
meta_mpd.py
chunk = fd.read()
in meta_mpd.pyEnvironment details
Attach logfile if applicable
The text was updated successfully, but these errors were encountered: