madVR - high quality video renderer (GPU assisted)

[Manni]

@Madshi:

One idea: is there any way to have MadVR reporting SDR BT2020 in the HDMI stream when doing a conversion? If that was the case, it would allow the Vertex to pick it up and select the correct baseline/calibration in the PJ, without having to deal with profiles/batch files. This is what happens for example if I set the UB900 to do the HDR to SDR conversion, SDR BT2020 is detected and the correct calibration is called. If we can also apply MadVR's 3D LUT, all the issues are solved in one go, at least for Vertex users. Thanks!

[-Hitman-]

Uh, that's weird! And is the raw data of all those identifications identical? Try deleting *all* of them. Does that stop the madness?

Yes all the data under each ident is exact and reports the denon avr everytime.

I do recall this also happening with my old intel 6700 machine and had to revert back to the version of madvr that worked to resolve it, possibly the madvr version that had just got HDR first added, worked fine.

I may have already tried to delete the idents with the old machine to try and get it working and tried again but still everytime my denon/tv display is used a new ident appeared everytime.

I'll try to delete them again tonight on this machine and report back.

Also i might add that the Dell display is on a displayport to hdmi dongle, whether this is attributing to this issue?

I need to use the convertor as i only have 1 display port and 1 hdmi.

Thanks.

[Cinemancave]

I just wanted to say "well done!", the result is significantly better than what I've been able to get with any custom curves, especially regarding saturation in shadow detail and highlights.


I have a similar setup with an X7000 and Vertex in the chain. So are you saying that it's better to let MadVR do the HDR-to-SDR conversion for all regular UHD HDR-content and then applying a BT2020 SDR-config in the JVC instead of using one of the custom curves created by Arves tool, for us JVC owners? Should I use MadVR regular settings for the conversion or modify it in any way?

[mclingo]

Silly question time?: for those with crappy GPU's, is there any way the rendering load can be shared between the GPU and the CPU, currently when playing a movie My GPU is running at 90% and my i7 CPU below 10%

[Siso]

@madshi

In a case where the EDID of the monitor is not detected correctly pic ---> http://imgbox.com/0Ba1cnK7 is it ok if I manually choose 8 bit which is my monitor's depth, "auto" seems odd to me?

[LUCi5R]

OK, so GT 1030 does have the VP9 decoder but no profile 2...I'll live without the latter...thx guyz

P.S. just found this screenshot posted way earlier on this forum: http://jpegshare.net/d2/3a/d23a630cf160163c5057946f6df5056c.jpg.html

seem like profile 2 is covered as well...seems like quite a little beast

Hi there,

I was reading some of your posts and I was wondering if you could help. I've come across posts & people who had difficulty playing back 2160p media using MadVR/MPC-BE combo with a GT 1030 GPU, and then I've come across others who are able to achieve flawless playback using the same.

I don't believe GT 1030 is "incapable" of UHD HDR (2160p) playback using MadVR/MPC-BE otherwise no one would be able to; but there is some golden settings that achieve this.

Unfortunately I'm experiencing terrible lag/frame rate issue where media is practically unplayable/unwatchable.

I'm not doing any upscaling / downscaling, but simple 1:1 2160p playback of UHD HDR media on a 4K HDR display.

The HTPC has an i5-2600K CPU OC'd to 4Ghz, 8GB DDR4 RAM, and GT 1030 GPU.

Is it possible for you to share your MadVR settings or any advice you can offer?

Thanks!

[Clammerz]

is there any way the rendering load can be shared between the GPU and the CPU
No, as that would defeat the purpose of using the hardware that's built for graphical number crunching. Your GPU is leagues ahead of what your CPU can do with graphics.

