1931436 - Cannot read a very specific h264 video file (Error Code: NS_ERROR_DOM_MEDIA_DECODE_ERR (0x806e0004) Details: RefPtr<MediaDataDecoder::DecodePromise> __cdecl mozilla::WMFMediaDataDecoder::ProcessError(HRESULT, const char *): MFTManager::Output(2):80004005)

Status: RESOLVED DUPLICATE of bug 1931597

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

Description

[Jean Nicolas]

Attachment: test.zip

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0

Steps to reproduce:

I'm trying to read a specific video file using the html (both attached in the zip file)

The video doesn't start, and the controls of the player cannot make the video start.

This is the only video file for which it happens. All other video files I tested seem to work properly.

This video can properly be read by vlc or Chrome.

Actual results:

The video doesn't start, and the controls of the player cannot make the video start.

There is no error on the console.

Expected results:

The video should start because of the autoplay), or the controls should make it start.

Comment 1

[Jean Nicolas]

Additional infos: bug can be reproduce on multiple PCs and with new firefox profiles

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Mayank Bansal]

Can repro on a build from 2020. So not a new regression.
Profie with media preset logging: https://share.firefox.dev/4erN27j

Comment 4

[az [:az]]

The video stream is 4:2:2/yuvj422p so I'm marking this as a duplicate of 1325847 and possibly related to 1887512, unless :chunmin has any ideas here?

Stream #0:0[0x1](und): Video: h264 (High 4:2:2) (avc1 / 0x31637661), yuvj422p(pc, progressive), 300x170, 185 kb/s, 30 fps, 30 tbr, 1000k tbn (default)

Comment 5

[Alastor Wu [:alwu]]

Currently this issue is a Media Foundation problem, and we won't be able to solve it. We will test it again once we finish the work of using D3D decoder via the ffmpeg.