- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Tue, 10 May 2016 22:55:02 +0200
- To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 05/10/2016 10:26 PM, Cullen Jennings (fluffy) wrote: > Question about this ... say I was on a mobile device that hard hardware support for the codec as well as the default software implementation in the browser. Would this tell me which was being used because that is really what I need to track down problems with hardware codecs on mobile devices? That's why we (Chrome implementors) want it! > > >> On May 6, 2016, at 2:29 AM, Harald Alvestrand <harald@alvestrand.no> wrote: >> >> Comment to list: >> >> There's been silence on this since TPAC. I hope the added text reflects >> the TPAC discussions. >> >> >> Den 06. mai 2016 09:59, skrev Harald Alvestrand via GitHub: >>> alvestrand has just merged pull request 33 for >>> https://github.com/w3c/webrtc-stats: >>> >>> == Adds the "implementation" variable to RTCCodec. == >>> Also pulls in the "fingerprint" implementation. >>> >>> Fixes #16 >>> >>> >>> See https://github.com/w3c/webrtc-stats/pull/33 >>> -- Surveillance is pervasive. Go Dark.
Received on Tuesday, 10 May 2016 20:57:54 UTC