madVR - high quality video renderer (GPU assisted)

[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]

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]

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]

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

[70MM]

Do these beta versions show up on the bottom left of the madvr menu?

[el Filou]

No, there's no official way to tell them apart from each other and from the official 92.17 release except the file dates (the HDR settings screen obviously changes from time to time but you can't tell the exact test build number from that).

[FabioMC]

After upgrading to Windows 11, mpc-be can no longer enter into Fullscreen Exclusive Mode (8-bit or 10-bit) with Madvr V0.92.17. It is always fullscreen windowed. Previously it was working on Windows 10. Anyone else having the same issue? Thanks.

The same is happening here but with MPC HC. Anyone has a solution ? I'm not able to use NV HDR, only OS HDR.

[Klaus1189]

Anyone has a solution ?

Yes, stay away from Windows 11 ;)

[70MM]

No, there's no official way to tell them apart from each other and from the official 92.17 release except the file dates (the HDR settings screen obviously changes from time to time but you can't tell the exact test build number from that).

Is there some way to see the HRD page of this 13 beta version to see if Im on that or not?

[brazen1]

After upgrading to Windows 11, mpc-be can no longer enter into Fullscreen Exclusive Mode (8-bit or 10-bit) with Madvr V0.92.17. It is always fullscreen windowed. Previously it was working on Windows 10. Anyone else having the same issue? Thanks.

Most likely your settings. Fwiw, been using W11 for months and no problems at all. D3D11 FSE 12bit NV HDR with MPC-BE/HC. Kodi internal VideoPlayer uses OS HDR as it should. madVR v113 and v0.92.17.

[janos666]

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

