Hey - we’re trying to align individual participant tracks to the composite from Room Composite Egress and want to stop estimating it via audio cross-correlation.
Looking at your protocol repo, RTCPSenderReportState (NTP<->RTP mapping) and RTPDrift (measured per-track clock rate) already exist internally. A few questions:
- Can any of that be surfaced per-track in FileInfo or the egress webhook payload?
- What’s currently written in the manifest_location JSON? Does it include any RTP/NTP timing data?
- If not exposed today, is this something your team would consider exposing — or a reasonable feature request?
Ideally we would get ~5ms accuracy across 1hr sessions, which should be straightforward with the data you’re already tracking but very hard in post processing.