Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

highly detailed text in video content #35

Open
aphillips opened this issue Feb 27, 2020 · 2 comments · May be fixed by #56
Open

highly detailed text in video content #35

aphillips opened this issue Feb 27, 2020 · 2 comments · May be fixed by #56

Comments

@aphillips
Copy link

MediaStreamTrack Content Hints, §2.2 Video Content Hints
https://www.w3.org/TR/2018/WD-mst-content-hint-20180703/#video-content-hints

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.

@alvestrand
Copy link
Contributor

Given that the content-hint provides no guarantee, just "please try harder in this direction", a health warning seems appropriate.

alvestrand added a commit that referenced this issue Oct 11, 2021
noting that it doesn't generate guarantees of legibility.
Fixes #35
@alvestrand alvestrand linked a pull request Oct 11, 2021 that will close this issue
@aboba
Copy link
Contributor

aboba commented Jan 8, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants