madVR - high quality video renderer (GPU assisted)

[QBhd]

I use PotPlayer and open the "share" URL from YouTube... I can even add the URL to a playlist... I do this weekly for Bill Maher's Overtime

QB

[aufkrawall]

Ty, but it also fails with 4k 60fps. :(

[mitchmalibu]

@madshi

Further informations :

The custom mode for 2160p23 is listed in the nvidia control panel as "3840 * 2160 @ 24Hz".
The only way to use this custom mode is to call it through the nvidia control panel (I have to check the checkbox in front of it to make it selectable). Using the standard Windows control panel or any third party tool (like display changer) just calls the standard modes.
Using 2160p24 in madvr available modes won't call the custom mode either (it just uses the standard 24Hz mode, not the optimized 23.XXX one).


Surprised I'm the only one reporting that kind of issue :o

[cork_OS]

Does anyone know a good way to watch YouTube videos with madVR without downloading them first and with working seeking?

SVPtube+mpv?

[madshi]

Oh, really? Can you link the driver you used?
I don't actually know, haven't touched it in ages, probably rather old. I don't think the version matters much.

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.
Does it list correctly in madVR's "display modes" tab? And does the OS still list 23 and 24?

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

chroma upscaling thing recommended to have a good video?
Huh? Not sure what you mean.

What version madVR can I use with my graphics card?
Always the newest, of course.

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.
The hard-coded threshold is exactly 10 minutes. Furthermore, it starts measuring only after 5 seconds or so. So you need to let it run for at least 10 minutes 10 seconds or so.

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.
That's quite surprising! Both my LCD computer monitor and my Sony 4K TV accept virtually anything I throw at them. And at some point I did a very quick test with my X35 and changing some timing parameter manually worked just fine, too. Maybe I need to improve my "compatability rating" somehow, I'm not sure. Or could it be possible that your AVR doesn't like custom modes? Could you try without the AVR, just as a test?

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.
Ok.

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.
There's only 2 options: Either I call the Nvidia APIs correctly or incorrectly. If I call the APIs correctly, then anything that goes wrong is the Nvidia driver's fault, and there will be nothing I can do about it. If I call the APIs incorrectly, then of course it's my bug can I can fix it. So the key question is if I've done something wrong or not.

Does the "custom modes" tab list the modes incorrectly, too, after you've created a custom timing?

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?
Smooth motion is for users whose TV can't do 23.976 (or 2 * 23.976 or 3 * 23.976). If your TV can do 3 * 23.976 = 71.928, then that's just fine and you don't need smooth motion, anymore! However, please also test if 71.928 actually runs smoothly, because the TV might accept 71.928 but internally convert it back to 60Hz.

Smooth motion off is always better than on, but only if your TV can (properly!) do 23.976, or an even multiply of it. 59.940Hz sucks for 23.976 content, because 59.940Hz is not an even multiply (59.940 / 23.976 = 2.5). So if you can only do 59.940, then you need smooth motion.

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.
There are 2 known issues where this happens: 1) Either if you have an AVR in between your HTPC and your display. Or 2) If you have profiles which include the "display modes" tab. Of course I'll try to fix this.

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 ?
It's a known driver issue. You can try to work around it by lowering the number of pre-presented frames in the madVR settings. There's nothing I can do about this.

For testing Full SBS HEVC 10 bit video: [...]
Thanks, downloaded and added to samples folder for future use.

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.
Good find, thanks!

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...
Testing only needs to be done once for each frame rate. It's not *such* a big deal, IMHO. Of course you can always use 60Hz and enable smooth motion, if you're too lazy to create custom resolutions for all needed frame rates.

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.
Unfortunately that's an issue with the current Nvidia drivers. I've reported it, and hope to get it fixed soon. But it's out of my hands, so I can't promise anything.

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)…

[...]

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.
The fix I made was not specific to win10, it should work on all OSs. So there's not really much I can do about this right now. It's definitely a driver issue, but my fix is supposed to help, at least it did for me.

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.
D3D11VA and new HDR default setting work like a charm here for SDR output, both performance and visuals are great. Very impressive, thanks.
:)

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've no idea, I haven't used ReClock for many years now.

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.
Known problem, to be fixed soon.

I also am seeing crashes with NNEDI set as chroma upscaler. Do you still need more crash reports for this?
Yes. Not sure why anybody still uses NNEDI3 for chroma upscaling, though. I'd suggest NGU-AA "low" quality instead.

Seems that custom mode tab disappears once a Profile is created.
Good to know, 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.
So it seems the custom mode is only effective in FSE mode? Or is it the other way round, and the custom mode is only effective in windowed mode? Are you 100% sure which is which?

Regarding the 23.700Hz test, how would I go about trying this refresh rate ? Using the custom modes feature ?
Yes, click on the custom mode, then on "edit", then change the pixel clock so you get a significantly different refresh rate (but still one your monitor/TV accepts). If you e.g. use 23.700Hz, then you can say for 100% sure if the custom mode is active either in windowed mode or FSE mode or both.

: 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.
I suppose I can add a "save bug report" button.

[madshi]

Further informations :

The custom mode for 2160p23 is listed in the nvidia control panel as "3840 * 2160 @ 24Hz".
The only way to use this custom mode is to call it through the nvidia control panel (I have to check the checkbox in front of it to make it selectable). Using the standard Windows control panel or any third party tool (like display changer) just calls the standard modes.
Using 2160p24 in madvr available modes won't call the custom mode either (it just uses the standard 24Hz mode, not the optimized 23.XXX one).


Surprised I'm the only one reporting that kind of issue :o
I'm currently not able to create *any* custom modes for standard refresh rates with my Nvidia driver. So I can't reproduce it here.

Your explanations leave me a bit confused. Can you make screenshots of the "display modes" tab, and tell me which refresh rates the OS offers you to switch to? And maybe also make a screenshot of the Nvidia control panel? Then maybe I understand better what happens.

And how does this new post of yours match together with your old? They somehow seem to contradict each other, because the old post seems to say that the custom mode is effective in FSE mode but not in windowed mode, but the new post seems to suggest that the custom mode is only effective if you activate it through the Nvidia control panel.

[madshi]

Those of you who have crash problems with v0.92.1, can you please try this test build?

http://madshi.net/madVR0921b.rar

Does this fix the issue for you?

[Neo-XP]

Does this fix the issue for you?

No crash for me with this one (I had crashes with v0.92.1).

:thanks:

[Siso]

Testing only needs to be done once for each frame rate. It's not *such* a big deal, IMHO. Of course you can always use 60Hz and enable smooth motion, if you're too lazy to create custom resolutions for all needed frame rates.

I'm not lazy at all, I was just writing my opinion, on a side note, does madvr has to be completely closed for the "optimize" function? Cause when I tested it, it doesn't gave me good results at all, it was open in the taskbar, also it doesn't recognize my added refresh rate with cru 1.3. Only when I untick "show native res modes, only" it is showed.

[Asmodian]

I'm currently not able to create *any* custom modes for standard refresh rates with my Nvidia driver. So I can't reproduce it here.

Your explanations leave me a bit confused. Can you make screenshots of the "display modes" tab, and tell me which refresh rates the OS offers you to switch to? And maybe also make a screenshot of the Nvidia control panel? Then maybe I understand better what happens.

The custom modes work well for me with Nvidia's current driver (385.28). madVR has to switch to it once using display modes, entered there as 2160p23, before it shows up but after that it is in Nvidia's control panel, albeit as a custom 24Hz mode.

Sorry for the large image:
http://i1222.photobucket.com/albums/dd496/asmodian3/madVR%20Custom%2023Hz_zps6uex7etu.png (http://s1222.photobucket.com/user/asmodian3/media/madVR%20Custom%2023Hz_zps6uex7etu.png.html)

No issues for me, the name of the custom mode is slightly odd but it all works as expected. :)

If I change the back porch at all, even with "test mode", this TV will turn off the input and not turn it on again until I unplug it and plug it back in.

Edit: Here is how it looks in Nvidia's custom resolution tool:
http://i1222.photobucket.com/albums/dd496/asmodian3/Custom%20Editor_zpsdvlbizqd.png

[el Filou]

I confirm no more crashes for me with build 0.92.1b !:)

Noted for NNEDI, I will try NGU.

[aufkrawall]

