search

Recording

OvenMediaEngine can record live streams. You can start and stop recording the output stream through REST API. When the recording is complete, a recording information file is created together with the recorded file so that the user can perform various post-recording processing.

hashtag
Configuration

hashtag
File Publisher

To enable recording, add the <FILE> publisher to the configuration file as shown below. <FilePath> and <InfoPath> are required and used as default values. <FilePath> is the setting for the file path and file name. <InfoPath>is the setting for the path and name of the XML file that contains information about the recorded files. If there is no file path value among parameters when requesting recording through API, recording is performed with the set default value. This may be necessary if for security reasons you do not want to specify the file path when calling the API to avoid exposing the server's internal path. <<RootPath> is an optional parameter. It is used when requesting with a relative path is required when requesting an API. also, it is applied to <FilePath> and <InfoPath> as in the example below.

You must specify .ts or .mp4 at the end of the FilePath string to select a container for the recording file. We recommend using .ts unless you have a special case. This is because vp8 and opus codecs are not recorded due to container limitations if you choose .mp4.

Server.xml
<Publishers>
   <FILE>  
      <!-- [Optional] -->
      <RootPath>/mnt/shared_volumes</RootPath>
      
      <!-- [Must] Recorded file and info path 
           When recording starts via the API, the following path is used as 
           the default path. If a path is set via the API, it will not be used.
      -->
      <FilePath>/${VirtualHost}/${Application}/${Stream}/
         ${StartTime:YYYYMMDDhhmmss}_${EndTime:YYYYMMDDhhmmss}.ts</FilePath>
      <InfoPath>/${VirtualHost}/${Application}/${Stream}.xml</InfoPath>
      
      <!-- [Optional] Recording settings for file-based automatic recording -->
      <StreamMap>
         <Enable>true</Enable>
         <Path>./record_map.xml</Path>
      </StreamMap>
   </FILE>
</Publishers>

hashtag
Recording via REST API

For control of recording, use the REST API. Recording can be requested based on the output stream name (specified in the JSON body), and all/some tracks can be selectively recorded. And, it is possible to simultaneously record multiple files for the same stream. When recording is complete, an XML file is created at the path specified in InfoPath. For a sample of the recorded file information XML, refer to Appendix B.

For how to use the API, please refer to the link below.

Recordchevron-right

hashtag
Automated Recording

Provides a way to automatically start and stop recording upon input stream that matches your file-based settings. In the above settings, the XML file path is specified in StreamMap.Path. You can create the XML file at the specified path and configure automatic recording as follows.

hashtag
Split Recording

Split recording methods provide SegmentInterval and SegmentSchedule. The interval method splits files based on the accumulated recording time. The Schedule method then splits files according to scheduling options based on system time. The scheduling option is the same as the pattern used in crontab. However, only three options are used: seconds/minutes/hour. You can set the SegmentRule parameter to determine whether the start timestamp of the separated recording files will start anew from 0(discontinuity) or continue from where the previous file left off(continuity).

circle-info

SegmentInterval and SegmentSchedule methods cannot be used simultaneously.

hashtag
Appendix A. Macro definition for the recording path

Various macro values are supported for file paths and names as shown below.

Macro
Description

${TransactionId}

Unique ID for the recording transaction. It is automatically created when recording starts. and is released when recording is stopped. In case of split recording, it is distinguished that it is the same transaction.

${Id}

User-defined identification ID

${StartTime:YYYYMMDDhhmmss}

Recording start time

YYYY - Year

MM - Month

DD - Days

hh : Hours (023)

mm : Minutes (0059)

ss : Seconds (00~59)

${EndTime:YYYYMMDDhhmmss}

Recording end time

YYYY - Year

MM - Month

DD - Days

hh : Hours (023)

mm : Minutes (0059)

ss : Seconds (00~59)

${VirtualHost}

Virtual host name

${Application}

Application name

${SourceStream}

Source stream name

${Stream}

Output stream name

${Sequence}

Sequence value that increases when splitting a file in a single transaction

hashtag
Appendix B. Recorded File Information Specification

The following is a sample of an XML file that expresses information on a recorded file.

Was this helpful?