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, 21:25 | #46541 | Link | |
Registered User
Join Date: Apr 2016
Posts: 25
|
Quote:
1. Open madVR settings, go to "custom modes": 2. This 23Hz mode is displayed as "missing", although some 23Hz mode can be selected in Nvidia Control Panel. 3. If I open this 23Hz mode in this window and then press "Apply" in a corresponding dialog window, messagebox "The GPU rejected this mode, for unknown reasons" is displayed. Tried with and w/o "D3D hack to use 24Hz and 60Hz" - same messagebox. So, Nvidia Control Panel allows to select some mode with 23 Hz, but madVR does not. One more mystery: 1. 59Hz mode is also present in Nvidia Control Panel, but is "missing" in "custom modes" window. 2. Open this mode, then press "Apply" button. 3. A message "the mode was successfully added" pops up. 4. But even after restarting the Windows this 59Hz mode is still "missing". And there is one more mystery - 50Hz mode is always marked as "active", regardless of the actually selected mode in Nvidia Control Panel. Last edited by rivera; 14th October 2017 at 21:46. |
|
14th October 2017, 23:42 | #46542 | Link | |
Registered User
Join Date: Sep 2012
Posts: 174
|
Quote:
(So you don't have to find my original posts: I'm using gtx 1080 ti, windonw 10 pro x64, MPC-HC x64 and my original problem was since I have standard modes for 23 and 24Hz, I couldn't create a custom mode inside madVR and also couldn't edit the existing modes. With the tweaked madHcCtrl.exe, editing is possible now) At the end some notes for madshi - I deleted my custom resolutions, so I'm back to zero. - Went into nvidia control panel, changed into 2160p30, full RGB and 12bit. - Opened a 23.976fps video, went into madVRs custom modes tab and clicked on the 2160p resolution with 23Hz (listed as standard mode) and clicked on edit - increased pixel clock by 0.01 mhz and clicked on test mode and clicked on Yes to save the custom mode. - the 23hz mode is now listed as "custom timings" - clicked on reset GPU - closed MPC-HC, reopened the video. - opened nvidia control panel and switched to my new custom mode (Note that in nvidia control panel the new custom mode is for 24Hz, not 23Hz for some reason) - checked custom modes tab in madVR to see that the custom timings 23Hz mode is selected as active, which it is and clicked on optimize - closed all menus and played the file for over 10min. - in custom modes tab in madVR, I clicked on "optimize", there I selected "optimized pixel clock #1" (which was the first option that had no frame drops.) and clicked on test mode, then on Yes. - played the file again and checked stats - in the first 10 sec "1 frame repeat" climbs to 2 hours, in the next 30 secs it climbs to about 4-6hours and eventually stablizes at about 9.0X hours This is again only for windowed fullscreen, with FSE I get the same output as standard 23 and 24Hz modes in FSE. --------------- Notes for madshi: (probably all nvidia bugs) 1. When I was switching around resolutions, trying things out I noticed that sometimes when I switch to the custom resolution and open nvidias control panel, in the "Resolution" section, it didn't show a custom resolution, but a new resolution at the bottom... To make it more clear: there are normally 2 sections in the "Resolutions" list in the control panel, "Ultra HD, HD, SD" with a bunch of resolutions and under that "PC" with a few more resolutions, going up to 1280x1024. If you have a custom resolution there is a new section on Top "Custom", Making it 3 sections total. *Sometimes* there is no "Custom" section, but the resolution created by madVR shows up at the top of the "PC" section with a new entry "3840x2160". When I switch to another resolution, the resolution under "PC" disappears and the "Custom" Section reappears. Couldn't really see a pattern, also don't really want to test things here, since it works and doesn't seem to be an issue. 2. When I was trying optimized pixel clocks, or other standard timings like "CVT Reduced Blanking v1" etc. I was always getting a black screen when I was in 8bit. I tried about 10 different modes, none worked. Then I went to nvidia control panel, switched to 12bit, then the timings suddenly worked. (this could obviously be caused by my TV or my AVR simply allowing more custom modes in 10/12bit) Interesting thing is though, when I'm in my custom mode, nvidias control panel doesn't have an output color depth selected https://i.snag.gy/7w9TKV.jpg the field is empty and only 8bpc is available to choose This is standard behaviour if you switch to a mode that doesn't have 10/12bit available, like when you switch from 30Hz 12bit to 60Hz, the field will be empty and only 8bit will be available to choose. The difference is, when I'm switching to 60Hz, I'm actually switching to 8bit, but when I switch from 30Hz 12bit to my custom resolution, I stay in 12bit, even though it's not available to choose afterwards. Confirmed visually with the 16bit gradient png with no dithering + the app for my AVR shows "RGB Full / 36bit" which is the 12bit mode, 8bit mode would show 24bit. If I'm in my custom resolution and try to change bitdepth from "empty" to 8 bit, I get a black screen again. So I'm definitely in 12bit here (right?) 3. Can you make it possible to change the "nvidia color settings" (output color depth, output color format and output dynamic range) inside madVRs custom modes tab? That way all settings are available from inside madVR. With all the bugs nvidia brings, I kind of trust madVR more than I do nvidia's control panel. ----------------- After all this writing I actually don't remember if there were any other things I wanted to point out, so it's those 3 things for now. Like I mentioned, probably just nvidia bugs, but those might be interesting to know, if you didn't know them already. Since I got 12bit and 9 hours without drops, I'm done with testing for now, unless you have something specific for me to test. Last edited by Q-the-STORM; 14th October 2017 at 23:50. |
|
15th October 2017, 01:26 | #46543 | Link |
Registered User
Join Date: May 2015
Posts: 29
|
I just installed Fall Creators Update and now HDR is acting differently.
I have HDR off on Windows and madvr on HDR passthrough. Before the update madvr would turn on HDR mode and turn it off after playback. Following the update it seems that windows HDR mode is also being activated, this can lead to a washed out effect. After playback then windows HDR stays on I haven't played around with it too much as it's late |
15th October 2017, 01:57 | #46544 | Link | |
Registered User
Join Date: Jun 2017
Posts: 71
|
Quote:
I have finally figured out how to see the final output of the gpu, and its 4k@60, RGB 8-bit. Definitely its the GPU converting it to 8-bit. If I get your suggestion correctly, I should create a new profile for 4k@60 videos to set the panel bit-depth at 8-bit instead? That should take away the GPUs 10bit to 8bit conversion and let madvr do it instead. I definitely prefer madvr handling any conversions over the gpu. On a side note I use the 12bit trick mentioned earlier here and manage to get 12bit RGB for all other resolutions, including 4k@23 UHD. I am hoping in this case the gpu is just padding data to 12 bits. Yes my TV is a native 10-bit panel. Last edited by austinminton; 15th October 2017 at 02:18. |
|
15th October 2017, 08:34 | #46546 | Link | |
Registered User
Join Date: Jun 2017
Posts: 155
|
Quote:
Last edited by j82k; 15th October 2017 at 08:46. |
|
15th October 2017, 08:46 | #46547 | Link |
Registered User
Join Date: Jun 2017
Posts: 155
|
As for 8-bit vs 10-bit vs 12-bit.
I have a LG 55C6V TV which is supposed to have a 10-bit panel and I tried this 10-bit test pattern to compare: https://yadi.sk/d/RPrX2C7l3HEjPq/03....2010bit%20test I'm actually getting the best gradient using full RGB 8-bit output. Not sure why this is. Either my TV is crap or nvidia isn't outputting 10 and 12 bit correctly. Last edited by j82k; 15th October 2017 at 08:52. |
15th October 2017, 09:02 | #46548 | Link | |
Registered User
Join Date: Apr 2017
Posts: 366
|
Quote:
K Last edited by oldpainlesskodi; 15th October 2017 at 09:08. |
|
15th October 2017, 10:39 | #46549 | Link | |||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
I'll add a note that resetting the GPU might not be sufficient in some cases and a reboot might be necessary instead. Quote:
Quote:
Quote:
Log 2 tries to play "John Wick", but the decoder never even sends a single frame. A couple of questions: 1) Is the media player frozen, or is the media player GUI still responsive? 2) Does the madVR OSD (Ctrl+J) still work? If so, I suppose the decoder queue is empty in these situations, right? 3) Do you have the option "delay playback start until render queue is full" activated? If so, does deactivating that option help? Quote:
Quote:
Quote:
Quote:
Quote:
Finally, a small video sample which shows all these problems you mentioned would be helpful. Or if it's hard to find one sample which reproduces all these problems, then I'm also fine with multiple smaller video samples, one for each problem. Quote:
The "The GPU rejected this mode" is unfortunately a GPU driver bug, not much I can do about it. I've already reported it to Nvidia, a fix might be coming at some point in the future, but probably not very soon. Quote:
Quote:
Quote:
No. Quote:
Quote:
Quote:
|
|||||||||||||||||
15th October 2017, 11:23 | #46550 | Link |
Registered User
Join Date: Jun 2007
Posts: 652
|
Anyway, I'm up to "no drops/repeats" for 23.976, 50 and 59.94Hz. I have perfect timings for 50 out of the box, I had 1 drop every 2 days before in CRU, through madVR I optimized it perfectly, I optimized 59.94 in madVR too. Then I removed everything and I inserted the calculated values in CRU. Which worked with 59.94.
I'd say I'm 99% there. As a side note... I've been an Nvidia HTPC user for more than 10 years. The mess that they had back then and the mess that they still have today concerning custom resolutions is beyond belief. For the life of me I can't understand how a multi-billion company can neglect a portion of its control panel for so long. Last edited by ashlar42; 15th October 2017 at 11:27. |
15th October 2017, 12:00 | #46551 | Link | |
Registered User
Join Date: Jun 2017
Posts: 71
|
Quote:
I prefer the gradient when I set 12 bit on nvidia in the above testing scenario. The file I have tested on is 4k@23. I am keeping RGB full. I also compared madvr 8-bit over nvidia for 4k@60. I honestly can't really tell the difference. |
|
15th October 2017, 12:16 | #46552 | Link | |
Registered User
Join Date: Jul 2017
Posts: 9
|
Quote:
no processing https://postimg.org/image/j79imzhv3/ upscale + olsAS https://postimg.org/image/5dl5xz7a7/ upscale + newAS https://postimg.org/image/rcrkl7b9r/ |
|
15th October 2017, 12:23 | #46553 | Link | |
Registered User
Join Date: Oct 2009
Posts: 930
|
Quote:
All the cues are empty. Also the line that shows the video file's resolutions is weird. It has an arrow in it like the scale line and doesn't start with "movie". I have "delay playback start until render queue is full" disabled because it increases seek or playback start times which I didn't like. Normal GUI/OSD appearance: Last edited by mzso; 15th October 2017 at 12:48. |
|
15th October 2017, 12:35 | #46554 | Link | |
Registered User
Join Date: May 2007
Posts: 454
|
Quote:
|
|
15th October 2017, 12:38 | #46555 | Link | |
Registered User
Join Date: May 2007
Posts: 454
|
Quote:
I think its nvidia driver related and not madVR or windows.. |
|
15th October 2017, 12:46 | #46556 | Link | ||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
reduce compression artifacts: 5 reduce random noise: 1 http://madVR.com/doom9/stuff/asRnnRca.png Maybe I've gone a bit overboard with the "reduce compression artifacts" strength, but with Anime content high values often barely harm. Quote:
Have you tried other media players like e.g. MPC-HC/BE? Does the problem occur with those, too? I'm not asking to make you switch, just trying to collect information. |
||||
15th October 2017, 12:52 | #46557 | Link | |
Registered User
Join Date: Oct 2009
Posts: 930
|
Quote:
|
|
15th October 2017, 13:05 | #46558 | Link | |
Registered User
Join Date: May 2007
Posts: 454
|
Quote:
Personally from the experiances I have had so far I think you should confirm the resolution and refresh rate is different than the resolution and refresh rate to be tested at the point the 'test mode' is pressesd. This might only apply to nvidia gfx cards. Wether you switch resolutions first silently, give a message and then switch resolutions or full error telling user to change resolution manually is up to you. I guess what makes the situation worse here is the fact there is a high probability the resolution/refresh rate will be the same already during a user trying to setup a custom resolution or optimise. This is because they are probably going to the madVR custom resolution options right from a paused movie which is playing at the refresh rate they want to play with (because madVR set the closest resolution when playback started). Last edited by Razoola; 15th October 2017 at 13:11. |
|
15th October 2017, 13:09 | #46559 | Link |
Registered User
Join Date: Oct 2009
Posts: 930
|
Update:
So I could reproduce a hang, but only one with mpc-hc (internal LAV): I can't reproduce a hang using internal codecs with Potplayer. (Sadly using the internal codecs is not really an option, because it also enables the craptastic built-in video processing filter...) Last edited by mzso; 15th October 2017 at 13:12. |
15th October 2017, 13:14 | #46560 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
PDB debug symbols for LAV are available in the first post of the LAV thread, IIRC, but the debug symbols MUST match the LAV version installed *exactly* otherwise they're doing more harm than good. PDB debug symbols for MPC should be available somewhere, too, not sure where, though. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|