|
|
How can I download that file? I don't see a download link. Is this a file where LAV Filters activates deinterlacing properly, and madVR does not - even if "if in doubt activate deinterlacing" is activated? |
|
|
http://rusfolder.com/40527629 Yes, this is the one. But I could reproduce the issue with "if in doubt activate deinterlacing" only before, after a couple of enabling and disabling "force video mode" / "force film mode" (enabling seemed to help forcing deinterlacing) and switching between "activate if in doubt" and "deactivate if in doubt". |
|
|
Downloading now. I don't understand your description of enabling and disabling various settings. Can you give me a step-by-step guide with which I can reproduce the problem, please? Thanks. |
|
|
Deinterlacing for the problematic video isn't enabled automatically: 1) with "if in doubt deactivate deinterlacing" 2) with "if in doubt activate deinterlacing" and "force film mode". |
|
|
With LAV Video Decoder set to "Deinterlacing Mode: Auto" which is the default setting, both 1) and 2) work here. Have you modified the LAV settings? |
|
|
lav.png (16,613 bytes) |
|
|
Yes I did or else madVR would have nothing to deinterlace. See attach for my LAV Video settings. |
|
|
I'm not talking about "Enable Adaptive HW Deinterlacing", I'm talking about the "Deinterlacing Mode", which still seems to be set to "Auto" in your screenshot, which is the same setting it has on my PC. Can you please redo your tests with software decoding? It's possible that the NVidia CUVID decoder doesn't properly forward the interlacing flags to madVR. Does the same problem occur with software decoding? It works fine on my PC with software decoding. |
|
|
I set "Hardware Decoder to use" to "None" - nothing has changed. The video is still interlaced in forced film mode. |
|
|
> I'm talking about the "Deinterlacing Mode", which still seems to be set to "Auto" in your screenshot Does it have any effect when deinterlacing (both hardware and software based) is disabled? |
|
|
> I set "Hardware Decoder to use" to "None" - > nothing has changed. The video is still > interlaced in forced film mode. What does the madVR debug OSD (Ctrl+J) say in that situation? Does it report deinterlacing to be on or off? > Does it have any effect when deinterlacing > (both hardware and software based) is disabled? Disabled where? In LAV or madVR? Not sure I understand your question. |
|
|
> What does the madVR debug OSD (Ctrl+J) say in that situation? Does it report deinterlacing to be on or off? deinterlacing on (settings) film mode, unknown cadence cadence breaks 0 decoder queue 16-16 / 16 ivtc queue 15-15 / 16 [Is there a way to write debug info to a file?] > Disabled where? In LAV or madVR? Not sure I understand your question. In LAV. You said I've misunderstood your question about deinterlacing mode - yes I did but I've completely disabled deinterlacing in LAV so I believe deinterlacing mode isn't important. Well nevermind. |
|
|
Originally in the madVR doom9 forum thread you said that you found that LAV sometimes detects interlaced content better than madVR. The purpose of this thread is to get to the bottom of that problem. There are 2 potential reasons for why you got to that conclusion: (1) Either madVR failed to activate deinterlacing at all. The OSD would then show "deinterlacing off". (2) Or madVR tries to deinterlace, but didn't do it correctly. So if you can reproduce a situation where LAV seems to deinterlace better than madVR, the first thing to figure out is whether the problem is (1) or (2). Generally, madVR's deinterlacing should work pretty much the same way as LAV's hardware deinterlacing works - as long as you don't force madVR's film mode on, which is totally different. So if you deactivate forced film mode, you should not be able to see a difference between LAV and madVR doing the deinterlacing. Both should be identical. Performance might be ever so slightly better when letting madVR do it. Could you please retest it with this new background information? If you can't reproduce any problems, anymore, then I'd like to close this bug report. If you can reproduce problems, then let's get to the bottom of it. |
|
|
Closed due to lack of feedback. |
|
|
Let's try again - after a year (sorry for lack of feedback). 1. Reset settings of MPC-HC and madVR to defaults. 2. Open the problematic video, press Pause, go to 00:56. 3. In madVR settings: processing | deinterlacing | [x] disable automatic source type detection, (.) force film mode. You'll see the interlaced picture immediately. |
|
|
can you share a new sample? if i understand you right you force film mode correct? are you even sure the file in question is telecine and not interlaced or hybrid? |
|
|
lav2.png (16,283 bytes) |
|
|
http://www.mediafire.com/watch/02ns1mjbgg4jef2/Breakthru.VOB >are you even sure the file in question is telecine and not interlaced or hybrid? No I'm not. But the same LAV settings (lav2.png) with EVR CP don't cause the similar issue. Besides that I force film mode but not deinterlacing itself - by default it is set to "if in doubt, deactivate deinterlacing", and I didn't change it. |
|
|
forced film mode can't handle interlaced sources is for telecine sources like most movies. use forced video mode or leave everything at default and everything should work as intended. EVR-CP doesn't have a inverse telecine filter and with your screen you feed it progressive frames. edit: you try to feed it deinterlaced frames but CUVID is not working. |
|
|
huhn is right. With forced film mode the Breakthru video at 00:56 shows interlacing because this video is not telecined film content, but it's native video content. Forced film mode only works for telecined film content. To explain the difference: Telecined film content is content which originally was shot in 24fps and then it was artificially split into interlaced fields to create a 60i encoding. In contrast to that native video content consists of 60 different fields, and each field comes from a different point of time. As a result, if you watch a scene with lots of motion (like 00:56), and if you then just copy two fields together, those two fields simply don't fit together, because they're both from different points in time. So you see interlacing/weaving artifacts. Film mode technically cannot handle such videos because film mode simply looks for fields which come from the same original progressive frame and puts them back together. So the solution is to disable forced film mode for videos like Breakthru. Sorry, this is not a bug, but as intended. If you want madVR to behave identical to EVR, simply use the default madVR settings, and don't change the "disable automatic source type detection" and "force film mode" settings. |
|
|
Thanks for the explanation. So the best I can do is to disable deinterlace completely in LAV and to leave default deinterlace settings in madVR? |
|
|
If you want this specific video (and other videos like this) to play correctly then yes. But that also mean that you won't get madVR's film mode, which means that you can't play telecined 60i movie sources smoothly at 24Hz. Unfortunately madVR can currently not automatically figure out which video needs which deinterlacing setting. So to get the best experience for all files, you currently have to manually adjust deinterlacing settings. If you can live without forced film mode, using the madVR and LAV default settings should give you the same experience as with EVR. |
|
|
I mean can I safely turn "Enable Adaptive HW Deinterlacing" off in LAV Video if I use madVR with its defaults? I used to always enable it 'cause I thought that it is the only way to deinterlace with GPU and therefore to reduce the CPU usage. |
|
|
yes you can disable this option it is pretty much "useless". deinterlacing madVR video mode deinterlacing is done using the GPU deinterlacer which is the same as the CUVID deinterlacer. CUVID is kind of totally superseded by DXVA decoding and deinterlacing. DXVA deinterlacing is using the correct 50/60 FPS mode with can be pretty hard on some GPUs. you can go to rendering trade quality for performence "use half frame rate for DXVA deinterlacing" this will result in 25/30 FPS mode. |
|
|
So I guess I can close this bug report now? |
|
|
Yes. Thank guys again for the explanations! |
|
|
I'm sorry to reopen this bug, but I do see the issue with madVR's deinterlacing. Again with Breakthru.vob, I believe it's what I told about in the very beginning. What I do, step by step: 1. Reset MPC-HC and madVR settings to defaults. 2. Open http://www.mediafire.com/watch/02ns1mjbgg4jef2/Breakthru.VOB and go to 00:56. Interlacing can be seen easily. 3. Change LAV Video properties: [x] Enable YADIF Deinterlacing (.) 50p/60p (Video) 4. Restart MPC-HC and open Breakthru.vob. No interlacing at 00:56. WinXP SP3, HD5770, Catalyst 14.4, MPC-HC 1.7.10.40. Another example: 00001.ts. Screenshots are taker under the conditions above. |
|
|
|
|
|
|
|
|
|
|
|
If you enable YADIF deinterlacing then it's LAV's responsibility to deinterlace, not madVR's. So if you get problems this way, it's also LAV's bug, not madVR's. |
|
|
I get problems with YADIF deinterlacing disabled (step 2 and madvr_ss.png). With YADIF deinterlacing enabled, the problem is gone (step 4 and lav_ss.png). Ctrl-J on both files with YADIF deinterlacing disabled shows "deinterlacing on (says upstream)". Interlacing is present. |
- Anonymous
