search

w3c / webrtc-svc

W3C Scalable Video Coding (SVC) Extension for WebRTC
https://w3c.github.io/webrtc-svc/
Other
39 stars 14 forks source link

Changing the interpretation if referenceScaling is absent #56

Closed aboba closed 2 years ago

aboba commented 2 years ago

This PR changes the interpretation when referenceScaling is absent.

Reflects discussion in Issue https://github.com/w3c/media-capabilities/issues/182

@chcunningham PTAL.

Preview | Diff

chcunningham commented 2 years ago

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.