A user has posted how to do it in Python in the JVC thread, but I don't know how to call a python script from a batch file.
python <filename>.py
Of if you can't use a physical file for some reason:
python -c "<insert code here>"
(You'll need to escape or use different quote style in the code)

[clsid]

Hmmmm... Interesting idea. What is the motivation for such a new option? Wouldn't you get the same result by creating a simple profile based on video resolution (e.g. disable RCA for 4K content, but enable it for lower res content)?I would like to avoid using profiles just for something like this. There is a big performance difference between regular RCA and the integrated one, which is not something that is obvious to most users. I want to be able to switch to a different NGU variant without having to disable (integrated) RCA.

That should already be the case! The only exception is if you have a "?" device, in that case the settings dialog always jumps there, to motivate you to tell madVR which display type it is.You are right. But this is certainly not obvious. Perhaps you could a red warning text on that page that says something like "please select the correct device type".

[madshi]

Thanks, but isn't this assuming the SAME profile/calibration is used in the display for all the 3D LUTs? As I can't do this, I have to use the custom profile external command to enable the correct calibration in the display, so that I can have iris open / high lamp / filter for HDR (SDR BT 2020) and iris closed / low lamp / no filter for SDR, correct?
I'm not sure I understand your problems with the madVR settings. Please expect everything to work just the way you'd want it to, and then you probably understood how it works.

Usually, HDR content is BT.2020, and SDR content is BT.709. So it should be easy for you to create a conventional SDR calibration 3DLUT for BT.709 SDR content, as you always did. For HDR content, you can switch your projector into a different mode, open the iris etc and then create a new calibration 3DLUT for that, based on madVR's HDR -> SDR pixel shader math. You would do that by creating an *SDR* calibration 3DLUT for BT.2020 with Calman/LightSpace/ArgyllCMS, with the iris fully open etc. Of course the 3DLUT needs to be made for SDR, because madVR converts the HDR content to SDR before feeding it into the 3DLUT. This way the BT.709 3DLUT would be for iris closed and the BT.2020 3DLUT would be for iris open.

If you want to support SDR BT.2020 content, too, with closed iris, then even that is easily possible, as well. Just make 2 calibration profiles, one for open iris and one for closed iris, auto select the open iris for HDR content and the closed iris for SDR content, then create proper SDR calibration 3DLUT for BT.709 and BT.2020 with open *and* closed iris (so 4 overall) and place them in the right slots in those 2 profiles. Done. I'm not sure where you see the problems here?

is there any way to have MadVR reporting SDR BT2020 in the HDMI stream when doing a conversion?
The OS doesn't give me control over that. Maybe it would be possible with private GPU APIs, but I've not looked into that yet.

Also i might add that the Dell display is on a displayport to hdmi dongle, whether this is attributing to this issue?
I don't see why that would be an issue.

If the problem is still there after you deleted all the identification cards, could you try to find out which exact madVR build introduced the problem? You can download all older builds here:

http://www.videohelp.com/tools/madVR/old-versions#download

In a case where the EDID of the monitor is not detected correctly pic ---> http://imgbox.com/0Ba1cnK7 is it ok if I manually choose 8 bit which is my monitor's depth, "auto" seems odd to me?
I'm not sure why the detection fails, it should work. But anyway, of course you can manually choose whatever value you want. In a case like this "auto" should default to 8bit, anyway, though.

I was reading some of your posts and I was wondering if you could help. I've come across posts & people who had difficulty playing back 2160p media using MadVR/MPC-BE combo with a GT 1030 GPU, and then I've come across others who are able to achieve flawless playback using the same.

I don't believe GT 1030 is "incapable" of UHD HDR (2160p) playback using MadVR/MPC-BE otherwise no one would be able to; but there is some golden settings that achieve this.

Unfortunately I'm experiencing terrible lag/frame rate issue where media is practically unplayable/unwatchable.

I'm not doing any upscaling / downscaling, but simple 1:1 2160p playback of UHD HDR media on a 4K HDR display.

The HTPC has an i5-2600K CPU OC'd to 4Ghz, 8GB DDR4 RAM, and GT 1030 GPU.
First of all you need to get decoding right. Decoding HEVC is very demanding, so your CPU most likely won't be able to handle it. You need to let the GPU do that. So in LAV Video Decoder pick either DXVA Copyback, DXVA Native or (with a newer LAV Nightly build) D3D11 decoding. Then in madVR press Ctrl+J and check the decoder queue during playback. It should be nearly full during playback.

Once you've got the decoder sorted out, next is rendering. You could start by restoring madVR default settings, then activate all the "trade quality for performance" settings. If playback is already smooth that way, you can uncheck the "trade quality" options one by one, starting at the bottom, moving up, until playback starts to judder again.

I would like to avoid using profiles just for something like this. There is a big performance difference between regular RCA and the integrated one, which is not something that is obvious to most users. I want to be able to switch to a different NGU variant without having to disable (integrated) RCA.
I fully understand. For me a big problem is that there are a LOT of settings where I could add additional options to avoid the need to use profiles. But adding more and more options always makes things more complicated for the average user. Of course using profiles is even more complicated for the average user, though. So it's not easy to decide which options to add and which not.

Any opions about this anyone? Would it be a good idea to offer an "use RCA only if its comes for free" option?

You are right. But this is certainly not obvious. Perhaps you could a red warning text on that page that says something like "please select the correct device type".
Haha, maybe I should. I thought users experienced with the device manager (? devices are BAD) would know what to do... :p

[madshi]

Anybody interested in an XySubFilter bugfix for external SRT subtitles with italic text in them?

http://madshi.net/XySubFilter746SrtFix.zip

This is not tested well, and it's a totally unofficial build, so please use on your own risk. If you do decide to give it a try, let me know if the "move subtitles" option now works properly in all situations.

I've asked cyberbeing to create a new official XySubFilter build with my fix, but it'd be great if some users would test it first.

[clsid]

You could make it a tri-state checkbox. Semi-checked would be NGU only.

I don't usually customize any of the device settings, so I assumed leaving it at "unknown" would not have any negative effects and just use same defaults.

[brazen1]

Any opions about this anyone? Would it be a good idea to offer an "use RCA only if its comes for free" option?

I think so. Those with strong GPU's and a good understanding of the setting probably would prefer it left as a selectable option though otherwise they can't utilize the full potential of their GPU (unless the option would be included with ticking RCA on or off as it is now). Like a sub option under it. Ticking enable and then 'only for free' wouldn't be greyed out anymore.
On the other hand, those with weaker GPU's would be doing more harm than good so enabling your option 'only for free' is a no brainer imo. I have a weak GPU. I'd use it.

[LUCi5R]

First of all you need to get decoding right. Decoding HEVC is very demanding, so your CPU most likely won't be able to handle it. You need to let the GPU do that. So in LAV Video Decoder pick either DXVA Copyback, DXVA Native or (with a newer LAV Nightly build) D3D11 decoding. Then in madVR press Ctrl+J and check the decoder queue during playback. It should be nearly full during playback.

Once you've got the decoder sorted out, next is rendering. You could start by restoring madVR default settings, then activate all the "trade quality for performance" settings. If playback is already smooth that way, you can uncheck the "trade quality" options one by one, starting at the bottom, moving up, until playback starts to judder again.


Super thanks for the advice!! I'll go ahead & set this up and do some testing. Will reach back.

Thanks again.

[Neo-XP]

Any opions about this anyone? Would it be a good idea to offer an "use RCA only if its comes for free" option?

Yes, because right now it is very complicated for new users to know when RCA comes for free.

To quote you :


A few details about how RCA/NGU fusion works:
1) Both RCA and NGU can run on just the luma channel or just the chroma channels or both. madVR automatically runs a combined algo if your settings allow it. It's possible that only luma "RCA + NGU" will be fused, or only chroma, or both, depending on your settings.
2) Currently fused RCA+NGU is only supported for NGU Sharp, but not for NGU AA, NGU Standard or NGU Soft.
3) If you have a 4:2:0 or 4:2:2 source and you activate "NGU Sharp" for chroma upscaling, and if you also activate RCA + "process chroma channels, too", then the chroma RCA will run as part of the chroma NGU Sharp upscaling. But if you select any other chroma upscaler, there's no chance for a fused NGU Sharp + RCA, so in that case RCA will still be performed separately for the chroma channels, followed by the chroma upscaler you've selected.
4) If you activate "NGU Sharp" for Image Upscaling/Doubling, then RCA for luma will run as part of NGU Sharp. But if you select a different Image Upscaling algo, or if image upscaling isn't performed at all, then RCA will be run separately.
5) If you select RCA "medium" quality, NGU Sharp quality is automatically upgraded to at least "high" quality. If you select RCA "high" quality, NGU Sharp is automatically upgraded to "very high" quality. It should still be faster overall than separate RCA + NGU Sharp Low/Medium processing.

