W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2021

Re: [webrtc-svc] Changing the interpretation if referenceScaling is absent (#56)

From: chcunningham via GitHub <sysbot+gh@w3.org>
Date: Mon, 20 Dec 2021 22:33:24 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-998320498-1640039602-sysbot+gh@w3.org>
Sorry for the delay. The defaulting language looks right. Ideally most of this language should just appear directly in the MC spec and you should be able to simplify this to something like: 

"Appliciations may use referenceScaling in MediaCapablities to detect decoding support for streams having spatial scalability. Decoding of temporal and quality scalability is assumed to always be supported."

I'm think @drkron will send a PR for MC. When we do add it to MC I'll prefer to define the values more in terms of the stream rather than the decoder.

If referenceScaling set to `true`, this indicates that the video track contains encoded frames that depend on (reference) other frames having a different resolution. This arrangement is typical of streams using spatial scalability. If referenceScaling is set to `false` or is absent, this indicates that the track does not contain video frame references between resolutions. 

I like this^ stream-pov better as that's how MC does most other properties and it allows implementers to say "supported = true" for decoders that actually do support referenceScaling, even if your stream doesn't need it. 

I don't want to speak for @drkron when it comes to timeline he might send a PR. I know folks (including myself) are heading OOO for the holidays. If you want to land this as is or massage some of the feedback above into your current text, I don't object. Always happy to iterate async. 

GitHub Notification of comment by chcunningham
Please view or discuss this issue at https://github.com/w3c/webrtc-svc/pull/56#issuecomment-998320498 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 December 2021 22:33:29 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC