test(playback): clarify LL-HLS over CMAF characterization - #276
Open
MrFr3di wants to merge 1 commit into
Open
Conversation
10 tasks
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
1 participant
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.
Refs #264
Clarifies the existing Media3 regression characterization terminology without changing fixture bytes, playback construction, assertions, or production behavior.
The test states explicitly that the defect is a byte-range LL-HLS delivery failure over CMAF/fMP4 media. LL-HLS is the delivery/signaling layer; CMAF/fMP4 is the media packaging. The fixture still uses the same AndroidX CMAF
audio_init.mp4and boundedaudio_2.m4sbytes exposed throughEXT-X-PART ... BYTERANGE.Changes are naming/KDoc/diagnostic text only: 1 file, +7/-6. Current
mainadvanced only through the unrelated #275 Android test-harness fix; GitHub reports this PR mergeable.Exact head
921ffe641bccb047cd656310f5bf86082da714adis terminal GREEN on all triggered lanes:No production HLS/parser/player behavior changes.