Dale Curtis
69f0b98430
Automatic update from web-platform-tests [WebCodecs] Route 4:4:4 H.264 content to the software decoder. As with https://crrev.com/c/7115500, hardware support for 4:4:4 H.264 is rare. Instead route this content to the software decoder. Also like the linked issue, we can only do this for AVC formatted content since we need the SPS/PPS information to determine this. R=eugene Fixed: 503709314 Change-Id: If2a68fd8a5dad274b2a101a934c2d4d9e1e0d702 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7818666 Reviewed-by: Eugene Zemtsov <eugene@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1625926} -- wpt-commits: 05637f455968b011be7566e7e0a14e49ae00fe63 wpt-pr: 59684
23 lines
562 B
JavaScript
23 lines
562 B
JavaScript
// META: global=window,dedicatedworker
|
|
// META: script=videoDecoder-codec-specific-setup.js
|
|
// META: variant=?h264_444_avc
|
|
|
|
promise_test(async t => {
|
|
await checkImplements();
|
|
|
|
const callbacks = {};
|
|
const decoder = createVideoDecoder(t, callbacks);
|
|
decoder.configure(CONFIG);
|
|
decoder.decode(CHUNKS[0]);
|
|
|
|
let outputs = 0;
|
|
callbacks.output = frame => {
|
|
outputs++;
|
|
assert_equals(frame.timestamp, 0, 'timestamp');
|
|
frame.close();
|
|
};
|
|
|
|
await decoder.flush();
|
|
assert_equals(outputs, 1, 'outputs');
|
|
}, 'Test decoding h.264 4:4:4 content');
|