SVPtube+mpv?
With mpv you can just use youtube-dl very easily (and this doesn't have buffer problems), but I want to use madVR. ;)

[j82k]

Does it list correctly in madVR's "display modes" tab? And does the OS still list 23 and 24?

Nevermind, this must be a nvidia bug. Win 10 still lists both the modified 23Hz mode and the original 24Hz mode and both work fine.
So it's only fucked in the nvidia control panel.


Need a crash report text file.

It pretty much crashes every time when I move MPC-HC from my main monitor to my TV screen while a video is playing. It doesn't crash when pausing the video before dragging it over, so not really a big deal but it would still be nice if it could be fixed.

Crash report attached.

[mitchmalibu]

Sorry for not being clear enough. I'll try to be as precise as possible in my next answers.

So it seems the custom mode is only effective in FSE mode? Or is it the other way round, and the custom mode is only effective in windowed mode? Are you 100% sure which is which

What it boils down to is that when FSE activates, it calls the custom mode. Then, while the file is playing, I am able to use that custom mode in non-fullscreen windowed or fullscreen windowed (if I disable FSE in the settings).
I am 100% sure that the mode summoned by FSE is the custom one (vastly improved frame drop frequency).

I'm currently not able to create *any* custom modes for standard refresh rates with my Nvidia driver. So I can't reproduce it here.

Your explanations leave me a bit confused. Can you make screenshots of the "display modes" tab, and tell me which refresh rates the OS offers you to switch to? And maybe also make a screenshot of the Nvidia control panel? Then maybe I understand better what happens.

And how does this new post of yours match together with your old? They somehow seem to contradict each other, because the old post seems to say that the custom mode is effective in FSE mode but not in windowed mode, but the new post seems to suggest that the custom mode is only effective if you activate it through the Nvidia control panel.

Here are the screenshots :

https://thumb.ibb.co/fedjnQ/nvidiacpl.png (https://ibb.co/fedjnQ)https://thumb.ibb.co/dqqx7Q/customres.png (https://ibb.co/dqqx7Q)https://thumb.ibb.co/kTAx7Q/madvrcm.png (https://ibb.co/kTAx7Q)https://thumb.ibb.co/gjDvu5/madvrdm.png (https://ibb.co/gjDvu5)

The custom modes in the nvidia control panel were created by madvr. Once I check the checkbox in front of them, they are available to select through the nvidia selection box, in the custom section. So if I changed the display using the nvidia control panel to that custom mode and launch a 23p file without triggering a display mode change, it is correctly using the new custom mode. Otherwise, switching to 23p either by using the standard windows display settings or using the madvr display mode switcher uses the standard 23p mode.

So my two posts aren't contradictory, but complementary : the first one gives an example of how I was able to trigger the custom mode using the FSE trick (without fiddling in the nvidia cpl), and the second one shows that I can directly summon the same custom mode through the nvidia cpl, but that the same custom mode won't be called by the windows display settings or madvr display mode switcher. So I am able to use the custom mode, but not without using roundabout ways each time.

(This is really a b***h to explain :D)

[jmonier]

Those of you who have crash problems with v0.92.1, can you please try this test build?

http://madshi.net/madVR0921b.rar

Does this fix the issue for you?

Seems to fix it for me.

Also the "Display Modes" now only appears once rather than twice on the display connected to the AVR (but "Custom Modes" still flashes on and off).

[mitchmalibu]

The custom modes work well for me with Nvidia's current driver (385.28). madVR has to switch to it once using display modes, entered there as 2160p23, before it shows up but after that it is in Nvidia's control panel, albeit as a custom 24Hz mode.

No issues for me, the name of the custom mode is slightly odd but it all works as expected. :)

Are you using FSE ? Does the custom mode correctly applies when using fullscreen windowed ?

[Prinz]

madVR0921b.rar fixes my crash.

But the D11 FSE is only (8 bit) since 0.92.x .... with 0.91.11 it's (10 bit) in OSD

[jmonier]

In testing a resolution on my secondary monitor, the secondary monitor becomes the main monitor and the original main monitor is disconnected (leaving me with one working monitor). I have to go back to "Screen Resolution" and extend the desktop to the other (disconnected) monitor to fix it.

[Asmodian]