It would be a quick way to ensure that you will not have a massive drop in performances if you do not use profiles and know exactly all these conditions when RCA is enabled.

This new option would be useless of course for users who know all this, but useful to some others I guess.

[-Hitman-]

If the problem is still there after you deleted all the identification cards, could you try to find out which exact madVR build introduced the problem? You can download all older builds here:

http://www.videohelp.com/tools/madVR/old-versions#download


I tried deleting the entries, however active displays/entries cannot be deleted (Denon AVR hdmi remains active in standby), which left 2 entries under the Dell display /after deleting the inactive cards.

I pulled the plug on the Denon to remove it and then my dell monitor + correct dell edid was added as a new 2nd dell entry eg. Dell (1).

I then was able to delete the original dell entry (due to now being inactive) and renamed the Dell (1) back to Dell, so good so far.

Then I re-powered the Denon, it was detected but then a second entry appeared under the Dell display and contained the Dell edid etc..., no sign of the Denon edid or a separate display entry for it :/

See image of what I have now...

https://i.imgur.com/cNLDzeG.png

I will revert back to versions to try and find the version that causes this wired issue to re-appear as you suggest.

Thanks again.

[-Hitman-]

Update... @madshi

Ok, madvr works fine - version 0.91.11, two separate displays show with correct id/edid under each.

