madVR - high quality video renderer (GPU assisted)

[madshi]

In some HDR movies, the 3DLut file does not take effect. Even if I press "ctrl + alt + shift + 3" the screen is not divided into 2. Why?
I've no idea. Can you try to find out in which conditions exactly it works and in which conditions it doesn't? Finding a clear pattern there would help a lot of finding and fixing the issue.

It "seems" that they finally added support for custom res:
https://communities.intel.com/thread/78158

Unfortunately only from 4th gen, so no HD4000 support, f***ck :)
It generally works on my HD4000, too, but with various bugs and limitions.

I did more investigation and realized that my HDMI Zone 2 in the AVR was on. I switched it off and the EDID discrepency went away. With it, the ability to use the custom modes tab with all my 4K modes came back.
Ah, cool!

Now that the custom modes tab works with 4K23, I've tried to optimize it, unfortunately MadVr doesn't register the playback of the video, and keeps saying timings not measured, so optimize always produces the same results (it tells you what to do and to come back there after playing).
I've recently noticed that the measurement currently only works if you originally created the custom mode with the new "custom modes" tab. If you use the Nvidia custom res control panel, or the old "madCustomRes.exe" tool, the measurements are not recorded. Could you please try to delete the custom mode, and then re-create it with the "custom modes" tab? After that measurement and optimization should work fine.

FYI, measurements are stored in HKCU\Software\madshi\madVR\DisplayModeMeasurements. This registry key is created when you create the custom mode with the "display modes" tab, but not when creating it any other ways. After creating the custom res, there will only be a "LatestMode" value there. After 10 minutes of playback, several other values should be added, like e.g. "ClockDeviation".

[chros]

It generally works on my HD4000, too, but with various bugs and limitions.
Oh, really? Can you link the driver you used? Thanks

[Prinz]

Getting a crash when stopping playback on secondary monitor (TV via AVR) in Zoomplayer with the new version.

[j82k]

So I created a pretty much perfect 23.976 mode using the new madVR custom tool which is awesome but this new mode is shown as 24Hz in the nvidia control panel and the original 24Hz mode is gone.
Is there any way to make it replace the original 23Hz mode and not the 24Hz mode.

Also when using the new D3D11 Decoder it often crashes when moving the MPC-HC window to the TV, which is my secondary screen.

[Siso]

Is it possible to add super-xbr and NGU in the regular upscaling, the maximum there is Jinc...

[cork_OS]

Is it possible to add super-xbr and NGU in the regular upscaling, the maximum there is Jinc...
It's already used for "regular" upscaling, just turn it on and check OSD for different scaling coeffs.

[dvd1]

That's really hard to say. You'll need to do some experimenting to find filter combinations that are fast enough with your GPU. I'd recommend setting chroma upscaling to Bilinear, because luma/image upscaling is so much more important and you need every bit of GPU power for that. For luma/image upscaling you can try if "NGU Anti-Aliasing" works at "low" quality level 720p24 content. I kinda doubt it, but you can try. If not, try maybe Lanczos3 AR instead.

In order to get the best possible quality, you may have to use different settings for different situations. E.g. 576i50 -> 1080p50 is quite demanding because the GPU has to render 50 frames per second. 720p24 -> 1080p24 is *much* easier. So for 720p24 upscaling you can use higher quality scaling algorithms. You can use profiles to setup different algorithms for different situations/video files.
576i 50 FRS at 1080p 50 FRS image upscaling Spline 64 AR filter
jnc jump with video, chroma upscaling thing recommended to have a good video?
What version madVR can I use with my graphics card?
thank you so much

[Manni]

I've recently noticed that the measurement currently only works if you originally created the custom mode with the new "custom modes" tab. If you use the Nvidia custom res control panel, or the old "madCustomRes.exe" tool, the measurements are not recorded. Could you please try to delete the custom mode, and then re-create it with the "custom modes" tab? After that measurement and optimization should work fine.

Thanks but I never used the nVidia custom res, and the last tests I reported were made after a clean re-install of the latest drivers, so no MadVR custom res either to start with.

I did delete the custom res to make sure and tried again, it made no difference.

So I tried to let the video run longer, and that did the trick. As you said you had only let it run for 10mn for your own tests, I did the same and that's when it didn't record anything. I let it run for more than 30mn, and the data was available. Is there a hard-coded threshold before which MadVR doesn't consider the data? I might have stopped just short of 10mn in my earlier test.