Are you using FSE ? Does the custom mode correctly applies when using fullscreen windowed ?

The custom mode correctly applies when using windowed, fullscreen windowed, or FSE. I didn't do anything in Nvidia's control panel, I do not check the box for the custom mode and just let madVR change to it.

But the D11 FSE is only (8 bit) since 0.92.x .... with 0.91.11 it's (10 bit) in OSD

It is 10-bit for me if I set my display to 10 bit.

[Xaurus]

The custom mode correctly applies when using windowed, fullscreen windowed, or FSE. I didn't do anything in Nvidia's control panel, I do not check the box for the custom mode and just let madVR change to it.



It is 10-bit for me if I set my display to 10 bit.
How can I set Nvidia control panel to output 10 bit?

I only have 8 bit there, using full range RGB. The LG 4K is a 10 bit native panel as far as I know.

[madshi]

does madvr has to be completely closed for the "optimize" function? Cause when I tested it, it doesn't gave me good results at all, it was open in the taskbar
The optimize function should have shown you a message box with the text that you need to reboot, or disconnect the display, or press the "reset gpu" button.

also it doesn't recognize my added refresh rate with cru 1.3. Only when I untick "show native res modes, only" it is showed.
Are you sure that those added refresh rates have exactly the same resolution as the native resolution? I highly doubt it. That would be a rather weird bug in madVR.

The custom modes work well for me with Nvidia's current driver (385.28). madVR has to switch to it once using display modes, entered there as 2160p23, before it shows up but after that it is in Nvidia's control panel, albeit as a custom 24Hz mode.

No issues for me, the name of the custom mode is slightly odd but it all works as expected. :)
It's strange that Nvidia lists it as 24Hz!

If I change the back porch at all, even with "test mode", this TV will turn off the input and not turn it on again until I unplug it and plug it back in.
That's sad to hear. Your TV seems to be very picky. What model is that? It should at least accept changes to the pixel clock, right? Does it dislike both horizontal and vertical back porch changes, or is just one of those problematic? What happens if you change front porch or sync width?

Nevermind, this must be a nvidia bug. Win 10 still lists both the modified 23Hz mode and the original 24Hz mode and both work fine.
So it's only fucked in the nvidia control panel.
Interesting! What happens if you also add an optimized 24Hz custom mode? Does the Nvidia control panel then show both 23Hz and 24Hz again?

It pretty much crashes every time when I move MPC-HC from my main monitor to my TV screen while a video is playing. It doesn't crash when pausing the video before dragging it over, so not really a big deal but it would still be nice if it could be fixed.

Crash report attached.
Unfortunately attachments to this forum take ages to get approved (if they get approved at all). Please upload the crash report somewhere else and link here. Thanks.

What it boils down to is that when FSE activates, it calls the custom mode. Then, while the file is playing, I am able to use that custom mode in non-fullscreen windowed or fullscreen windowed (if I disable FSE in the settings).
I am 100% sure that the mode summoned by FSE is the custom one (vastly improved frame drop frequency).

[...] if I changed the display using the nvidia control panel to that custom mode and launch a 23p file without triggering a display mode change, it is correctly using the new custom mode. Otherwise, switching to 23p either by using the standard windows display settings or using the madvr display mode switcher uses the standard 23p mode.

So my two posts aren't contradictory, but complementary : the first one gives an example of how I was able to trigger the custom mode using the FSE trick (without fiddling in the nvidia cpl), and the second one shows that I can directly summon the same custom mode through the nvidia cpl, but that the same custom mode won't be called by the windows display settings or madvr display mode switcher.
Ok, got it! Very weird, though. Did you try to reboot the OS? Doesn't help?

madVR0921b.rar fixes my crash.

But the D11 FSE is only (8 bit) since 0.92.x .... with 0.91.11 it's (10 bit) in OSD
Glad to hear the crash is fixed.

The 8bit problem was also reported by another user to me via email, but I can't seem to be able to reproduce it on my PC. Can you maybe try to find out if it's caused by any specific madVR settings? Or maybe it happens with some videos but not all or something like that?