Dell U2413
Denon-AVRHD

Install next version up - V0.92.1 and only the Dell display is now present /with the Denon ID and edid under it.

Also with v0.92.1, the Dell display entry does not keep adding idents every time the Denon/tv is used, it just remains - Dell display with a single indent containing the Denon info+edid data.

[Manni]

python <filename>.py


Thanks, that's great.

@Madshi: thanks for the replies above, I think I have all I need to experiment. Creating the calibrations or the 3D LUTs isn't the issue, I'm used to doing that. I'll get back to you to report success or if I hit any problem trying to apply the correct calibration and correct 3D LUT.

[leeperry]

good idea to offer a "use rca only if it comes for free" option?
+1 :)

[amayra]

Does Madvr have Performance Impact after Meltdown, Spectre bug patch ?

[huhn]

it'S GPU based.
it's not a data center.

so no.

[mytbyte]

Hi there,

I was reading some of your posts and I was wondering if you could help. I've come across posts & people who had difficulty playing back 2160p media using MadVR/MPC-BE combo with a GT 1030 GPU, and then I've come across others who are able to achieve flawless playback using the same.

I don't believe GT 1030 is "incapable" of UHD HDR (2160p) playback using MadVR/MPC-BE otherwise no one would be able to; but there is some golden settings that achieve this.

Unfortunately I'm experiencing terrible lag/frame rate issue where media is practically unplayable/unwatchable.

I'm not doing any upscaling / downscaling, but simple 1:1 2160p playback of UHD HDR media on a 4K HDR display.

The HTPC has an i5-2600K CPU OC'd to 4Ghz, 8GB DDR4 RAM, and GT 1030 GPU.

Is it possible for you to share your MadVR settings or any advice you can offer?

Thanks!

I just installed the GT 1030 into my old Athlon X4 rig, and am able to smoothly play UHD HDR titles as a conversion to SDR, but only with "preserve hue in..." set to "low quality" but I understand you probably have HDR set to passthrough because you are playing to an HDR TV...there is some general opinion that 2GB VRAM might not be enough for 4K output so that may be the reason...unfortunately, I cannot check this for you since I don't have a 4K display near this particular rig, my output is up to 1080p only...

Speaking of that, does anyone know how to get 8K VP9 60 fps play smooth with MadVR, which setting to change, I have tried everything...please note that it plays smooth in EVR, just would like to avoid switching between MadVR and EVR...

[brazen1]

Did you select VP9 in LAV video filter?
Side note: DID YOU GUYS SEE THE NYSE TODAY!

[Sideeffect]

Does Madvr have Performance Impact after Meltdown, Spectre bug patch ?

Nvidia cards are susceptible to only Spectre which was patched in GeForce 390.65 and so far gaming performance hasn't changed notably I would expect MadVR performance to also remain unchanged.

GeForce 390.65
"Fixed CVE-2017-5753
Computer systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis."

The driver is good because it supports Nvidia HDR API again and also it no longer names receivers with a dynamic number or letter after them so speaker settings are no longer lost. This is the best Nvidia driver for HTPC for a long time so I would recommend updating to it.

Edit - If your on AMD Vega it is not susceptible to either Meltdown or Spectre because it doesn't perform speculative execution.

[nevcairiel]

Nvidia cards are susceptible to only Spectre which was patched in GeForce 390.65 and so far gaming performance hasn't changed notably I would expect MadVR performance to also remain unchanged.

This isn't true. GPUs are not susceptible.

However, any driver is, since driver code runs on the CPU and has kernel acccess. So any critical driver should be hardened against Spectre attacks with code changes and compiler improvements. This is exactly what NVIDIA did, they protected their driver from being used as a platform to perform a Spectre attack. The graphics hardware itself is unaffected.

[mytbyte]

Did you select VP9 in LAV video filter?
Side note: DID YOU GUYS SEE THE NYSE TODAY!

Thanks but it's checked, I guess it wouldn't play it with EVR either if I weren't checked...wander if there is somethihg I could do with the filter graph

P.S. the GPU video decoder and 3D graphs in windows task manager are almost at full swing, as well as VRAM but there is maybe 1 fps/minute...render queue is empty

[Sideeffect]

This isn't true. GPUs are not susceptible.

However, any driver is, since driver code runs on the CPU and has kernel acccess. So any critical driver should be hardened against Spectre attacks with code changes and compiler improvements. This is exactly what NVIDIA did, they protected their driver from being used as a platform to perform a Spectre attack. The graphics hardware itself is unaffected.

