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

[pull] gh-pages from webrtc:gh-pages #77

Merged
merged 2 commits into from
Dec 5, 2024
Merged

Conversation

pull[bot]
Copy link

@pull pull bot commented Dec 5, 2024

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

StaZhu and others added 2 commits December 4, 2024 15:52
Based on conversation with Chrome Media Team, we should only
support valid mimetype for future new codecs like HEVC.

For HEVC/H.264/AV1, it is recommend to use valid mimetype instead
of just `hvc1`, `avc1` or `av01`.

There are some limitation for `avc1` / `hvc1` as they only allow
"out of band parameter sets", so if capture device can produce
dynamic resolution video stream, only `avc3` / `hev1` can satisfy
the needs as they supports "in band parameter sets".

Chromium may support `hev1` and `avc3` in the future, so also added
these mimetypes for future testing.
Use valid mimetype for HEVC/H.264/AV1 and add `hev1`/`avc3` mimetypes
@pull pull bot added the ⤵️ pull label Dec 5, 2024
@pull pull bot merged commit 45187d9 into Mu-L:gh-pages Dec 5, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants