madVR - high quality video renderer (GPU assisted)

[IngramAU]

Have ran into an interesting issue with madvr dropping out bitstream audio. After trying nearly everything I seem to have landed on the Error Diffusion option 1 or 2 causing it for some strange reason. I am using 24Hz 12Bit RBG over HDMI enhanced to an AVR/Sony HDR TV. MPC-HC latest, latest nvidia, D3D11 renderer, wasapi is handling bitstream out.

I'm wondering if with error diffusion 1/2 I'm maxxing out the HDMI cable and it's dropping audio as a result. It seems DTSHD/DTS doesn't have this issue but happens frequently with DD+ 5.1 audio.

I can use PCM 5.1 and encounter no issues as a work around.

I'll keep testing to make sure this specific option is what is causing the bitstream drop outs.

I was convinced it was a Windows issue and was going to format and start from scratch!

EDIT:

Well plot thickens. It seems the issue happens with Jinc for chroma and Error Diffusion 1 or 2 on my 4k HDR files which don't need upscaling besides the chroma. I've changed to NGU Sharp Med/High and Error Diffusion 2 and so far seems to be resolved. Glad to have gotten to the bottom of this one.

[aufkrawall]

Originally Posted by tp4tissue

I haven't observed any "additional" banding with reshade that isn't already present in the source material or the poor handling of most non-pro display devices.

I can easily observe it in old Mirror's Edge, it gets noticeably worse with ReShade 3D LUT inject with 8 bit frame buffer.
Also, most LCD displays shouldn't introduce additional banding anymore these days.

Originally Posted by tp4tissue

Oversaturation isn't a huge problem unless it's very uneven or starts really early where it affects skintones too much.

It affects everything and even slight tints by e.g. color grading get annoyingly obtrusive.

Originally Posted by tp4tissue

NO sense in paying for all this wide-gamut and not using it.

Geez. You can't make proper use of wide gamut when the source isn't explicitly using it (which is ~never the case for SDR content). You just get shifted chromatic coordinates: Saturated red will turn pinkish everywhere and blue turquoise etc.. This is just garbage...

[mpchelp10]

Originally Posted by clsid

In the devices section of madvr settings, set "native display bitdepth" for your device to 10bit.

If that does not help, then change HDR mode in madvr from "let madvr decide" to "tone map HDR using pixel shaders" + "output video in HDR format".

Native display bitdepth is already set to 10bit
HDR mode was set to "passthrough HDR" with "send HDR metadata" checked.
Changing it to "tone map HDR using pixel shaders" + "output video in HDR format" results in the same issues.

[DMU]

Originally Posted by mpchelp10

my laptop has one of those "8+2bit hdr" screens with 2 gpus (igpu + dgpu)

Specify, please, which GPUs are used in your laptop?

[ashlar42]

Originally Posted by nevcairiel

This might also happen if you use an old version of LAV Filters (pre-0.74) and madVR has dropped its previously accepted values for PQ HDR in recent development versions.
Some time ago, madVR introduced a custom value for PQ HDR signaling, but that value then collided with the official value for HLG when it was introduced, so you need to make sure all parts are up to date.

