The Dolby Interactivity APIs platform enables recording conferences in two ways. The recording type depends on the liveRecording parameter:
- If liveRecording is set to true, the recording file, in MP3 or MP4 format, is available at the end of the conference.
- If liveRecording is set to false, the recorded conference is available via the replay method.
To record a conference in MP3 or MP4 format, the Dolby Interactivity APIs platform uses a special participant called Mixer. When any conference participant calls the recording.start() method, Mixer joins a conference and begins recording a conference. The recording stops when Mixer leaves a conference, which occurs when a participant calls recording.stop() or when the conference ends.
To join conferences, Mixer uses the enabled MixingOptions parameter. This option allows the application to treat Mixer as a special participant who is not visible to other conference participants.
Application users can record conferences using any layouts, even different from layouts used during conferences. To change the default recording layout, provide the desired Recording Mixer Layout URL in the dashboard. The recording layout is only visible to Mixer; other conference participants cannot see the recording layout during a conference.
Mixer can only join conferences when the liveRecording parameter is set to true. When the liveRecording parameter is disabled, the recorded conference is not available in MP3 or MP4 files, it is only available through the replay method. However, the Remix REST API enables creating MP3 and MP4 files out of such recordings. The Remix REST API allows Mixer to access the replayed conference using the replay method and record the replayed conference to generate the recorded files after the end of the replay. This solution requires more time because Mixer has to replay the entire conference to record it.