Recordings are an important part of the live video stack as they convert live, ephemeral content into a long-term asset. But the use of this asset varies from business to business depending on their respective use case.
For example, one of the common use cases for recording is for archival purposes versus, for some, its content to be publicized.
Based on your end goal, you can choose one of the recording types and its implementation. You can understand some key differences using the comparison table below.
- Recording types
- Configure storage
|Recording Features||Browser Recording [Recommended]||SFU Recording [Advanced]|
|Resolution||Upto 1080p||Only 720p|
|Participant-level Audio/Video Tracks||Not Available||Available|
|Portrait/Landscape Mode||Available||Not Available|
|Start/Stop Recording||On-demand||Auto start/stop with the session|
|Custom Layout||Available||Not Available|
|Role-Specific Recording||Available||Not Available|
|Recording Output||MP4||MP4, WebM|
Browser Recording [Recommended]
Browser recording is built to give users a participant-first recording experience. When enabled, our browser-based bot Beam joins a room to record the viewport like any other participant. The output is an MP4 file that captures the room's published audio/video tracks together into one single file. This option removes the complexity of syncing various audio/video tracks and offers an intuitive, participant-first recording experience. An example use case is to record a sales meeting for later usage.
SFU Recording [Advanced]
SFU recording is built for advanced use cases, which require individual audio and video tracks for each participant. This recording option allows you to isolate recording at a participant level. Track recording allows you to record audio and video streams separately, making it easier to edit, layer, or reuse each of them. An example use case is to record a live podcast and later edit it for publishing.
You can get track recordings in two forms:
Individual: Media for each peer is provided as a separate mp4 file. This file will have both audio and video of the peer. These files can be used for offline review or in implementing custom composition.
Composite and video of all peers are composed as per their joining/leaving the meeting and provided as a single mp4. This file can be used for offline viewing of the meeting.
Recordings for Live Streaming Use-cases
These are the types of live streaming recordings:
Video-on-demand recording is available for our Interactive Live Streaming capability. This recording will be a file with an M3U8 file (same playback format as HLS), which can be used for replaying your HLS stream. This option is more suitable for Video-on-Demand use cases. For the implementation of this type of recording, please contact us.
A multi-resolution recording is available for Interactive Live Streaming capability. This type of recording will have a multi-file structure for all available resolutions of the stream. The output will be multiple MP4 files with these resolutions: 240p, 480p, 720p, and 1080p. For an implementation of this type of recording, please contact us.
You can specify a cloud storage location for your recording files in your template. Our current offering allows you to store your recordings in Amazon S3 buckets. Once you configure the S3 config of your bucket in a template, all respective recordings of sessions created via those templates will be sent to your configured bucket. This holds true for all types of aforementioned recordings.
How to configure recording storage?
Generate your credentials; for this example, you can check out a guide from AWS. You can skip this step if you already have credentials. Please note that if you are running a Browser recording, you need to give upload permission to your key, but if you are running an SFU recording, you need to give both upload and download permission.
Go to 100ms Dashboard and go to template configuration by selecting the configure icon.
- Head over to the Destinations tab.
Key in your credentials (using an example of an S3 bucket here):
- Access Key: Access Key generated from AWS IAM Console
- Secret Key: Secret Key generated from AWS IAM Console
- Bucket: Name of the bucket in S3
- Region: Name of the region, for example, ap-south1
- Prefix for Upload Path: Define the directory name (optional)
- Use the Validate Config button to test your storage setup.
- You will see a message that the AWS configuration was successfully validated.
The above message ensures that your configuration is successful now, and all your recordings will start collecting in your configured destination.