Found this as I was looking for why a file with this mediainfo was not activating HDR on my LG OLED (which supports HLG AFAIK):

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 58 min 0 s
Bit rate : 18.6 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.090
Stream size : 7.52 GiB (99%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : BT.2020 (10-bit)
transfer_characteristics_Original : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

I use LAV 0.75.1.17 and a still active madVR beta (I think the last one available).

[mpchelp10]

Originally Posted by DMU

Specify, please, which GPUs are used in your laptop?

integrated graphics is Intel UHD 630
discrete graphics is GTX 1050 Ti MaxQ

[huhn]

Found this as I was looking for why a file with this mediainfo was not activating HDR on my LG OLED (which supports HLG AFAIK):

it does not matter that your TV support it the file it is HLG and madVR and windows, nvidia/amd or both does not support it yet.

mpcVR can convert it to HDR10 which madVR should do in my opinion too but doesn't.

[janos666]

I started to have some stuttering issues lately. I am currently on Win11 (22000.434) and nVidia 511.17. I tried to go back to an older nVidia driver (497.29) but it didn't make a difference.
The video playback is smooth while the media player is in windowed mode. Stuttering starts when it enters borderless windowed fullscreen mode and the surface switches from 8 to 10 bit. Bringing up the GUI (the seek bar) drops it back to regular 8 bit windowed mode and playback is smooth again. Once the GUI disappears and 10 bit is engaged again, the stuttering comes back.
I think I had this issue a while back (maybe 1 year ago) but it was so long ago that I can't remember what solved it. But back then it was enough to pause and resume the playback a few times after the transition to 10 bit mode and then playback remained smooth (until another transition or pause/play cycling, at somewhat random). This time pause/play doesn't help.
What could be the problem? (The hardware and the MB UFEI Setup settings didn't change for months.) Should I go back even further with the nVidia driver? Or is it a Win11 bug? (This was already present with the previous Win11 CU, .376.)

[clsid]

To fix stuttering:

* madvr settings > general settings > windowed mode / exclusive mode > frames presented in advance = 1

* NVIDIA settings > Power Management Mode = Adaptive / Normal
* NVIDIA settings > Vertical Sync = Adaptive
* NVIDIA settings > GSync = Disabled globally (use profiles for games)
* NVIDIA settings > disable Multiplane Overlay

[ashlar42]

Originally Posted by huhn

it does not matter that your TV support it the file it is HLG and madVR and windows, nvidia/amd or both does not support it yet.

mpcVR can convert it to HDR10 which madVR should do in my opinion too but doesn't.

Oh, ok. So that's madVR's limitation. Well, at least I know what's not working. Thanks for your answer. :-)

[Manni]

Originally Posted by clsid

To fix stuttering:

* madvr settings > general settings > windowed mode / exclusive mode > frames presented in advance = 1

* NVIDIA settings > Power Management Mode = Adaptive / Normal
* NVIDIA settings > Vertical Sync = Adaptive
* NVIDIA settings > GSync = Disabled globally (use profiles for games)
* NVIDIA settings > disable Multiplane Overlay

Thanks. Not everyone has all these options though. For example, in NCP 8.1.961.0 that comes with the latest 511.09, I can't find the multiplane overlay option in my nVidia settings and I can't set Gsync to disabled globally (I can only set monitor technology to fixed refresh instead of Gsync compatible).

[IngramAU]

Hmm I'm still experiencing bitstream audio drop outs. Have just changed HDMI cables hopefully that's the cause. Weird I've never had this sort of problem before.

[janos666]

Originally Posted by clsid

To fix stuttering:

* madvr settings > general settings > windowed mode / exclusive mode > frames presented in advance = 1

* NVIDIA settings > Power Management Mode = Adaptive / Normal
* NVIDIA settings > Vertical Sync = Adaptive
* NVIDIA settings > GSync = Disabled globally (use profiles for games)
* NVIDIA settings > disable Multiplane Overlay

Well, thank you for the tips but installing 511.23 somehow fixed the stuttering issue (without applying any of the changes you listed).

Originally Posted by IngramAU

Hmm I'm still experiencing bitstream audio drop outs. Have just changed HDMI cables hopefully that's the cause. Weird I've never had this sort of problem before.

Try to update the nVidia driver (unless you have an AMD card). There is an audio issue mentioned in the latest changelog.

[70MM]

Sorry but I havent checked this thread for a very long time....
Im on version madVR v0.92.17 which was the last one, will this still be safe to use, I heard v0.92.13 was the safest since there are no more updates?

[ryrynz]

There aren't any deal breaking bugs in the latest version that would make you want to use an earlier version. Use .17

[70MM]

Does anyone have any good setup instructions for using HRD on version 17 for me please? I have 145" microperf Stewart G4 scope screen 1.3 gain and the JVC NX9 projector.

[LenniePaz]

Originally Posted by 70MM

Sorry but I havent checked this thread for a very long time....
Im on version madVR v0.92.17 which was the last one, will this still be safe to use, I heard v0.92.13 was the safest since there are no more updates?

v113 is the best to use in my opinion, especially if you want to do tone mapping. There's no expiration on v113.

Sent from my SM-N975U using Tapatalk

[Polopretress]

Hello.

Based on the first page for the syntax of the profile rules, there is a numerical value for maxCLL which is called "hdrVideoPeak "
Is there also another numerical value to monitor "max Mastering Display Luminance" since it is also usefull to manage script compared to this value ?

Thank you.

[70MM]

Originally Posted by LenniePaz

v113 is the best to use in my opinion, especially if you want to do tone mapping. There's no expiration on v113.

Sent from my SM-N975U using Tapatalk

I think v113 is a beta version and not on the main release page, where do I find that please?

[LenniePaz]

Originally Posted by 70MM

I think v113 is a beta version and not on the main release page, where do I find that please?

http://madshi.net/madVRhdrMeasure113.zip

Sent from my SM-N975U using Tapatalk