Merge pull request #266459 from sloanster/patch-46

Patch 46

Author: Stacyrch140

articles/communication-services/concepts/voice-video-calling/video-constraints.md

@@ -7,32 +7,26 @@ ms.author: micahvivion
 manager: nmurav
 
 services: azure-communication-services
-ms.date: 2/20/2023
+ms.date: 2/15/2024
 ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
 # Video constraints
 
-[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
+The Video constraints API is a powerful tool that enables developers to control the video quality from within their video calls. With this API, developers can set maximum video resolutions, frame rate, and bitrate used so that the call is optimized for the user's device and network conditions. The ACS video engine is optimized to allow the video quality to change dynamically based on devices ability and network quality. But there might be certain scenarios where you would want to have tighter control of the video quality that end users experience. For instance, there may be situations where the highest video quality isn't a priority, or you may want to limit the video bandwidth usage in the application. To support those use cases, you can use the Video Constraints API to have tighter control over video quality.
 
-The Video Constraints API is a powerful tool that enables developers to control the video quality from within their video calls. With this API, developers can set maximum video resolutions, frame rate, and bitrate used so that the call is optimized for the user's device and network conditions. The Azure Communication Services video engine is optimized to allow the video quality to change dynamically based on devices ability and network quality. But there might be certain scenarios where you would want to have tighter control of the video quality that end users experience. For instance, there may be situations where the highest video quality is not a priority, or you may want to limit the video bandwidth usage in the application. To support those use cases, you can use the Video Constraints API to have tighter control over video quality.
-
-Another benefit of the Video Constraints API is that it enables developers to optimize the video call for different devices. For example, if a user is using an older device with limited processing power, developers can set constraints on the video resolution to ensure that the video call runs smoothly on that device
-
-Azure Communication Services Web Calling SDK supports setting the maximum video resolution, framerate, or bitrate that a client sends. The sender video constraints are supported on Desktop browsers (Chrome, Edge, Firefox) and when using iOS Safari mobile browser or Android Chrome mobile browser.
-
-The native Calling SDK (Android, iOS, Windows) supports setting the maximum values of video resolution and framerate for outgoing video streams and setting the maximum resolution for incoming video streams. These constraints can be set at the start of the call and during the call.
+Another benefit of the Video Constraints API is that it enables developers to optimize the video call for different devices. For example, if a user is using an older device with limited processing power, developers can set constraints on the video resolution to ensure that the video call runs smoothly on that device.
 
 ## Supported constraints
 
 | Platform | Supported Constraints | 
 | ----------- | ----------- |
-| Web | Outgoing video: resolution, framerate, bitrate |
-| Android | Incoming video: resolution<br />Outgoing video: resolution, framerate |
-| iOS | Incoming video: resolution<br />Outgoing video: resolution, framerate |
-| Windows | Incoming video: resolution<br />Outgoing video: resolution, framerate |
+| **Web** | **Incoming video**: resolution<br />**Outgoing video**: resolution, framerate, bitrate |
+| **Android** | **Incoming video**: resolution<br />**Outgoing video**: resolution, framerate |
+| **iOS** | **Incoming video**: resolution<br />**Outgoing video**: resolution, framerate |
+| **Windows** | **Incoming video**: resolution<br />**Outgoing** video: resolution, framerate |
 
 ## Next steps
 For more information, see the following articles:

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

@@ -2,23 +2,23 @@
 ms.author: enricohuang
 title: Quickstart - Set video constraints in your web calling app
 titleSuffix: An Azure Communication Services document
-description: In this quickstart, you'll learn how to set video constraints in your existing web calling app using Azure Communication Services.
+description: In this quickstart, you learn how to set video constraints in your existing web calling app using Azure Communication Services.
 author: sloanster
 services: azure-communication-services
-ms.date: 07/13/2023
+ms.date: 02/15/2024
 ms.topic: include
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
-You can set video constraints in your calls to control the video quality based on resolution or frameRate or bitrate in your video calls. In this quickstart guide, we'll illustrate how to set video constraints at the start of a call and how to use our `setConstraints` method on the call object to set video constraints dynamically during the call.
+You can set video constraints in your calls to control the video quality based on resolution or frameRate or bitrate in your video calls. In this quickstart guide, we illustrate how to set video constraints at the start of a call and how to use our `setConstraints` method on the call object to set video constraints dynamically during the call.
 
-> [!NOTE]
-> Currently, we only support setting video send constraints. You cannot set video constraints on incoming videos at this point of time.
+## Send video constraints
+Azure Communication Services Web Calling SDK supports setting the maximum video resolution, framerate, or bitrate that a client sends. The sender video constraints are supported on Desktop browsers (Chrome, Edge, Firefox) and when using iOS Safari mobile browser or Android Chrome mobile browser.
 
-## Setting video constraints at the start of a call
-The video constraints setting is implemented on the `Call` interface. To use the Video Constraints, you can specify the constraints from within `CallOptions` when you make a call, accept a call, or join a call. You will also have to specify `localVideoStreams` in `videoOptions`. <br/>
-Do note that constraints don't work if you join a call with audio only option and turn on the camera later. In this case, you can set video constraints dynamically using the `setConstraints` method on the `Call` interface (guide below).
+### Setting video constraints at the start of a call - outgoing (send) video
+The video constraints setting is implemented on the `Call` interface. To use the Video Constraints, you can specify the constraints from within `CallOptions` when you make a call, accept a call, or join a call. You must specify `localVideoStreams` in `videoOptions`. <br/>
+Do note that constraints don't work if you join a call with audio only option and turn on the camera later. In this case, you can set video constraints dynamically using the `setConstraints` method on the `Call` interface.
 
 ```javascript
 const callOptions = {
@@ -84,7 +84,7 @@ export declare type MediaConstraintRange = {
 };
 ```
 
-When setting video constraints, the SDK will choose the nearest value that falls within the constraint set (to prevent the values for resolution, frameRate and bitrate to not exceed the maximum constraint values set). Also, when the resolution constraint value is too small, the SDK will choose the smallest available resolution. In this case, the height of chosen resolution can be larger than the constraint value.
+When setting video constraints, the SDK chooses the nearest value that falls within the constraint set to prevent the values for resolution, frameRate, and bitrate to not exceed the maximum constraint values set. Also, when the resolution constraint value is too small, the SDK chooses the smallest available resolution. In this case, the height of chosen resolution can be larger than the constraint value.
 
 > [!NOTE]
 > For all `bitrate`, `frameHeight` and `frameRate`, the constraint value is a `max` constraint, which means the actual value in the call can be the specified value or smaller.
@@ -94,7 +94,7 @@ The `frameHeight` in `VideoSendConstraints` has a different meaning when a mobil
 
 If you use MediaStats API to track the sent video resolution, you may find out that the sent resolution can change during the call. It can go up and down, but should be equal or smaller than the constraint value you provide. This resolution change is an expected behavior. The browser also has some degradation rule to adjust sent resolution based on cpu or network conditions.
 
-## Setting video constraints during the call
+### Setting video constraints during the call - outgoing (send) video
 You can set video constraints during the call by using the `setConstraints` method on the `Call` object.
 ```javascript
 // For eg, when you've started a call,
@@ -141,7 +141,12 @@ await currentCall.setConstraints({
 
 <br/>
 
-### Media stats
+## Receive video constraints
+To control resolution on the receiver side using Azure Communication Services Web Calling SDK, you can adjust size of the renderer of that video. The calling SDK automatically adjusts received resolution based on the dimensions of the renderer. The SDK won't request an incoming video stream (width and height) that can fit into the renderer video window.
+
+
+
+## Using Media statics to understand video constraints impact
 To evaluate and compare the video quality after applying the video constraints, you can access [MediaStats API](../../../../concepts/voice-video-calling/media-quality-sdk.md) to get video resolution and bitrate information of the sending stream. The media stats also include other granular stats related to the streams, such as jitter, packet loss, round trip time, etc.
 
 ```javascript