You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Had some stutters I never had before, now feeding Snapcast with Mopidy + gstreamer. Doesn't matter if I used 0.25 or 0.27, problem is the same. It might have stabilized now but:
jul 18 15:25:16 debian11 snapserver[4046]: next read < 0 (Mopidy): -16.169 ms
jul 18 15:25:16 debian11 snapserver[4046]: Too many frames available, fast forw>
jul 18 15:25:16 debian11 snapserver[4046]: next read < 0 (Mopidy): -36.007 ms
jul 18 15:25:16 debian11 snapserver[4046]: Not enough data available: 32 ms, mi>
jul 18 15:25:16 debian11 snapserver[4046]: onResync (Mopidy): 64 ms
jul 18 15:25:16 debian11 snapserver[4046]:
jul 18 15:25:16 debian11 snapserver[4046]: next read < 0 (Mopidy): -16.005 ms
jul 18 15:25:17 debian11 snapserver[4046]: next read < 0 (Mopidy): -3.922 ms
Pausing and playing again sometimes fixed the issue, which indicates that it's a Mopidy problem, but it's weird that "too many frames" and "not enough data available" is logged at the same time. I tried upping the chunking to 64ms and the buffer to 1500ms, changed to pcm and back and tried fifo/tcp/alsa sinks between mopidy and snapserver. Currently it seems to be working again -- dunno why -- but has anyone seen something similar?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Had some stutters I never had before, now feeding Snapcast with Mopidy + gstreamer. Doesn't matter if I used 0.25 or 0.27, problem is the same. It might have stabilized now but:
jul 18 15:25:16 debian11 snapserver[4046]: next read < 0 (Mopidy): -16.169 ms
jul 18 15:25:16 debian11 snapserver[4046]: Too many frames available, fast forw>
jul 18 15:25:16 debian11 snapserver[4046]: next read < 0 (Mopidy): -36.007 ms
jul 18 15:25:16 debian11 snapserver[4046]: Not enough data available: 32 ms, mi>
jul 18 15:25:16 debian11 snapserver[4046]: onResync (Mopidy): 64 ms
jul 18 15:25:16 debian11 snapserver[4046]:
jul 18 15:25:16 debian11 snapserver[4046]: next read < 0 (Mopidy): -16.005 ms
jul 18 15:25:17 debian11 snapserver[4046]: next read < 0 (Mopidy): -3.922 ms
Pausing and playing again sometimes fixed the issue, which indicates that it's a Mopidy problem, but it's weird that "too many frames" and "not enough data available" is logged at the same time. I tried upping the chunking to 64ms and the buffer to 1500ms, changed to pcm and back and tried fifo/tcp/alsa sinks between mopidy and snapserver. Currently it seems to be working again -- dunno why -- but has anyone seen something similar?
Beta Was this translation helpful? Give feedback.
All reactions