Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
3rd December 2015, 17:34 | #34461 | Link | ||
Registered User
Join Date: Jan 2013
Posts: 41
|
Quote:
Two possibilities: Let my TV doing the deinterlacing stuff Let MadVr doing it If MadVr , how to modify your rules ? Quote:
If TV 10 bits compliant, dithering must be set to 8 bits or 10 bits and more during the |
||
3rd December 2015, 17:35 | #34462 | Link | ||
Registered User
Join Date: Jan 2013
Posts: 41
|
Quote:
Two possibilities: Let my TV doing the deinterlacing stuff Let MadVr doing it If MadVr , how to modify your rules ? Quote:
If TV 10 bits compliant, dithering must be set to 8 bits or 10 bits and more during the calibration processus ? regards. |
||
3rd December 2015, 18:02 | #34463 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
you can't scale an interlaced picture vertikal and than deintelrace it. it's not possible just the chroma scaling to 4:4:4 is already destroying the chroma.
so madVR should handle the deinterlacing. local dimming results in incorrect results. the colors are different depending on the zone brightness. for most accurate results it should be left disable completely. if you want to use it. i would first try to calibrated with an disabled local dimming and than activated it. |
3rd December 2015, 21:44 | #34464 | Link | |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Quote:
So, you have to find what frame rates are possible with specific madVR settings. If you can play 25 fps (progressive) content with one profile, that could be a starting point. Everything at this framerate and below should stay under the rendering queue: (deintFPS <= 25) A second profile would cover content higher than 25 fps after deinterlacing: (deintFPS > 25) Below is an example of integrating the deinterlaced fps and the source resolution: if (deintFps <= 25) and ((srcWidth > 1280) and (srcWidth <= 1920)) "1080p25" else if (deintFps <= 25) and ((srcWidth <= 1280) and (srcHeight > 720) and (srcHeight <= 1080)) "1080p25" if (deintFps > 25) and ((srcWidth > 1280) and (srcWidth <= 1920)) "1080p60" else if (deintFps > 25) and ((srcWidth <= 1280) and (srcHeight > 720) and (srcHeight <= 1080)) "1080p60" Essentially, you are ignoring the deinterlacing process and focusing instead on the frame rate after deinterlacing. The frame rate after deinterlacing will determine the load placed on madVR. Double the frame rate, for example, and double the load is placed on madVR.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players Last edited by Warner306; 3rd December 2015 at 21:55. |
|
4th December 2015, 07:36 | #34467 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
My issue with the November Windows 10 update was fixed with a driver update.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
4th December 2015, 16:58 | #34468 | Link |
Registered User
Join Date: Apr 2006
Posts: 299
|
I thought upgrading from a 1600x1200 to 1920x1200 monitor alone was causing dropped frames but I guess it's the new AMD driver too. For now I'm enabling 'use 10 bit buffer instead of 16bit' under 'trade quality for performance'. This allows me to use super-xbr75 image doubling and SuperRes x3 for 720p on HD7700.
|
4th December 2015, 18:58 | #34469 | Link | |
Registered User
Join Date: May 2010
Posts: 236
|
Quote:
Madshi, I uploaded log, bug report and DxDiag information in one archive: https://yadi.sk/d/8Y5cl6AAkyp5t |
|
4th December 2015, 23:31 | #34470 | Link | |
Registered User
Join Date: Oct 2015
Posts: 99
|
Quote:
1) Choosing deint=Film, deint=Off or frameRate=25 all look identical to me. But if I use deint=Film, I get several ms worth of performance hit and the OSD says "IVTC", even though, as far as I know, only the repeat flags of the DVD are being ignored. For example in Handbrake, it's "safe" to simply leave deinterlacing off and set fps to 25 when ripping progressive material DVDs. So I'm just struggling to grasp the real world difference between the tags I mentioned 2) In the case of progressive segmented frame material, two consecutive fields should be merged/weaved (whatever the correct term is) into a progressive frame. Again, when using "deint=Film", the OSD reads "IVTC" and 2:2 cadence - does that mean madVR is properly merging the fields? I would have thought the term "IVTC" isn't applicable in this case. At a quick glance at least, the playback appears identical whether I use deint=Film or frameRate=25 (the content within the container is progressive 25 fps). 3) Anyone know which tag to use to get proper PAL speed down? I have some natively progressive 25 fps content, so unfortunately I can't use the global Reclock PAL speed down setting. However, when setting the speed variation in Reclock to 5% and using the tag "frameRate=24p", I also get the pitch tuned down, so I assume I'm doing it right? Last edited by Uoppi; 4th December 2015 at 23:37. |
|
5th December 2015, 15:09 | #34472 | Link | |
Registered User
Join Date: Oct 2015
Posts: 99
|
Quote:
The only thing I can think of is that in this case madVR's IVTC is just detecting cadence and nothing more (?). If that really is the case, I'd much rather use deint=Off because: a) deint=Film screws up native progressive 30 fps content by displaying it at 24 fps. b) deint=Film results in ~5 ms of apparently unnecessary performance hit on my already overtaxed Pentium CPU So, unless I've got the above wrong, there is no pressing need to use deint=Film except with (some) NTSC material for detecting pulldown and cadence? Last edited by Uoppi; 5th December 2015 at 15:14. |
|
5th December 2015, 16:35 | #34473 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
not all pal source have matching fields and. and even for your pentium it is nothing. just ignore the number. if it is lower than the refresh interval than every is totally fine.
this algorithm is kind of totally free. why should you add deint=film on progressive content? |
5th December 2015, 21:47 | #34474 | Link |
Registered User
Join Date: Oct 2015
Posts: 99
|
Mainly because:
- Using madVR's auto detection on any of its settings, progressive segmented frame videos (from a Canon camcorder) are detected as interlaced and are deinterlaced instead of merging the consecutive fields into progressive frames - Content I've verified as progressive (going frame by frame) sometimes still gets deinterlaced with madVR's auto detection, regardless of the detection setting I prefer to tag folders/files manually instead of relying on automatic detection (which I've sometimes found to be unreliable). That's why I'm trying to get my head around the difference between some of the tags. Like why deint=Off looks exactly the same to me as deint=Film, even when one of them involves "IVTC" according to the OSD and the other one does not (talking only of PAL - with something like 3:2 pulldown they would obviously look different). I'm paranoid/OCD about getting the picture right (aren't we all here ), so I'd just like to be sure what I'm seeing is actually true. Up until now I thought deint=Off was OK to use because it at least resulted in the correct framerate and looked alright to me. But now I'm as confused as ever. Last edited by Uoppi; 5th December 2015 at 21:58. |
5th December 2015, 23:34 | #34475 | Link | |
Registered User
Join Date: Mar 2007
Posts: 934
|
Quote:
__________________
TV Setup: LG OLED55B7V; Onkyo TX-NR515; ODroid N2+; CoreElec 9.2.7 |
|
5th December 2015, 23:39 | #34476 | Link |
Visual Novel Dev.
Join Date: Nov 2015
Location: Bucharest
Posts: 200
|
Hello!
I managed to get a crash report from a crash mpc-hc+madvr that has happened. I thank in advance if someone could explain to me what is the problem. I uploaded the .txt file to my dropbox account. https://www.dropbox.com/s/0fxakdk93w...eport.txt?dl=0 Another thing, I always send my crash reports to mpc-hc automatically, but the crashes only happen when using mpc-hc with madvr, so I really hope that someone can offer me a helping hand. Thanks! |
6th December 2015, 00:18 | #34477 | Link | |
Registered User
Join Date: Oct 2015
Posts: 99
|
Quote:
I've developed a semi-neurotic habit of checking the madVR OSD on every playback start to see what's happening (or not), to ensure all is well. Tags I can at least always rely upon, although it does require some double-checking too to verify the tag is correct for the material. No escape from tweaking, I guess! |
|
6th December 2015, 11:17 | #34478 | Link | |
Registered User
Join Date: Mar 2007
Posts: 934
|
Quote:
__________________
TV Setup: LG OLED55B7V; Onkyo TX-NR515; ODroid N2+; CoreElec 9.2.7 |
|
6th December 2015, 13:49 | #34479 | Link |
Registered User
Join Date: Oct 2015
Posts: 99
|
OK. So if the GPU is detecting everything properly, progressive 25 fps PAL should never be displayed at a 50 Hz refresh rate? Just asking because 50 Hz is what I'm always getting with progressive segmented frames using madVR's automatic interlace detection. The only way to get proper playback at 25 Hz is using tags.
So, summa summarum, from what I've gathered here, it doesn't hurt anything to always use deint=Film for all progressive PAL content stored in an interlaced-flagged container. I'll be using that then instead of deint=Off. |
6th December 2015, 14:14 | #34480 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Quote:
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|