2FFmpeg LogoFFDShow DXVA H.264 corruption resolved

I have recently been suffering corruption playing back some H.264 files with FFDShow tryouts.  After a bit of experimenting I’ve found that the last build without this issue is build 3949 from 24th-July.  I previously had issues with earlier releases of FFDShow that didn\’t work with DXVA at all – fortunately build 3949 doesn’t suffer this issue.  I also previously had a problem where some builds of FFDShow were less efficient on my HTPC and were unable to smoothly decode some high bitrate movies, e.g. a rip of the Inglorious Basterds Blu-Ray, which has forced me to continue to use an old build from mid-2010 until now.  Build 3949 doesn’t suffer from these issues either – so in terms of the 3 problems I’ve had over the years with ffdshow, build 3949 doesn’t suffer from any of them, making it my build of choice for the foreseeable future.

Please send us your thoughts by commenting below! If you would like to subscribe please use the subscribe link on the menu at the top right. You can also share this with your friends by using the social links below. Cheers.

Leave a Reply

2 Comments

gravatarzd

Sorry for the question, but did you know FFDShow has a GUI with a lot of settings? F.ex. you can switch on or off DXVA support, in case some files are not compatible with it. Also, you can set it up to try to do it automatically.

Reply
gravatarJon Scaife

Thanks you, yes I did. I’ve used them extensively to tweak the subtitle settings. I require DXVA as the E350 CPU in my HTPC is too under-powered to decode full 1080p BluRay’s on the CPU. I use ffdshow specifically because it supports DXVA and subtitles which is something I can’t do with other decoders.
In my experience with ffdshow tryouts files aren’t incompatible with it, so much as certain revisions of it are incompatible with some files. This isn’t all that surprising given that it is in alpha or beta stage constantly.
Anyway, for now my recommendation for build 3949 stands – it works well with all the files I’ve tried it with – and it does so with lower CPU usage than any other build I’ve tried – which is most of them.

Reply