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. |
25th November 2015, 12:23 | #34381 | Link | ||||
Registered User
Join Date: Dec 2014
Posts: 34
|
As for fullscreen exclusive mode, I have it disabled because the screenshot issue.
My gpu is an integrated in an old laptop! Quote:
Quote:
Quote:
Quote:
Many thanks! |
||||
25th November 2015, 12:37 | #34382 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
In that case when watching 1920x1080 only doubling runs but when watching 1916x1076 both doubling and quadrupling run. Doubling 3832x2152 to 7664x4304 and then downscaling to 3840x2160 takes a lot of performance and is pointless. Set quadrupling to only run with 1.5 or 2x scaling, in fact I would recommend setting doubling and quadrupling to 1.5x scaling, maybe 1.2x if you really like doubling, but always does more harm than good in my opinion. Doubling or Quadrupling do not run unless the image is upscaled, no matter what you set in "image doubling" quadrupling will never run for 1920x1080 video on a 4K display.
__________________
madVR options explained Last edited by Asmodian; 25th November 2015 at 12:40. |
|
25th November 2015, 13:07 | #34383 | Link |
Registered User
Join Date: Oct 2012
Posts: 99
|
If you send 1920x1080 TV 1280x720 signal, then yes, it should fill the screen. I don't know why you would want to do this instead of using lighter players though. I'm guessing whatever good madvr is achieving is lost during TV's processing.
|
25th November 2015, 13:58 | #34384 | Link |
Registered User
Join Date: Nov 2012
Posts: 99
|
I found a strange behavior/bug by using the new Radeon Crimson driver. I updated recently the rest of the video software (madVR, LAV filters, MPC HC nightly) so the driver is not certainly the culprit.
GPU: Radeon R7 250 Driver: Radeon Crimson affected rendering modes: fullscreen modes (both windowed and exlusive), no problem while NOT rendering fullscreen behavior: all 4 queues + rendering and presenting times jumping wildly, queues partially running empty so dropped frames, decoder queue showing 20-25/24 "remedy": deactivating smoothmotion and/or checking "use 10bit image buffer instead of 16bit" in trade quality for performance section -> normal behavior Edit: Reverted now back to Catalyst 15.7.1. Everything ok now. In my case Radeon Crimson seems to be not ok for my system. Furthermore I found out that most of video related settings are completely removed from Control Center. I stay with 15.7.1 meanwhile, was a mistake to install new AMD crap. Edit2 (10.12.15): New test with Crimson: new "real" remedy: reducing rendering queues to maximum 21 (was 24 in my case). Last edited by hannes69; 10th December 2015 at 15:51. |
25th November 2015, 16:05 | #34385 | Link | |
Registered User
Join Date: Mar 2002
Posts: 2,323
|
Quote:
Was FSE Old path faster for you? Unistall them first, move them, them install them again.
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config |
|
26th November 2015, 00:56 | #34386 | Link | |
Registered User
Join Date: Jan 2014
Posts: 63
|
Quote:
The new driver is 3-5% faster so it's worth trying it out. |
|
26th November 2015, 05:11 | #34387 | Link | |
QB the Slayer
Join Date: Feb 2011
Location: Toronto
Posts: 697
|
Quote:
As for the new AMD drivers... I think they are pretty good, still in need of some work (some settings are in the old CCC interface and others in the new interface)... But one thing that is fantastic, the new Custom Resolutions. No need for a separate app like CRU anymore QB
__________________
|
|
26th November 2015, 10:44 | #34389 | Link |
Registered User
Join Date: Oct 2013
Location: France - Paris
Posts: 21
|
Madvr 3dlut gamma editor
Hello Madshi
I have one demand/question: Many of us are experiencing the same problem: i1d3 (or low end colorimeters) measure our display with a perfect black (accuracy problem) and the result is always a linear gamma from 0 to 100%. The reason is simple: perfect black = infinite contrast ratio but we don't have an oled tv! As a consequence the blacks are crushed between 0 to approximately 2.5%. The 17-18 blanking bars are always invisibles after 3dlut creation. I tried to decrease the gamma @1.25% with videoequalizer v2.06. It works very good (17-18 became visibles again) but it's not compatible with a 3dlut and I can't use this solution. Do you think it could be possible to create a tool in madvr to modify the gamma curve in realtime after the 3dlut? The goal is not to make a new gamma curve but only to correct the grayscale with our eyes at very low ire because the i1d3 can't. A 100 points gamma editor would be really amazing for us. Something like videoequalizer but in madvr, after the 3dlut... The idea is just to lower the gamma between 0 to 5%. It would be so cool... I'm not sure if it's clear or if it's the good way to ask but... Thanks Madshi
__________________
HC:Arcam AV888 + BSS-BLU 100-120 + 3x LabGruppen C series + 3x JBL 3678 + 4x Klipsch THX5000 (surrounds) + DIY subwoofer DISPLAY:JVC RS3100 + Screenline 150" HTPC: Bi Xeon + RTX3700 + LAV + Madvr |
26th November 2015, 16:02 | #34390 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
Quote:
and yeah don't forget disco madVR before the PC crashed. and AMD calls that "stable"... |
|
26th November 2015, 16:19 | #34391 | Link | |
Registered User
Join Date: Jan 2013
Posts: 41
|
Quote:
Hi Warner306, Thanks for the cookbook in your signature. I tried to follow it with my 960GTX. Display: 3840 x 2160p Medium profiles With 720p video, got lot of dropped frames with deinterlacing in auto mode. I have to deactivate it in order to get things ok. How comes ? regards. |
|
26th November 2015, 19:17 | #34392 | Link | |
Registered User
Join Date: Jan 2008
Posts: 589
|
Quote:
|
|
26th November 2015, 19:41 | #34393 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
__________________
madVR options explained |
|
26th November 2015, 22:21 | #34394 | Link | |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Quote:
You can create separate profiles for deinterlaced content (srcInterlaced) using madVR profile rules, which what I would recommend. Then, you could turn down your settings when deinterlacing is encountered, and turn them back up when it is not. Also, I realize you are likely using image quadrupling at 720p -> 2160p. You could simplify things by disabling image quadrupling and using image doubling + image upscaling instead. I think I would still go with the separate profile for deinterlaced content, but that would probably provide immediate relief to your graphics card. The moral of the story is your settings are likely too aggressive for your card.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players Last edited by Warner306; 26th November 2015 at 22:27. |
|
26th November 2015, 23:02 | #34395 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
deinteralcing is taken the source framerate and is doubling it.
so madVR has to scale 50-60 frames a sec this is way and without it is 25-30 frames per sec. so double the power is needed to scale the deinterlaced stream. deinterlacing it self is nearly free. Last edited by huhn; 26th November 2015 at 23:05. |
26th November 2015, 23:21 | #34396 | Link | |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Quote:
So to the previous poster...You might have to completely abandon image doubling for these sources and use lesser settings. I thought a tweak here or there would bring the rendering queue down. Also, you could use (deintFps > X) to create separate profile rules as opposed to (srcInterlaced), because huhn says it is the deinterlaced frame rate that is the problem once interlacing is complete, not the deinterlacing itself. The source frame rate and amount of scaling are two most important factors in determining the load placed on madVR. As a starting point, these are my rules for a 1080p display: if (deintFps <= 24) and (srcWidth > 1280) "1080p24" else if (deintFps > 24) and (srcWidth > 1280) "1080p60" else if (deintFps <= 24) and ((srcWidth > 960) and (srcWidth <= 1280)) "720p24" else if (deintFps > 24) and ((srcWidth > 960) and (srcWidth <= 1280)) "720p60" else if (srcWidth <= 960) "SD" Or, using height: if (deintFps <= 24) and (srcHeight > 720) "1080p24" else if (deintFps > 24) and (srcHeight > 720) "1080p60" else if (deintFps <= 24) and ((srcHeight > 540) and (srcHeight <= 720)) "720p24" else if (deintFps > 24) and ((srcHeight > 540) and (srcHeight <= 720)) "720p60" else if (srcWidth <= 960) or (srcHeight <= 540) "SD"
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players Last edited by Warner306; 27th November 2015 at 00:05. |
|
27th November 2015, 00:19 | #34397 | Link | |
Registered User
Join Date: May 2010
Posts: 27
|
Quote:
With your explanation, I finally understand how to set image doubling. It all makes sense now! And the OSD will show what is happening, as others have pointed out. Thanks for everyone's assistance. |
|
27th November 2015, 00:32 | #34398 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Can someone with better profile knowledge tell me how to write a profile where, if the width component is failed, madVR will check the source height before proceeding to the next profile?
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players Last edited by Warner306; 27th November 2015 at 07:15. |
27th November 2015, 00:39 | #34399 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
if (srcWidth > number) "profile/action"
else if (srcHeight > number) "profile/action" i don't use profiles but i can write code (or at least i was able to do that 10 years ago...) so not 100 % sure if the syntax is correct for the profile |
27th November 2015, 02:25 | #34400 | Link | |
Registered User
Join Date: Aug 2011
Posts: 51
|
Quote:
Code:
if (deintFps <= 24) and ((srcWidth > 1280) or (srcHeight > 720)) "1080p24" else if (deintFps > 24) and ((srcWidth > 1280) or (srcHeight > 720)) "1080p60" I think you should check with 30 fps instead of 24. And you can use more generic profile names like sd (480p), hd (720p), fhd (1080p) and uhd (>1080p). So something like these: uhd, uhd_hifps, fhd, fhd_hifps, hd, hd_hifps, sd, sd_hifps. You can remove the underscore to suit madshi's naming preferences. hifps = High FPS Last edited by lanzorg; 27th November 2015 at 03:43. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|