1438045 - [wpt-sync] PR 7929 - Test for segments that don't start with keyframe.

Status: NEW

(Core :: Audio/Video: Playback, defect, P3)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

On Safari, segments that do not start on a keyframe cause a decoder
error. This test exposes that bug.
See https://bugs.webkit.org/show_bug.cgi?id=160460

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=54d2220dcbbec27ea227b0206ebdea3de749d103

Comment 2

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=b0a303db69fb244400c7b1042465a06853f09a5f

Comment 3

[Ralph Giles (:rillian)]

Jean-Yves, looks like we fail the new test. Is that correct?

Comment 4

[Jean-Yves Avenard [:jya]]

not looking at the actual content, but one of the test is with webm and looking at the name:
webm/webm-no-keyframe-cluster.webm

a webm cluster must start with a keyframe per spec.
https://www.webmproject.org/docs/container/
"Muxers should treat all guidelines marked SHOULD in this section as MUST. This will foster consistency across WebM files in the real world."

Key frames SHOULD be placed at the beginning of clusters.
    Having key frames at the beginning of clusters should make seeking faster and easier for the client.