Closed Lis-TV closed 2 years ago
Where can I find the "sparse Matrix - AVC" reference?
The terminology is copied from the WAVE device playback spec.
I think the important bit here is not the presence of B-Frames or the fragmentation at P-Frames. I think what we are trying to check is multiple ISOBMFF fragments per segment, correct?
If so, I suggest to change the wording of the sparse matrix.
Long story short, supporting "p-frame to p-frame with b-frames" in a generic way would be a permanent hack in the current code.
Adding B-Frames is trivial. Should I add them anyway?
The origin of this text is section 10.2.3 of the DPCTF specification.
This does explicitly reference B-frames. @haudiobe, I assume you wrote this?
So I've added B-frames with fragment duration based on the number of B-frames in that case.
There was still an issue in the fragment duration computation. Should be solved by 32f04dd34d8f701edd7f4be068d5522e22a5cb9b.
Resolved in the latest test content, see https://github.com/cta-wave/Test-Content/issues/40#issuecomment-1310031376. I believe this issue can be closed.
2022-11-22: Closed based on Nicholas' validation testing of 2022-10-17 test vectors release.
The test code sparse Matrix - AVC requires for T16 B-Frames to be present:
Fragment contains multiple chunks (p-frame to p-frame with b-frames)
But when I used
ffprobe -i whole_content.mp4 -show_frames
there was only I-frames (pict_type=I
) and P-frames (pict_type=P
)