madVR - high quality video renderer (GPU assisted)

[huhn]

4 GB should be fine with current algorithms and UHD output.

[Stereodude]

Is madVR or the video driver responsible for the depth information in 1080p 3D frame packed output? I found at least one of my 3D BD's when ripped to .mkv and played back from the PC has intermittent odd depth shifts (like the image will jump forward or backward a bit mid scene). The jumps aren't there when the 3D BD is played from a Blu-ray player.

[BogaMoge]

Hi everyone.

So I got a new LG CX OLED and I have this issue with subtitles using MPC-HC with MadVR :
- with the internal subtitle renderer, no problem with .ass subtitles (I can change their look) but in HDR, subtitles stay bright white whatever my changes
- with xySubFilter, .ass subtitles are out of whack (generally looking extemely small) but I can change the color of HDR subtitles
- with DirectVOBsub, any subtitle in SDR is easy to set up as I want, but then MPC-HC doesn't output in HDR (I guess since DirectVOBsub is not part pf MadVR)

Does anyone know the settings to be able to set the color of subtitles to light gray and with whatever font and size I want, whatever the resolution of the content and whether it is SDR or HDR?

Thanks

[chros]

Do you have issue with ass subs only? If so, upload it somwhwere.

[fotb]

Hi and happy new year!

How does madvr detect hdr and where does it get the essential information?
I want to render a not tone mapped 4k hdr stream from a capture card, but madvr does not detect the video stream as hdr. For matrix, primaries and color range it only does a "(best guess)" with bt.709 and limited. When looking at the pin info, there is only VIDEOINFOHEADER set, but no VIDEOINFOHEADER2 with DWCONTROLFLAGS.
Is it possible to inject this information upstream of madvr or force madvr to do a "best guess" with bt.2020?

Pin info for the capture stream from the capture card:


Filter : Smart Tee - CLSID : {CC58E280-8AA1-11D1-B3F1-00AA003761C5}
Module : C:\Windows\System32\qcap.dll

- Connected to:

CLSID: {17CCA71B-ECD7-11D0-B908-00A0C9223196}
Filter: Game Capture 4K60 Pro MK.2 Video
Pin: Video Capture

- Connection media type:

Video: YUY2 3840x2160 60fps 3667 mbit/s

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_YUY2 {32595559-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo {05589F80-C356-11CE-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 16588800
cbFormat: 88

VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(0,0)
dwBitRate: 3667656704
dwBitErrorRate: 0
AvgTimePerFrame: 166666 (60.000 fps)

BITMAPINFOHEADER:
biSize: 40
biWidth: 3840
biHeight: 2160
biPlanes: 1
biBitCount: 16
biCompression: YUY2
biSizeImage: 16588800
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0



Pin info from a recorded clip of the capture card stream where hdr detection is working:


Filter : madVR - CLSID : {E1A8B82A-32CE-4B0D-BE0D-AA68C772E423}
Module : C:\madVR\madVR64.ax

- Connected to:

CLSID: {EE30215D-164F-4A92-A4EB-9D4C13390F9F}
Filter: LAV Video Decoder
Pin: Output

- Connection media type:

Video: dxva 3840x2160 59.96fps

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: MEDIASUBTYPE_P010 {30313050-0000-0010-8000-00AA00389B71}
formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 24883200
cbFormat: 112

VIDEOINFOHEADER:
rcSource: (0,0)-(3840,2160)
rcTarget: (0,0)-(3840,2160)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 166778 (59.960 fps)

VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x7a421581
- VideoChromaSubsampling: 5 (MPEG-2)
- NominalRange : 1 (0-255)
- VideoTransferMatrix : 4 (BT.2020)
- VideoLighting : 0
- VideoPrimaries : 9 (BT.2020)
- VideoTransferFunction : 15 (SMPTE ST 2084 (PQ))
dwReserved2: 0x00000000

BITMAPINFOHEADER:
biSize: 40
biWidth: 3840
biHeight: 2160
biPlanes: 1
biBitCount: 24
biCompression: dxva
biSizeImage: 24883200
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0


I hope anybody has an idea. Thank you!


I was wondering if you ran into any favorable results in trying to figure this out. Ive been trying to accomplish this all month.

[chros]

Isn't pipes available in windows (like in linux)? I mean redirecting the captured output into a fake file.

[fotb]

Isn't pipes available in windows (like in linux)? I mean redirecting the captured output into a fake file.

Sounds like a great option if there is. Not sure how its done

[lansing]

Hi I have noticed a problem recently with the audio on playback while using MadVR in mpc. There is a very low frequency noise during playback. If I pause the video it would stop. The problem occurred when playing h264, hevc videos, but not mpg or mpeg2. It doesn't happen when I switch to another video renderer.

To reproduce it, mute mpc, turn up the speaker and play a video.

[Asmodian]

What audio device are you using? Do you have a way to test a method where the audio leaves your PC in a digital format (e.g. digital out or HDMI audio device)?

That sounds like a hardware issue, with analog audio circuits getting crosstalk from somewhere.

Sounds like a great option if there is. Not sure how its done

Use the pipe symbol "|" between commands but the applications need to know how to send to and receive from stdout.

[lansing]

What audio device are you using? Do you have a way to test a method where the audio leaves your PC in a digital format (e.g. digital out or HDMI audio device)?

That sounds like a hardware issue, with analog audio circuits getting crosstalk from somewhere.


I am outputting the audio from pc directly to my speakers. I doubt it's a hardware issue because it only happen when I'm using MadVR.

[Asmodian]

That is normal, madVR puts a unique load on the hardware so it is common for issues like this to only show up when running madVR.

Also, there is no software mechanism for madVR to add sounds like that to the audio. A pop or click maybe, but not a low frequency noise.

If it only happens when you send analog audio out it really sounds like crosstalk. This is a common issue with on-motherboard audio, especially if it is pretty old or a cheaper model. The newer higher end boards have gotten better about the audio circuitry but it is still possible.

[lansing]

That is normal, madVR puts a unique load on the hardware so it is common for issues like this to only show up when running madVR.

Also, there is no software mechanism for madVR to add sounds like that to the audio. A pop or click maybe, but not a low frequency noise.

If it only happens when you send analog audio out it really sounds like crosstalk. This is a common issue with on-motherboard audio, especially if it is pretty old or a cheaper model. The newer higher end boards have gotten better about the audio circuitry but it is still possible.

You're right, after more testing, it turns out to be an analog issue. I was connecting my speaker to the analog audio out from the motherboard. Now I'm connecting through gpu -> hdmi -> monitor -> audio line out ->subwoofer/speakers and the noise is gone.

[Asmodian]

Great news! An easy fix. :)

[jmone]

I know but there wasn't there your increased queue sizes of madVR for Gemini Man (BD UHD 59.94fps HDR 4:2:0) in that thread that's why I asked here several times ;)
I've just watched Gemini Man VP9 4K (notHDR - my GTX750v2 can't hardware acceleration of VP9.2 HDR) from https://www.youtube.com/watch?v=vX2vsvdq8nw - very impressive quality...

The Queue Sizes I used (and it is just for testing on SW decoding) is in the madVR OSD part of the Screen Shot. This will probably not work on your GPU as it increases the memory used on the GPU (and I have 24GB on the 3090).

[VictorLS]

I've seen your screenshot and 5 different queues but I'm not pro in madVR so I'd ask you provide screenshot like mine at http://forum.doom9.org/showthread.php?p=1934564#post1934564 or although write like "my CPU/GPU queue sizes increased from default 16/8 to 128/24" - I bekieve it wasn't too hard to write that in your first post about increased queue sizes ;)

[jmone]

Victor - here is the screen shot. It was just an extreme setting to test SW Decoding with the very high CPU Queue helps buffer against the CPU 100% spikes. You would need to play with a setting that works with your GPU Memory. It will not help if your CPU can not keep up with SW Decoding, it only helps with 100% spikes causing dropped frames. https://behome.dyndns.info/index.php/s/LewWEQLf85Gg2PN

[VictorLS]

I see. Thank for screenshot - I thought so ;)

[IngramAU]

Never seen it before but MPC-HC popped up in the top left corner telling me to update MadVR? I'm already using 113 or 114 build lol.

[vanden]

Hello, I have 2 computer, one with 4 processor (Xeon X7460) + Gtx 650ti Win10 1809, the other with a Core 2 Duo E6550 + Gtx 1060 Win10 20H2.

Both have Media Player HC 1.9.8, MadVR 0.92.17 and madVRhdrMeasure122.
The Xeon X7460 reads in CPU and Core 2 Duo E6550 reads in GPU (I can test in CPU frame by frame).

On the Xeon X7460 I can set "color tweaks for fire & explosions" and "constast recovery":
http://vandenk.free.fr/X7460.gif
On the Core 2 Duo E6550 I cannot adjust them (In CPU or GPU):
http://vandenk.free.fr/Core2DuoE6550.gif

But even by setting both the same, I have a display difference:
http://vandenk.free.fr/Pc1&Pc2.html

Can someone explain this difference to me ?!

[SirMaster]

Never seen it before but MPC-HC popped up in the top left corner telling me to update MadVR? I'm already using 113 or 114 build lol.

You are using test build 114.

Test builds from 114 on are timed-limited.

[el Filou]

The Xeon X7460 reads in CPU and Core 2 Duo E6550 reads in GPU (I can test in CPU frame by frame).
On the Xeon X7460 I can set "color tweaks for fire & explosions" and "highlight recovery":
On the Core 2 Duo E6550 I cannot adjust them (In CPU or GPU):
But even by setting both the same, I have a display difference:To get access to the color tweaks and highlight recovery options, go to rendering => trade quality for performance, and uncheck "compromise on HDR tone & gamut...".
It's also best to uncheck "compromise on HDR luminance..." for best quality. Note that this will obviously use more GPU but the 1060 should be able to handle it.
Also, note that if you are using "DXVA2 native" as the hardware decoder with the 1060 then madVR won't be able to do some steps of HDR processing. With D3D11 native (or other decoders) it will work.
I hope this fixes the colour differences you are having.

[IngramAU]

You are using test build 114.

Test builds from 114 on are timed-limited.

Does this mean it will stop working? Seems ok so far besides the message appearing.

Is there a 115 or anything newer to update to?

[VBB]

Yes, it means your particular build will stop working soon.

The latest test build can be found here: http://madshi.net/madVRhdrMeasure122.zip

[vanden]

To get access to the color tweaks and highlight recovery options, go to rendering => trade quality for performance, and uncheck "compromise on HDR tone & gamut...".
It's also best to uncheck "compromise on HDR luminance..." for best quality. Note that this will obviously use more GPU but the 1060 should be able to handle it.
Also, note that if you are using "DXVA2 native" as the hardware decoder with the 1060 then madVR won't be able to do some steps of HDR processing. With D3D11 native (or other decoders) it will work.
I hope this fixes the colour differences you are having.

Thank you !

I first tick "color tweaks for fire & explosions" and "constast recovery" on the 2 PCs :
http://vandenk.free.fr/X7460&Core2DuoE6550-Reg1.png
I get the same colors :
http://vandenk.free.fr/Pc1&Pc2-2.html

My 650 Ti bug, as soon as I uncheck "color tweaks for fire & explosions" ...:
http://vandenk.free.fr/X7460&Core2DuoE6550-Reg2.png
http://vandenk.free.fr/X7460&Core2DuoE6550-Reg2-2.png
http://vandenk.free.fr/Pc1&Pc2-3.html
I let them tick on the 650 Ti!
But it works well on the 1060 !!

[IngramAU]

Yes, it means your particular build will stop working soon.

The latest test build can be found here: http://madshi.net/madVRhdrMeasure122.zip

Thankyou. I upgraded to 118 so I'll hold off on 122 until I get the message to move on lol.

I use HDR passthrough so these builds won't be doing anything for me anyway.

[ang3l]

hi,

how is the situation on hdr switching for amd rx6000 and nvidia rtx3000? right now I have a rx480 and it works without problems

also the 23.976hz for the nvida rtx has improved? in the past I had a 9600gt and it was a disaster compared to amd

sorry guys but it's hard to get this fresh new information

[Klaus1189]

hi,

how is the situation on hdr switching for amd rx6000 and nvidia rtx3000? right now I have a rx480 and it works without problems

also the 23.976hz for the nvida rtx has improved? in the past I had a 9600gt and it was a disaster compared to amd

sorry guys but it's hard to get this fresh new information

I created a dedicated thread for this stuff and update it daily if necessary for new driver updates, new infos of bugs or known limitations of specific GPUs and or drivers:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)

I summarized in the first two posts ;)

[Zulithe]

MPC-BE crashes when madVR is enabled now. Just shows a black screen and shortly after the player crashes. I tried both current madVR stable and the latest madVRhdrMeasure123.zip build. I haven't changed any madVR settings in months, but reset its settings and it didn't help. Seemed to start within the last week, during that time I got a series of windows updates and updated to MPC-BE new stable version. For the time being I switched to MPC Video Renderer and it works fine. Any thoughts on what I should try?
setup:
Win 10 x64 20H2 (19042.789)
MPC-BE x64 1.5.6.6000
nvidia 461.40 drivers
display: hdr capable but I don't have hdr enabled in Windows currently
Since it only happens with madVR I thought I should post it here, if I should instead ask in the MPC-BE thread I will.

