search

raczek / lavfilters

Automatically exported from code.google.com/p/lavfilters
GNU General Public License v2.0
0 stars 0 forks source link

No playback for h264 4:4:4 video when hardware acceleration is enabled #490

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I record some game footage with x264vfw, at YUV 4:4:4.
That kind of video does not playback if I have hardware acceleration enabled.
It works perfectly fine if I set the hardware decoder to none, or if I untick 
the H.264 checkbox.
I would assume LAV wouldn't use hardware decoding in that case like for hi10p.

This is on MPC-HC x64 1.7.6 (LAV 0.62).

Let me know if you need a sample file.

Original issue reported on code.google.com by stepien....@gmail.com on 29 Sep 2014 at 10:53

GoogleCodeExporter commented 9 years ago 
Fallback to software decoding for 4:4:4 generally works just fine, it however 
has to rely on the file offering this information up front, and if your file 
doesn't do that, there may not be enough information to know that its 4:4:4 and 
it has to use software decoding.

Original comment by h.lepp...@gmail.com on 30 Sep 2014 at 8:01

GoogleCodeExporter commented 9 years ago 
With hardware decoding enabled or not, MPC's media info does tell 4:4:4.
Is that not enough somehow?

Original comment by stepien....@gmail.com on 30 Sep 2014 at 8:11

Attachments:

GoogleCodeExporter commented 9 years ago 
Media Info is pretty useless, it has access to the full file and can do 
whatever it wants, the video decoder doesn't have access to the file at all, it 
only gets the information it is told.

Original comment by h.lepp...@gmail.com on 30 Sep 2014 at 8:23

GoogleCodeExporter commented 9 years ago 
Right, I found two solutions:
- Let x264vfw do the muxing itself.
  This isn't ideal: only one filename possible.
- Switch the container from mkv to avi in msi afterburner.
  This has another problem: MPC-HC won't loop the video properly.

If there is nothing the lavfilters project can do about it, feel free to close 
this issue.

Original comment by stepien....@gmail.com on 30 Sep 2014 at 9:00

GoogleCodeExporter commented 9 years ago 
That seems to indicate that MSI Afterburner creates bad mkv files, where 
detection is not reliable.

Original comment by h.lepp...@gmail.com on 30 Sep 2014 at 10:46