Platforms and browsers supported
The following WCS settings are intended to limit publishing bitrate:
|Minimum bitrate limit|
|Maximum bitrate limit|
On browser side, bitrate limits are set in kilobits per second, for example
If maxBitrate is set, WCS server will send REMB command to decrease bitrate when this limit is reached.
If minBitrate is set, WCS server will stop sending REMB command to decrease bitrate when this limit is reached.
Therefore, the settings define 3 ranges with its own bitrate management algorithm:
WCS stops bitrate management and not send any REMB commands
WCS server makes active bitrate management: depending on jitter and incoming traffic uniformity WCS decides to send REMB commands to decrease bitrate. If channel is good, WCS does nothing and bitrate is not decreasing
WCS constantly sends bitrate decrease commands until it reduce to maxBitrate
How to enforce bitrate increasing
These parameters are ste set in bps. In the exampel example above, the settings have a same effect as
These settings are intended for Chromium-based browsers and work with, e.g., Opera, Vivaldi and Yandex.Browser. Also, they are applied when iOS Safari 12 is used. They do not work with Firefox and Edge.
Bitrate limiting in certain borders can be useful for example when publishing video to Safari browser subscribers. This browser is sensitive to bitrate jumps, in this case picture quality loses until freeze and browser hangs. It is recommended to stabilize bitrate when publishing streams for Safari viewers by setting narrow limits of bitrate change, for example