[VBB]

Go back one build number. The new build is reportedly crashing a lot of systems.

EDIT: Workaround seems to be to open madVR at least once before attempting playback.

2nd EDIT: Mathias posted a fixed build: http://madshi.net/madVRhdrMeasure123b.zip

[ang3l]

I created a dedicated thread for this stuff and update it daily if necessary for new driver updates, new infos of bugs or known limitations of specific GPUs and or drivers:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)

I summarized in the first two posts ;)

thxxx :)

[Zulithe]

Go back one build number. The new build is reportedly crashing a lot of systems.

EDIT: Workaround seems to be to open madVR at least once before attempting playback.

2nd EDIT: Mathias posted a fixed build: http://madshi.net/madVRhdrMeasure123b.zip
Sadly did not fix it... the crash happens on stable too. I'm not sure it's related to the changes in the test builds, since I also tried rolling back to stable

*edit* ack, thought I fixed it but nope

[VBB]

Does it crash with MPC-HC instead of MPC-BE?

[Zulithe]

Does it crash with MPC-HC instead of MPC-BE?

It crashes both. Just downloaded MPC-HC 1.9.8.26 Portable Beta to test it.

[VBB]

That is odd. If I were you, I'd completely uninstall madVR by using the included batch file. Then re-install using this http://madshi.net/madVR.zip. After that, you can copy any of the test builds on top, if you feel like it. Also, try the latest MPC-HC here https://github.com/clsid2/mpc-hc/releases/download/1.9.8.26/MPC-HC.1.9.8.157.x64.zip, just in case (unless that's the version you are talking about).

[Zulithe]

That is odd. If I were you, I'd completely uninstall madVR by using the included batch file. Then re-install using this http://madshi.net/madVR.zip. After that, you can copy any of the test builds on top, if you feel like it. Also, try the latest MPC-HC here https://github.com/clsid2/mpc-hc/releases/download/1.9.8.26/MPC-HC.1.9.8.157.x64.zip, just in case (unless that's the version you are talking about).
I sincerely thank you for the replies, but I have tried that over and over again. Tried rebooting. Tried re-installing my video drivers. reinstalled every program in my video playing stack and reset all their settings. tried madvr stable (same as your link) and even the test build, freshly extracting the files each time in case I was making some kind of error. tried mpc-be and latest stable mpc-hc (used the installer you linked just to make sure), both crash when using madvr but not other renderers. Tried opening madHcCtrl after I cleanly install madvr (with settings reset) first to see if that helped as I saw that mentioned in the AVS thread. Tried checking my system for errors with SFC and DISM commands. Nothing has worked and I'm stumped!

I've used MadVR for years and years, never encountered this.

Only thing I can come up with is that it might have something to do with the Cumulative updates MS pushed on 2/3, guess i'll have to try reverting those next since nothing else is working, but I've never had an update rollup break something like this before.

[VBB]

Hmm, that sucks. I can tell you that I also have those latest cumulative previews installed, and I don't have your issues. Same Nvidia driver, too. Hope you get it sorted out soon.

[mclingo]

I sincerely thank you for the replies, but I have tried that over and over again. Tried rebooting. Tried re-installing my video drivers. reinstalled every program in my video playing stack and reset all their settings. tried madvr stable (same as your link) and even the test build, freshly extracting the files each time in case I was making some kind of error. tried mpc-be and latest stable mpc-hc (used the installer you linked just to make sure), both crash when using madvr but not other renderers. Tried opening madHcCtrl after I cleanly install madvr (with settings reset) first to see if that helped as I saw that mentioned in the AVS thread. Tried checking my system for errors with SFC and DISM commands. Nothing has worked and I'm stumped!

I've used MadVR for years and years, never encountered this.

Only thing I can come up with is that it might have something to do with the Cumulative updates MS pushed on 2/3, guess i'll have to try reverting those next since nothing else is working, but I've never had an update rollup break something like this before.

I've had this issue once a long time ago when I used to host MADVR on my C windows drive, I think the registry entries got currupted somehow.

try throwing everything at it in one go.

remove MADVR
remove GFX your drivers
reboot
reinstall known working GFX driver
reinstall madvr in a new location on another hard drive, use default settings, dont change anything just to see if plays stable.

[jkauff]

Another approach to try would be to change the permissions on the c:\madVR folder. Like most things on the C: drive, it's probably set to Read Only, which means madVR can't write the Settings file to the folder.