Yes true technically GPU's are not susceptible but the Nvidia driver code could leave CPU's susceptible which is what Nvidia have patched and the performance impact of the Nvidia change and future upcoming changes to combat Spectre variants is still unknown but at least in the first change performance seems unaffected.

[ryrynz]

Really not the thing to be asking here.

[VBB]

I haven't updated to the 390.65 driver yet, because I wasn't sure if they had fixed the bug with custom resolutions not being able to select 12-bit. The last driver not broken in this regard was 385.28. Is this fixed now?

[tyrindor]

I don't understand how to get HDR to work. I have an LG OLED and the latest W10 update, fully supporting HDR10. Exclusive fullscreen is checked, and HDR passthrough is enabled.

When I launch a 4K HDR rip, there's no HDR and it looks washed out. If I enable HDR in windows, everything looks terrible, and the movie still doesn't look right.

What am I missing?

[Manni]

I haven't updated to the 390.65 driver yet, because I wasn't sure if they had fixed the bug with custom resolutions not being able to select 12-bit. The last driver not broken in this regard was 385.28. Is this fixed now?

It's the same for all drivers post 385.28: you have to select 12bits in a standard res before switching to a custom res. Make sure you're in 23p-30p or you can't select 12bits in 4:4:4 anyway.

Once you've selected 12bits in another mode, 12bits is working in custom res (at least here in 4K23p 12bits 4:4:4) even if you can't select it (greyed out) in the custom res.

Once selected, the custom res will switch automatically between RGB 8bits at 60p and RGB 12bits below 50p, even if the selection for bit depth is greyed out.

[Asmodian]

What am I missing?

AMD or Nvidia? If Nvidia don't use exclusive fullscreen. Do not enable Windows' HDR mode. Make sure you are using driver 390.65. Set madVR to passthrough HDR.

Some rips seem to be made incorrectly so LAV does not pass HDR data to madVR (this reminds me, make sure you are actually decoding with a new LAV).

[tyrindor]

AMD or Nvidia? If Nvidia don't use exclusive fullscreen. Do not enable Windows' HDR mode. Make sure you are using driver 390.65. Set madVR to passthrough HDR.

Some rips seem to be made incorrectly so LAV does not pass HDR data to madVR (this reminds me, make sure you are actually decoding with a new LAV).

NVIDIA, everything is up to date. Must be the rips... EDIT: It's working now, it was the rips. Now how does one have MadVR automatically switch to 12bit for UHD HDR? FS exlusive mode also seems to work fine for me, is there a reason to disable?

