Re: [webrtc-extensions] Add onssrcchange/oncsrcchange events to RTCRtpReceiver (#243)

My understanding is SSRC lives in the RTP header, available as soon as an SRTP-authenticated packet arrives, long before any depacketization or codec decode.

> audioTag.srcObject = stream /w track; would simply never fire because you need to set srcObject first in order to unblock decoding and you need decoding for onssrcchange to fire.

Chrome is skipping more than decode absent a sink if this is true. This seems like an implementation optimization, and not something we want to standardize.

I can't think of a reason other than implementation convenience to limit the API to when sinks exist. Conceptually, I'd expect the event to fire regardless of sink.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/243#issuecomment-3366542832 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 3 October 2025 17:17:57 UTC