- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Apr 2018 20:20:11 +0000
- To: public-media-capture-logs@w3.org
> Is it just Chrome's specific policy Yeah hardware accelerated encoders (and decoders, for the case) can fail to initialize/process for a variety of reasons (e.g. a minimu/maximum resolution), so there's always the need for a sw fallback. Note that this is a requirement per platform, i.e. Android/CrOs/Linux/Win/Mac. -- GitHub Notification of comment by yellowdoge Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/142#issuecomment-378732023 using your GitHub account
Received on Wednesday, 4 April 2018 20:20:21 UTC