GVP MCP:mpc:rtp-source buffer video size
(6 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
|valid=rtp.source_buffer_video_size must be an integer that is greater than or equal to 200 and less than or equal to 2000. | |valid=rtp.source_buffer_video_size must be an integer that is greater than or equal to 200 and less than or equal to 2000. | ||
|takeseffect=Immediately/session | |takeseffect=Immediately/session | ||
− | |shortdesc=Specifies the maximum number of packets that the RTP source video buffer can contain. The default value 500 is correct for most applications.<br /><br /> If video conferencing with video_output_type set to mixed is to be utilized, the platform will buffer the last video IFrame and subsequent packets received for each conference participant. This parameter sets the number of packets that can be buffered. It should be set to the maximum expected input IFrame interval (in packet count) plus 20. For example, if a device will be connected that sends an IFrame every 600 packets, the value should be set to 620. | + | |shortdesc= |
+ | |||
+ | Specifies the maximum number of packets that the RTP source video buffer can contain. The default value 500 is correct for most applications.<br /><br /> | ||
+ | |||
+ | If video conferencing with video_output_type set to mixed is to be utilized, the platform will buffer the | ||
+ | last video IFrame and subsequent packets received for each conference participant. This parameter sets the number of | ||
+ | packets that can be buffered. It should be set to the maximum expected input IFrame interval (in packet count) plus 20. For example, if a device will be connected that sends an IFrame every 600 packets, the value should be set to 620. | ||
+ | |||
+ | |||
}} | }} | ||
{{DraftOption}} | {{DraftOption}} |
Latest revision as of 15:43, June 29, 2020
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Draft Option
No draft option
This page was last edited on June 29, 2020, at 15:43.
Comments or questions about this documentation? Contact us for support!