After a change of priorities last year, the launch unfortunately didn't
happen.
But we are now ready to ship and are targeting M111.
The API that would be launched is:
RTCRtpEncodingParameters extension scalabilityMode (
https://w3c.github.io/webrtc-svc
/#dom-rtcrtpencodingparameters-scalabilitymo
When are you hoping to ship?
On Wednesday, January 5, 2022 at 9:16:28 AM UTC-8 yoav...@chromium.org
wrote:
> LGTM3
>
> On Wed, Jan 5, 2022 at 5:52 PM Daniel Bratell wrote:
>
>> LGTM2
>>
>> /Daniel
>> On 2022-01-05 17:51, Chris Harrelson wrote:
>>
>> LGTM1 to ship scalabilityMode, but not the pl
LGTM3
On Wed, Jan 5, 2022 at 5:52 PM Daniel Bratell wrote:
> LGTM2
>
> /Daniel
> On 2022-01-05 17:51, Chris Harrelson wrote:
>
> LGTM1 to ship scalabilityMode, but not the pluralized name or
> referenceScaling.
>
> Please open a new intent if you wish to ship one of the others (otherwise
> this
LGTM2
/Daniel
On 2022-01-05 17:51, Chris Harrelson wrote:
LGTM1 to ship scalabilityMode, but not the pluralized name or
referenceScaling.
Please open a new intent if you wish to ship one of the others
(otherwise this intent-to-ship would be too confusing).
Thanks, and happy new year.
On M
LGTM1 to ship scalabilityMode, but not the pluralized name or
referenceScaling.
Please open a new intent if you wish to ship one of the others (otherwise
this intent-to-ship would be too confusing).
Thanks, and happy new year.
On Mon, Dec 20, 2021 at 12:07 PM 'Chris Cunningham' via blink-dev <
b
Sorry I'm late. Lots of family stuff this month. I'm about to be OOO for
the holidays.
> There seems to be agreement to add support for referenceScaling in Media
Capabilities (https://github.com/w3c/media-capabilities/issues/182) so I'm
assuming that a PR will follow.
I can confirm this agr
At the moment, I think we can safely ship:
- RTCRtpEncodingParameters extension scalabilityMode (
https://w3c.github.io/webrtc-svc/#dom-rtcrtpencodingparameters-scalabilitymode
)
We have an open discussion on whether or not to ship this part on senders
(we've decided not to ship it on receivers):
There seems to be agreement to add support for referenceScaling in Media
Capabilities (https://github.com/w3c/media-capabilities/issues/182) so I'm
assuming that a PR will follow.
Chris - please jump in if I'm misunderstanding the consensus on Issue 182.
RTCRtpEncodingParameters.scalabilityM
Hi Bernard,
Can you clarify what the consensus is on RTCRtpEncodingParameters's
scalabilityMode member? That remains in https://w3c.github.io/webrtc-svc/,
but will it be removed? Meanwhile, referenceScaling is only partly spec'd,
there's no IDL for it but a link to
https://github.com/w3c/media-cap
Harald said:
"It seems like we don't have a strong push towards either the
MediaCapabilities or the Codec Capabilities solution in the issue on the
sender side (https://github.com/w3c/webrtc-svc/issues/49). This is bad for
quick resolution."
[BA] On the receiver/decoder side (for WebRTC-SVC,
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
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 RTCRtpEncodingParameters's scalabilityMode, but is
that right?
Best regards,
Philip
On Mon, Dec 6, 2021
It seems like we don't have a strong push towards either the
MediaCapabilities or the Codec Capabilities solution in the issue on the
sender side (https://github.com/w3c/webrtc-svc/issues/49). This is bad for
quick resolution.
In the interest of getting the uncontroversial parts shipped - what wou
Friendly ping on Yoav's question about timelines.
-mike
On Wed, Nov 10, 2021 at 7:04 PM Yoav Weiss wrote:
> How long of a delay are we talking about here? Weeks? Months? Years?
>
> On Monday, October 25, 2021 at 11:00:46 PM UTC+2 Harald Alvestrand wrote:
>
>> The scalability modes (being able
How long of a delay are we talking about here? Weeks? Months? Years?
On Monday, October 25, 2021 at 11:00:46 PM UTC+2 Harald Alvestrand wrote:
> The scalability modes (being able to set them) are the point of the launch.
> Figuring out which of the desired ones are available seems like it would
The scalability modes (being able to set them) are the point of the launch.
Figuring out which of the desired ones are available seems like it would be
a requirement.
On Mon, Oct 25, 2021 at 9:32 PM Fernando Serboncini
wrote:
> It seems they are asking for a delay on Chrome launching this until
It seems they are asking for a delay on Chrome launching this until the
WebRTC WG makes a decision on it.
It's not clear from the issue that there's a consensus on the right
approach there.
Did you consider launching things separately and delaying the scalability
modes? Or does the whole launch ma
Note - the change request from WebKit (
https://github.com/w3c/webrtc-svc/issues/49) involves removing the list of
scalability modes from the codec information in WebRTC and instead using
the MediaCapabilities API with the "webrtc" usage to detect whether a given
scalability mode is available or no
18 matches
Mail list logo