Also 3D doesn't work for me either, i've had it working in the past. I have LAV 3d drivers installed and 3d enabled but when i go into fullscreen mode with 3d enabled then MPC-BE crashes. :(

[austinminton]

Few tips for 3D to work on nvidia, if this doesnt work we will go deeper into the issue.

Do these only before playing a 3D file.
- Enable stereoscopic 3D in nvidia control panel (run wizard if its the first time).
- Enable fullscreen exculsive in madvr
- Enable 3D in madvr

This should get 3D working on your setup. If it works we can set everything up to do the above automatically using profiles.

[tyrindor]

Few tips for 3D to work on nvidia, if this doesnt work we will go deeper into the issue.

Do these only before playing a 3D file.
- Enable stereoscopic 3D in nvidia control panel (run wizard if its the first time).
- Enable fullscreen exculsive in madvr
- Enable 3D in madvr

This should get 3D working on your setup. If it works we can set everything up to do the above automatically using profiles.

Sadly it does not, "3D enabled" then "3D signal loss", then I full screen the window and MPC-BE crashes. I tried MPC-BE and MPC-HC. I also noticed if I have 3D enabled in NVIDIA Control Panel, it breaks fullscreen for UHD HDR too (despite 3D not actually being enabled because I am at 4K).

I think Win10 Fall update might have broken it completely. Before I had to disable DX11 fullscreen or I'd crash, but now if I disable that exclusive fullscreen doesn't work at all (even for 2D content). I searched around and other people had this same problem with the fall update. :(

[Manni]

For those who might be interested, I've put together a quick How To guide to control the JVC from MadVR in order to select a specific calibration using the now fixed external command line with custom profiles. It's a pack with six python files, six batch files and a short PDF.

It works fine, except when coming back, my "after" calibration doesn't seem to work but I don't have the time to debug right now.

Here you go: http://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2246658-jvc-calibration-software-v6-2015-models-x9000-x7000-x5000-rs400-rs500-rs600-55.html#post55519234

Happy to report that I can now launch the nVidia 3D batch files to enable/disable 3D using the same external commands, and it works great.

Thanks Madshi for fixing this, it's super useful. :)

Now if only we could find a way to fix the frame drops in 3D for nVidia users, it would be great. I couldn't get anywhere with CRU in 1080p23FP I'm afraid.

[SamuriHL]

Madshi, wanted to let you know I'm a very happy person right now. I've got everything dialed in at full->full->full 12 bit now including 3D. I'm also able to downscale 4K HDR->1080p SDR which looks fantastic. And I'm able to upscale DVD's to 1080p which also looks fantastic. All on my 1060 with the 390 driver and 0.9.11. I should probably leave well enough alone until I get a 4K OLED. LOL

[Manni]

Madshi, wanted to let you know I'm a very happy person right now. I've got everything dialed in at full->full->full 12 bit now including 3D. I'm also able to downscale 4K HDR->1080p SDR which looks fantastic. And I'm able to upscale DVD's to 1080p which also looks fantastic. All on my 1060 with the 390 driver and 0.9.11. I should probably leave well enough alone until I get a 4K OLED. LOL

As you have an nVidia GPU, have you found a way to get better 3D than one frame drop every 3-5 minutes or are you just happy with that?

[tyrindor]

Madshi, wanted to let you know I'm a very happy person right now. I've got everything dialed in at full->full->full 12 bit now including 3D. I'm also able to downscale 4K HDR->1080p SDR which looks fantastic. And I'm able to upscale DVD's to 1080p which also looks fantastic. All on my 1060 with the 390 driver and 0.9.11. I should probably leave well enough alone until I get a 4K OLED. LOL

How'd you get exclusive mode fullscreen working for 3D with the fall W10 update? I've been trying to fix it for months. I start playing a 3d movie and 3d enables, but as soon as I fullscreen it crashes immediately ever since the fall update.

[ryrynz]

Samurai make sure you give HDR the full quality SDR treatment by selecting convert to HDR to SDR with pixel shader math and selecting preserve hue in high quality. 1060 could handle that.
Can anyone comment on whether let madVR decide actually does this automatically if there's enough headroom?

[austinminton]

I think Win10 Fall update might have broken it completely. :(

So I have both HDR and 3D working perfectly on fall update with the latest madvr and nvidia 390.65. Those steps I mentioned are only for 3D. Other files will probably crash with stereoscopic enabled in nvidia cp. As I said, all this can be automated once we have your 3D working.

Does your nvidia correctly go into 3D resolution when stereoscopic is enabled and you select a 3D resolution in nvidia cp for your desktop?

[brazen1]

Sadly it does not, "3D enabled" then "3D signal loss", then I full screen the window and MPC-BE crashes. I tried MPC-BE and MPC-HC. I also noticed if I have 3D enabled in NVIDIA Control Panel, it breaks fullscreen for UHD HDR too (despite 3D not actually being enabled because I am at 4K).

I think Win10 Fall update might have broken it completely. Before I had to disable DX11 fullscreen or I'd crash, but now if I disable that exclusive fullscreen doesn't work at all (even for 2D content). I searched around and other people had this same problem with the fall update. :(

Couple things to consider:
You keep saying 'then when I go to fullscreen, everything crashes. You shouldn't be having to fullscreen anything? Check full screen exclusive mode in madVR. Check start in fullscreen in MPC. We know you installed LAV with 3D. Good. Hopefully you matched 32bit or x64 software. When you setup nVidia driver install and ran stereoscopic wizard, when finished it returned you to NCP. There you should have changed 720p 3D mode to 1080p 3D mode and set RGB FULL 12 bit at 24Hz and saved. Then you should have selected 2160p 60Hz, your native mode, and confirmed your RGB FULL now showed 8bit and saved. There are other unrelated settings in here too. Unless the 3D settings in madVR, Windows, and nVidia are not cooperating together as of all the new releases, you might need to enable stereoscopic in NCP and the Windows global setting under display properties. Start a 3D frame packed title. If it still crashes or doesn't decode and render 3D, you have problems outside normal users imo. Hope this helps.

Here's more that might be related:
madVR - switch to matching display mode and restore original.
madVR display modes - add 2160p23, 2160p24, 2160p25, 2160p59, 2160p60
madVR stereo 3d - check all 3 then, enable when playing 3D. Also, disable when 2d.

[tyrindor]

So I have both HDR and 3D working perfectly on fall update with the latest madvr and nvidia 390.65. Those steps I mentioned are only for 3D. Other files will probably crash with stereoscopic enabled in nvidia cp. As I said, all this can be automated once we have your 3D working.

Does your nvidia correctly go into 3D resolution when stereoscopic is enabled and you select a 3D resolution in nvidia cp for your desktop?

Yes, it does.

Couple things to consider:
You keep saying 'then when I go to fullscreen, everything crashes. You shouldn't be having to fullscreen anything? Check full screen exclusive mode in madVR. Check start in fullscreen in MPC. We know you installed LAV with 3D. Good. Hopefully you matched 32bit or x64 software. When you setup nVidia driver install and ran stereoscopic wizard, when finished it returned you to NCP. There you should have changed 720p 3D mode to 1080p 3D mode and set RGB FULL 12 bit at 24Hz and saved. Then you should have selected 2160p 60Hz, your native mode, and confirmed your RGB FULL now showed 8bit and saved. There are other unrelated settings in here too. Unless the 3D settings in madVR, Windows, and nVidia are not cooperating together as of all the new releases, you might need to enable stereoscopic in NCP and the Windows global setting under display properties. Start a 3D frame packed title. If it still crashes or doesn't decode and render 3D, you have problems outside normal users imo. Hope this helps.

Here's more that might be related:
madVR - switch to matching display mode and restore original.
madVR display modes - add 2160p23, 2160p24, 2160p25, 2160p59, 2160p60
madVR stereo 3d - check all 3 then, enable when playing 3D. Also, disable when 2d.

Verified it's all 64bit. Launching in fullscreen doesn't help. Verified manually selecting 1080p 3D in NVIDIA CP works fine with correct RGB FULL/12bit/24hz. Launch MPC-BE with 3D movie (which worked prior to the fall update), it plays fine while windowed, fullscreen it = crash. I already have all those display modes added and MadVR settings are setup exactly like that.

If I enabled my 4K native resolution and launch a 3D video (in windowed mode), everything switches to 3D and the desktop requires glasses to read... but it still crashes soon as I fullscreen the video.

Tried latest LAV nightly drivers, latest nvidia drivers, latest madvr. I'm really out of options other than setting up a virtual machine to see if this happens on a brand new install with the fall update already applied.

[brazen1]

Shot in the dark: Although all this should work, before I messed with fresh O/S, I'd clean default all the software including the drivers and reset - reset the registry by rebooting after uninstalls and rebooting each install. But first I'd put the driver in 1080 3D, let the display switch, then deselect 12bit and change it to 8 which should flash your display again and be prepped for 3D playback. Let the title start FSE. I assume you are testing by starting your title in explorer? By "crash MPC" what exactly happens?

[tyrindor]

OK, this makes no sense. I did a fresh driver reinstall and restarted and now it's doing something completely different. No more crashes.

I launch a 3D movie and it enables 3D - but it's not actually 3D. Launching it in FSE. There's no depth and no blur without glasses. TV says "3D is enabled" in the corner and "3D signal loss" when I exit. If I force 1080p 3D, the desktop is clearly in 3D but when I launch a movie the 3D effect is removed (from the desktop even) despite the TV still claiming it's receiving a 3D signal. To troubleshoot, I just told MadVR to always keep 3D enabled but it didn't fix it.

I tried latest stable LAVFilters + the nightly build.

I'm close to giving up on 3D. :(

[austinminton]

OK, this makes no sense. I did a fresh driver reinstall and restarted and now it's doing something completely different. :(

No crashes is a good first step. I had the same problem with no depth, and I realized I wasn't in fse. I know you have mentioned fse in your post, but something to double check maybe?

Also what do you have exactly in the 3D settings of madvr?

I think you are quite close to getting it to work.

[tyrindor]

No crashes is a good first step. I had the same problem with no depth, and I realized I wasn't in fse. I know you have mentioned fse in your post, but something to double check maybe?

Also what do you have exactly in the 3D settings of madvr?

I think you are quite close to getting it to work.

It's gotta be in FSE because I am getting the FSE seek bar at the bottom.

I tried basically every combo of 3D settings in the 3D tab. I noticed if I tell it to "enable 3D for 3D content", and then disable 3D in nvidia CP it doesn't actually enable 3D automatically. If I check the box in the nvidia CP and launch a 3D movie, it will pop up and say "3D enabled" but theres's no depth even in FSE. These are known to work rips, I watched them in 3D about a year back.

EDIT: I tried Nvidia's built in 3D test. When it starts up my TV says "3D enabled" but there's no depth in that either. Seems like NVIDIA 3D is broken for me in general. My TV's internal 3D test works fine. The NVIDIA 3D wizard also works, and the desktop is clearly "double vision" if I set 1080p 3D. What a headache, lol.

[austinminton]

Yes, not autoenabling nvida cp using madvr is a known problem. We use batch files to automate that process, but that comes later.

In the 3d wizard, the last step is a 3d box with depth. Do you see depth in that?

Blurred vision in 1080p3D is good, you definitely have 3D running in some form. Not too sure which built in test you are running for Nvidia. Is it for stereoscopic 3D outside the wizard?

I remember I had this problem once too in mpc-hc when i forgot to install lav with 3d enabled.

[tyrindor]

Yup, I see depth in that.

However, I just restarted again and now it's back to crashing immediately. Thanks for your help but I am giving up, by this time next year I'll have a new display and none of the new OLEDs even support 3D anymore. :(

[xyndv]

madshi, could you bring back the old AdaptiveSharpen from v92.4? Please see my screenshot comparison:
Screenshot 1:
Original (https://serving.photos.photobox.com/2131321529eeb9a3a9d041c31533e5acdebf832abd9deef48d86adb3f86fe7d3eeffe846.jpg) | Upscaled + AdaptiveSharpen (v92.4) (https://serving.photos.photobox.com/90505150c0078060173bcdc47ddd613d8c22444ccfe43361bccb158c30c9839e0212679e.jpg) | Upscaled + AdaptiveSharpen + reduce compression artifacts: 3 + reduce random noise: 1 (v92.10) (https://serving.photos.photobox.com/06693650cb4e8f77191355f55fd4a6c2952ddb98119e05524b8c0929485910d318acbb40.jpg) | Upscaled + AdaptiveSharpen (v92.10) (https://serving.photos.photobox.com/53048493db8ff5baf7d712cf72efb84f7c74dfc76afd21dfb6e6acce430a8192bc74b3a9.jpg)

Screenshot 2:
Original (https://serving.photos.photobox.com/98871772e88aac1e2ec14d50519b6630aaf17f81f1e54657e9c2e0cc774d9f1cdeb6e46f.jpg) | Upscaled + AdaptiveSharpen (v92.4) (https://serving.photos.photobox.com/64761582d73bb3ee05f4e872a3efda9a203c91fc17ae6e006a28bf52970f087c93d69de7.jpg) | Upscaled + AdaptiveSharpen + reduce compression artifacts: 3 + reduce random noise: 1 (v92.10) (https://serving.photos.photobox.com/05308717e9b4abb0915b609bbfe049b4708ba3337e0f44621704d2de19a123728f75a90e.jpg) | Upscaled + AdaptiveSharpen (v92.10) (https://serving.photos.photobox.com/413784439e3710a0f1f8e1471d27dc483ad0ed8499639b16feb9778cf7919d171945fc60.jpg)

I used these settings for all of the upscaled images: "NGU AA": very high (doubling) + Jinc AR, "reduce banding": low, "reduce ringing", AdaptiveSharpen: 2.5 + anti-bloating: 100% and linear light for the new AdaptiveSharpen (linear light didn't change much).
The sharpening was done in "image enhancements" (the characteristics are the same if it's used in "upscaling refinement", only milder).

The reasons why I prefer the old version for anime/cartoons are:
1) Arguably, it's not much different in terms of "quality" alone, but subjectively the lines in the old version look more defined and thinner to me.
2) By turning off the anti-bloating filter, you can get even more darker lines, which is a preference of mine for anime/cartoons. You can't achieve this anymore with the new AdaptiveSharpen.
3) The new AdaptiveSharpen brings forward background artifacts and details as you increase the strength (like LumaSharpen), while the old one doesn't almost at all. This is probably good for most real life content, but not really beneficial for anime/cartoons, and especially bad for lower quality ones - because it will only accenuate compression artifacts that you will then have to hide with "Reduce compression artifacts". Using the old AdaptiveSharpen, you can additionally enable "Enhance detail" for higher quality content, if you wish.

Of course, objective quality improvements would be welcome, but I can't give up on the aforementioned "traits" of the old AdaptiveSharpen, which makes it a very suitable sharpener choice for cartoon content (also I assume I'm not the only one who likes the old version, based on previous comments). That's not to say the new AdaptiveSharpen might not be useful too, perhaps it's suitable for 3D animation or real life content, where line darkening is less desirable.
So hopefully you can take these points to your consideration for future versions. Thank you.

By the way, do you think it would be a good idea or possible to add a "bitrate" profile value or something like a ratio of resolution/bitrate, as wouldn't it be better to trigger "reduce compression artifacts" or a sharpener based (also?) on this rather than just resolution, if you want to use them by video quality?

[ryrynz]

Honestly, the old one looks worse in those screenshots (you're way oversharpening). We definitely like thinner lines for lower res content, which is why I've been asking madshi for a line darkener and awarpsharp to be brought into madVR.
The old AS isn't coming back I'm afraid, it may be that AS get's an update later this year and changes things a bit, if you like 0.94's AS that much I recommend you just use that for the time being or use a batch file to swap versions for animated content.