#539: MediaStreamTrack Content Hints

Visit on Github.

Opened Jul 29, 2020

Saluton TAG!

I'm requesting a TAG review of MediaStreamTrack Content Hint.

This specification extends MediaStreamTrack to provide a media-content hint attribute. This optional hint permits MediaStreamTrack consumers such as PeerConnection (defined in [webrtc]) or MediaRecorder (defined in [mediastream-recording]) to encode or process track media with methods more appropriate to the type of content that is being consumed.

☂️ open a single issue in our GitHub repo for the entire review

Discussions

Discussed Aug 1, 2020 (See Github)

Ken: I looked at it... applying other algorithms to streams, noise reduction, want this hint. I would want to make sure you're getting the right type of hint. Depends on the algorithms...

Sangwhan: Main question.. who sets the content hint?

Ken: The author.

Yves: Yeah, the producer.

Yves: Should be an option for games... low-latency... expense of (?) being more precise.. Respect a certain latency... some things hwere you don't want to have a delay.

Sangwhan: degradation preference: framerate or resolution or (?). Games might want to maintain the framerate. Not sure what might want to maintain resolution in favour of framerate.

Ken: Something in style guide about naming...

Yves: Since it's a hint, I'm ok with it.

Sangwhan: I'm also OK with this. I just have one question...

Yves: Not sure about the encoding part... don't know that they need to be hints or more enforced than hints.

Ken: I'll file an issue on (?) as well.

Comment by @kenchris Aug 18, 2020 (See Github)

Our style guide says that string enums should be lowercase and with hyphen, thus "speechRecognition" should be "speech-recognition": https://w3ctag.github.io/design-principles/#casing-rules

Enumeration values | Lowercase, dash-delimited | e.g. "no-referrer-when-downgrade"

Comment by @cynthia Aug 18, 2020 (See Github)

Why are arbitrary values (anything aside from well-known values or "", since on the surface it is a DOMString property) disallowed for hints? (Wasn't quite clear from the spec; is it because internally [e.g. during transport] these values are encoded into enums?)

Comment by @kenchris Aug 19, 2020 (See Github)

Apart from the filed issues, we are fine with this. Closing.

Thanks for staying at home with the TAG :-)