Awwhh, F'ck. I just noticed that madVR no longer get's 10bit in windowed fullscreen mode anymore with 511.23. It's stuck at 8 bit mode. So it seems like disabling 10 bit mode was nVidia's "fix" for the suffering issue. :(

[aufkrawall]

http://madshi.net/madVRhdrMeasure113.zip

Is there a known crash issue? As it crashes for me with various files with that particular version.

[LenniePaz]

Is there a known crash issue? As it crashes for me with various files with that particular version.Not that I'm aware of. Did you extract the files from v113 into the original MadVR folder ?

Sent from my SM-N975U using Tapatalk

[aufkrawall]

Not that I'm aware of. Did you extract the files from v113 into the original MadVR folder ?

Yep. Weird thing it crashes with some plain H.264 videos, while it doesn't with others.

[LenniePaz]

Yep. Weird thing it crashes with some plain H.264 videos, while it doesn't with others.What was the version in the original MadVR folder ?

Sent from my SM-N975U using Tapatalk

[huhn]

113 is known to be buggy. for example it will crash with SM so if your h264 file you are talking about has a different frame rate that could be just it.

there are more issue but i'm not here to remember them all.

[IngramAU]

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

I'm on the latest currently, I also tried going back several drivers with no success. This issue seems to have come from nowhere.

I have 2 brand new HDMI 2.1 cables coming to totally rule out dodgy cables. No idea why bitstream drops out but PCM is fine. I've been using NGU Sharp High with same for Chroma, DX11 exclusive w/Error Diffusion, and RGB 12bit output for a while before this issue cropped up.

First noticed this problem on 4k files that don't even get rescaled besides chroma so not sure how much madvr is to blame but if I use EVR instead bitstream is fine. Also adjusting madvr settings influences it somehow.

[clsid]

It is listed as a "known issue" for latest driver, so using latest one isn't going to fix it.

Judging from this topic you may need to go back several months in driver version:
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/462620/dolby-atmos-dropouts-with-rtx-3090-founders-editio/

Maybe also try disabling GSync in case you use that:
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/471903/bug-report-audio-crackling-after-sleep-since-drive/

[IngramAU]

Hmmm that seems Atmos related and I'm just a humble bitstreamer with DD+/DTHD/DTSHD and an old Yamaha AVR that is HDMI 2.0. The driver notes the issue is for HDMI 2.1.

I've tried all sorts of stuff tonight and to be honest I can't really say anything is standing out that is a likely cause. After trying 4:2:0 8bit and stripping MadVR to low low settings I wasn't getting issues. Then I ramped back up to RGB 12bit NGU Sharp High/High everything is still working fine.

Potentially it's a video card OC that was the culprit. On my EVGA 1060 GTX 6Gb OC I was running the core +100 in MSI Afterburner. I found a thread where a user said you must operate in 12hz increments as it's the timing the card expects. I've dropped to +96 and have been playing various files just fine. Perhaps I have found the culprit! In 24Hz I am now getting no drops/repeats expected which is new. I'm also getting drops every 1.06hr in 23.976 which is usually what stock Nvidia gives.

So perhaps I was screwing the timings up. We'll see in 24hrs how the timings behave. Fingers crossed.

[aufkrawall]

Judging from this topic you may need to go back several months in driver version:
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/462620/dolby-atmos-dropouts-with-rtx-3090-founders-editio/

It might work to continue using the older HDMI audio driver with newer graphics driver as a workaround.

[Charky]

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 (https://nvidia.custhelp.com/app/answers/detail/a_id/5157)
This post should be highlighted somewhere, not buried in a 3000+ pages thread...

[Ceremony]

http://madshi.net/madVRhdrMeasure113.zip

Sent from my SM-N975U using Tapatalk

The latest version is actually http://madshi.net/madVRhdrMeasure144.zip, carbondated to today, 2022-01-19, if one can trust timestamps.

Didn't test it, tho

[SirMaster]

The latest version is actually http://madshi.net/madVRhdrMeasure144.zip, carbondated to today, 2022-01-19, if one can trust timestamps.

Didn't test it, tho

And now it's http://madshi.net/madVRhdrMeasure145.zip

:D

He's back working on DTM. Been 4 new builds in the last week or so.

[mclingo]

I hope the 5 people who bought an ENVY appreciate all the work he's putting in :)

[SirMaster]

I hope the 5 people who bought an ENVY appreciate all the work he's putting in :)

There are actually a lot of Envy customers out there. I think you would be surprised.

[mclingo]

yeah, I was being a little cruel, to be honest I hope there are as I think we all want to see MADSHI succeed, I guess it depends on how you define a lot, but I just dont see there a large customer base for this, especially now it must be costing a whole heap more due to gfx cards being completely unaffordable at the moment and projectors also seems to be be getting onboard tone mapping too which begs the question whether this will be obsolete before they start to make money on it.

He should have taken the safe paid license route but that wasnt his passion and I respect that.

[claw]

Is there a known crash issue? As it crashes for me with various files with that particular version.

Smooth Motion must be turned off in 113. It will crash with it enabled.

[FabioMC]

The same is happening here but with MPC HC. Anyone has a solution ? I'm not able to use NV HDR, only OS HDR.

I´ve found out the solution for FSE absence on win11. I was using the explorerpatch app. Apparently it disables FSE on mpc hc.

[aufkrawall]

Smooth Motion must be turned off in 113. It will crash with it enabled.
That probably was it. It works again with build 145. Though I'm not sure I'm sold for the recent tonemapping changes.

[x7007]

Why when I use http://madshi.net/madVRhdrMeasure145.zip it has HDR without enabling AMD/OS TV HDR?? but it uses 8bit. and 0.92.17 works fine with HDR detect and 10bit? using Potplayer

[kasper93]

That probably was it. It works again with build 145. Though I'm not sure I'm sold for the recent tonemapping changes.Can you elaborate? It is good time to voice concerns. But looking at it, it's going really well and madshi has clear plan to consolidate and agree on proper settings. Let's hope he will have enough spare time to keep at it :)

[aufkrawall]

I think I missed that some trade quality options were set for HDR. With them unchecked, it actually looks really good (now build 146). The difference between targeting for BT.709 and pure power display gamma curve is btw. very distinct ("display already calibrated" via clamping/calibrating with novideo_srgb).

[sexus]

would also be cool to have madvr integrate vulkan rendering ...surely should give big boost in performance

btw still havent figured out how to have BT2020 primaries be autoforced on playback start ...besides using a hotkey ...which sucks

[huhn]

look up profiles.

vulkan is not plain faster than DX9.
it's different madVR uses mostly shader and these don't benefit massively from vulkan which uses a completely different shader language so everything has to be rewritten for most likely small gains at best.

there are reasons to do that for feature like dx12 or at least 11 but this is a lot of work.

[aufkrawall]

You are lucky when you can even successfully switch to fullscreen with mpv Vulkan and AMD's bug infested Windows driver.

[FabioMC]

I´m running with serious trouble with dolby atmos passthrough using madvr and mpc-hc/mpc-be. If I don´t seek (forward or backward) the audio runs smoothly for about 10min, but whenever I seek the movie it starts skipping and stuttering. I´ve tried almost everything, even a windows 10 and 11 (normal and lite versions) fresh installs. I´ve tried lav audio and mpc audio (mpc-be). The video runs smoothly no drop/rep/glich. It works fine with other audio sources (Dolby Digital+, DTS-HD). It looks like its loosing sync. Anyone can help me ? Do you think it´s something related to hdmi cable quality ? Thanks.

[dbezerra]

I´m running with serious trouble with dolby atmos passthrough using madvr and mpc-hc/mpc-be. If I don´t seek (forward or backward) the audio runs smoothly for about 10min, but whenever I seek the movie it starts skipping and stuttering. I´ve tried almost everything, even a windows 10 and 11 (normal and lite versions) fresh installs. I´ve tried lav audio and mpc audio (mpc-be). The video runs smoothly no drop/rep/glich. It works fine with other audio sources (Dolby Digital+, DTS-HD). It looks like its loosing sync. Anyone can help me ? Do you think it´s something related to hdmi cable quality ? Thanks.

I fixed ATMOS issues by installing the latest Lav Filters :

https://github.com/Nevcairiel/LAVFilters/releases

[IngramAU]

wow nice to see others having the same issue. I will try the new LAV.

[FabioMC]

I fixed ATMOS issues by installing the latest Lav Filters :

https://github.com/Nevcairiel/LAVFilters/releases


Did u have the same issues ? I´ve already tried both latest stable and nightly lav builds. No luck.

[dbezerra]

Did u have the same issues ? I´ve already tried both latest stable and nightly lav builds. No luck.

I had sound issues with ATMOS with an earlier version of Lav Filters. At some point the sound would just stop playing in certain titles. Since Nev fixed it, I never had problems again.

[IngramAU]

I'm still getting drop outs. Interestingly, I can get through a whole episode of a show and then as the scene changes to credits at the end I will get a drop out. I just can't work out what is the cause.

[IngramAU]

Have changed over to new HDMI cables and have MadVr145 going. I have unticked every performance saving option and now I'm getting lots of audio drop outs on this file.

General
Unique ID : 147447891194989394090149118539767442042 (0x6EED6E4EBC7380B57C68AF58A0AB6A7A)
Complete name : D:\TV Series Keepers\Yellowstone (2018)\Season 4\Yellowstone (2018) - S04E10 - Grass on the Streets and Weeds on the Rooftops WEBDL-1080p.mkv
Format : Matroska
Format version : Version 4
File size : 5.10 GiB
Duration : 1 h 16 min
Overall bit rate : 9 582 kb/s
Writing application : mkvmerge v58.0.0 ('Supper's Ready') 64-bit
Writing library : libebml v1.4.2 + libmatroska v1.6.4

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 16 min
Bit rate mode : Constant
Bit rate : 9 197 kb/s
Nominal bit rate : 10 000 kb/s
Width : 1 920 pixels
Height : 960 pixels
Display aspect ratio : 2.000
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.208
Stream size : 4.89 GiB (96%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : A_EAC3
Duration : 1 h 16 min
Bit rate mode : Constant
Bit rate : 384 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 209 MiB (4%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No


https://i.ibb.co/4jmyJHD/madvr1.jpg (https://ibb.co/gDj16xX)

Using latest NVidia on a 1060GTX. Latest MPC-HC and latest LAV.

Keep in mind that the audio drop out occurs in KODI too which uses it's own internal pathways.

[FabioMC]

I´ve finally found out the solution to my case. I think it´s related to the "hdmi arc cycle". In my setup the vga hdmi out is connected to the LG OLED TV and then the HDMI ARC of the TV to the AVR. I think it´s causing the delay. My solution was to use a secondary connection from my vga to the AVR (direct connection), set the resolution to 720p and use it as an extended display. After that I set the default audio to the AVR connection (secondary). Now the audio problems are totally gone.

[mclingo]

the ARC port will only come into play and affect audio coming from your TV, it should not affect audio coming from your HTPC, i'm also using an LG OLED TV from 2015 and I have no issues with ATMOS.

[huhn]

depending on how he cabled it it makes sense.
bad implemented arc solution are not rare.

[FabioMC]

the ARC port will only come into play and affect audio coming from your TV, it should not affect audio coming from your HTPC, i'm also using an LG OLED TV from 2015 and I have no issues with ATMOS.

I don´t know why but I was having several issues with this route:

VGA HDMI 1-> LG OLED C1 -> AVR (VIA ARC)

My solution:

VGA HDMI 1 -> LG OLED C1 (AUDIO DISABLED)
VGA HDMI 2 -> AVR (EXTENDED AND AUDIO DEFAULT)

I know there´s a route 3 (VGA -> AVR -> TV) but my AVR is not dolby vision compatible.

[mclingo]

Hi, I dont think that is right, I have mine setup as follows.

ARC port on TV is connected to ARC port on receiver, then receiver input is connected to pc.

[wushantao]

http://madshi.net/madVRhdrMeasure151.zip

151 is out

[Siso]

http://madshi.net/madVRhdrMeasure151.zip

151 is out

Does it have expiration date?