Rokamun
commented
1 year ago Your latency is ~497ms, as jitter is the start point where your playback starts as seen from the live point.
The maxkeepaway is the maximum jitter that will ever be used. This is something you can set when editing the stream. The field Maximum live keep-away distance: is this and defaults to 45 seconds. It is almost never used at this high.
Since your jitter value is far below 45000 the actual jitter value of 497 will be used.
The real reason your playback takes 4+ seconds to start is most likely because the player tries WebRTC and takes about 4 seconds to notice it failed and then goes to a fallback protocol.
To see this more clearly, you'll want to extend the Data field a bit to the right, the relevant information is cut off right now.
Most likely you want to just completely remove the WebRTC protocol from your protocols tab, as I assume it's not working in the current state.
If you want to verify it not working you can use the .html output and force it to only attempt WebRTC.
You force playback to WebRTC by going to the http://mistserveraddress:port/streamname.html?dev=1&forcetype=webrtc link. Fill in the mistserveraddress port and streamname to fit your setup.
Need to find there is initial buffering of mist player and remove it or shorter, now it takes 4+ sec to load. I found that I get last 45 sec of stream ('maxkeepaway') and it can cause long time stream loading. Can anyone know how I can decrease the 'maxkeepaway' time and minimize it? Or maybe I can fix it with another approach?