You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**Maximum # of outgoing local streams that can be sent simultaneously**| 1 video and 1 screen sharing | 1 video + 1 screen sharing |
173
-
|**Maximum # of incoming remote streams that can be rendered simultaneously**| 9 videos + 1 screen sharing on desktop browsers*, 4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
173
+
|**Maximum # of incoming remote streams that can be rendered simultaneously**| 16 videos + 1 screen sharing on desktop browsers*, 4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
174
+
175
+
174
176
175
177
\* Starting from Azure Communication Services Web Calling SDK version [1.16.3](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1163-stable-2023-08-24)
176
-
While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine how many current incoming video streams your web environment can support.
178
+
While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine how many current incoming video streams your web environment can support. To properly support 16 incoming videos the computer should have a mimimum of 16GB RAM and a 4-core or greater CPU that is no older than 3 years old
177
179
178
180
## Supported video resolutions
179
181
The Azure Communication Services Calling SDK automatically adjusts resolutions of video and screen share streams during the call.
@@ -192,8 +194,8 @@ The Azure Communication Services Calling SDK supports sending following video re
192
194
## Number of participants on a call support
193
195
- Up to **350** users can join a group call, Room or Teams + ACS call.
194
196
- Once the call size reaches 100+ participants in a call, only the top 4 most dominant speakers that have their video camera turned can be seen.
195
-
- When the number of people on the call is 100+, the viewable number of incoming video renders automatically decreases from 3x3 (9 incoming videos) down to 2x2 (4 incoming videos).
196
-
- When the number of users goes below 100, the number of supported incoming videos goes back up to 3x3 (9 incoming videos).
197
+
- When the number of people on the call is 100+, the viewable number of incoming video renders automatically decreases from 4x4 (16 incoming videos) down to 2x2 (4 incoming videos).
198
+
- When the number of users goes below 100, the number of supported incoming videos goes back up to 4x4 (16 incoming videos).
197
199
198
200
## Calling SDK timeouts
199
201
The following timeouts apply to the Communication Services Calling SDKs:
@@ -445,7 +445,7 @@ application should render at a given moment. Applications should handle these ch
445
445
accordingly to the recommendation. There's a debounce period (around 10 s) between each update.
446
446
447
447
**Usage**
448
-
The `optimalVideoCount` feature is a call feature. You need to reference the feature `OptimalVideoCount` via the `feature` method of the `Call` object. You can then set a listener via the `on` method of the `OptimalVideoCountCallFeature` to be notified when the optimalVideoCount changes. To unsubscribe from the changes, you can call the `off` method.
448
+
The `optimalVideoCount` feature is a call feature. You need to reference the feature `OptimalVideoCount` via the `feature` method of the `Call` object. You can then set a listener via the `on` method of the `OptimalVideoCountCallFeature` to be notified when the optimalVideoCount changes. To unsubscribe from the changes, you can call the `off` method. The current [maximum number of incoming videos](../../../../concepts/voice-video-calling/calling-sdk-features.md#supported-number-of-incoming-video-streams) that can be rendered is 16. To properly support 16 incoming videos the computer should have a mimimum of 16GB RAM and a 4-core or greater CPU that is no older than 3 years old.
0 commit comments