In testing a resolution on my secondary monitor, the secondary monitor becomes the main monitor and the original main monitor is disconnected (leaving me with one working monitor). I have to go back to "Screen Resolution" and extend the desktop to the other (disconnected) monitor to fix it.
I suppose this happens after you pressed "reset gpu"? Or did it happen even without that? It's probably not something I can do anything about.

The custom mode correctly applies when using windowed, fullscreen windowed, or FSE. I didn't do anything in Nvidia's control panel, I do not check the box for the custom mode and just let madVR change to it.
You're lucky then. For most other nvidia users it seems that some refresh rates are rejected, while some may work.

How can I set Nvidia control panel to output 10 bit?

I only have 8 bit there, using full range RGB. The LG 4K is a 10 bit native panel as far as I know.
You need to activate D3D11 presentation in madVR, and in the display properties in madVR set your display to 10bit.

[Xaurus]

You need to activate D3D11 presentation in madVR, and in the display properties in madVR set your display to 10bit.
Thanks madshi but won't that just be compressed then when the image is leaving the graphics card by the Nvidia setting of 8 bit? I thought it was necessary to set the output correctly as well.

[huhn]

there are limitations with HDMI.

for 60 hz RGB you have "only" 8 bit for example.

[mitchmalibu]

The custom mode correctly applies when using windowed, fullscreen windowed, or FSE. I didn't do anything in Nvidia's control panel, I do not check the box for the custom mode and just let madVR change to it.

Ok, got it! Very weird, though. Did you try to reboot the OS? Doesn't help?

I did reboot a few times inbetween tests, nothing changed. Given that Asmodian has it working using an Nvidia setup, it may be a problem on my end. I did tinker with CRU a few months back and may have screwed up something OS wise. A fresh Windows install wouldn't hurt I guess :)

Anyway, with all the improvements made to windowed mode (10bit support) and DXVA11, using a 32bit player and reclock is still a viable option if you tolerate the audio resampling until I get to format (it now handles those pesky 60fps HDR demo clips without a hitch).

Thanks for your help !

Edit : as a side note, after adding the 23p custom mode through madvr, the nvidia cpl lists the mode under the custom section under "3840*2160, progressive, 24hz", but the 23hz remains in the "Ultra HD, HD, SD" section under "4k x 2k, 3840*2160, 23hz" (24hz is gone from the dropbox).

[dvd1]

madshi


If I use Spline AR in image upscaling, in chromatic upscaling which filter i can use, for best video quality 576i 50 frs to 1080p 50 frs.
Can I use the latest version of madVR, even with my small graphics card?
thank you so much

[FDisk80]

DXVA11 mode crashes when switching from 60hz to fullscreen 24hz (in fullscreen windowed 10-bit mode). With MPC-BE x64.
If I switch to 24hz before going fullscreen it does not crash.

[jmonier]

I suppose this happens after you pressed "reset gpu"? Or did it happen even without that? It's probably not something I can do anything about.

It happens just when I hit "Test" even on a standard mode at the very beginning of the process. Nothing to do with "reset gpu".

I suppose that I can set up the custom resolutions while working with a single monitor and then go back to the dual monitor afterwards, but that seems unwieldy. I'm still at the beginning of the learning curve, though.

[Prinz]

Glad to hear the crash is fixed.

The 8bit problem was also reported by another user to me via email, but I can't seem to be able to reproduce it on my PC. Can you maybe try to find out if it's caused by any specific madVR settings? Or maybe it happens with some videos but not all or something like that?

I tried a lot of files all are 8 bit now in FSE. Nothing changed in settings, I don't use the new custom resolutions (i have no need for them). Display is set to be 10bit in madvr. Switching back to 0.91.11 and everything is back to 10 bit.

It's again the secondary monitor set to: 1080p23, 1080p50, 1080p59 (removing the values doesn't help) via hdmi through AVR to TV with Nvidia 1060.

[vanschneidermann]

