Skip to content

Commit c6f22a0

Browse files
authored
Update call-recording.md
1 parent 54355b8 commit c6f22a0

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

articles/communication-services/concepts/voice-video-calling/call-recording.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -37,18 +37,20 @@ Call Recording supports multiple media outputs and content types to address your
3737

3838
### Video
3939

40-
| Channel Type | Content Format | Resolution | Sampling Rate | Output | Description |
41-
| :----------- | :------------- | :----------- | :---- | :--------------------------- | :------------ |
42-
| mixed | mp4 | 1920x1080, 16 FPS (frames per second) | 16 kHz | single file, single channel | mixed video in a default 3x3 (most active speakers) tile arrangement with display name support |
40+
| Channel Type | Content Format | Resolution | Sampling Rate | Bit rate | Data rate | Output | Description |
41+
| :----------- | :------------- | :----------- | :---- | :----------- | :------------ | :--------------------------- | :------------ |
42+
| mixed | mp4 | 1920x1080, 16 FPS (frames per second) | 16 kHz | 1 mbps | 7.5 MB/min* | single file, single channel | mixed video in a default 3x3 (most active speakers) tile arrangement with display name support |
4343

4444
### Audio
4545

46-
| Channel Type | Content Format | Sampling Rate | Output | Description |
47-
| :----------- | :------------- | :----------- | :---- | :---------------- |
48-
| mixed | mp3 & wav | 16 kHz | single file, single channel | mixed audio of all participants |
49-
| unmixed | wav | 16 kHz | single file, up to 5 wav channels | unmixed audio, one participant per channel, up to five channels |
50-
46+
| Channel Type | Content Format | Sampling Rate | Bit rate | Data rate | Output | Description |
47+
| :----------- | :------------- | :----------- | :--------- | :--------- | :--------- | :---------------- |
48+
| mixed | mp3 | 16 kHz | 48 kbps | 0.36 MB/min* | single file, single channel | mixed audio of all participants |
49+
| mixed | wav | 16 kHz | 256 kbps | 1.92 MB/min | single file, single channel | mixed audio of all participants |
50+
| unmixed | wav | 16 kHz | 256 kbps | 1.92 MB/min* per channel | single file, up to 5 wav channels | unmixed audio, one participant per channel, up to five channels |
5151

52+
> [*NOTE]
53+
> Azure Communication Services provides short term media storage for recordings. **Recordings will be available to download for 48 hours.** After 48 hours, recordings will no longer be available.
5254
5355
## Get full control over your recordings with our Call Recording APIs
5456
Call Recording APIs can be used to manage recording via internal business logic triggers, such as an application creating a group call and recording the conversation. Also, recordings can be triggered by a user action that tells the server application to start recording. Call Recording APIs use exclusively the `serverCallId` to initiate recording. To learn how to get the `serverCallId`, check our [Call Recording Quickstart](../../quickstarts/voice-video-calling/get-started-call-recording.md).
@@ -70,9 +72,9 @@ Call Recording use [Azure Event Grid](../../../event-grid/event-schema-communica
7072

7173

7274
> [!NOTE]
73-
> Azure Communication Services provides short term media storage for recordings. **Recordings will be available to download for 48 hours.** After 48 hours, recordings will no longer be available.
75+
> Mp3 and Mp4 formats use lossy compression that results in variable bitrate; therefore, data rate values in the tables above reflect the theoretical maximum. WAV format bitrate is fixed, so the data rate provided above is a high-confidence estimate.
7476
75-
An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated` is published when a recording is ready for retrieval, typically a few minutes after the recording process has completed (for example, meeting ended, recording stopped). Recording event notifications include `contentLocation` and `metadataLocation`, which are used to retrieve both recorded media and a recording metadata file.
77+
An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated` is published when a recording is ready for retrieval, typically a few minutes after the recording process has completed (for example, meeting ended, recording stopped). Recording event notifications include `contentLocation` and `metadataLocation`, which are used to retrieve both recorded media and a recording metadata file.
7678

7779
### Notification Schema Reference
7880

0 commit comments

Comments
 (0)