- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Oct 2023 08:51:18 +0000
- To: public-webrtc-logs@w3.org
**Proposal:** Make `media-source` reflect input to the sender, NOT the track's stats (`track.stats`). This means that: 1. If adaptation is happening, the media source fps can be lower than the `track.stats` fps. 2. The `media-source` is not "per track", since it reflects the `outbound-rtp`'s adaptation. E.g. two senders encoding the same track could still result in two `media-source` objects with the same `trackIdentifier`. 3. This is what Chromium has already implemented. So media-source and outbound-rtp would map 1:1 if not for the fact that outbound-rtp lifetime is said to start when the first packet is sent, and media-source could be created as soon as `pc.addTrack` is called -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/708#issuecomment-1774720083 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 October 2023 08:51:19 UTC