Unfortunately, none of the custom timings worked. All of the ones with a different pixel clock failed (no HDMI sync at all / no signal detected by the PJ). Out of the two with the same pixel clock, one failed (same as above) and one half worked, in that the PJ detected a signal and displayed it, but the colors of the desktop were altered and my mouse pointed was not displaying properly, so clearly not usable.

So as far as I'm concerned, the non-optimized EDID timings are what works best for me. MadVR confirms after measuring that I should expect around 1 hour without a drop/repeat if I apply these, and that's what happens.

Small request: please could you slightly extend the timout delay when testing a mode? Some displays (like my JVC) can take up to 15=20 seconds, sometimes more to sync. So extending the delay to 30 secs before it reverts to the current mode would be great. Maybe it could be an option, so that those with fast-syncing displays are not penalised? I have changed the OS timeout so that I have the time to test a new mode, but I have to go blind (left arrow / enter) when changing them with the nVidia control panel.

Also I have the same issue as j82k, the custom res I tested is 23p but it replaces the 24p res in the nVidia control panel. It would be great if it replaced the 23p one and left the 24p intact.


FYI, measurements are stored in HKCU\Software\madshi\madVR\DisplayModeMeasurements. This registry key is created when you create the custom mode with the "display modes" tab, but not when creating it any other ways. After creating the custom res, there will only be a "LatestMode" value there. After 10 minutes of playback, several other values should be added, like e.g. "ClockDeviation".

Thanks for the info.

[JarrettH]

If your display can't do 23p, then you're probably using smooth motion? In that case custom modes are not needed for you, neither is Reclock.

Yeah, but can I not create a custom mode to replace using smooth motion? Maybe I'm not understanding something. No, my display won't do 23 hz. Is 72 hz preferable to 59.940 hz for 23.976 movies?

https://c1.staticflickr.com/5/4431/36469621982_c94b68cce2_o.jpg

[jmonier]

The only thing that makes sense to me is if somehow your media player might be crashed but still lurking in the background. madVR automatically restores SDR mode when your media player closes - or when madVR is properly freed. If you can reproduce this problem, close your media player and double check that it's not listed in the task manager, anymore. If it still is, terminate it. Does that help?

I'm using Zoomplayer, so ZP is still there after the player portion has stopped, but this problem persisted even after ZP was closed completely. NOTHING returned it to SDR except a reboot.

Since then, I've replaced the 1060 6gb with a 1070 (which, I believe, is what you use). With that and (I believe) no other changes, it works fine. It switches to SDR as soon as playing stops within ZP. And, it also works fine in FSE.

I would find it hard to believe that 1060 vs 1070 was the culprit but I don't have any other explanation.

[huhn]

Yeah, but can I not create a custom mode to replace using smooth motion? Maybe I'm not understanding something. No, my display won't do 23 hz. Is 72 hz preferable to 59.940 hz for 23.976 movies?

https://c1.staticflickr.com/5/4431/36469621982_c94b68cce2_o.jpg

you can use smoothmotion or try your luck with ~48 hz or 72 hz

[Razoola]

Im trying the latest version but the custom modes tab does not show. well I see it for a moment and then it disapeers. I have confirmed the display is active and listed in the PC's control panel. I'm on windows 7 with nvidia 980.

[x7007]

Madshi, why when using Exclusive the performance of Render Queue and Present Queue are cut to half from 8 it's 3 and 1 . on Windowed mode it's fine . Rendering time doesn't change and stays 10-15ms . it's a 24Fps movie 1080p MKV .

EDIT : Found the issue : This is only happens when using the 24" hack to 60. without it enabled everything is fine in exclusive.. what could be the issue ?

http://i.imgur.com/iAiYHez.jpg

[AngelGraves13]

