View Full Version : madVR - high quality video renderer (GPU assisted)
Klaus1189
5th November 2017, 19:00
I managed to solve the issue I was having, here's what I did trying to optimize 2160p23:
- I started a 25Hz movie in order to *not* get the "you cannot edit the active resolution" when doing the following:
- Under "custom modes" tab I deleted the mode I was trying to optimize (2160p23)
- I then had to also delete 2160p23 in the regular "Display Modes" tab
- Under "custom modes" tab, I edited 2160p23 - test mode - success - reset gpu - optimize
- go back to "Display Modes" tab, I add back 2160p23
- Close the 25Hz movie
- Start a 23 Hz movie
- Wait 30 min
- Start the 25Hz movie again - choose to optimize the 2160p23 custom mode - choose a timing with no dropped frames - Test mode - success
- Close
- Start a 23 Hz movie, wait a couple of minutes - no dropped frames for 2-3 days - iterate the process if I want to
So to summarize my thoughts as someone who was doing this for the first time and using your guide: It seems I have two options when doing this iterative process, either I edit the custom modes when playing a movie with the framerate I am trying to optimize in the background (alt A), or when playing a movie with a different framerate than the one I am trying to optimize (alt B). The intuitive way is to do alt A, which is where I ran into most problems. If I choose to test a mode with the desired timings, I will get the "you cannot because of this being the active mode"-message. The only way to get around this (as far as I understand?) is to, say, have the display running in 60Hz (or something other than 23 Hz), and then delete the 2160p23 under "Display modes" - go to Custom Modes - optimize 2160p23, test, success, now go back to the "Display Modes" tab and then once again add the 2160p23 - close the program - start a 23Hz movie. Since this alt A seems to be the intuitive way of doing this as a newbie, the big problem is having to delete the 2160p23 mode under "Display Modes" tab, in order for the "optimize" button to work without getting the "activate display" error message - and then *adding it back* directly afterwards before closing and then starting a 23Hz movie again in order for MadVR to do its calculations when running an optimized mode.
That's why I choose alt B, which is totally counter-intuitive - because why would I playback a 25Hz (or 30Hz, it doesn't matter) movie when I am trying to optimize a 23 Hz mode? Well, because this lets me access MdVR settings and go into the "custom modes" tab, choose to optimize 2160p23, test mode, success - *without having to delete the "2160p23" under the "Display Modes" tab everytime I want to iterate the process*. I then, off course, close the program and start a 23 Hz movie to let MadVR do its calculations - close program - open a 25Hz movie - and do it all again.
Maybe I am missing something? This could be solved if I could edit MadVR settings *without having to playback a movie in the first place*. This way I could be in 60Hz, edit settings, exit, and then start a clip which forces the display into the mode I am tryng to optimize. Is there a way to do edit MadVR settings when not playing anything? If not, I would suggest that MadVR tells you (or the guide) that if you run a 23Hz movie in the background, and this is the mode you want to optimize, you have to delete the 2160p23 under the "Display Modes" tab everytime you want to iterate the process - and then adding it back directly afterwards once you have tested the new timings under "Custom Modes" tab.
I apologize if I have missed something basic, but like I said, as a newcomer this is how I approached it, and the guide didn't tell me that I needed to do this "delete the mode under display modes tab, go into custom modes to test timings, go back into display modes tab and add it back" - then playback movie to calculate - iterate.
On another note - I saw some comparison screenshots of blu-ray upscaled with NGU compared to UHD bluray that only has 2K Digital Intermediate - and the NGU ones were clearly better. So congrats Madshi - you officially beat Hollywood. :thanks: so much for all your effort, it is truly appreciated!
I can not create a custom resolution with 3840x2160p60,
Have you created one?
pirlouy
5th November 2017, 23:57
I finally took time to try this custom resolution modes. And I can say it does NOT work with 23Hz.
Cause Nvidia custom resolution (control panel) uses 24Hz (as "title") for 23,976Hz (in reality)
Whereas madVR expects "title" to be 23Hz. It's a bug in nVidia control panel, but it's like this for so much time that I can't imagine nVidia fix it one day (I'm still in 385.41 though).
If I let madVR create the custom resolution itself, the title is "23Hz" in madVR, but madVR never manages to do optimization on it.
It would be great if nVidia managed to fix this for madVR custom modes to work, but for now, it's not a big problem since I use this setting in nVidia control panel, and it has always worked: https://forum.doom9.org/showthread.php?p=1781800#post1781800
Ed Riffles
6th November 2017, 03:30
I have currently been experiencing and issue with Madvr where the Render queues and the present queues are not fillig when using madvr to upscale to 3840x2160p, this leads to frame drops.
I have tried reinstalling the Lav Filters, MPC-HC, and Madvr multiples times in order to try and fix the issue. When this did not work i then decided to try DDU-ing my display drivers and installing and older version, that did not work either.
The only time i was able to get the Render queues and present queues to fill up was when i disconnected my second display off of my 980ti. My render queues and present queues then went up to 8 / 8. No more frame drops. Now i do not want to have to disable my second monitor in order to upscale movies and television with Madvr.
I then tried running the second monitor off of the internal igpu, i have an igpu630, with this when upscaling i was able to get 3-5 out of 8 render queues and present frames but was still dropping frames. This was not satisfactory. As of Right now i am unable to fix this.
OS Windows 10 pro latest Hardware: Intel core i5 7600k running at 4.0ghz, 980ti running at stock clocks, 16gbs of ram.
Software: Madvr version 0.92.7 (settings https://i.imgur.com/17BC4YZ.png https://i.imgur.com/nt4rruu.png https://i.imgur.com/BYsdkBp.png https://i.imgur.com/PDNgB44.png https://i.imgur.com/0b0sWfH.png https://i.imgur.com/knvDYar.png https://i.imgur.com/4xbll0A.png https://i.imgur.com/3D267hA.png ), Lav Filters 0.71.0 (video decoder settings https://i.imgur.com/z98BYcH.png), MPC-HC 1.7.13.112
ryrynz
6th November 2017, 03:42
Excessive screenshots. Just post your OSD.
Sent from my Mars pro using Tapatalk
Ed Riffles
6th November 2017, 03:56
OSD
https://i.imgur.com/kvwrGHu.jpg
ryrynz
6th November 2017, 04:13
What nvidia power profile you using?
Ed Riffles
6th November 2017, 05:41
I am running off of prefer Maximum performance
ryrynz
6th November 2017, 06:40
Try adaptive.
TheProfosist
6th November 2017, 09:22
@madshi I found a bug with the screenshots. I have 2x render resolution set for the screenshot. I have crop enabled. The source is a BD with 4x3 video. It is pillarboxed 1080p. So the video is 1920x1080 and its then cropped to ~1440x1080 but the screenshots get saved as 3840x2160. Since the image is cropped it ends up being stretched abnormally. Let me know if you need/want an example screenshot.
Cinemancave
6th November 2017, 10:08
I can not create a custom resolution with 3840x2160p60,
Have you created one?
No, I haven't, but I have added it under Display Modes without optimizing it. Don't think I have any 30/60 Hz material atm.
"Out of Memory bug"
On another note, I wanted to play a 3D movie yesterday, and when I went back to watching 2D I got the red "Out of Memory" message when entering fullscreen. I've searched and found that this is a problem people have been having for years - but I cannot find a satisfactory solution? If I turn off stereoscopic 3D under Nvidia CP, the bug goes away. But then I have to always run the 3D Wizard before I play a 3D movie, and I would really like to avoid having to do that. Btw, I have 24 GB RAM and 11 GB VRAM, so that can't be a problem. I am running Win 10 with Creator's update. Does anyone know how to fix this? There is already an old bug report about this, so I don't want to create a new one if this has already been fixed.
Gopa
6th November 2017, 10:10
No! Using anything but the native resolution is a very bad idea. Nothing in madVR is worth running a non-native resolution and the results would not be similar at all.
Turning up NGU quality or high for reduce compression artifacts are very minor improvements compared to the terrible quality from running the wrong resolution. Resolution is absolutely the last thing you would ever touch to get playback working. Switch to EVR before dropping the resolution.
You are correct. even with lower settings, native resolution, has better image. I am still learning. Thank you very much!
Ed Riffles
6th November 2017, 12:45
Changing the power settings doesn't do anything at all
My card is not down clocking itself when watching videos, it stays at 1150 mhz
VAMET
6th November 2017, 13:04
Dear Friends
My system, Windows 10 and i5 4690K with GTX 1070.
I have a strange issue with madVR. I have enabled 10bit (it's only happend with 10bit enabled) in Settings and in the NVIDIA Control Panel. I watch movies with Fullscreen Exclusive mode enabled. So after few minutes (it's mostly random) my screen goes black during playback, but I still hear audio and the movie continues, after 1-2 seconds my screen backs to normal and I can watch my movie. It only happens once per movie. I have tried lots of settings and it always happens.
madVR 0.9.29 (the same problem was in earlier versions too), LAV Filters and MPC-HC the latest ones. File .mkv HEVC 10bit 3840x2160 HDR, but it happens with any .mkv file.
Maybe someone had such problem and know how to resolve it?
I would be glad for any help, clue and solution.
Thank you in advance for your help.
Sincerely
Cinemancave
6th November 2017, 14:06
...I have a strange issue with madVR. I have enabled 10bit (it's only happend with 10bit enabled) in Settings and in the NVIDIA Control Panel. I watch movies with Fullscreen Exclusive mode enabled. So after few minutes (it's mostly random) my screen goes black during playback, but I still hear audio and the movie continues, after 1-2 seconds my screen backs to normal and I can watch my movie....
This same exact problem happened to me last night also, but it doesn't occur on every film, it seems much more random. I was thinking it's an HDMI sync issue, but since I have quality cables and seeing your post I'm not so sure anymore.
VAMET
6th November 2017, 14:47
Dear Cinemancave
This same exact problem happened to me last night also, but it doesn't occur on every film, it seems much more random. I was thinking it's an HDMI sync issue, but since I have quality cables and seeing your post I'm not so sure anymore.
Nope, I don't think it is HDMI related issue. I have also good quality cables and device. And it's only happen, when 10bit is set in madVR and 12bit in NVIDIA Control Panel (there is no 10bit option there).
Maybe there is some options in madVR there should be enabled and I have them disabled, or disabled and I have them enabled. I don't know, why this black screen occurs for 1-2 seconds and then everything is OK. Yep, you are right, that sometimes it doesn't happen, not every movie, but most of them and it is random, but rather at the first minutes of movies.
If you will find a solution, please share it here. Maybe someone had such problem? Anybody?
Do you also have this problem, when 10bit in madVR and 12bit NVIDIA Control Panel is set? May you also make screenshot of every option set in Settings of madVR, I will compare to mine and maybe we will solve it once for all.
Sincerely
Anima123
6th November 2017, 20:12
RCA medium plus NGU standard or sharp produces very pleasant visual effect when playing good 720p materials, which is amazing.
I used to avoid NGU standard or sharp, due to the unnatural overly sharped border effect.
el Filou
6th November 2017, 23:37
My card is not down clocking itself when watching videos, it stays at 1150 mhzIf it has performance problems in Prefer High Performance I think it will still have problems in Adaptive. Adaptive is just better for when you don't really need high clocks, but it's not the case here as your GPU seems to be maxed out.
Did you try simply lowering settings to see if it changes anything? For example, disable quadrupling just to see what the rendering times are.
I know it's counterintuitive, but in my experience you can have empty rendering queue and dropped frames even if the reported rendering times are not close to the frame time, if your GPU is at 100% load and max boost.
Ed Riffles
7th November 2017, 00:51
If it has performance problems in Prefer High Performance I think it will still have problems in Adaptive. Adaptive is just better for when you don't really need high clocks, but it's not the case here as your GPU seems to be maxed out.
Did you try simply lowering settings to see if it changes anything? For example, disable quadrupling just to see what the rendering times are.
I know it's counterintuitive, but in my experience you can have empty rendering queue and dropped frames even if the reported rendering times are not close to the frame time, if your GPU is at 100% load and max boost.
Yeah i did try this. The issue is that it is completely fine with only one monitor up and i get my queues at 7-8 in single monitor
huhn
7th November 2017, 01:17
multi screen is hit and miss on windows 10 maybe the fall update is another miss.
do both screen have the same resolution and most important refresh rate.
Ed Riffles
7th November 2017, 01:54
My main monitor is a 4k display running at 60 hz and then i have my second monitor running at 1440x2560p at 60 hz.
jkauff
7th November 2017, 02:57
I'm watching one of my noisiest Blu-ray movies, Red River. Render times got too high using both RCA and RRN at 3, and I didn't see very much effect anyway (rig is GTX 1080 driving a 4K monitor), so I disabled RCA and upped RRN to 6. The effect is amazing, almost all the noise is gone and the picture looks great (maybe a slight loss in detail, haven't played around with that yet).
Excellent work, madshi! It's not quite up to NLMeans denoising, but it's in real time! madVR just gets better and better. Congratulations on yet another great algorithm.
EDIT: Applying Crispen Edges and Enhance Detail while doubling restored the detail.
Razoola
7th November 2017, 10:48
Dear Cinemancave
Nope, I don't think it is HDMI related issue. I have also good quality cables and device. And it's only happen, when 10bit is set in madVR and 12bit in NVIDIA Control Panel (there is no 10bit option there).
Maybe there is some options in madVR there should be enabled and I have them disabled, or disabled and I have them enabled. I don't know, why this black screen occurs for 1-2 seconds and then everything is OK. Yep, you are right, that sometimes it doesn't happen, not every movie, but most of them and it is random, but rather at the first minutes of movies.
If you will find a solution, please share it here. Maybe someone had such problem? Anybody?
Do you also have this problem, when 10bit in madVR and 12bit NVIDIA Control Panel is set? May you also make screenshot of every option set in Settings of madVR, I will compare to mine and maybe we will solve it once for all.
Sincerely
I think I can say with 95% certainty that what you are experiancing is related to the quality of the HDMI cable you are using. 10bit puts more bandwidth over the cable and 12bit will be even more, espicially if its a long length. I use 12bit in control panel and 10bit in madVR and only had a problem like that until I replaced the cable with a new one.
VAMET
7th November 2017, 10:51
Dear Razoola
I think I can say with 95% certainty that what you are experiancing is related to the quality of the HDMI cable you are using. 10bit puts more bandwidth over the cable and 12bit will be even more, espicially if its a long length.
If it was related with quality of HDMI cable, but it is not, the problem will be not only for 1-2 seconds (black screen) of whole movie.
Sincerely
Razoola
7th November 2017, 11:07
Dear Razoola
If it was related with quality of HDMI cable, but it is not, the problem will be not only for 1-2 seconds (black screen) of whole movie.
Sincerely
I had the same problem with the screen going blank for a couple of seconds and then coming back when I first started using 12bit. Like I said though, it was related to the cable, I was using a high quality one but it was not enough and so the connection would drop out and come back (I guess due to data corruption).
My problem was a little worse given my TV is far away and I needed a long cable. Remember UHD with HDR (10bit) is not expected to work with a real long cables, it starts getting flaky at 7m plus.
Got a new cable and everything is now fine, I'm using this at a 6M length, not sure it can handle UHD at 60fps but I have no issues with 24fps movies at 12 bit with Dolby Atmos 7.1 HD audio...
https://www.amazon.de/gp/product/B00FK0YI4E/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
VAMET
7th November 2017, 11:14
Dear Razoola
I had the same problem with the screen going blank for a couple of seconds and then coming back when I first started using 12bit. Like I said though, it was related to the cable, I was using a high quality one but it was not enough and so the connection would drop out and come back.
My problem was a little worse given my TV is far away and I needed a long cable. Remember UHD with HDR (10bit) is not expected to work with a real long cable gets flaky at 7m plus.
Got a new cable and everything is now fine, I'm using this at a 6M length, not sure it can handle UHD at 60fps but I have no issues with 24FPS movies with Dolby Atmos...
https://www.amazon.de/gp/product/B00FK0YI4E/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
Like I said before it is not cable related. I have checked it with my best HDMI cable for UHD transfers and it's 1.0m long, I have checked UHD 60FPS Billy Lynn's Long Halftime Walk and problem still exist. I have also checked with 5 more HDMI cables the longest is 15.0m. If it is 1.0m or 15.0m the problem is still there.
Sincerely
Razoola
7th November 2017, 12:05
Dear Razoola
Like I said before it is not cable related. I have checked it with my best HDMI cable for UHD transfers and it's 1.0m long, I have checked UHD 60FPS Billy Lynn's Long Halftime Walk and problem still exist. I have also checked with 5 more HDMI cables the longest is 15.0m. If it is 1.0m or 15.0m the problem is still there.
Sincerely
I'll let you get on with it then, there is no way you'll get any picture at UHD 60fps through a 15m cable though, thats well out of spec the last I checked.
Only other thing I can think is the picture is dropping as madVR goes from windowed to exclusive mode but really it should not.
VAMET
7th November 2017, 12:30
Dear Razoola
I'll let you get on with it then, there is no way you'll get any picture at UHD 60fps through a 15m cable though, thats well out of spec the last I checked.
Only other thing I can think is the picture is dropping as madVR goes from windowed to exclusive mode but really it should not.
I don't know, why you deny, that I am not able to watch Billy Lynn's Long Halftime Walk, which is 3840x2160@60 with HDR, 10bit, BT.2020, Dolby Atmos 7.1. I assure you, that this movie works without any problems the same with 1.0m and 15.0m long HDMI cable.
The only problem is 1-2 seconds black screen, which is random, it shows even on AVC 1920x1080 without HDR, 10bit, but 10bit is enabled in madVR and 12bit in NVIDIA Control Panel.
As for Fullscreen Exclusive I have disabled 3 seconds delay automatic launch option, so it works from start directly, when I click to play the movie.
Sincerely
jeryll
7th November 2017, 16:41
...
The only problem is 1-2 seconds black screen, which is random, it shows even on AVC 1920x1080 without HDR, 10bit, but 10bit is enabled in madVR and 12bit in NVIDIA Control Panel.
...
I can confirm that the problem with black screen exist (I was almost sure that it is somehow related to my old HD 7950), but now I am not so sure seeing it doing the same behavior on modern hardware ...
I am on win 8.1 with latest AMD crimson drivers and yes mostly it is when I watch something in 2160p 10bit (HEVC or AVC), not so sure about 8 bit though...
Razoola
7th November 2017, 19:17
I'm going to say if its not the cable the next most likley thing is some kind of grounding issue around the house. For example, in my home (because its old) turning off the FL light in the bathroom can cause the audio to drop out but not the picture. On my old TV it would cause the picture and audio to drop for a couple of seconds. So if your cases if you know its not something else your turning off or on around the house then it might be something like the fridge or freezer. Try plugging your PC and TV into a different socket and see if it helps.
njfoses
7th November 2017, 21:50
Dear Friends
My system, Windows 10 and i5 4690K with GTX 1070.
I have a strange issue with madVR. I have enabled 10bit (it's only happend with 10bit enabled) in Settings and in the NVIDIA Control Panel. I watch movies with Fullscreen Exclusive mode enabled. So after few minutes (it's mostly random) my screen goes black during playback, but I still hear audio and the movie continues, after 1-2 seconds my screen backs to normal and I can watch my movie. It only happens once per movie. I have tried lots of settings and it always happens.
madVR 0.9.29 (the same problem was in earlier versions too), LAV Filters and MPC-HC the latest ones. File .mkv HEVC 10bit 3840x2160 HDR, but it happens with any .mkv file.
Maybe someone had such problem and know how to resolve it?
I would be glad for any help, clue and solution.
Thank you in advance for your help.
Sincerely
Are you on 385.xx Nvidia drivers? All the newer versions are buggy as hell
mzso
7th November 2017, 21:52
Are you on 385.xx Nvidia drivers? All the newer versions are buggy as hell
Yeah but which is the best (least bad) one?
VAMET
7th November 2017, 22:11
Dear Friends
I'm going to say if its not the cable the next most likley thing is some kind of grounding issue around the house. For example, in my home (because its old) turning off the FL light in the bathroom can cause the audio to drop out but not the picture. On my old TV it would cause the picture and audio to drop for a couple of seconds. So if your cases if you know its not something else your turning off or on around the house then it might be something like the fridge or freezer. Try plugging your PC and TV into a different socket and see if it helps.
;) ;) ;) I have 4 friends with the same issue and here on this very forum there are alredy 3 of us with the same one too. It's not a cable and sockets.
Are you on 385.xx Nvidia drivers? All the newer versions are buggy as hell
I will check the older drivers, but as far as I remember, it happens for good six months or more, so when 385.xx was released? And in my opinion it's not a driver issue, because I have got NVIDIA and other user (jeryll) here on this page of forum said, that he has got AMD GPU HD 7950.
All things, that connects us and our problem are madVR and 10bit settings. All of us has got different GPU vendors, different Windows versions. This issue may be related with madVR, maybe some settings, which we have enabled or disabled and should be different. This problem occurs with 10bit option enabled.
Sincerely
ryrynz
7th November 2017, 22:17
Yeah but which is the best (least bad) one?
Determine that for yourself if you want, nobody evaluates every driver. Grab 358.28, no need to ask.
Neo-XP
8th November 2017, 02:54
madVR v0.92.9 released
http://madshi.net/madVR.zip
* added "reduce compression artifacts" quality option "high"
Option "high" looks a little better, but needs more GPU resources than I have to spare for >= 720p sources.
I tested AS again, with and without LL, and for films at least LL is not good, because for the same sharpness effect there are a lot more ringing and dark halos with LL on and no other improvements. For instance, I had to increase the AS value to 0.6 with LL on to get (almost) the same sharpness than AS 0.2 without LL.
So here are my new settings (GTX 970) :
artifact removal : reduce banding artifacts medium & high
chroma upscaling : NGU Anti-Alias (high)
luma doubling : NGU Sharp (high), supersampling always, quadrupling disabled
chroma doubling : Bicubic60 AR
upscaling algo : Jinc AR
downscaling algo : Bicubic150 AR [relaxed]
upscaling refinement : AS 0.2 AR + soften edges 1 + add grain 3
dithering : Ordered + colored noise + change dither
trade quality for performance : all disabled
They are good to upscale films to UHD, if you like sharp images and have good quality sources.
And since there are now some films in UHD, I will try to compare FHD films upscaled to UHD by madVR VS "native" UHD.
Of course I will have to find a true UHD film : http://realorfake4k.com/list/ and if possible from the same master.
To be continued...
Manni
8th November 2017, 08:22
Yeah but which is the best (least bad) one?
385.28 is the last one that allows to change bit depth to 12 when a custom/optimized 23p profile is active.
385.41 doesn't allow this, you have to set 12bits in a standard mode, but it still handles HDR fine.
I'm on 385.28 as it does eveything I need, until a Fall Creators Update + newer nVidia driver is declared as working correctly with HDR.
varekai
8th November 2017, 08:25
Determine that for yourself if you want, nobody evaluates every driver. Grab 358.28, no need to ask.
Is the driver version number right? Or just a typo? Should be 385.28?
I'm om 385.69 and no issues as far as I can tell...
Anyone having trouble with 385.69?
ryrynz
8th November 2017, 08:34
It doesn't matter, anything 358 is fine. Nobody is having issues with 358.xx AFAIK.
jeryll
8th November 2017, 08:43
...
All things, that connects us and our problem are madVR and 10bit settings. All of us has got different GPU vendors, different Windows versions. This issue may be related with madVR, maybe some settings, which we have enabled or disabled and should be different. This problem occurs with 10bit option enabled.
Well for me, the whole thing gets pretty weird, because the same "black screen" bug happens to me while playing specific game (ETS2) or while watching content through MADVR, so for a long time I was sure this is a graphic driver bug (AMD drivers for win 8.1 are pretty old compared to win7 or win10 (currently 17.7.1))
Now the only thing I can come up with so far - which connects this two different environments - (if its not the AMD driver bug) is DirectX, maybe its related to the new D3D11 acceleration used in newest LAV, so for now I switched back to old DXVA2 CB and will test if anything changes and will report back, but this might take a while, because I can watch something for maybe 1 - 2 days without a glitch, then suddenly it happens 3 times within 10 minutes ...
varekai
8th November 2017, 08:49
It doesn't matter, anything 358 is fine. Nobody is having issues with 358.xx AFAIK.
You mean 385?
ryrynz
8th November 2017, 08:51
Yeah whatever.
varekai
8th November 2017, 08:51
Yeah whatever.
Huh...
VAMET
8th November 2017, 09:01
Dear jeryll
Well for me, the whole things gets pretty weird, because the same "black screen" bug happens to me while playing specific game (ETS2) or while watching content through MADVR, so for a long time I was sure this is a graphic driver bug (AMD drivers for win 8.1 are pretty old compared to win7 or win10 (currently 17.7.1))
Now the only thing I can come up with so far - which connects this two different environments - (if its not the AMD driver bug) is DirectX, maybe its related to the new D3D11 acceleration used in newest LAV, so for now I switched back to old DXVA2 CB and will test if anything changes and will report back, but this might take a while, because I can watch something for maybe 1 - 2 days without a glitch, then suddenly it happens 3 times within 10 minutes ...
OK, please try to check DXVA2 Copy Back, I use D3D11, but I used DXVA2 Copy Back and I think I remember, that this problem exist too.
Sincerely
austinminton
8th November 2017, 11:06
I am with Razoola on your black screen issue. It sounds like an hdmi cable which cant do 18Gbps properly. The easiest way to check is if you are getting blackouts on normal windows desktop when you set nvidia to 4k@60 4:4:4 (or RGB).
Razoola
8th November 2017, 11:42
Dear Friends
;) ;) ;) I have 4 friends with the same issue and here on this very forum there are alredy 3 of us with the same one too. It's not a cable and sockets.
On the other side I could say, how many years have your friends or others with this problem been watching movies in 2160p? Then of these users with this issue, how many report it goes away when they switch to either 2160p 8bit or 1080p.
Going on this thread the vast ammount of users do not have the issue you are experiancing at the resolution/bit depths you have stated (you said you get it at 1080p also). On top of this, going from other forums I have read in the past relating to UHD gaming and video, this issue of the picture dropping for a couple of seconds has always been the result of one of the following (with the first being the most likely).
1) Poor quality HDMI cable or cable to long.
2) Grounding or electrical interference from other electronic things around the home.
3) Fault in the HDMI connection in the TV or PC / console.
If this were a madVR or GFX driver situation I think there would be many more people flagging this up already and I would be one of them.
ashlar42
8th November 2017, 13:19
I finally took time to try this custom resolution modes. And I can say it does NOT work with 23Hz.
Cause Nvidia custom resolution (control panel) uses 24Hz (as "title") for 23,976Hz (in reality)
Whereas madVR expects "title" to be 23Hz. It's a bug in nVidia control panel, but it's like this for so much time that I can't imagine nVidia fix it one day (I'm still in 385.41 though).
If I let madVR create the custom resolution itself, the title is "23Hz" in madVR, but madVR never manages to do optimization on it.
It would be great if nVidia managed to fix this for madVR custom modes to work, but for now, it's not a big problem since I use this setting in nVidia control panel, and it has always worked: https://forum.doom9.org/showthread.php?p=1781800#post1781800
That's strange. I have 23.976 working on a GTX 660 with "no frame drops/repeats"- Although, to be fair, I inputted the values madVR calculated into CRU.
Edit: and now, for the first time in ages... I have both working 1080p23 and 1080p24 (23.976 and 24.000) refresh rates. I simply went back to CRU and added 24.000 as an extra resolution. madVR is switching correctly to it when playing back 24.000 material and it switches to 23.976 when playing back corresponding material.
I don't know what changed but I think it's either the first time it happened to me or it's happened so long ago that I don't remember when.
23.976 with no drops/repeats, 24.000 with 1 frame drop every 1 day. 50.000 with no drops/repeats, 59.94 with no drop/repeats. I'm in heaven.
Win 10 x64 (Spring Creators Update, I'm skipping Fall for however long I'll manage to), GTX 660 with 385.69 drivers.
jeryll
8th November 2017, 14:13
...
1) Poor quality HDMI cable or cable to long.
...
If this were a madVR or GFX driver situation I think there would be many more people flagging this up already and I would be one of them.
Hm, truth to be told, it could be the cable on my side, I have very cheap hdmi cable from Tesco (only 3m long though). Never had any problem with it (and madVR) until my 1080p plasma TV died suddenly few months ago. Then I decided to buy 4k HDR display from LG and the "black screen" problem start to appear ... thanks for pointing this out, I will buy new quality cable and see if it helps ...
Neo-XP
8th November 2017, 14:18
Ok so I did some tests with a true UHD source (Passengers). I have found the UHD image here : http://madvr.com/doom9/passengers/PassengersUHD.png
UHD | Old NGU Sharp (v0.91.1) | New NGU Sharp (v0.92.9) :
https://thumb.ibb.co/gQZ33G/Passengers_UHD_frame_149159.png (https://image.ibb.co/j0tKcb/Passengers_UHD_frame_149159.png) https://thumb.ibb.co/dDVbOG/Passengers_Old_Ngu_Sharp.png (https://image.ibb.co/fdNCxb/Passengers_Old_Ngu_Sharp.png) https://thumb.ibb.co/hqKsxb/Passengers_New_Ngu_Sharp.png (https://image.ibb.co/jHvAiG/Passengers_New_Ngu_Sharp.png)
And the FHD source :
https://thumb.ibb.co/bM49tG/Source.png (https://image.ibb.co/fhgB7b/Source.png)
When comparing the two upscaled images to the UHD one, the old NGU Sharp image is closer to the UHD one because the little details are better processed and there are less artifacts (ringing, dark halos, aliasing, etc.) around the edges.
Of course, you need to zoom quite a lot to see this.
Also, there is 5.28% difference between the UHD image and the image upscaled by the old NGU Sharp and 5.40% with the new NGU Sharp. Tested here : https://huddle.github.io/Resemble.js/
For information, there is 6.11% difference when comparing the UDH image with the FHD image upscaled to UHD by Lanczos3 AR.
Now I guess the goal is to find the right settings to match the UHD image with the less % difference, with a lot of images.
Edit : If you have a hard time spotting the differences between the two NGUs, this can help :
https://thumb.ibb.co/ftMVYG/differences.png (https://image.ibb.co/dyc4tG/differences.png)
Thunderbolt8
8th November 2017, 14:33
Now I guess the goal is to find the right settings to match the UHD image with the less % difference, with a lot of images.while this might be mathematically correct, my guess is that this does not necessarily correspond how much "correct" or "similar" the upscaled image has to look to the viewer. visual perception often doesnt seem to work that way.
Neo-XP
8th November 2017, 15:26
I think you are right, because if it were true, we just had to downscale a source image with the best algorithm and then upscale it again and try to get the closest image to the source.
Also, the UHD image is not perfect either.
David
8th November 2017, 15:36
And the FHD source :
https://thumb.ibb.co/guqPcb/Source.png (https://image.ibb.co/bWVeAw/Source.png)
Why does it have 1536*864 resolution?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.