Facing crashs with MPC-HC and MPC-BE.
Opening any mkv file, on the first display (120Hz BenQ) and then going to fullscreen (which automatically open the video on the second display (LG LED TV @ HDMI 60Hz) both MPCs crash.

I have to open any of the MPC,have to drag the file to the second display, then go to fullscreen, then drag the file to there. That way I dont face crash.

Sorry about my English :x

Using GTX 1070 (driver 382.53)
Windows 10 LTSB x64
Last versions of MPC-BR and MPC-HC
LAV Nightly
Last version madvr


Well, it looks like that D3D11, at Lav Video Decoder (Nightly) the culprit.

Is that hardware related, driver ?
What s the benefits of using D3D11 instead of copyback ?

[AngelGraves13]

Those of you who have crash problems with v0.92.1, can you please try this test build?

http://madshi.net/madVR0921b.rar

Does this fix the issue for you?

Worked fine for a bit, but now says "madvrsettings32" corrupt and and error code 216 and madvr crash in an endless loop.

Went back to 0.92.1 and it's working ok again, minus the random crashes.

UPDATE: Deleted settings and uninstalled and installed 0.92.1 and then 0.92.1b and it seems ok. Don't know why it was crashing like that. Hope it doesn't pop up again.

[el Filou]

there are limitations with HDMI.
for 60 hz RGB you have "only" 8 bit for example.Gee, I discovered thanks to your response that my graphics card was actually outputting 12 bit RGB when set to 23/24 Hz. :eek:
Is there any advantage in quality to do that with a GT60 and would it benefit madVR? Panasonic says it has "24576 steps of gradation", which from the way they calculate that number supposedly equals 13 bit, but I have a hard time believing that. :confused:

madshiIf I use Spline AR in image upscaling, in chromatic upscaling which filter i can use, for best video quality 576i 50 frs to 1080p 50 frs. Can I use the latest version of madVR, even with my small graphics card? thank you so muchIt's not possible for anybody else to tell you what settings can be used with your specific combination of software+hardware+content, you have to test to find it out.
Yes, it's always best to use the latest version whatever the hardware as long as it meets the minimum requirements (= GPU with D3D9, which your GT730 does).
Luma is more important than chroma, so always use a better upscaling method for luma. Try successively better ones until you see that your GPU is dropping frames and then back down one level.

[x7007]

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.

How does it work for you ? I tried clean installation and it doesn't work. since driver 384.xx it didn't work, 382.xx works fine. did you also install 3DTV ? or just the 3Dvision that comes with nvidia drivers ?

[cork_OS]

Before madVR i've used CRU to create custom display modes, but mode switching in madVR didn't work properly. After 0.92 release i've realised that my WQHD display EDID data is somehow corrupted and madVR shows that it's native resolution is 1920x1080. I did reset display modes back to default with CRU "reset-all" tool and now madVR can create and switch custom display modes!

[austinminton]

How does it work for you ? I tried clean installation and it doesn't work. since driver 384.xx it didn't work, 382.xx works fine. did you also install 3DTV ? or just the 3Dvision that comes with nvidia drivers ?

Just the basic 3D drivers that come with nvidia. I went straight from 378.92 to 385.28 and things are working fine for me. This is the software i reinstalled during the clean installation

nvidia drivers 385.28
MPC-HC (x64) 1.7.13
madvr 0.92.1
lav 0.70.2

I am on windows 10 Pro 1703 (x64) with the latest aug update.

Please note that only 3D files work when I enable stereoscopic 3D in nvidia. I get a crash for any 2D file. Its not really a problem as I use a batch file to enable 3D, play the 3d file and then disable 3D.

[Siso]

The optimize function should have shown you a message box with the text that you need to reboot, or disconnect the display, or press the "reset gpu" button.


Are you sure that those added refresh rates have exactly the same resolution as the native resolution? I highly doubt it. That would be a rather weird bug in madVR.

The custom refresh rate I added in cru 1.3 was 72 hz with "automatic lcd standart". Also when the optimize message was shown, in madvr it was 1 frame repeat every 1 hour but in optimized timings it was 40 sec...

[Ava Pug]

So far I've only been testing 23p custom resolutions.

My setup is:
sony 1080p tv
nvidia 1070, 385.28 driver
mpc-hc 1.7.13.89
madvr 0.92.1
lav 0.70.2
windows 10 pro

I've found that my custom resolution works only if I have FSE enabled.

FSE On, DX11 Off -> fullscreen ok, -> windowed ok
FSE On, DX11 On, -> fullscreen ok -> windowed defaults to nvidia profile
FSE Off, DX11 Off -> fullscreen defaults to nvidia -> windowed defaults to nvidia profile

[oldpainlesskodi]

Those of you who have crash problems with v0.92.1, can you please try this test build?

http://madshi.net/madVR0921b.rar

Does this fix the issue for you?

Fixed it for me using dsplayer.

Thanks Madshi.

K

Update - after testing further, I have to say, with the patch and the latest release, this is the most rock solid stable and best release so far! well done (I always use FSE Exclusive)

[madshi]

Thanks madshi but won't that just be compressed then when the image is leaving the graphics card by the Nvidia setting of 8 bit? I thought it was necessary to set the output correctly as well.
The Nvidia setting has multiple different settings, I think. If you force it to 8bit then probably the Nvidia driver downconvert madVR's 10bit output to 8bit, which is bad. So if you want madVR to output 10bit, it would make sense to not force the output to be 8bit in the Nvidia GPU driver, of course. I think you can just let the driver decide the output bitdepth. Or if you have to override/force it to a specific bitdepth, for some reason, then for 10bit output to reach the display, you need to use 10bit (which I think is not available) or 12bit.

I did reboot a few times inbetween tests, nothing changed. Given that Asmodian has it working using an Nvidia setup, it may be a problem on my end. I did tinker with CRU a few months back and may have screwed up something OS wise. A fresh Windows install wouldn't hurt I guess :)
Maybe the CRU "reset all" helps?

If I use Spline AR in image upscaling, in chromatic upscaling which filter i can use, for best video quality 576i 50 frs to 1080p 50 frs.
Luma/image is much more important than chroma. But if you can't use anything better than Spline AR for luma, you can try if Bicubic works for chroma. But it's not a dramatic problem if Bilinear is all you can use for chroma.

Can I use the latest version of madVR, even with my small graphics card?
Newer madVR versions aren't slower than older versions. So you should always use the latest madVR version.

It happens just when I hit "Test" even on a standard mode at the very beginning of the process. Nothing to do with "reset gpu".
Ah ok. Well, there's nothing I can do about that. That's just what the Nvidia driver seems to be doing on your PC, for some reason.

I tried a lot of files all are 8 bit now in FSE. Nothing changed in settings, I don't use the new custom resolutions (i have no need for them). Display is set to be 10bit in madvr. Switching back to 0.91.11 and everything is back to 10 bit.

It's again the secondary monitor set to: 1080p23, 1080p50, 1080p59 (removing the values doesn't help) via hdmi through AVR to TV with Nvidia 1060.
Strange, I can't reproduce this here... :(

Worked fine for a bit, but now says "madvrsettings32" corrupt and and error code 216 and madvr crash in an endless loop.
That sounds like some of the files really were damaged somehow. I'd recommend to run a scandisk on your harddrive, just to be safe.

Gee, I discovered thanks to your response that my graphics card was actually outputting 12 bit RGB when set to 23/24 Hz. :eek:
Is there any advantage in quality to do that with a GT60 and would it benefit madVR? Panasonic says it has "24576 steps of gradation", which from the way they calculate that number supposedly equals 13 bit, but I have a hard time believing that. :confused:
How do you get from 24576 steps of gradation to 13bit? 2^13 = 8192. I'm not sure what Panasonic is trying to say with 24576 steps, to be honest. It doesn't make a lot of sense to me.

Before madVR i've used CRU to create custom display modes, but mode switching in madVR didn't work properly. After 0.92 release i've realised that my WQHD display EDID data is somehow corrupted and madVR shows that it's native resolution is 1920x1080. I did reset display modes back to default with CRU "reset-all" tool and now madVR can create and switch custom display modes!
Interesting, I tried "reset-all", but it didn't help for me. The NVidia driver still refuses to override any 2160p modes with my 4K Sony TV, for whatever reason.

So far I've only been testing 23p custom resolutions.

I've found that my custom resolution works only if I have FSE enabled.

FSE On, DX11 Off -> fullscreen ok, -> windowed ok
FSE On, DX11 On, -> fullscreen ok -> windowed defaults to nvidia profile
FSE Off, DX11 Off -> fullscreen defaults to nvidia -> windowed defaults to nvidia profile
Very weird!!

