OPC/mediamtx
2
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

replace incoming absolute timestamps of any source (#5081)

Browse Source 
Absolute timestamps are used to generate recording segments, so users
should not be able to change them, unless explicitly allowed.

Parameter useAbsoluteTimestamp allowed to re-enable absolute timestamps
with RTSP and WebRTC, now it is extended to all protocols.
This commit is contained in:
Alessandro Ros
2025-10-13 12:23:51 +02:00
committed by GitHub
parent 75420552b9
commit ccaccc51b4
5 changed files with 27 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/2-usage/14-route-absolute-timestamps.md
+10 -2
View File
@@ -3,8 +3,8 @@
Some streaming protocols allow to route absolute timestamps, associated with each frame, that are useful for synchronizing several video or data streams together. In particular, _MediaMTX_ supports receiving absolute timestamps with the following protocols and devices:
- HLS
- RTSP (when the `useAbsoluteTimestamp` parameter is `true`)
- WebRTC (when the `useAbsoluteTimestamp` parameter is `true`)
- RTSP
- WebRTC
- Raspberry Pi Camera
and supports sending absolute timestamps with the following protocols:
@@ -13,6 +13,14 @@ and supports sending absolute timestamps with the following protocols:
- RTSP
- WebRTC
By default, absolute timestamps of incoming frames are not used, instead they are replaced with the current timestamp. This prevents users from arbitrarily changing recording dates, and also allows to support sources that do not send absolute timestamps. It is possible to preserve original absolute timestamps by toggling the `useAbsoluteTimestamp` parameter:
```yml
pathDefaults:
# Use absolute timestamp of frames, instead of replacing them with the current time.
useAbsoluteTimestamp: false
```
## Absolute timestamp in HLS
In the HLS protocol, absolute timestamps are routed by adding a `EXT-X-PROGRAM-DATE-TIME` tag before each segment: