public class RembParams extends Object
Constructor and Description |
---|
RembParams()
Create a RembParams
|
Modifier and Type | Method and Description |
---|---|
Float |
getDecrementFactor()
get Determine how much is decreased the current REMB when too losses are detected.
|
Float |
getExponentialFactor()
get Factor used to increase exponentially the next REMB when it is below the threshold.
|
Float |
getLinealFactorGrade()
get Determine the value of the next linearFactor based on the threshold and the current REMB.
|
Integer |
getLinealFactorMin()
get Set the min of the factor used to increase linearly the next REMB when it is over the threshold.
|
Integer |
getPacketsRecvIntervalTop()
get Size of the RTP packets history to smooth fraction-lost.
|
Integer |
getRembOnConnect()
get Initial local REMB bandwidth estimation that gets propagated when a new endpoint is connected.
|
Float |
getThresholdFactor()
get Determine the next threshold (TH) when too losses are detected.
|
Integer |
getUpLosses()
get Max fraction-lost to no determine too losses.
|
void |
setDecrementFactor(Float decrementFactor)
set Determine how much is decreased the current REMB when too losses are detected.
|
void |
setExponentialFactor(Float exponentialFactor)
set Factor used to increase exponentially the next REMB when it is below the threshold.
|
void |
setLinealFactorGrade(Float linealFactorGrade)
set Determine the value of the next linearFactor based on the threshold and the current REMB.
|
void |
setLinealFactorMin(Integer linealFactorMin)
set Set the min of the factor used to increase linearly the next REMB when it is over the threshold.
|
void |
setPacketsRecvIntervalTop(Integer packetsRecvIntervalTop)
set Size of the RTP packets history to smooth fraction-lost.
|
void |
setRembOnConnect(Integer rembOnConnect)
set Initial local REMB bandwidth estimation that gets propagated when a new endpoint is connected.
|
void |
setThresholdFactor(Float thresholdFactor)
set Determine the next threshold (TH) when too losses are detected.
|
void |
setUpLosses(Integer upLosses)
set Max fraction-lost to no determine too losses.
|
public Integer getPacketsRecvIntervalTop()
public void setPacketsRecvIntervalTop(Integer packetsRecvIntervalTop)
public Float getExponentialFactor()
public void setExponentialFactor(Float exponentialFactor)
public Integer getLinealFactorMin()
public void setLinealFactorMin(Integer linealFactorMin)
public Float getLinealFactorGrade()
public void setLinealFactorGrade(Float linealFactorGrade)
public Float getDecrementFactor()
public void setDecrementFactor(Float decrementFactor)
public Float getThresholdFactor()
public void setThresholdFactor(Float thresholdFactor)
public Integer getUpLosses()
public void setUpLosses(Integer upLosses)
public Integer getRembOnConnect()
The REMB congestion control algorithm works by gradually increasing the output video bitrate, until the available bandwidth is fully used or the maximum send bitrate has been reached. This is a slow, progressive change, which starts at 300 kbps by default. You can change the default starting point of REMB estimations, by setting this parameter.
WARNING: If you set this parameter to a high value that is higher than the network capacity, then all endpoints will start already in a congested state, providing very bad video quality until the congestion control algorithm is able to recover from the situation. Network congestion is very unpredictable, so be careful when changing this parameter; for most use cases it is safer to just start with a low initial value and allow the REMB algorithm to raise until the optimum bitrate is reached.
public void setRembOnConnect(Integer rembOnConnect)
The REMB congestion control algorithm works by gradually increasing the output video bitrate, until the available bandwidth is fully used or the maximum send bitrate has been reached. This is a slow, progressive change, which starts at 300 kbps by default. You can change the default starting point of REMB estimations, by setting this parameter.
WARNING: If you set this parameter to a high value that is higher than the network capacity, then all endpoints will start already in a congested state, providing very bad video quality until the congestion control algorithm is able to recover from the situation. Network congestion is very unpredictable, so be careful when changing this parameter; for most use cases it is safer to just start with a low initial value and allow the REMB algorithm to raise until the optimum bitrate is reached.
Copyright © 2022 Kurento. All rights reserved.