Re: [blink-dev] Question regarding webrtc

the discuss-webrtc list is probably a better place to ask in the future. Adding video to an audio-only call will, by design, require renegotiation. There is a sample for that at https://webrtc.github.io/samples/src/content/peerconnection/upgrade/ - it a

Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

the ID of the sink needs to be obtained from navigator.mediaDevices.enumerateDevices because https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/selectAudioOutput is not implemented anywhere? Am Di., 30. Aug. 2022 um 19:02 Uhr schrieb 'Ajay Rahatekar' via blink-dev < blink-dev@chromium.o

[blink-dev] Re: [discuss-webrtc] Deprecated "track" and "stream" stats are unshipped in M109.

Henrik, while I understand that this has been ongoing for a while in Canary and Beta for a while without anyone raising issues, the timeline "tomorrow

Finch trials percentages history (was: Re: [blink-dev] Re: Intent to Remove: Rename User-Agent Client Hint ACCEPT-CH tokens)

old thread alert (hence reducing the cc list) but I've found the data scraped by https://github.com/nornagon/finch-trials-history (see https://github.com/nornagon/finch-trials for how it works) to be incredibly useful (most recently in this issue

Re: [blink-dev] Intent to deprecate and remove: SDES key exchange for WebRTC

stats here: https://www.chromestatus.com/metrics/feature/timeline/popularity/2383 Away with it! Am Do., 26. Aug. 2021 um 10:45 Uhr schrieb 'Harald Alvestrand' via blink-dev : > Contact emails...@chromium.org > > ExplainerNone > > Specificationhttps://www.rfc-editor.org/rfc/rfc8826#section-4.3.1 >

Re: [blink-dev] Intent to deprecate and remove: SDES key exchange for WebRTC

t :-) > > >> >> >>> >>> >>>> What's the requested timeline for the deprecation part of this? >>>> >>> >>> I'd like to get the deprecation warning in 95 (stable Oct 19), start >>> throwing in 97 (stable Jan

Re: [blink-dev] Re: Intent to Ship: WebRTC Scalable Video Coding extensions

Am Mi., 8. Dez. 2021 um 17:52 Uhr schrieb Philip Jägenstedt < foo...@chromium.org>: > Hi Harald, > > Can you spell out what the uncontroversial parts of this would be? Looking > at the IDL in https://w3c.github.io/webrtc-svc/ it looks like it's all > about modes. > > My guess is that it's RTCRtpEn

Re: [blink-dev] Re: Intent to deprecate and remove: SDES key exchange for WebRTC

Am Sa., 26. März 2022 um 21:39 Uhr schrieb dxssx dxssx < dxssx.dx...@gmail.com>: > Is this the right place to ask question? (I came across from google > results) > the discuss-webrtc mailing list is a better place (so please remove blink-dev when responding) > Just curious about the intention "

Re: [blink-dev] Ready for Developer Testing: Media Previews opt-out

Interesting, this goes in the direction of https://github.com/w3c/mediacapture-extensions/issues/2 which I had considered "that ship has sailed". The spec landed https://w3c.github.io/mediacapture-extensions/#camera%20and%20microphone%20picker but I don't recall any implementations. Will this be

Re: [blink-dev] Re: [discuss-webrtc] Re: PSA: H264 profile level changed from 3.1 to 4.2

I haven't heard many complaints from the larger vendors using H264 yet. And I know many of them test in Chromium Canary and Beta as they should. Bear with me... the original change is quite good as it makes the announced capabilities match the actual software decoder capabilities: https://webrtc

Re: [blink-dev] Intent to Ship: WebRTC Codec Selection API

Am Do., 21. Sept. 2023 um 10:43 Uhr schrieb Florent Castelli < orp...@chromium.org>: > > > On Wed, Sep 20, 2023 at 5:21 PM Yoav Weiss wrote: > >> LGTM1 >> >> On Wed, Sep 20, 2023 at 11:48 AM Florent Castelli >> wrote: >> >>> Contact emailsorp...@chromium.org >>> >>> Explainer >>> https://github.

[blink-dev] Intent to Ship: DTLS ClientHello extension permutation (WebRTC)

Contact emails phan...@microsoft.com, h...@chromium.org Specification https://datatracker.ietf.org/doc/rfc8446 Summary Randomize the order of DTLS ClientHello extensions, to reduce potential ecosystem brittleness. This is a WebRTC specific follow-up to https://groups.google.com/a/chromium.org/

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

Should/can this also be applied to WebRTC's DTLS connections? (we don't have numbers but that can be fixed) Am Mo., 25. Sept. 2023 um 19:13 Uhr schrieb Yoav Weiss < yoavwe...@chromium.org>: > LGTM1 to remove support, given that 0.009% of TLS connections divided by > ~30 is roughly at our typical

Re: [blink-dev] Intent to Ship: DTLS ClientHello extension permutation (WebRTC)

mium.org/g/blink-dev/c/bYZK81WxYBo/m/lKLrZ_P2BwAJ. >> Big fan! >> > heh, great original I2S ;-) > On Fri, Sep 22, 2023 at 12:00 AM 'Philipp Hancke' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Contact emails >>> phan...@micros

[blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

Contact emails *phan...@microsoft.com , bernard.ab...@microsoft.com *Explainer *None*Specification *https://www.w3.org/TR/webcodecs-av1-codec-registration/#dom-av1encoderconfig-forcescreencontenttools

Re: [blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

Am Mi., 25. Okt. 2023 um 18:40 Uhr schrieb Mike Taylor < miketa...@chromium.org>: > On 10/20/23 2:27 PM, 'Philipp Hancke' via blink-dev wrote: > > Contact emails > > > * phan...@microsoft.com , > bernard.ab...@microsoft.com * Explainer > > * None * &

Re: [blink-dev] Intent to Prototype: MediaStreamTrack Stats (Audio)

[snip] > > > *Web developers*: Positive > > > Any links? > > > I don't have any links but I've been told that web developers have been > "asking for input latency metrics for years". > On behalf of Google, Google Meet web developers are asking for both > dropped frames ratio metrics and input late

Re: [blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

>> On Wednesday, November 1, 2023 at 3:07:22 PM UTC+1 >> philipp...@googlemail.com wrote: >> >>> Am Mi., 25. Okt. 2023 um 18:40 Uhr schrieb Mike Taylor < >>> miketa...@chromium.org>: >>> >>>> On 10/20/23 2:27 PM, 'Ph

[blink-dev] Intent to Ship: RTCRtpSender setParameters() extensions for requesting the generation of a key frame

Contact emails phan...@microsoft.com, ma...@microsoft.com Explainer https://fippo.github.io/webrtc-explainers/rtcrtpsender-setparameters Specification https://w3c.github.io/webrtc-extensions/#rtcrtpsender-setparameters-keyframe Summary Adds an optional second parameter to WebRTC's RTCRtpSend

[blink-dev] Intent to Ship: RTCIceCandidate url and relayProtocol attributes

Contact emails phan...@microsoft.com Explainer None Specification https://w3c.github.io/webrtc-pc/#rtcicecandidate-interface Summary https://w3c.github.io/webrtc-pc/#rtcicecandidate-interface gets implementations for two new properties for RTCIceCandidate objects emitted from the 'icecandid

[blink-dev] Re: Intent to Ship: RTCIceCandidate url and relayProtocol attributes

Am Mi., 14. Feb. 2024 um 16:09 Uhr schrieb Yoav Weiss (@Shopify) < yoavwe...@chromium.org>: > > > On Monday, February 12, 2024 at 7:52:17 PM UTC+1 philipp...@googlemail.com > wrote: > > Contact emails > > phan...@microsoft.com > > Explainer > > None > > > I think it would be useful to write a few

Re: [blink-dev] Intent to ship: MP4 container support for MediaRecorder

Safari's "choice" of containers and codecs has basically led to a situation where there was no interoperable way to record a video using MediaRecorder that could be played in other browsers? Am Do., 29. Feb. 2024 um 01:46 Uhr schrieb 'Sunggook Chue' via blink-dev < blink-dev@chromium.org>: > Here

Re: [blink-dev] Intent to ship: MP4 container support for MediaRecorder

Yoav, in WebRTC land "we have a sample for that" (thanks to the one and only WebRTC devrel guy Sam Dutton, I think I stole this tagline from him)! https://webrtc.github.io/samples/src/content/getusermedia/record/ with recent changes to improve MP4 support. Discovery currently happens with isTyp

Re: [blink-dev] Re: [discuss-webrtc] Deprecated "track" and "stream" stats are unshipped in M109.

ut you have to look at the non-deprecated locations: > RTCOutboundRtpStreamStats > <https://w3c.github.io/webrtc-stats/#outboundrtpstats-dict*> and > RTCInboundRtpStreamStats > <https://w3c.github.io/webrtc-stats/#dom-rtcinboundrtpstreamstats> > dictionaries > instead (type == &q

Re: [blink-dev] Intent to Deprecate and Remove: WebRTC's RTCStats of type "track" and "stream".

Am Fr., 27. Jan. 2023 um 11:49 Uhr schrieb Henrik Boström : > *Contact emails* > h...@chromium.org, h...@chromium.org > > *Background* > I attempted to remove this feature before but had forgotten to file an > intent to deprecate, background here >

Re: [blink-dev] Intent to Deprecate and Remove: Legacy callback-based RTCPeerConnection.getStats() API

hey Yoav, Am Fr., 17. Feb. 2023 um 08:52 Uhr schrieb Yoav Weiss < yoavwe...@chromium.org>: > Hey Henrik! > > I think the general outline of the plan makes sense, but the timelines > seem too aggressive. As we've recently seen in the track stats removal, > there can be a time difference between th

[blink-dev] PSA: Removal of WebRTC getStats encoderImplementation "unknown" and dataChannelIdentifier "-1"

The WebRTC getStats API exposes the encoder and decoder implementation names for outbound and inbound video: https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-encoderimplementation It will no longer provide the value “unknown” in cases where statistics are queried before a video f

[blink-dev] Intent to Ship: WebRTC RTP header extension control

Contact emails h...@google.com, h...@google.com, phan...@microsoft.com (sticking to my already subscribed email for sending) Explainer https://docs.google.com/document/d/1y1hTsMeav5ijPvoqu1R6U4YC564i1QzgkMeIqWhgiis/edit# (slightly outdated but still conveys the general idea) Spec https://w3c.

Re: [blink-dev] Intent to Implement and Ship: Per-frame quantizer in VideoEncoder

Am Mi., 19. Juli 2023 um 14:25 Uhr schrieb Yoav Weiss < yoavwe...@chromium.org>: > > > On Thu, Jul 13, 2023 at 10:53 PM 'Eugene Zemtsov' via blink-dev < > blink-dev@chromium.org> wrote: > >> Any new feedback or resolution on this one? >> >> On Fri, Jul 7, 2023 at 5:53 AM Sangwhan Moon wrote: >> >