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. |
14th October 2017, 03:14 | #46521 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Don’t use D3D11 native for better results....
__________________
madVR options explained |
14th October 2017, 12:47 | #46523 | Link |
Registered User
Join Date: Apr 2016
Posts: 25
|
Is there any step-by-step explanation how to provide a 23.976 for Nvidia?
My TV (Panny 65VT60) already has a native "1920x1080@23" mode in Nvidia Control Panel. According to madVR stats, this mode is actually 23.972. I read a manual (http://madvr.com/crt/CustomResTutorial.html) but it gives a very poor explanation for my case. |
14th October 2017, 13:48 | #46524 | Link | |
Registered User
Join Date: Jun 2007
Posts: 656
|
Quote:
I followed the instructions but could not see results. And I completely understand the underlying logic. It's just that I do not see the things that should be happening... well, happen. |
|
14th October 2017, 15:36 | #46526 | Link | |
Registered User
Join Date: May 2007
Posts: 454
|
Quote:
1) Make sure the monitor to receive the new refresh rate is not at the refresh rate you want to alter (so not at 23Hz in the nvidia control panel). 2) In the madVR custom resolution options, select the predefined 23Hz refresh rate in the list and click edit (that is your case). 3) Click 'test mode'. 4) The monitor will set the new resolution, confirm that you see it. If its fine click save. 5) Reboot PC When you now play a video it should now be closer to 23.976. Once MadVR has played a video in the new resolution for 30 minutes or so you will be able to go back into the custom resolution and use the optimise option. In my case that was not needed as it was already bang on 23.976 with no need to optimise (1 dropped frame every 12 1/2 hours is good enough for me).. Last edited by Razoola; 14th October 2017 at 15:42. |
|
14th October 2017, 15:36 | #46527 | Link | |
Registered User
Join Date: Jun 2007
Posts: 656
|
Quote:
Even though I've activated the "D3D hack to use 24Hz and 60Hz", I'm getting the "The GPU rejected this mode, for unknown reasons." error when trying to input original EDID's values for timings (pressing Edit the first time). And I do that while using a different refresh rate. Last edited by ashlar42; 14th October 2017 at 15:45. |
|
14th October 2017, 15:39 | #46528 | Link | |||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
As always, we need a good compromise between easy intuitive GUI, without taking too many useful options away. I'm not sure right now what I'll do... Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Anyway willing to do the leg work? Which means create an exact "formula" which outputs a quality level, based on: - codec - resolution - frame rate - chroma subsampling - bitrate Quote:
I may add more RCA quality steps in between, but it's not as easy it might seem, so before I do that, I'll need more feedback first about all these new changes. Quote:
HDMI 2.0 can't do 4Kp60 RGB with more than 8bit. So even if you tell the GPU *and* madVR to output 10bit RGB at 4Kp60, it won't happen. Someone somewhere will have to drop it down to 8bit. Probably it will be the GPU driver, and I'm not sure they'll apply proper dithering. So it's better if you take care of this yourself, e.g. by using profiles. My recommendation is to always output RGB. 10bit is nice if your TV fully supports it (and benefits from it), otherwise 8bit is just fine, too, even for HDR content, thanks to madVR's high quality dither. Quote:
So does the tweaked madHcCtrl.exe which I made available a couple posts ago fix the probem? Quote:
There's one key difference, though: If you choose option 2, you can select a number of options for how madVR should do the HDR -> SDR conversion. If you choose option 1, you don't have these options, so madVR chooses itself. You're saying you have darker colors when using option 1. That means you probably have a lower "display peak nits" number selected than madVR chooses for option 1. If you increase the "display peak nits" number, you'll probably get the same image as when using option 1. Quote:
Quote:
New build out maybe later today (6-7 hours from now), or maybe tomorrow. Quote:
Quote:
https://www.videohelp.com/software/m...sions#download Furthermore: Does this problem only occur when using the new "D3D11" decoder in LAV? Or does it also occur when e.g. using software decoding? Quote:
Quote:
|
|||||||||||||||||||
14th October 2017, 15:50 | #46529 | Link | |
Registered User
Join Date: Jun 2007
Posts: 656
|
Quote:
See the other problem I described for 24Hz and 60Hz. I was writing at the same time as you |
|
14th October 2017, 16:18 | #46531 | Link |
Registered User
Join Date: May 2007
Posts: 454
|
@madshi,
I know this was brought up years ago (I think it was leeperry who did) but have you any plans to add customisable enhancements to madVR in relation to 'near black' processing? I'm thinking something on the lines of being able for example to boost or manipulate brightness in the 0%-5% range. This would be for those with panels what no matter how well they can be calibrated, due to ABL or whatever else, shadow details are sometimes lost. |
14th October 2017, 16:39 | #46533 | Link | |
Registered User
Join Date: Oct 2009
Posts: 930
|
Quote:
But I've been getting hang with madVR for ages and complained a few times here. Also did to the PP dev and the progDVB dev. It's just that it's far more common of an occurrence with newer versions of PP, where I can reproduce a hang in seconds by quickly opening files after each other for playback. Now if I get a different issue with older PP and new madVR I'm pretty screwed. |
|
14th October 2017, 16:42 | #46534 | Link |
Registered User
Join Date: Jan 2017
Posts: 2
|
What is a good madvr setting for 4k display?
Hi this is my 1st post here. There are several articles related to madvr settings but i was wondering what is the optimal setting for my configuration.
Specs: i7 4770k @4.2Ghz Zotac GTX 1070 amp extreme SLI 16gb ram I am using potplayer with lav filters. I specifically want to know about how much important the artifact removal, image enhancements settings are and when i should use them? |
14th October 2017, 16:49 | #46535 | Link | |
Registered User
Join Date: Jan 2017
Posts: 2
|
Quote:
If i disable the d3d11 for rpesentation everything starts to work fine again. Right now i dont have the problem anymore and the only thing that changed for the is i updated msi afterburner and rivatuner with latest version. Using win 10 rs3. Nvidia driver 387.92 |
|
14th October 2017, 16:49 | #46536 | Link | |
Registered User
Join Date: Mar 2016
Location: Switzerland
Posts: 140
|
Quote:
I will try to find more. |
|
14th October 2017, 17:11 | #46537 | Link | |
Registered User
Join Date: May 2007
Posts: 454
|
Quote:
1) Automatically first change the current refresh rate to something other than the refresh rate setting to be tested. 2) Tell the user that madVR first needs to change the current display refresh rate which then happens after the user presses ok. 3) Stop with an error telling the user to first change the current refresh rate to something else. Last edited by Razoola; 14th October 2017 at 17:21. |
|
14th October 2017, 17:35 | #46538 | Link |
Registered User
Join Date: Oct 2016
Posts: 896
|
Regarding the idea by clsid for a quality variable, in the meantime I've found a workaround where I include the TV channel name in the filename of the recording, and then I've set rules in madVR that match specific channel names to an "awful source" profile
Only thing is this cannot work for live TV, only recordings.
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40 |
14th October 2017, 19:26 | #46539 | Link |
Registered User
Join Date: Nov 2016
Posts: 10
|
@madshi
I did some testing, all madvr settings to default but D3D11 fullscreen windowed on a second monitor. I deleted the settings.bin and reset the settings every time just in case. v0.92.02 DXVA2(Copy-Back) No issues. D3D11 Automatic (Native) sometimes freezes for 2 or 3 seconds but no actual crashes and playback resumes like usual. D3D11 cb direct(Hardware Device selected) No issues. v0.92.03 DXVA2(Copy-Back) No issues. D3D11 Automatic (Native) Crashes, no error messages, MPC-HC freezes and CPU usage goes crazy. D3D11 cb direct(Hardware Device selected) No issues. v0.92.04 DXVA2(Copy-Back) No issues. D3D11 Automatic (Native) Crashes, no error messages, MPC-HC freezes and CPU usage goes crazy. D3D11 cb direct(Hardware Device selected) No issues. v0.92.05 DXVA2(Copy-Back) Crashes with "MPC-HC has stopped working" window. D3D11 Automatic (Native) Crashes with "MPC-HC has stopped working" window. D3D11 cb direct(Hardware Device selected) Crashes with "MPC-HC has stopped working" window. All three happen just from going from in-game fullscreen to windowed mode, definitely a lot more sensitive that the previous releases. Actually got a madvr crash error window with this version but got not log file(I assume it goes to the desktop, right?) v0.92.06 DXVA2(Copy-Back) No issues. D3D11 Automatic (Native) Crashes, no error messages, MPC-HC freezes and CPU usage goes crazy, sometimes behaves similar to v0.92.02 with 2-3 second freezes and playback continues. D3D11 cb direct(Hardware Device selected) No issues. All of the above happens when launching a game or when closing the game or going from in-game fullscreen to windowed and vise versa, if you manage to get in-game without MPC-HC crashing then you're not very likely to encounter issues unless you do try to go into windowed mode or encounter a loading screen. Some files seem to be more susceptible to crashing but it's not an issue of only happening with "x" specific file or "x" specific game. GPU is Nvidia GTX 970, driver 385.69. Game was Battlefield 4 Fullscreen exclusive(it happens in other games too). Last edited by valdeski; 14th October 2017 at 21:20. Reason: Fomating |
14th October 2017, 20:27 | #46540 | Link |
Registered User
Join Date: Oct 2003
Posts: 273
|
@madshi
I'm not whether or not this has been previously reported or nobody noticed, but I see 2 very annoying issue with the "move subtitles to the bottom of the screen" feature (which as you know is extremely useful for 2.35:1 movies). (I can't comment on whether it was okay in previous versions as I only now started using madVR with XYsubfilter). Issue 1 - It seems that every subtitle is displayed in a slightly different horizontal position (more than a few pixels up or down). Issue 2 - Unrelated to issue 1, which happens regardless, I think you're treating the subtitle as an image and just move it down not accounting for actual text or characters. A little complicated to explain, but I'll try - Consider the following different subpictures: SUB 1 - aaaaaaaaaaaaaaaaa SUB 2 - aaaaaaaaaaapaaaaaaaaaaq Because the lowest pixel in SUB1 is at the bottom part of the 'a' character, it will align the entire text in a certain horizontal position. On SUB2, the lowest point is at the bottom of the 'q' and 'p' characters, and it will align the entire text based on that, so that the rest of the characters ('a' characters) are in a different position on SUB2 than they were in SUB1. I know this example makes it seem as if it's a rare case, but in some languages, and even in English - this is EXTREMELY noticeable and as subtitles changing fast it make it seem that the entire sub picture stream is just moving up and down between subs. Issue 3 - Some sub pictures are 1 line while others are 2 lines. When rendering subtitles, there's a fixed virtual position for each line (row 1 and row 2), so if you have just 1 line it's displayed on row 2 (the lower row) and if you have 2 of them they're displayed on both rows. What I'm seeing is that if there's a single line, it's actually displayed in a third location seemingly in between row 1 and row 2. I couldn't find a better way to describe this, so let me know if you want me to include some screenshots to clarify. What I can tell you is that if you turn off the 'move subtitles to bottom' feature in madVR, while the subtitles are then rendered on the video itself instead of the black bars area, the positioning is perfect and you don't have any of the above issues, thus eliminating xysubfilter as the cause for this. Thanks for all your hard work, much appreciated! |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|