Skip to content

Commit 6d1817f

Browse files
authored
Update again
1 parent 7b6db69 commit 6d1817f

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/communication-services/quickstarts/voice-video-calling/includes/video-constraints/video-constraints-javascript.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -152,20 +152,20 @@ Managing video quality for incoming streams involves understanding the Azure Com
152152

153153
Defining the video render size is a crucial step for developers aiming to control the bitrate and frame rate of an incoming video stream. The initial quality and resolution of a video stream are determined by the size of the renderer created and placed on a web page. For instance, if the renderer is small, the WebJS SDK requests a smaller resolution. Conversely, if the renderer is large, the ACS SDK aims for the best possible resolution from the server. This process ensures that the video quality is optimized based on the client's requirements and capabilities. When a client requests a specific resolution, the server consults the resolution ladder to allocate the appropriate video bitrate, considering both network conditions and device capabilities.
154154

155-
This table provides what the WebJS calling SDK resolution ladder consists of with the estimated incoming video bitrates for various resolutions. These details help developers understand the relationship between resolution, bit rate, and frame rate and the approximate amount of bandwidth a specific incoming video stream uses. For example, a resolution of 1280x720 streams at 30 FPS with the the client using an approximate minimum bitrate of 1 MBPS and an approximate maximum bitrate of 2.5 MBPS.
155+
The resolution ladder table provides what the WebJS calling SDK resolution ladder consists of with the estimated incoming video bitrates for various resolutions. These details help developers understand the relationship between resolution, bit rate, and frame rate and the approximate amount of bandwidth a specific incoming video stream uses. For example, a resolution of 1280x720 streams at 30 FPS with the the client using an approximate minimum bitrate of 1 MBPS and an approximate maximum bitrate of 2.5 MBPS.
156156

157157
The Azure Communication Services WebJS Calling SDK adjusts video size based on available bandwidth to ensure a consistent communication experience. WebJS Calling SDK adjusts the video size based on algorithms that monitor network conditions. When network bandwidth is sufficient, the SDK increases video resolution to its maximum level based on the render size defined on the web page. Conversely, when bandwidth is limited, it reduces video resolution to prevent buffering and maintain a stable connection.
158158

159-
The following table provides some estimated bitrates for each resolution.
159+
The following table provides the resolution ladder and estimated bitrates for each resolution and associated FPS that will be delivered at that resolution.
160160

161161
| Height | Width | FPS | Min Bitrate (MBPS) | Max Bitrate (MBPS) |
162162
|--------|-------|-----|------------------|------------------|
163-
| 1080 | 1920 | 30 | 1.75 | 10 |
164-
| 720 | 1280 | 30 | 1 | 2.5 |
165-
| 540 | 960 | 30 | 0.5 | 1.125 |
166-
| 360 | 640 | 30 | 0.4 | 0.57 |
167-
| 240 | 426 | 15 | 0.125 | 0.5 |
168-
| 240 | 320 | 15 | 0.2 | 0.175 |
163+
| 1080 | 1920 | 30 | 1.75 | 10 |
164+
| 720 | 1280 | 30 | 1 | 2.5 |
165+
| 540 | 960 | 30 | 0.5 | 1.125 |
166+
| 360 | 640 | 30 | 0.4 | 0.57 |
167+
| 240 | 426 | 15 | 0.125 | 0.5 |
168+
| 240 | 320 | 15 | 0.2 | 0.175 |
169169

170170

171171
## Using Media statics to understand video constraints impact

0 commit comments

Comments
 (0)