- From: Danilo Bargen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Apr 2022 14:50:04 +0000
- To: public-webrtc-logs@w3.org
> developers are already having to write "if safari and 15.1... disable h264" kinds of conditions.... In case this information is useful, at Threema we already have a exclusion list of devices with broken hardware codecs. (Not surprisingly, all of them are made by Samsung.) https://github.com/threema-ch/threema-android/blob/557b69f33dd1db96f58e41f6602e32522470f53e/app/src/main/java/ch/threema/app/voip/Config.java#L59-L64 Additionally we also have an exclusion list for hardware AEC: https://github.com/threema-ch/threema-android/blob/557b69f33dd1db96f58e41f6602e32522470f53e/app/src/main/java/ch/threema/app/voip/Config.java#L35-L41 Maybe an API for disabling hardware acceleration for video codecs could be extended to also support disabling hardware AEC? -- GitHub Notification of comment by threema-danilo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/98#issuecomment-1091836338 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 April 2022 14:50:06 UTC