eLove
榮譽會員
- 已加入
- 4/5/08
- 訊息
- 1,394
- 互動分數
- 8
- 點數
- 38
有需要硬體去交錯的，可以試試看
目前測試 MPEG2 編碼畫面會有閃爍、H.264 編碼畫面穩定
硬體去交錯的效果感覺上跟 ffdshow 開啟 yadif+double framerate 效果一樣
補上作者的說明：
added DXVA2 Deinterlacing
no support for DXVA2 Decoding, just to avoid any misunderstandings
Some things to note:
(1) Deinterlacing requires DXVA2 to be present. On XP you probably need to install .NET 3.0 (or higher) to get DXVA2.
(2) Using DXVA2 deinterlacing means that potentially all the nasty GPU algorithms like noise reduction and edge enhancement are introduced to madVR. So make sure you have all this stuff turned off in your GPU driver's control panel. Of course madVR only uses DXVA2 if deinterlacing is needed. So for progressive stuff (or if you deinterlace externally) nothing changes compared to older madVR versions.
(3) At this point in time madVR mostly does the same that VMR and EVR do. Which is not ideal in some cases. E.g. MPEG2 flags are trusted, so movie deinterlacing might not always be correct, especially with MPEG2 DVDs and broadcasts. I might improve that in a future version.
(4) madVR is less picky than other renderers about which color spaces you can send. madVR will happily deinterlace all 8bit YCbCr formats. Even 4:2:2 and 4:4:4, which madVR then converts down to 4:2:0 for DXVA2 deinterlacing.
(5) ATI users please activate the switch "Advanced Color -> Dynamic Range" and set it to "Limited (16 - 235)". This will make sure that BTB and WTW are not cut off by DXVA2 deinterlacing.
(6) I've removed the Intel software decoder DLL from the madVR zip in order to cut down the zip file size, and because most people probably use the libav decoders, anyway. If you want to use the Intel decoders, you can download the dll separately here. Just copy it to the madVR folder and the Intel decoders should start working again.
(7) This is a first experimental version, bugs are to be expected.
FEEDBACK:
I need to know...
(a) ... how deinterlacing quality and performance compares to LAV CUVID, could you please check that? If LAV CUVID looks or performs better, maybe there's room for me to improve, too.
(b) ... whether the option "perform deinterlacing in separate thread" makes things better or worse for you. Ideally I hope it will be better or worse for everybody so that I can then hard code the "right" setting and remove the option. On my PC it seems that having this option off works better for windowed mode, but having it on works better for exclusive mode.
