- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Mar 2018 22:15:57 +0000
- To: public-media-capture-logs@w3.org
> The implementation status page you point to specifically notes that the supported values currently differ based on the chipset (ARM or Intel) in Chrome and link to bugs that suggest that the values will differ based on the particular chipset (chipsets that support VP9). Am I reading those tables/bugs correctly? Those are informational for developers but they are not offered to the JS, i.e. a hardware accelerated version is only supported if and where there's a software fallback, and a positive response to `isTypeSupported()` is not enough to differentiate among them. In due time we should have wired all possible accelerated encoders, which should be transparent to the users, beyond a nice speed increase / power consumption decrease :-) -- GitHub Notification of comment by yellowdoge Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/142#issuecomment-376693814 using your GitHub account
Received on Tuesday, 27 March 2018 22:16:01 UTC