You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The track should be treated as if video details are extra important, and that significant sharp edges and areas of consistent color can occur frequently. This is generally applicable to presentations or web pages with text content. This setting would normally optimize for detail in the resulting individual frames rather than smooth playback, and may take advantage of encoder tools that optimize for text rendering. Artefacts from quantization or downscaling that make small text or line art unintelligible should be avoided.
Different written scripts might require different levels of detail (e.g., so that small features such as aspiration marks can be distinguished), and even a video content hint with a value of "text" might not be adequate for some scripts. Perhaps a "health warning" that a value of "text" provides no guarantee that textual features can be distinguished might be helpful.
This issue was originally reported by @stpeter. This is an I18N issue that we forgot to submit to you previously.
The text was updated successfully, but these errors were encountered:
This isn't just an internationalization issue. Encoder settings such as 4:4:4 can improve text legibility on colored backgrounds. Also, currently the libwebrtc implementation does not take the "text" hint into account in applying encoder settings, only whether the input track came from a screen share.
MediaStreamTrack Content Hints, §2.2 Video Content Hints
https://www.w3.org/TR/2018/WD-mst-content-hint-20180703/#video-content-hints
Different written scripts might require different levels of detail (e.g., so that small features such as aspiration marks can be distinguished), and even a video content hint with a value of "text" might not be adequate for some scripts. Perhaps a "health warning" that a value of "text" provides no guarantee that textual features can be distinguished might be helpful.
This issue was originally reported by @stpeter. This is an I18N issue that we forgot to submit to you previously.
The text was updated successfully, but these errors were encountered: