Skip to content

Commit cc9060e

Browse files
authored
update 2
1 parent bc124a7 commit cc9060e

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

articles/communication-services/quickstarts/voice-video-calling/optimizing-video-placement.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ titleSuffix: An Azure Communication Services quickstart
55
description: This document describes how to place video on a web page based on resolution size to optimize video placement and enhance overall page performance.
66
author: sloanster
77
services: azure-communication-services
8-
ms.date: 03/07/2025
8+
ms.date: 04/08/2025
99
ms.topic: quickstart
1010
ms.service: azure-communication-services
1111
ms.subservice: calling
@@ -76,14 +76,14 @@ When there's a change in the optimal video count value, if the result indicates
7676

7777
Conversely, if the optimal count decreases and is [less than the current number of videos on the page](../../resources/troubleshooting/voice-video-calling/video-issues/reaching-max-number-of-active-video-subscriptions.md), consider disposing of a video using the dispose method and updating the application layout accordingly.
7878

79-
### Things to consider when adding a 1080P or 720P video to a page.
79+
### Things to consider when adding a 1080p or 720p video to a page.
8080

81-
- You can place one 1080p incoming video with the rest smaller than 720P.
81+
- You can place one 1080p incoming video with the rest smaller than 720p.
8282
- You can place two 720p incoming videos with the rest smaller than 720p.
8383

8484
[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
8585

86-
In [version 1.33](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1332-beta1-2025-01-30) and later of the public preview calling SDK support putting 2 720P videos simultaneously on a web page.
86+
In [version 1.33](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1332-beta1-2025-01-30) and later of the public preview calling SDK support putting 2 720p videos simultaneously on a web page.
8787

8888
For instance, in a group call where seven participants have their video cameras on, on each client page you can select two participants' videos are displayed at higher resolutions. These two participants set to show their video at 720p by setting their views on the web page to be 720 pixels in height by 1280 pixels in width (or greater). The remaining five participant videos should be set to a lower resolution, such as 360p or lower.
8989

@@ -98,12 +98,12 @@ For instance, in a group call where seven participants have their video cameras
9898

9999
Simulcast isn't supported on all browser devices. Currently, simulcast is unavailable when sending videos on mobile browsers or macOS Safari. If a participant attempts to render 720p video from a user on iOS Safari, Android Chrome, or macOS Safari and another participant on the call tries to render the same video at a smaller resolution, both receive the smaller resolution. This change happens because the devices prioritize smaller resolutions when simulcast send isn't supported.
100100

101-
## How to configure to SEND 1080P
101+
## How to configure to send a 1080p stream
102102
[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
103103

104-
[Version 1.35.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.35.1-beta.1) and higher of the public preview calling SDK supports sending a 1080P video.
104+
[Version 1.35.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.35.1-beta.1) and higher of the public preview calling SDK supports sending a 1080p video.
105105

106-
When using the WebJS SDK to send video at a 1080P resolution, you must use the [Video Constraints API](../voice-video-calling/get-started-video-constraints.md?pivots=platform-web) and specify that you want to use 1080P. If the Video Constraints API is not used and 1080P is not specified, the default video stream resolution will be 720P.
106+
When using the WebJS SDK to send video at a 1080p resolution, you must use the [Video Constraints API](../voice-video-calling/get-started-video-constraints.md?pivots=platform-web) and specify that you want to use 1080p. If the Video Constraints API is not used and 1080p is not specified, the default video stream resolution will be 720p.
107107

108108
```javascript
109109
const callOptions = {
@@ -125,8 +125,8 @@ When using the WebJS SDK to send video at a 1080P resolution, you must use the [
125125
this.callAgent.startCall(identitiesToCall, callOptions);
126126
```
127127

128-
### Items to note when sending a 1080P video stream
129-
* The camera in use should be capable of sending a 1080P video. To check what resolutions your camera supports, you can use the following JavaScript example to determine the available resolutions.
128+
### Items to note when sending a 1080p video stream
129+
* The camera in use should be capable of sending a 1080p video. To check what resolutions your camera supports, you can use the following JavaScript example to determine the available resolutions.
130130

131131
```javascript
132132
async function getSupportedResolutions() {
@@ -154,18 +154,18 @@ async function getSupportedResolutions() {
154154
getSupportedResolutions();
155155
```
156156

157-
* The machine sending a 1080P must have a powerful enough machine to suppor sending a 1080P.
158-
* The client that is on the receiver side (people accepting of a 1080P video) must have a video render HTML5 element capable of 1080P to accept 1080P. If any participants on the call do not have a 1080P element enabled to receive the video, the call will adjust and negotiate down to a smaller resolution.
159-
* All the people on the call that are sending and receiving a 1080P video stream must have the bandwidth to support a 1080P stream.
157+
* The machine sending a 1080p must have a powerful enough machine to suppor sending a 1080p.
158+
* The client that is on the receiver side (people accepting of a 1080p video) must have a video render HTML5 element capable of 1080p to accept 1080p. If any participants on the call do not have a 1080p element enabled to receive the video, the call will adjust and negotiate down to a smaller resolution.
159+
* All the people on the call that are sending and receiving a 1080p video stream must have the bandwidth to support a 1080p stream.
160160

161161
| **Resolution** | **Min framerate** | **Max framerate** | **Max bitrate** |
162162
|--|--|--|--|
163-
| 1080P | 30 | 30 | 4m |
164-
| 720P | 30 | 30 | 2.5M |
165-
| 540P | 30 | 30 | 2M |
166-
| 360P | 30 | 30 | 1M |
167-
| 240P | 15 | 15 | 650k |
168-
| 180P | 7.5 | 15 | 250k(350k if 15 FPS)|
163+
| 1080p | 30 | 30 | 4m |
164+
| 720p | 30 | 30 | 2.5M |
165+
| 540p | 30 | 30 | 2M |
166+
| 360p | 30 | 30 | 1M |
167+
| 240p | 15 | 15 | 650k |
168+
| 180p | 7.5 | 15 | 250k(350k if 15 FPS)|
169169

170170
You can use the media quality statistics API within the WebJS SDK to determine the real time video send and receive resolution. See [here](../../concepts/voice-video-calling/media-quality-sdk.md?pivots=platform-web) for more details.
171171

0 commit comments

Comments
 (0)