- NNEDI3 Chroma Crash - Wasn't able to copy to clipboard, but uploaded the report using madvr and said it crashed when I selected NNEDI3 Chroma. MPC-HC also uploaded a report...here it is. I'm using MPC-HC 1.7.13.89x64, LAV 0.70.2-35 and madvr 0.92.1. LAV is set to use DX11 for decoding and I'm using DX11 presentation in madvr as well. This is easy to reproduce every single time, at least on my system. I select NNEDI3 for Chroma and it crashes. Every single time. I can send my madvr settings if needed.
Crash report - https://drdump.com/UploadedReport.aspx?DumpID=16423490&SecondVisit=1
- The other issue where the player and madvr will randomly freeze can only be reproduced if you scrub the file by jumping back and forth to different timecodes of the file or skipping to different chapters, or simply clicking on the seek bar in random positions until it crashes. Probably a stack overflow in the renderer? Just my best stupid guess.

[mparade]

@madshi

Can you provide me with a small sample? Then I'll have something to test with

For testing Full SBS HEVC 10 bit video:

http://s4.toldacuccot.hu/letoltes?sid=3a3cd0a8d9cc32a0c41dbcc1ffc68a3c&file=test_hevc_10bit.3D.SBS-001.zip

Again, thank you very much.

[Manni]

OMGosh. I'm not sure if it's the new Nvidia drivers or Windows 10, but I can't get 3D to work *at all* on my PC now, using my Nvidia 1070. Activating 3D in the OS control panel doesn't do squat. Trying to activate 3D in the Nvidia control panel is painful, it opens up a new window, which then crashes.

Fixed the nVidia 3D Vision issue, so although it's not MadVR related I thought I'd share the solution to save you (and others) some time.

At first I tried to run the wizard in Windows 8 compatibility mode, but although it allowed to go further, it was still crashing. So I did some registry exploration and a bit of internet research. Here is the digest:

All the 3D Vision related keys are in =[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D] for x64 machines, and [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D] for x86 machines.

There are two registry keys that need to be set to make it possible to enable 3D vision without going through the wizard:

StereoVisionConfirmed
and
StereoViewerType

Both need to be set to 1.

For the nVidia control panel, this means that 3D is set-up and that the wizard doesn't need to be run.

