![]() If for this special MBAFF file YADIF is truely active, it will flicker, because YADIF is not frame adaptive. It's always greyed, and seems to work only for "(CUVID/QS only)".Ģ. I cannot use HW/GPU deinterlacing whatever is selected in HW acceleration. If I select "no software deinterlacing", there is a strong comb effect, but still no flicker at all on the chinese sponsor (camera does not move). I use software YADIF deinterlacement of LAV decoder. I normaly do not use hardware acceleration in my process. In the "video tab" of Options in MPC-BE, Output Range is greyed using madVR (only available for VMR-9 and EVR-CP). If I switch madVR from 0-255 to 16-235 (Devices/Properties), then it does what is supposed to happen : Blacks are lifted, and whites dimmed. My HTPC is connected to Denon AVR-X4300 then to Epson EH-LS10500.ġ/ My video stream is in RGB 4:4:4 10bit 0-255. If a Radeon VII user is reading this, please test this also for me and let me know the below the answer of my contact who has a Vega64 Since you know someone who has a Vega64, would you mind to ask him/her to test this with the Vega64, too. If you use LAV Filters use DXVA2 copyback, but not D3D11 for deinterlaing test.ĭisable Software deinterlacing in LAV Filters, if it is enabled. Play it and check the charakters above "for flickering: Does this setting make a difference if you choose 0-255 and then 16-235?įor the deinterlacer test you need to download: ![]() In MPC-BE, probably also in MPC-HC there is an option in "Video" Tab in options which lets you override the output range. Are the blacks elevated or black as it should be. Make sure you have a TV in pc mode which wants 0-255 and play a video in MPC-BE or also MPC-HC and check the black levels. I am really at the end of investigation to understand/identify the in my thread :)Ĭan you test something for me? I am interested in hardware capabilities of Vega64 and RX6800XT. One is in 32 bits configuration, the other is full 64 bits (same result) The PCHCs use standard software such as Lav filters 0.76, MPC-BE, MadVR 0.92.17 with and without the beta 157. GPU Benchmark test are OK (no problem highlighted) - scan with GPU-Z are correct. (some settings inside the driver configuration ?)įor information, i have provided some specific settings.bin of madvr and video to test and compare the rendering time and we confirm the problem. So, i post to ask if there is a known tip about that to fix this problem before to send back the GPU. Normally, rendering time should be highly below the previous boards and we cannot find a solution so far to explain the issue and i suppose that most of users have no issue. ![]() One has previoulsly a Vega64 and the other had a GTX1080. On my side, already 2 people using this GPU have seen their rendering time increased a lot compared to their previous GPU.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |