mediamtx/internal/protocols/webrtc
Alessandro Ros 0cdae40fe3
estimate absolute timestamp more precisely (#5078)
When the absolute timestamp of incoming frames was not available, it
was filled with the current timestamp, which is influenced by latency
over time.

This mechanism is replaced by an algorithm that detects when latency is
the lowest, stores the current timestamp and uses it as reference
throughout the rest of the stream.
2025-10-12 11:02:14 +02:00
..
from_stream.go rewrite Unit definition (#5079) 2025-10-11 12:18:51 +02:00
from_stream_test.go estimate absolute timestamp more precisely (#5078) 2025-10-12 11:02:14 +02:00
incoming_track.go estimate absolute timestamp more precisely (#5078) 2025-10-12 11:02:14 +02:00
outgoing_track.go switch to gortsplib/v5 (#4978) 2025-09-16 13:10:34 +02:00
peer_connection.go estimate absolute timestamp more precisely (#5078) 2025-10-12 11:02:14 +02:00
peer_connection_test.go remove context from webrtc.PeerConnection arguments (#4854) 2025-08-12 15:19:59 +02:00
stats.go api: add additional WebRTC statistics (#4795) 2025-07-29 10:43:52 +02:00
stats_interceptor.go api: add additional WebRTC statistics (#4795) 2025-07-29 10:43:52 +02:00
tcp_mux_wrapper.go remove custom forks of pion/webrtc and pion/ice (#4861) 2025-08-12 14:30:08 +02:00
to_stream.go estimate absolute timestamp more precisely (#5078) 2025-10-12 11:02:14 +02:00
to_stream_test.go estimate absolute timestamp more precisely (#5078) 2025-10-12 11:02:14 +02:00