[clsid]

It stores the settings in the Registry:
HKEY_CURRENT_USER\Software\madshi\madVR

The settings .bin file is just an extra backup copy of the settings. It is not required.

[Zulithe]

I've had this issue once a long time ago when I used to host MADVR on my C windows drive, I think the registry entries got currupted somehow.

try throwing everything at it in one go.

remove MADVR
remove GFX your drivers
reboot
reinstall known working GFX driver
reinstall madvr in a new location on another hard drive, use default settings, dont change anything just to see if plays stable.
Fixed it. What finally did it was disabling my internet, booting into safe mode and using DDU to completely remove my nvidia drivers, reboot, install latest drivers, reboot, enable internet, and now it works. Had to go HAM on the drivers, something got broken somehow. All done. Thanks for the replies all.

[Dogway]

Is there a way to show file title OSD on exclusive fullscreen? Looked for it on keymaps so probably not? or through pixel shaders maybe (MPC-HC)?

[zveroboy]

2nd EDIT: Mathias posted a fixed build: http://madshi.net/madVRhdrMeasure123b.zip
Statistics show 1920x2160 instead of 1920x1080.
Why? Is it issue?

Please tell me on which site can I get test builds of the madVR?

[jkauff]

It stores the settings in the Registry:
HKEY_CURRENT_USER\Software\madshi\madVR

The settings .bin file is just an extra backup copy of the settings. It is not required.
I know, but does it try to write settings.bin, and does it fail gracefully if it can't?

Just curious, since the OP solved his problem.

[Asmodian]

I know, but does it try to write settings.bin, and does it fail gracefully if it can't?


Yes, if it cannot write the user doesn't even know; settings.bin is simply not created.

[VBB]

Statistics show 1920x2160 instead of 1920x1080.
Why? Is it issue?

Please tell me on which site can I get test builds of the madVR?

No issues with this build. For new builds, use the same link and simply change the number. For example, the next one will be called "madVRhdrMeasure124.zip".

If you want to know more about the testing, see here https://www.avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector.2954506/

[zveroboy]

No issues with this build.
LAV-Video-Filter ---> 1920x1080 (No issue)
MPC-BE (Internal Filter) ---> 1920x2160 :(

For new builds, use the same link and simply change the number. For example, the next one will be called "madVRhdrMeasure124.zip".
Thanks alot!

[stmhlm]

I'm unable to load a custom arve curve for tone mapping in madVR.


I understand that madVR's own tone mapping is better since it's dynamic, but figured I could try loading arve curves into madVR to see how they would perform in my projector.

Once I select 'arve custom curve' in 'tone mapping curve' an explorer window opens where it lets me select the .conf file, once selected/loaded by pressing 'Open', madVR instead selects 'BT.2390'.

If I select 'BT.2390' from the list, I cannot 'Apply' it, because it has already been applied by trying to load the custom arve curve.


Support for arve curves was implemented in v0.92.13, I've tried that build, and all builds up to the most recent build, no luck at all.

You cannot load arve curves with the latest HDR build installed/patched, so obviously those builds are not installed.


I've tried two different curves, one with 'eo' set to 'eotf_pq' and one set to 'eotf_gamma_2_4' but none seem to bite.

Can anyone of you replicate the issue?


I'm using Javs V3 curve, from AVSforum, specifically the '1200nitv3' curve, you'll find it below.

https://www.dropbox.com/s/xbwz9fyt628ea1x/Javs%20Curves%20v3.zip?dl=1


Thanks!

[slappy]

Can someone confirm that new AMD cards like the 6800xt are supporting 3D mvc mkv. I need to upgrade my system and nvidia dropped the 3D support on their drivers.

[mclingo]

the 5700 series does so it should do, there has been no announcement about pulling this, all current drivers still work on my card

[HillieSan]

how is the situation on hdr switching for amd rx6000 and nvidia rtx3000? right now I have a rx480 and it works without problems

also the 23.976hz for the nvida rtx has improved? in the past I had a 9600gt and it was a disaster compared to amd

sorry guys but it's hard to get this fresh new information

Hi, I had a similar question regarding the AMD RX480 not long ago. I went to the nvidia rtx 3060 Ti because the newest AMD cards were not available and the prices were high sky. Also madvr is fast on nvidia.

NVidia runs correct and stable out of the box with madvr. No cru required. Only Windows doesn't switch to HDR automatically. It's known to be a driver issue.