Closed InanisOmnia closed 2 years ago
Getting warnings like so when doing service mopidy status
[HttpServer] mopidy_iris.core Updating Snapcast stream metadata: http://localhost:1780/jsonrpc
../gst/gstpad.c:4621:gst_pad_push_data:<wavenc0:src> Got data flow before segment event
../gst/gstpad.c:4368:gst_pad_chain_data_unchecked:<filesink0:sink> Got data flow before segment event
Have you tried using something other than a fifo? Such as:
All of these should work better than a gstreamer filesink, which doesn't work very well with a fifo. See https://github.com/mopidy/mopidy/issues/775 and https://github.com/mopidy/mopidy/issues/1636 which already cover much of this (and I've no interest in re-opening). If you have futher problems using Mopidy with Snapcast, create a topic on the Forum.
Describe the bug The mopidy frontend does not match what is actually being played. The scrub bar runs faster than the actual time in seconds (randomly jumping large amounts of time), the pause/play buttons appear to have no affect. However, finding a track and clikcing "play now" make that track play but then all mentioned issues immediately re-occur.
I've been listening to the output whilst writing this issue and it has now randomly started at the beginning of the same song (without allowing it to finish) and it now just looping over that specific section of the song.
How to reproduce Have mopidy output to a file, in my case "/tmp/snapfifo" Snapserver and snapclient running, reading from this file
Expected behaviour A clear and concise description of what you expected to happen.
Environment Please complete the following information:
sudo mopidyctl config
)sudo mopidyctl deps
)Additional context The music still plays syncrhonised across all devices (using snapcast) and all frontends state incorrect timings and incorrect tracks (slowly getting more and more out of time and further away from current song in the queue) including
ncmcpp
in terminal and mopidy mobileIf appropriate, upload an appropriately verbose log file showing the bug.