...
- MP4 for H.264 + AAC codecs
- WebM for VP8 + Vorbis codecs
- WebM for H264 + opus codecs (since WCS build 2.0.2001)
- TS for H.264 + ADTS
- MKV (since WCS build 5.2.1190)
...
Note that audio only streams are always recorded to MP4 container (using AAC codec).
Since build 2.0.2001, WebM container is supported for WebRTC H264+opus streams recording
| Code Block | ||
|---|---|---|
| ||
record_formats=h264-webm,vp8-webm |
Recording to MPEG-TS container
...
Updating the MP4 container atoms with actual recording data
Since build 5.2.1990 it is possible to update MP4 atoms data on the fly
...
This feature allows to play the recording file even if the recording was interrupted due to some error. The media data in such MP4 file will be available to play according to MP4 atoms.
Recording file rotation by MP4 header filling
Since build 5.2.2012 a recording MP4 file will automatically be rotated when MOOV atom in MP4 header becomes filled. For example, if a 1920x1080 stream is publishing with bitrate 3 Mbps and 30 fps, and the stream is recording with the following settings
| Code Block | ||
|---|---|---|
| ||
mp4_container_moov_first_reserve_space=true
mp4_container_moov_reserved_space_size=2048 |
then one recording part should be near 22 minutes long (near 510 Mb in size).
Client side
If stream recording is enabled on the server, whether the stream is recorded or not is determined by the value of record parameter passed into the createStream function in the script of the publisher client:
...