#539: MediaStreamTrack Content Hints
Discussions
2020-08-17
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.
OpenedJul 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.
Explainer¹ (minimally containing user needs and example code): https://github.com/w3c/mst-content-hint/blob/gh-pages/explainer.md
Specification URL: https://www.w3.org/TR/2020/WD-mst-content-hint-20200728/
Tests: [wpt folder(s), if available] https://github.com/web-platform-tests/wpt/tree/master/mst-content-hint
Security and Privacy self-review²: https://github.com/w3c/mst-content-hint/blob/gh-pages/security-privacy-questionnaire.md
GitHub repo (if you prefer feedback filed there): https://github.com/w3c/mst-content-hint/
Primary contacts (and their relationship to the specification):
Organization(s)/project(s) driving the specification: W3C WebRTC Working Group Further details:
I have reviewed the TAG's API Design Principles
Relevant time constraints or deadlines: ideally by september, no hard deadline set
The group where the work on this specification is currently being done: WebRTC WG
Major unresolved issues with or opposition to this specification: none We'd prefer the TAG provide feedback as (please delete all but the desired option):
☂️ open a single issue in our GitHub repo for the entire review