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
Hello,
I'm wonder about the latency setting for clients. These are my questions:
Are negative numbers supposed to be valid? Snapdroid allows those, while the webinterface does not.
What's the valid number range? Snapdroid allowed numbers more than 1000 ms while the webinterface at max 900 ms IIRC. I guess the answers to 1) and 2) might show that there is a bug in either Snapdroid or Webinterface.
what is the user actually supposed to put into that field and why is it even necessary to have a latency setting considering the whole purpose of the snapcast-protocol is that it syncs playback across devices with them being aware of the servers "playback time code". Is the latency setting fed back to the server or does only the device itself know about the latency the user has set?
Is the latency setting thought of as a last resort setting meaning the user should rather first try to optimize his server settings in order to reduce delay/latency (if so which buffer, chunk etc. settings decrease/increase latency).
I'm looking forward to solve those mysteries for myself and probably others :-)
Greets!
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
-
Hello,
I'm wonder about the latency setting for clients. These are my questions:
I'm looking forward to solve those mysteries for myself and probably others :-)
Greets!
Beta Was this translation helpful? Give feedback.
All reactions