Unfortunately, there are no registry keys to enable the 3D Stereoscopic Vision option itself in the panel, so you need to run the nVidia nvstlink.exe utility in \Program Files (x86)\NVIDIA Corporation\3D Vision (that's where I found it even on my x64 machine).

nvstlink.exe /enable will enable 3D in the control panel
nvstlink.exe /disable will disable 3D in the control panel

This switch doesn't work if the above registry keys haven't been changed to 1 first, at least here.

I don't know if this will stick but there is a batch file here https://forums.geforce.com/default/topic/544995/handy-batch-file-to-fix-3d-settings/ that can be called to do all this (and more) automatically.

I've made a shorter version to just deal with the two registry keys and launch the nvstlink.exe /enable utility.

If it doesn't stick, I'll put that batch file in my startup folder or will launch it using the group policy / task scheduler, but before doing this I'd like to check if it's necessary or not (i.e. if the 3D disables itself or if it sticks).

Hopefully that will do until nVidia/MS fixes this more permanently.

Of course enabling 3D permanently works for me because I'm in 2160p23 by default, so unless I need to playback 3D there is no downsides to having 3D on permanently, as it will simply be enabled when I switch to 1080p23 for 3D playback.

Someone using 1080p will have to switch manually otherwise having 3D permanently on will be detrimental to PQ in 2D.

Not a permanent fix, but a decent workaround. Hope this helps!

[EDIT]: once the registry keys are set, you can actually enable/disable the 3D option in the nVidia control panel without using the utility (and without the buggy wizard insisting to run), but it looks like it's not sticky. Viewertype had changed again, so I have to re-change it.
Looks like I'll have to run the batch file at startup.

[Xaurus]

Holy moly just saw the posts for the last few days and the new version, gonna spend some time now setting it up. Great work @madshi!

[Siso]

Holy moly just saw the posts for the last few days and the new version, gonna spend some time now setting it up. Great work @madshi!

The custom resolution is a good feature, but imho if you want to cover more frame rates etc. 23.976, 24, 25 you need a multiple of 24 and reclock, otherwise you have to test a lot for each refresh rate and fps...

[cyberscott]

Did more tests with the AVR as a display, and sadly the custom modes tab seems to reject most relevant modes (GPU rejects the custom mode), especially 2160p23, which work fine with the standalone experimental tool when the AVR is set to AVR and the PJ as a PJ.

I noticed that the only reported difference when the AVR is set to a display is that the native resolution is 720p (vs 2160p when the JVC is set to be the display). This leads the custom modes tab to only display 720p modes until you uncheck the display native modes only. Otherwise, all the other attributes are the same.
-
One suggestion I have about your receiver and the native resolution being listed as 720p. I have a Denon receiver that does the same thing if you have the receiver's dual HDMI output set to both. If I set the receiver's HDMI output to only one (not dual) the receiver's native resolution detected by window's becomes 2160p.

[Xaurus]

Good news, managed to create a custom res for 50p.

Unfortunately, the mode I use 99% of the time, 59p refuses to cooperate.
I just get the "the gpu driver rejected the mode for unknown reasons" when trying the EDID mode, the CVT v1 and CVT v2.
I have a LG B6 OLED 4K TV. Prior to starting this adventure I uninstalled the old GPU driver by using DDU, then installed the latest Geforce 385.28 driver for my GTX 1060.

Any tips?

[arrgh]

@Madshi
since you have several times advertised to use Win81 instead of Win10, I have given it a shot…

the problem obviously are the graphics drivers; Intel & MS decided to support KBL graphics only in Win10 (in my case HD620)…

but one can patch it (e.g new driver 154519.4678.zip)…
enter in file „igdlh64.inf“ (in folder „Graphics“), section…

;=====================================================================
; Windows 8.1 Install - DT Only
;=====================================================================
[IntelGfx.NTamd64.6.3]
…

The following line (for HD620):
%iKBLULTGT2% = iKBLD_w10, PCI\VEN_8086&DEV_5916

Then install manually (with switched-off driver signature) by choosing this igdlh64.inf.
It works up to the point where I get the same problems with “jumping” frames (both, in 2D and 3D) which was already addressed some month ago for Win10 (…an Intel driver issue). You were able to fix it for Win10.
I know you are deep into other things… but maybe now, since in principle you know what the basic problem is, it would be easier to fix it for Win81… (the very same driver 154519.4678.zip works for Win10)

Thanks

[el Filou]

Thanks a lot to madshi and nevcairiel, DX11VA is awesome!
Now I can watch 4K without any dropped frames when with DXVA2CB it was just a slideshow.
Additionally, it shaves 2-3 ms off the rendering time while at the same time making the graphics card consume 5-10W less Vs. DXVA2N, which is nice considering the boost in chroma quality.

Something strange I've noticed: I'm using ReClock, and it seems like madVR in DX11VA mode makes it behave differently: it detects a different system clock, it (finally) sees the display as 23/59 Hz instead of 24/60 previously (but it always detected the actual refresh rate correctly), and - last but not least - madVR now reports it expects one frame drop every 1 day instead of every 2.2 hours with DXVA2.
Can anyone explain this?
I'll also ask in the ReClock forum.

I also am seeing the 'custom modes' tab appear for a very short moment and then disappear from the GUI. I'm using a Panasonic plasma in RGB Full 8-bit on HDMI through a Denon AVR, and they are setup as such in madVR. The Denon has only one output and is configured as Repeater, not Scaler. I have no other display connected.

I also am seeing crashes with NNEDI set as chroma upscaler. Do you still need more crash reports for this?

[mv]

@madshi
Seems that custom mode tab disappears once a Profile is created.
Screenshots:
http://imgur.com/ldO6Vsl
http://imgur.com/215bOEk

Otherwise works really good!
Thanks for your great work.

[Manni]

-
One suggestion I have about your receiver and the native resolution being listed as 720p. I have a Denon receiver that does the same thing if you have the receiver's dual HDMI output set to both. If I set the receiver's HDMI output to only one (not dual) the receiver's native resolution detected by window's becomes 2160p.

Thanks, as already reported this was due to HDMI Zone 2 being on by mistake. Switching it off solved it.

[egandt]

Are the profiles inside of the "device" section? Are they covering the "diaplay modes" tab?




Got it to work if I move the display modes out side of a Profile Group, if I put it in a profile group it disappears.

ERIC

[aufkrawall]

D3D11VA and new HDR default setting work like a charm here for SDR output, both performance and visuals are great. Very impressive, thanks.

[x7007]

Fixed the nVidia 3D Vision issue, so although it's not MadVR related I thought I'd share the solution to save you (and others) some time.

At first I tried to run the wizard in Windows 8 compatibility mode, but although it allowed to go further, it was still crashing. So I did some registry exploration and a bit of internet research. Here is the digest:

All the 3D Vision related keys are in =[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D] for x64 machines, and [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D] for x86 machines.

There are two registry keys that need to be set to make it possible to enable 3D vision without going through the wizard:

StereoVisionConfirmed
and
StereoViewerType

Both need to be set to 1.

For the nVidia control panel, this means that 3D is set-up and that the wizard doesn't need to be run.

Unfortunately, there are no registry keys to enable the 3D Stereoscopic Vision option itself in the panel, so you need to run the nVidia nvstlink.exe utility in \Program Files (x86)\NVIDIA Corporation\3D Vision (that's where I found it even on my x64 machine).

nvstlink.exe /enable will enable 3D in the control panel
nvstlink.exe /disable will disable 3D in the control panel

This switch doesn't work if the above registry keys haven't been changed to 1 first, at least here.

I don't know if this will stick but there is a batch file here https://forums.geforce.com/default/topic/544995/handy-batch-file-to-fix-3d-settings/ that can be called to do all this (and more) automatically.

I've made a shorter version to just deal with the two registry keys and launch the nvstlink.exe /enable utility.

If it doesn't stick, I'll put that batch file in my startup folder or will launch it using the group policy / task scheduler, but before doing this I'd like to check if it's necessary or not (i.e. if the 3D disables itself or if it sticks).

Hopefully that will do until nVidia/MS fixes this more permanently.

Of course enabling 3D permanently works for me because I'm in 2160p23 by default, so unless I need to playback 3D there is no downsides to having 3D on permanently, as it will simply be enabled when I switch to 1080p23 for 3D playback.

Someone using 1080p will have to switch manually otherwise having 3D permanently on will be detrimental to PQ in 2D.

Not a permanent fix, but a decent workaround. Hope this helps!

[EDIT]: once the registry keys are set, you can actually enable/disable the 3D option in the nVidia control panel without using the utility (and without the buggy wizard insisting to run), but it looks like it's not sticky. Viewertype had changed again, so I have to re-change it.
Looks like I'll have to run the batch file at startup.


Does the 3D works for you when you do it from the Windows Display ? Enabling 3D doesn't work, only Disabling disables it from NVCP when you change it from the Windows Display menu.

[ryrynz]

X7007… don't quote an entire post that big ever.

[austinminton]

First I would like to thank madshi for the latest madvr release. HDR10 now works fine with the latest nvidia drivers (385.28 on gtx 1080), even in FSE. Automatic switching works flawlessly as well. I have finally moved from 378.92 as it seems all HDR problems are now fixed with the latest drivers.

Unfortunately 3D has stopped working with the latest drivers. I am able to enable stereoscopic 3D and run the wizard successfully. But once 3D is enabled MPC-HC crashes as soon as it goes to full screen. I have tried with both 3D and non-3D mkvs. Even 4K files which will not launch in a 3D resolution crash MPC instantly on going into full screen (if stereoscopic 3D is enabled in nvidia).

Another minor problem is that enabling 3D in OS doesn't enable nvidia's setting, so the madvr settings on auto enabling nvidia stereoscopic 3D is broken.

I have another PC with a gtx 1080 still on the old drivers (378.92) on which 3D works fine with madvr 0.92.1. Both PCs are on windows 10 creators update. My feeling is something has changed recently on the nvidia 3D drivers. I humbly request madshi to please look into this problem as madvr 3D is a great feature.

Thanks.

[Asmodian]

As long as you're able to switch your display to HDR manually (or using a device like the HD Fury Linker/Integral/Vertex)

This is the part I don't think works (at least on my system, a GPU directly connected to an LG OLED C7). My display needs metadata to enable HDR mode and how do you make sure the metadata is the same as what madVR sends?

To make a calibration 3DLUT for HDR output from madVR's HDR processing I need to set my display to use madVR's "DCI-P3 at 1000 nits" metadata (or whatever is set in madVR) when measuring the patterns, however I don't know how to do that. :(

I've compared Calman HDR10 Workflow readings with profiled i1D3 between madTPG+manual HDR switch (launched a HDR video file and then collapsed the player window) and calibration patterns from R.Masciola's HDR-10 UHD Test Patterns disk. Result were pretty close not 100% identical though.

Even took a crazy attempt to create a 3DLUT but of course it was a total failure because of the display tonemapping (LG OLED) which couldn't be disabled at the moment.

Doesn't this cause the TV to use whatever metadata that video had, not the metadata madVR would send when using a 3DLUT?

We need the display's tone mapping, that is the entire point of HDR, but we want to "correct" its input (by using a 3DLUT to generate a specific fixed set of metadata) so that when sent to that particular display, at its current settings, it produces the best image, based on a meter.


While writing this it made me think of a (hopefully) simple addition to madTPG. A button to enable HDR mode. :)

Edit: Even with this button, CalMAN doesn't have an option to create madVR HDR 3DLUTs (as far as I can tell). :(

[Manni]

Does the 3D works for you when you do it from the Windows Display ? Enabling 3D doesn't work, only Disabling disables it from NVCP when you change it from the Windows Display menu.

The 3D in the OS needs to be enabled, but that alone doesn't enable 3D. It also need to be enabled in the nVidia control panel.

I've made a batch file (adapted from the one in the link in my earlier post) to fix the registry keys and enable 3D on the fly (without having to go through the buggy 3D wizard). I now run this batch file every time I switch my PJ to 3D with iRule, so 3D works for me 100% of the time, whether it was enabled or not in the nVidia control panel. I hit the 3D button on iRule, it runs the batch file to make sure 3D is enabled in the nVidia control panel, selects the 3D mode on my JVC (high lamp) and 3D works reliably (finally!). Of course not as good as a driver/OS fix, but a very acceptable temporary workaround.


Unfortunately 3D has stopped working with the latest drivers. I am able to enable stereoscopic 3D and run the wizard successfully. But once 3D is enabled MPC-HC crashes as soon as it goes to full screen. I have tried with both 3D and non-3D mkvs. Even 4K files which will not launch in a 3D resolution crash MPC instantly on going into full screen (if stereoscopic 3D is enabled in nvidia).

Another minor problem is that enabling 3D in OS doesn't enable nvidia's setting, so the madvr settings on auto enabling nvidia stereoscopic 3D is broken.

I have another PC with a gtx 1080 still on the old drivers (378.92) on which 3D works fine with madvr 0.92.1. Both PCs are on windows 10 creators update. My feeling is something has changed recently on the nvidia 3D drivers. I humbly request madshi to please look into this problem as madvr 3D is a great feature.

Thanks.
See above. My rig is similar to yours (see my sig below) and I have no crash, but I still have to use FSE for 3D otherwise I get 2D, even if the display switches to 1080p23FP and MadVR OSD reports D3D11 (3D). The picture definitely isn't 3D without FSE. With FSE, no crash, all perfect, and that's with the latest drivers.

[austinminton]

Thanks for your response. I too have the same batch file to enable and disable 3D in nvidia. I checked the registry entries and they were already enabled. Probably by the nvidia 3D wizard. I will try a full clean install next to see if that solves the issue. Not sure if this is relevant but I use my TV (Sony 75Z9D) to playback 3D.

Edit: I use FSE for playback but have tried both with and without FSE with the same crash.

[mitchmalibu]

Hmmm... So you're saying the custom mode seems to be effective for D3D11 FSE, only, but not for fullscreen windowed mode? How's non-fullscreen windowed mode? Would be nice if you could test all the variants and report which modes are effected by the custom mode and which are not. Please reboot the OS, just to be safe, before you do the tests. And it might make sense to make the custom mode extra weird, to get totally clear results. E.g. make it 23.700Hz instead of 23.976Hz, or something like that (if your display syncs to 23.700). Thanks!
Ok, I had some time to tinker around and here are my findings (I did a reset of madvr settings on a clean driver install with madvr custom mode enabled and optimized for 2160p23).

- D3D version isn't a factor in this issue, it happens the same way regardless of which version I'm choosing.
- Non fullscreen windowed behaves the same as fullscreen windowed .

However I did find something interesting regarding display modes. Here are the step to reproduce it on my setup :
- Windows is set @2160p60
- madvr is set up with the following options

support for automatic mode switching and revert to original mode on exit.
2160p23 mode is listed in madvr as an acceptable mode
FSE isn't enabled

- Open a 23.976 fps video file
- madvr switches to 2160p23 (it is shown as being the active mode in the custom modes tab)
- stats after things settled down (stats NOT coherent with the optimizations previously made with the custom modes feature) :

refresh rate : 23.97971hz
clock deviation : -0.00035%
Frame repeat every 4.4min

- while the movie is still playing, go into madvr settings and enable FSE
- there is a visible display mode change occuring.
- stats after things settled down (stats coherent with the optimizations previously made with the custom modes feature) :

refresh rate : 23.9569hz
clock deviation : -0.00035%
Frame drop every 1.1hr

- while the movie is still playing go into madvr settings and disable FSE
- stats after things settled down are identical to these obtained after enabling FSE, 2160p23 is still shown as being the active mode in the custom modes tab.
- Exit the media player, the display mode goes back to 2160p60
- Open the movie again, back to the 2160p23 unoptimized mode.

Side note : if I disable the revert to original mode on exit option and while I do not switch display mode while in 2160p23 optimized, I can reopen another 23p file and play it without a hitch.

So it seems I do have 2 competings 2160p23 modes on my setup : an unoptimized one that is called by the madvr switcher or the windows settings (I tried launching the file while being already in 2160p23, no difference), and the optimized one produced by madvr which is called upon entering FSE.

Regarding the 23.700Hz test, how would I go about trying this refresh rate ? Using the custom modes feature ?

Anyway, I hope my explanations were clear enough !

[austinminton]

It worked! I did a clean uninstall + reinstall of mpc-hc, madvr, lav filters and the nvidia drivers. Enabled stereoscopic 3D in nvidia which ran the wizard successfully. Enabled 3D in madvr and FSE. Opened 3D mkv and voila, TV switches to 3D and no crash! Thanks again for the responses, gave me the confidence it could be done and just something was wrong at my end. Not too sure what it was, but clean install did the trick.

Thanks again to madshi for this fantastic new release of madvr. Now we have full HDR + 3D support on the latest drivers.

[Manni]

Thanks for your response. I too have the same batch file to enable and disable 3D in nvidia. I checked the registry entries and they were already enabled. Probably by the nvidia 3D wizard. I will try a full clean install next to see if that solves the issue. Not sure if this is relevant but I use my TV (Sony 75Z9D) to playback 3D.

Edit: I use FSE for playback but have tried both with and without FSE with the same crash.

The main difference is I use MPC-BE, so you might want to try that. [EDIT: sorry didn't see your message above, glad it works for you too now]

[andybkma]

Just a heads up, pressing stop in Zoom Player with new mVR 92.1 causes Zoom Player to intermittenly crash. Previous version mVR 91.11 no such problem.

A user on the Zoom Player forum has also reported this problem but for him it was a secondary monitor. For me, it crashes on my one monitor (which is hooked up via HDMI to a laptop so perhaps it is also a secondary monitor). Cheers

[Manni]

This is the part I don't think works (at least on my system, a GPU directly connected to an LG OLED C7). My display needs metadata to enable HDR mode and how do you make sure the metadata is the same as what madVR sends?


This is why I said "or using an HD Fury device such as the Integral/Linker/Vertex". Any of these will allow you to force any display into HDR mode, even if you feed it SDR content.

Easier and cheaper to wait for the announced HDR support in MadTPG if that would be your only use for one of these :)

[jmonier]

It also consistently crashes for me when pressing stop in Zoomplayer. This happens on either monitor when there are 2 (or probably more) active. It does not happen when only 1 monitor is connected. The crash location is within madVR.

[QBhd]

Seems we now have a link with all these crash reports... multiple monitors. I too have a monitor and a TV active. I tried again last night and looked for any useful info on the crash, but alas Windows 10 only has a pop-up that says PotPlayer crashed and the program will close. The only link I see from the reports is multi-monitors, the applications are various (PotPlayer, Kodi, ZoomPlayer, MPC, etc etc)... I'm on Widows 10 and use D3D11 for presentation with FSE... I also use AMD's Custom Resolutions built into the Radeon Settings. What about the other people with these crashes? What other info?

QB

[oldpainlesskodi]

Seems we now have a link with all these crash reports... multiple monitors. I too have a monitor and a TV active. I tried again last night and looked for any useful info on the crash, but alas Windows 10 only has a pop-up that says PotPlayer crashed and the program will close. The only link I see from the reports is multi-monitors, the applications are various (PotPlayer, Kodi, ZoomPlayer, MPC, etc etc)... I'm on Widows 10 and use D3D11 for presentation with FSE... I also use AMD's Custom Resolutions built into the Radeon Settings. What about the other people with these crashes? What other info?

QB

Single display here (HDMI @ 4K)

K

[QBhd]

Single display here (HDMI @ 4K)

K

Are you using a laptop?

QB

[oldpainlesskodi]

Are you using a laptop?

QB

No, dedicated HTPC (Quad 4.2ghz, 16gb ram with a 1080 Strix) and a Samsung 4k display.

K

[jmonier]

More info: It crashes consistently when the single monitor is 1920x1080 via HDMI. It does NOT crash when the single monitor is 1600x1200 via VGA.

[QBhd]

Okay.... How about Custom Resolutions? Any of you guys and gals have those setup? FSE? D3D11 presentation? OS? AMD or NVidia? We're going to need to help madshi reproduce this, and not enough info is being supplied by most of us.

QB

[andybkma]

More info: It crashes consistently when the single monitor is 1920x1080 via HDMI. It does NOT crash when the single monitor is 1600x1200 via VGA.

This is exactly my set up (1080). Thanks

[aufkrawall]

Does anyone know a good way to watch YouTube videos with madVR without downloading them first and with working seeking?
MPC BC and 3DYD YouTube Source don't work well enough for high bitrate video.

[hannes69]

Okay.... How about Custom Resolutions? Any of you guys and gals have those setup? FSE? D3D11 presentation? OS? AMD or NVidia? We're going to need to help madshi reproduce this, and not enough info is being supplied by most of us.

QB

D3D11 FSE 8 bit, Windows 10 x64 current build, AMD R7 250 GPU.
I have implemented 5 custom resolutions for my TFT monitor and 5 custom resolutions for my projector according to common video frame rates and the valid refresh rate range for each device.
TFT: 50.000Hz, 59.940Hz, 60.000Hz, 71.928Hz, 72.000Hz
Projector: 47.952 Hz, 48.000 Hz, 50.000 Hz, 59.940 Hz, 60.000 Hz

Everything is working perfectly.
There were no problems to create the custom resolutions through madVR and no problems to optimize them.
My devices are very relaxed towards custom resolutions, so they "eat" nearly everything suggested by madVR´s optimization dialogue.

:cool::cool::cool:
:)

