OTZIILORD / lavfilters

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

4:4:4 playback corrupted #146

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Describe the issue you're having:
There is a green bar at the bottom of video frame when playing 4:4:4 file

How can the issue be reproduced? Sample File?
Just play sample file: http://www.mediafire.com/?7hxf4leo4vu729o

What version of the product are you using? In which Player?
LAVFilter 0.42 (also tried with latest revision - 2364519bf2f3)
MPC-HC 1.5.3.3875

Please provide any additional information below.
madVR's internal decoder can play sample without issues

Original issue reported on code.google.com by porsche9...@gmail.com on 5 Dec 2011 at 1:21

GoogleCodeExporter commented 8 years ago
The file plays just perfectly for me, both with madVR or EVR-CP.

Original comment by h.lepp...@gmail.com on 5 Dec 2011 at 7:34

GoogleCodeExporter commented 8 years ago
Oh well, here is a screenshot as a proof that i'm not just trolling: 
http://imageshack.us/f/51/lavfiltersgreenbar.png/

Any additional info i can provide? ffprobe output for example? (it helped last 
time i reported issue, dunno if it can help now)

Original comment by porsche9...@gmail.com on 5 Dec 2011 at 9:29

GoogleCodeExporter commented 8 years ago
I've tried the linked sample, and it I get corruption too, depending on 
selected output format.

Using:
Windows 7 64bit
Nvidia Geforce 9600GT with drivers v285.62 (WHQL)
LAV Video Decoder 0.42
LAV Splitter 0.42
MPC-HC (32bit) 1.5.3.3884

It plays fine on EVR/VMR, with MadVR it depends on output format from LAV Video:
- AYUV gets green bar on like 1/3 of the image from bottom
- RGB32 gets black bar on like 1/3 of the image from bottom
- RGB24 gets perfect playback

Hope this helps to debug.

Original comment by michk...@gmail.com on 5 Dec 2011 at 9:34

GoogleCodeExporter commented 8 years ago
This is not a decoder problem (as you can see from EVR working). I discussed 
this with madshi quite a while ago, and we concluded that the most likely case 
is a driver problem with some cards.

Sadly neither him nor me can reproduce it, making fixing impossible.
As a work around, just disable AYUV and RGB32 output.

Original comment by h.lepp...@gmail.com on 5 Dec 2011 at 10:07