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. |
23rd September 2015, 20:20 | #33121 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Ouch. That's the worst case scenario. Those changes in 88.17 to render in paused and stopped mode, and for low latency OSD really do bite me in the a... Unfortunately they're very important for some media players, so I can't really remove them. Will have to invest some work to create test builds between 88.16 and 88.17, but not today, anymore.
|
23rd September 2015, 21:25 | #33123 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Ok, please use this debug build to create a new debug log and upload it for me:
http://madshi.net/madVRXRyche1.rar This build will not do anything differently, just the debug log will give me some more information. Just to double check: When disabling NNEDI3 everywhere (both chroma upscaling and image doubling) all problems are gone, right? |
23rd September 2015, 21:57 | #33125 | Link | |
Registered User
Join Date: May 2008
Posts: 211
|
Quote:
I will run your special build after I try huhn's suggestion because Windows 10 is seriously paranoid with it's security (although they have no problem with keeping track of you if they(Microsoft) are doing the tracking.). As I told madshi I'll try it. I'm willing to try anything at this point.
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM |
|
23rd September 2015, 22:22 | #33126 | Link |
Registered User
Join Date: May 2008
Posts: 211
|
madshi, here's the log for the custom debug build: https://www.mediafire.com/?hujbvatwmw0rj6k . It's even compressed :P . I did notice that there was a slight pause (3 seconds at most) when I started the file which starts in windowed mode when I initially played the file. When I played it again in debug mode there was no pause until I went to FSE mode than there was the typical 350 fps skip.
huhn, unfortunately moving the madVR folder to even an entirely different drive didn't make a difference. I made sure I uninstalled and deleted the madshi entry in the registry before I installed madVR from it's new location.
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM |
24th September 2015, 00:09 | #33129 | Link |
QB the Slayer
Join Date: Feb 2011
Location: Toronto
Posts: 697
|
Let me start off with some history. First, for the longest time the best performing AMD driver has been 13.12. Second, I have never been able to use D3D11 in any form, it worked, but as soon as I would pause PotPlayer, it would flash and queues would fall to zero and never recover, oddly it would not report dropped frames, but the video would stutter like mad because of the empty queues. So I have been stuck on a very old driver (if I wanted to push NNEDI3 to the max) and stuck with D3D9 (not that it really mattered when it comes to quality). I continued doing updates to both driver and madVR and always ended up rolling back features/driver.
Now along comes this spectacular version of madVR! First I just updated madVR and ran it as is. WOW! GPU usage dropped from 93% to 66% HUGE improvement. So I bumped up one of the three NNEDI3 settings from 32 neurons to 64 (yes I do chroma and I do both in luma) and this pushed the GPU up to 78% (couldn't get any more neurons even though there is still room). Nice little bonus, more neurons is always better. So I figured with this headroom I should be able to run the latest AMD drivers without having to dial back my neuron counts. And sure enough it worked... GPU usage did go up as expected (78% up to 85%) so 13.12 is still the best performing AMD driver when it come to madVR. However, the magic you did madshi, does allow users like me to upgrade driver without worrying about reducing settings in madVR. HUGE kudos for that! Also, D3D11 now also works flawlessly with PotPlayer, yet another nice little bonus. I just wanted to say a big Thank You! As for the missing screen config option when using a digital flat panel. I could see there being a use to including it. As I mentioned above, I have an old Plasma with rectangular pixels (1024x768). I tested out the screen config (set it to projector to expose the settings) and setting the anamorphic lens to 4/3 did work flawlessly to compensate for these rectangular pixels. I personally don't need this, since I know how to set PotPlayer's Output Device to "TV-Out 16:9" to fix any mis-matched aspect ratios. But maybe others don't know this or their player won't allow this. It could be useful, but of course the choice is yours Anyway huge Kudos to making madVR more efficient! QB EDIT: Should have mentioned this is all on Windows 8.1 x64
__________________
Last edited by QBhd; 24th September 2015 at 04:39. |
24th September 2015, 01:20 | #33131 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
steps to reproduce from madVR default settings: disable fullscreen exclusive mode. enable nnedi3 64 neurons for luma. play a 720p source in fullscreen on a 1080p screen. |
|
24th September 2015, 08:02 | #33135 | Link | |
Registered User
Join Date: May 2010
Posts: 236
|
Quote:
|
|
24th September 2015, 09:45 | #33136 | Link |
Registered User
Join Date: May 2009
Posts: 72
|
madshi,
Yeah, you told me not to use stretch to window, I'll try to explain things a bit better. Tested using Windows 7 64bit Pro and Mpc-hc 1.7.9 (x64). Using the keep black bars visible if they contain subtitles option and setting it to forever doesn't work for me, the video is still being cropped (osd shows 720*450). Changing it to 90min or any other setting lower works without any problems, using the DVD sample I uploaded and a handful of disc's and videos I have. The reason I use stretch to window on that Blu-ray sample is because in full screen mode touch window from the inside does not remove the pillar boxing, using stretch to window does which is exactly what I want. These are the settings I use: automatically detect hard coded black bars. notify media player about black bars, no more than once every 2 sec. crop black bars. What I was asking for is the ability to simply crop the black bars without doing anything else, no aspect ratio correction. The same as using Avisynth to crop before re-encoding or on the fly via FFDshow. As I said before it's not a big deal but would come in handy for people like me who don't mind breaking the AR and stretching the image a little. The advantage this method has is that you can remove the black bars and keep the subtitles intact, here is an example using the DVD sample. madVR, touch window from inside: https://www.dropbox.com/s/q4ixihzrfj...0crop.jpg?dl=0 re-encode cropped to 720*450, stretch to window: https://www.dropbox.com/s/ypia193l5b...0crop.jpg?dl=0 Thanks. |
24th September 2015, 10:35 | #33137 | Link | |
Registered User
Join Date: Mar 2002
Posts: 2,323
|
Quote:
2. About my NNEDI3 chroma upsampling crash: I just refreshed to newest vga drivers, doing a clean install (see my signature): - the crash is still there - Windowed Overlay mode still isn't available with this combination Thanks for your awesome work!!!!
__________________
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 |
|
24th September 2015, 11:13 | #33138 | Link | ||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Unfortunately the new log isn't helpful (thanks for compressing it though). The log still seems to be from the old build. I think what happened is that you probably copied the new build into the madVR folder, and then did the manual file rename thing afterwards. By doing that you practically disabled the new build again, because you renamed it to "madVR [release].ax" and the media player only ever uses "madVR.ax". Please copy the special XRyche build into the madVR folder and afterwards do *not* rename the files. The new build is a debug build. Maybe I should have named it "madVR [debug].ax" to avoid confusion, but I did say that it was a debug build. I will need 3 logs from you now. Sorry about the extra work, but your problem descriptions are very confusing to me (see above). So I need those 3 logs to understand what's really going on: 1) Same as before. Just start playback with NNEDI3 enabled. Wait for the video to appear. Then stop. 2) Start in windowed mode, so the delay does *not* occur, let it play for about 10 seconds. Then switch to FSE mode, so the delay occurs. Wait for the video to appear. Then stop. 3) Disable NNEDI3 everywhere (all chroma upscaling, luma doubling, chroma doubling, luma quadrupling and chroma quadrupling). Start playback, reproduce the long delay, wait for the video to appear. Then stop. Please create 3 separate logs for these 3 situations. After every situation simply rename the log file with a suitable name to explain what the log contains. Thanks! Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Does anybody know which software (internal subtitle renderer, external subtitle renderer, LAV Video Renderer, whatever) draws subtitles output by the DVD Navigator onto the video image - and at what time (before madVR gets the images or after or something)? Looked at your log. The crash should be solved in the next build, in any case. However, it seems you're using the old exclusive mode path (meaning: "present several frames in advance" unchecked). Is that correct? Doing so means that madVR cannot share the render device, which also means the new D3D11 OpenCL interop cannot be used, nor Windowed Overlay. You'll have to activate "present several frames in advance" in the FSE settings, to make the new NNEDI3 work, and Windowed Overlay. |
||||||||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|