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
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/raw-media/raw-media-access-android.md
@@ -23,13 +23,13 @@ The Azure Communication Services Calling SDK offers APIs allowing apps to genera
23
23
This quick start builds upon [QuickStart: Add 1:1 video calling to your app](../../get-started-with-video-calling.md?pivots=platform-android) for Android.
24
24
25
25
26
-
## Virtual Video Stream Overview
26
+
## Virtual video stream overview
27
27
28
28
Since the app will be generating the video frames, the app must inform the Azure Communication Services Calling SDK about the video formats the app is capable of generating. This is required to allow the Azure Communication Services Calling SDK to pick the best video format configuration given the network conditions at any giving time.
29
29
30
30
The app must register a delegate to get notified about when it should start or stop producing video frames. The delegate event will inform the app which video format is more appropriate for the current network conditions.
31
31
32
-
### Supported Video Resolutions
32
+
### Supported video resolutions
33
33
34
34
| Aspect Ratio | Resolution | Maximum FPS |
35
35
| :--: | :-: | :-: |
@@ -214,13 +214,13 @@ After that, create the ByteBuffer backing the video frame if needed. Then, updat
214
214
}
215
215
```
216
216
217
-
## Screen Share Video Stream Overview
217
+
## Screen share video stream overview
218
218
219
219
Repeat steps `1 to 4` from the previous VirtualRawOutgoingVideoStream tutorial.
220
220
221
221
Since the Android system generates the frames, you must implement your own foreground service to capture the frames and send them through using our Azure Communication Services Calling API
0 commit comments