fix(iso): use hvc1 sample entry for H.265 fMP4#2253
Draft
modeitsch wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hvc1instead ofhev1hev1entries while addinghvc1supportRoot cause
go2rtc advertises H.265 MSE streams with an
hvc1codec string, but the fMP4 init segment was written with anhev1sample entry. Some browsers reject that mismatch when creating or appending to the MSE SourceBuffer.Validation
GOCACHE=/private/tmp/go-build-cache GOPATH=/private/tmp/go-path go test ./pkg/isoFixes #2205