webrtcsink: growing minPlayoutDelay
Hi there, could you assist in clarifying the significance of the "minPlayoutDelay" parameter when it comes to the receiver's end? After initiating a WebRTC stream, I observe that the playout delay gradually increases to reach a specific threshold (approximately 100 milliseconds when running locally):
[1532497:17:0913/204246.540984:WARNING:video_receive_stream2.cc(994)] Multiple playout delays set. Actual delay value set to 24 ms frame min delay=<unset> base min delay=0 us sync min delay=24 ms
[1532497:17:0913/204248.540965:WARNING:video_receive_stream2.cc(994)] Multiple playout delays set. Actual delay value set to 47 ms frame min delay=<unset> base min delay=0 us sync min delay=47 ms
[1532497:17:0913/204250.540979:WARNING:video_receive_stream2.cc(994)] Multiple playout delays set. Actual delay value set to 68 ms frame min delay=<unset> base min delay=0 us sync min delay=68 ms
[1532497:17:0913/204252.540966:WARNING:video_receive_stream2.cc(994)] Multiple playout delays set. Actual delay value set to 84 ms frame min delay=<unset> base min delay=0 us sync min delay=84 ms
[1532497:17:0913/204255.540983:WARNING:video_receive_stream2.cc(994)] Multiple playout delays set. Actual delay value set to 99 ms frame min delay=<unset> base min delay=0 us sync min delay=99 ms
[1532497:17:0913/204259.540896:WARNING:video_receive_stream2.cc(994)] Multiple playout delays set. Actual delay value set to 114 ms frame min delay=<unset> base min delay=0 us sync min delay=114 ms
It then remains relatively stable at that level, with minor fluctuations. I have a couple of questions:
- Is there a parameter within the GStreamer pipeline that has an impact on this value?
- Are there any parameters within the WebRTC settings on the client (browser) side that can influence this value? I'm also curious about the significance of the "minimum delay" and why it tends to increase.