...
| Element | Description | Maximum size |
|---|---|---|
| {streamName} | Stream name | |
| {duration} | File duration, for MP4 recordings only | |
| {startTime} | Recording start time | 20 characters |
| {endTime} | Recording end time | 20 characters |
| {startTimeMillis} | Recording start time based on server clock | 20 characters |
| {endTimeMillis} | Recording end time based on server clock | 20 characters |
| {sessionId} | Session ID in BASE64 encoding | 60 characters |
| {mediaSessionId} | Media session ID | 36 characters |
| {login} | Login | 32 characters |
| {audioCodec} | Audiocodec | 4 characters |
| {videoCodec} | Videocodec | 4 characters |
...
Sinca build 5.2.458, recording start taimetime, end time and duration time are calculated by stream frames time stamps. note that RTMP stream timestamps are always starting from 0, but WebRTC publisher usually sets full time stamp by its own clock for ever frame.
| Code Block | ||
|---|---|---|
| ||
stream_record_policy_template={streamName}-{startTime}-{endTime}-{duration} |
Since build 5.2.635 it is possible to use start time and end time based on server clock
| Code Block | ||
|---|---|---|
| ||
stream_record_policy_template={streamName}-{startTimeMillis}-{endTimeMillis} |
In general, stream time stamps are different from server clock time stamps.
To calculate recording times more preciosly, audio data should be buffered to keep synchronization. To do this, the following parameter is added
...