Does anyone know a good way to watch YouTube videos with madVR without downloading them first and with working seeking?
MPC BC and 3DYD YouTube Source don't work well enough for high bitrate video.
Maybe Kodi DSPlayer with a YouTube addon...

[el Filou]

Interesting information on the crashes that happen when stopping playback. On my system, it:

- never happens with MPC-HC (latest release version, configured to use external LAV Filters)
- happens with MediaPortal only when using LAV Splitter. I noticed that because playing .TS files didn't bring a crash, and MP always plays those files with its own source/splitter filter. When enabling an option to play TS files with 3rd-party system splitters, which uses LAV Splitter, TS files also crash when stopping playback.

Edit: I'm using latest LAV nightly (-40)

@madshi: would it be possible to add a "save bug report" option to madVR with instructions on how to send it manually? I don't have an email program installed on the HTPC (I remove everything that is not needed for media playback), and it gives an error when I click Finish to send the bug report. I'd like to send it using Gmail's web interface.

[imhh11]

Does anyone know a good way to watch YouTube videos with madVR without downloading them first and with working seeking?
MPC BC and 3DYD YouTube Source don't work well enough for high bitrate video.

Hi, it's working fine using MPC-BE/MADVR on my end.

It even works with HDR videos. HDR is triggered on my TV and PJ.
Seeking works too.
http://www.avsforum.com/forum/26-home-theater-computers/2913198-guide-how-play-youtube-hdr-pc.html

[aufkrawall]

I know that it supports that stuff, but that doesn't help me in any way.
Buffer/queue runs empty for 4k 60fps, which makes it totally useless for me.

Just gave Kodi a try with YT plugin, can only select 1080p 30fps as maximum resolution.
And I don't like that HTPC control concept for my PC (honestly, I don't like Kodi at all).