- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Oct 2024 22:49:03 +0000
- To: public-webrtc-logs@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc: == Spec says to send black frames for ended tracks == The spec says: _"If [track](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-track) is ended, or if the track's output is disabled, i.e. the track is disabled and/or muted, the [RTCRtpSender](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender) MUST send black frames (video) and MUST NOT send (audio). In the case of video, the [RTCRtpSender](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender) SHOULD send one black frame per second. If [track](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-track) is null then the [RTCRtpSender](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender) does not send."_ This seems unequivocal: sender.track.stop() = send black frames! Pity no browser is doing this. [Try it](https://jsfiddle.net/jib1/Lay5g92r/) (local video on the left, remote video on the right): - Chrome: <img width="244" alt="image" src="https://github.com/user-attachments/assets/bdd1cdec-9f8d-472b-9819-e0e891dd1c98"> - Safari: <img width="238" alt="image" src="https://github.com/user-attachments/assets/c7b62c12-643e-4b8e-9b86-2ba766a0fafc"> - Firefox: <img width="241" alt="image" src="https://github.com/user-attachments/assets/cb7773bf-25fc-45c1-a5f7-3f57c7f070b7"> Ignoring the variance on the left (different issue), none of the browsers send black frames on `ended`. ### Do we: 1. File bugs on implementations? 2. Or align the spec with implementations? Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3014 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 October 2024 22:49:04 UTC