DXVA11 mode crashes when switching from 60hz to fullscreen 24hz (in fullscreen windowed 10-bit mode). With MPC-BE x64.
If I switch to 24hz before going fullscreen it does not crash.
Facing crashs with MPC-HC and MPC-BE.
Have you tried the test build?

http://madshi.net/madVR0921b.rar

[FDisk80]

Have you tried the test build?

http://madshi.net/madVR0921b.rar

I did, same crash.
Also If I switch to full screen exclusive it doesn't crash.
That way it switches from 60hz to 24hz without a problem.



DXVA2CB, fullscreen windowed 10-bit, going full screen from 60hz to 24hz = no crash
DXVA2CB, fullscreen exclusive 10-bit, going full screen from 60hz to 24hz = no crash
DXVA11, fullscreen exclusive 10-bit, going full screen from 60hz to 24hz = no crash
DXVA11, fullscreen windowed 10-bit, going full screen from 60hz to 24hz = crash
DXVA11, fullscreen windowed 10-bit, going full screen from 60hz to 60hz = no crash
DXVA11, fullscreen windowed 10-bit, going full screen from 24hz to 24hz = no crash


Tested with Windows 10 and MPC-BE x64 all latest nightlies.

[madshi]

Need a crash report, then.

[FDisk80]

Need a crash report, then.

Where is the log saved?
It actually asked me to send a report but I don't have any email client installed and there is no save log option, at least I didn't find one.

[madshi]

Press "show bug report", then Ctrl+C to copy the bug report to your clipboard.

[FDisk80]

Press "show bug report", then Ctrl+C to copy the bug report to your clipboard.

Aha, ok. Will do that when I get home.

[nevcairiel]

How do you get from 24576 steps of gradation to 13bit? 2^13 = 8192. I'm not sure what Panasonic is trying to say with 24576 steps, to be honest. It doesn't make a lot of sense to me.


Colored steps in RGB? 24576 is suspiciously 3x 8192.

[takenori]

so im curious, ive got a single gtx card, is it applicable doing SLI with madvr and gains more, at -least twice the performance?

[nevcairiel]

so im curious, ive got a single gtx card, is it applicable doing SLI with madvr and gains more, at -least twice the performance?

No. SLI does not benefit madVR at all.

[mitchmalibu]

So far I've only been testing 23p custom resolutions.
...

I've found that my custom resolution works only if I have FSE enabled.
...

Did you by any chance use CRU previously to try to make custom resolution ? I'm encountering the same exact behaviour.

Maybe the CRU "reset all" helps?

I did use "reset all" and made a fresh driver install after I stopped using CRU and reverted back to Reclock. But I think somehow something got screwed up OS wise: as cork_OS mentionned, I think it did something to the way the EDID of my TV setup is read, only "reset all" didn't work for me. After using CRU, the native resolution for my AVR / TV was 1080p whereas beforehand it was 2160p. I frankly don't want to make you lose time over this until I do a fresh Windows install to be sure.

[Ava Pug]

Did you by any chance use CRU previously to try to make custom resolution ? I'm encountering the same exact behaviour.

No I've never used CRU. I've only tried doing a custom resolution through the nvidia control panel once but I always do a "clean install" when I update drivers.

[j82k]

Interesting! What happens if you also add an optimized 24Hz custom mode? Does the Nvidia control panel then show both 23Hz and 24Hz again?

Ok I have created an optimized 23 and 24 Hz mode using madVR now. Using Win 10 Display Adapter Properties both are listed and I can switch between both just fine.

The Nvidia control panel shows the original 23Hz mode and a custom 24Hz mode. But both result in switching to the optimized 23.976 Hz mode. No way to get 24Hz from nvidia control panel.

This is what it looks like:
http://imgur.com/a/b5mI8


Unfortunately attachments to this forum take ages to get approved (if they get approved at all). Please upload the crash report somewhere else and link here. Thanks.


https://pastebin.com/P5yCW0dM

[AngelGraves13]

Another bug I've found is if I skip to different part of the file I'm playing either with chapters or the timeline and pause it immediately before the queues fill it, and attempt to play it, it'll stop responding and I have to close the media player with Task Manager. Sometimes I'll be playing a file and accidentally pause it after skipping to a chapter and then it will no longer play.

Let me know if you need more info.