- From: youennf via GitHub <noreply@w3.org>
- Date: Thu, 02 Oct 2025 11:57:54 +0000
- To: public-webrtc-logs@w3.org
> * frames don't necessarily come from the network but we would still want "inbound-rtp" stats objects to show up since it contains valuable decode and playout related metrics This is one difference between encoded transform, which does not allow to decode frames until receiving packets and insertable streams which allow to do so. I would tend to wait for new proposals like `encoded sink` to decide whether we want to do this change. It seems strange to expose inbound-rtp stats while there is no rtp at all. Maybe these new proposals would call for another kind of stat, or maybe no stat will be needed (web app fully controls what goes into the sink and has MediaStreamTrack stats + rvfc on the output side). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/816#issuecomment-3360836769 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 October 2025 11:57:55 UTC