Page History

...

Since WCS build 5.2.1395 a more strict jitter buffer implementation was added. The strict jitter buffer waits awaits for key frame receiving from a publisher and does not pass an incomplete frames to the server engine. It may look like video freeze until key frame is received and collected if stream publisher channel is bad, and buffer capacity is not enough to collect the frame from all its parts which are not received in time due to packet losses. The strict jitter buffer can be enabled by the following parameter

...

jitter_buffer_capacity=30

Since WCS build 5.2.1988 the following parameter is available

jitter_buffer_strictness=DEFAULT

The parameter accepts the following values:

• DEFAULT - strict jitter buffer is disabled
• TOLERANT - the strict jitter buffer awaits for key frame receiving from a publisher, with a soft key frame detection
• STRICT - the strict jitter buffer awaits for key frame receiving from a publisher, with a strict key frame detection (as like as use_strict_jitter_buffer=true )