- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Feb 2022 08:24:33 +0000
- To: public-webrtc-logs@w3.org
I went through my list-of-interesting bugs and found quite a few which were related to hardware encoding or decoding. The last one was the worst but the size of the list emphasizes the need for an API that at least offers an escape hatch. Hardware H264 Encoder is being used instead of OpenH264 on MacOS resulting in poor frame rate / pixelated video https://bugs.chromium.org/p/chromium/issues/detail?id=1142273& Consider adding support for hardware vp8 decoding on Windows. https://bugs.chromium.org/p/chromium/issues/detail?id=1062849 Disabling hardware acceleration silently fails to encode camera frames in WebRTC on macOS https://bugs.chromium.org/p/chromium/issues/detail?id=1168948& If the stream obtained via HTMLVideoElement.captureStream() is sent on peer connection, it does not send any actual data https://bugs.chromium.org/p/chromium/issues/detail?id=1156408 Green Screen on WebRTC (w/ H264 Codec) Recorded Videos when Hardware Acceleration is disabled https://bugs.chromium.org/p/chromium/issues/detail?id=1176817 VP9 decoder shows a green strip at the bottom (Windows only) https://bugs.chromium.org/p/chromium/issues/detail?id=1201801#c11 Encode fps drops sharply after pc.replaceTrack, due to FrameDropper kicking in from too many hugesFrames encoded, when encoding H.264 on MacOS https://bugs.chromium.org/p/webrtc/issues/detail?id=12704 WebRTC video stream shows green and garbled in chrome 91 Beta https://bugs.chromium.org/p/chromium/issues/detail?id=1213063 Resolution cannot ramp-up to 720P on Windows Chrome 91 with HW acceleration enabled https://bugs.chromium.org/p/webrtc/issues/detail?id=12942 VP8 encoder issue when hardware acceleration enabled on mobile device https://bugs.chromium.org/p/chromium/issues/detail?id=1237677 Windows H264 encoder may freeze https://bugs.chromium.org/p/chromium/issues/detail?id=1252710 Android MediaCodec Encoder requires 16-pixel alignment https://bugs.chromium.org/p/webrtc/issues/detail?id=13089 VP8 encoder issue when hardware acceleration enabled on mobile device [https://bugs.chromium.org/p/chromium/issues/detail?id=1237677](https://bugs.chromium.org/p/chromium/issues/detail?id=1237677#c36) iPadOS 15 / iOS 15 unable to decode VP9 stream https://bugs.webkit.org/show_bug.cgi?id=230604#c11 WebRTC Output FPS Drops to 0 and Does Not Recover https://bugs.chromium.org/p/chromium/issues/detail?id=1261560 Android HW Encoder produces corrupted images (also in Google Duo) https://bugs.chromium.org/p/webrtc/issues/detail?id=11337 Chrome Canary - WebRTC RTCPeerConnection.close() not returning https://bugs.chromium.org/p/chromium/issues/detail?id=1264465 root cause was hw decoder deinit WebRTC framesSent plummets for no obvious reason [https://bugs.chromium.org/p/chromium/issues/detail?id=1088650](https://bugs.chromium.org/p/chromium/issues/detail?id=1088650#c56) Corrupt WebRTC video from VP9 hardware decoder on Intel/Windows https://bugs.chromium.org/p/chromium/issues/detail?id=1279214 Safari: VP9-SVS no video stream from remote peer on some devices https://bugs.webkit.org/show_bug.cgi?id=231074 Apple Silicon: Black screen share on remote side of peerconnection https://bugs.webkit.org/show_bug.cgi?id=236870 H264 HW encoding/decoding cause breaks the picture https://bugs.chromium.org/p/webrtc/issues/detail?id=13693 H264 HW encoder produces 1 key frame per second on webrtc https://bugs.chromium.org/p/chromium/issues/detail?id=1296524 Chrome version 98(which introduces HW encoding) degrades sent resolution and increases keyframe generation https://bugs.chromium.org/p/chromium/issues/detail?id=1295815 -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/98#issuecomment-1054005251 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 February 2022 08:24:35 UTC