W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2023

Re: [webrtc-stats] Expose powerEfficientEncoder/Decoder if MediaCapabilities allows it (#732)

From: Sun Shin via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Feb 2023 08:38:27 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1439626009-1677055104-sysbot+gh@w3.org>
> Add an interface under chrome.test (nonstandard stuff) that forces the source of a track into software rendering mode? Demo pages, unlike WPTs, can use non-standard functionality.
> My optimistic read of the meeting was that the other browser vendors wanted to wait until the Media WG had had the chance to review the issue (a week from now?) before supporting the "let MC own it" approach.

@henbos, @alvestrand  Thank you for the updated feedback. Would be the correct understanding if I could prove that software fallback could be identifiable by only using the MC interface, that would be more convincing to other browser vendors?

GitHub Notification of comment by xingri
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/732#issuecomment-1439626009 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 February 2023 08:38:28 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:20:00 UTC