madVR - high quality video renderer (GPU assisted)

[dvd1]

restore default settings madVR but nothing D3D11 only D3D9
how to get D3D11?

[AngelGraves13]

The TV is being exclusively used for video/movies and absolutely nothing else.

...

I do not really understand what is wrong.

Have you setup the Nvidia control panel for "fullscreen video" under Adjust desktop color settings because if not then it will select Auto and not give you full range.

[huhn]

If you're sending 12bits there is no dithering by the GPU when sending YCC 4:4:4 as MadVR is dithering down to 10bits.

that needs dithering too obviously.

you missconfusoin about TV FULL and Nvidia FULL ..

You need to understand it is also for PS3 and PS4 and XBOX 360/One.

If you put TV Full which is Low on LG at least same for samsung my guess, and Nvidia Full , you will have crashed dark. why ? because the TV is doing 0 -255 and when Nvidia also doing that it is crashing the black. you will crash you black if you go LOW and FULL on PS4 and Also PS3 ..

You need to choose one, preferably choosing LOW on the TV and on everything else Limited or AUTO , because then when changing between HDR or such the signal will always stay with the TV and the program won't mess it up randomly .


So last words is to use TV Low/Full , Nvidia Auto/Limited , Madvr 0-255 . for me it works perfect, the annoying brightness that on 16-235 is not visible, you can see all the bar between 17-25

no he is absolutely right. i have no clue what the hell is going wrong at your side.
not sure what your low setting is doing but you can clearly use a gaming console with full range and TV full range.

The TV is being exclusively used for video/movies and absolutely nothing else.

However, none of the following work:

TV Full, NVIDIA Full, madVR Full: Extremely dark, like "Full" is being applied 3 times.
TV Limited, NVIDIA Limited, madVR Full: Looks like "Full" and not "Limited" in movies.
TV Limited, NVIDIA Full, madVR Limited: Looks too dark, like "Full is being applied 2 times.

The only one working is:

TV Limited, NVIDIA Limited, madVR Limited

Additionally, as before, for some reason the TV needs to be set to "Full" to provide a "Limited" range, and "Normal" provides a darker image - this applies in all cases.

I do not really understand what is wrong.

well not sure if you ever used a simple test pattern or if your screen is simply broken but "TV Limited, NVIDIA Limited, madVR Limited" is never ever be correct.

just to be sure what nvidia setting are you setting to limited there are some you simply don't use and leave at default

Have you setup the Nvidia control panel for "fullscreen video" under Adjust desktop color settings because if not then it will select Auto and not give you full range.

this shouldn't do much if anything with madVR.

[Manni]

that needs dithering too obviously.


Can you explain? MadVR is sending 10bits and the GPU 12bits. Why would the GPU do any dithering?

[nevcairiel]

Can you explain? MadVR is sending 10bits and the GPU 12bits. Why would the GPU do any dithering?

madVR is sending 10-bit RGB, if the GPU converts that to YCbCr for output, it hopefully does it in high enough precision that it "has to" dither afterwards to 12-bit.

[Manni]

madVR is sending 10-bit RGB, if the GPU converts that to YCbCr for output, it hopefully does it in high enough precision that it "has to" dither afterwards to 12-bit.

Thanks, makes sense.

[el Filou]

However, none of the following work [...]

The only one working is:

TV Limited, NVIDIA Limited, madVR Limited

Additionally, as before, for some reason the TV needs to be set to "Full" to provide a "Limited" range, and "Normal" provides a darker image - this applies in all cases.

I do not really understand what is wrong.
Are you on Windows 10 Creators Update by any chance?
I was running RGB Full on the whole "chain" without any issue previously and since updating to Windows 1703, RGB Full output is buggy on my 1050 Ti (whites are clipped and blacks are dark gray). I tried several drivers and full cleanup of driver files and registry, but it's always buggy.
I filed a bug report via NVIDIA driver survey page last week but haven't heard back yet, I hope they look into it because I'm stuck with RGB Limited until it's fixed. :(

[austinminton]

because the TV is doing 0 -255 and when Nvidia also doing that it is crashing the black. you will crash you black if you go LOW and FULL on PS4 and Also PS3 ..


Please explain a bit more what you mean. Why would Nvidia crush the blacks in this scenario?

I have everything set to full on my PC (lav, madvr, nvidia) and my tv set to auto (which sets to full when it receives PC signal - Sony 75Z9). I have tried a few patterns and don't notice black crush.

I am on creators update with 385.41 drivers.

[x7007]

Please explain a bit more what you mean. Why would Nvidia crush the blacks in this scenario?

I have everything set to full on my PC (lav, madvr, nvidia) and my tv set to auto (which sets to full when it receives PC signal - Sony 75Z9). I have tried a few patterns and don't notice black crush.

I am on creators update with 385.41 drivers.


For example there is an issue with HDR and Dolby Vision if you manually change the signal the TV receive because if you set it Manually then the TV can't enter HDR mode, it needs to change from YCbcr 4:4:4 to 4:2:2 , and when you set it manually it Ycbcr 4:4:4 then it won't be able to change, and who want to change every time from mode to mode. not this is the only way you will get Full Range because if I try to set on the TV to AUTO it will use 16-235 , so I need to keep it on LOW. if I try to put from Nvidia like what I talked before on Manual and choose Full Range, all the desktop screen becomes crashed Black. if you check AVSForums, they also say, if you put LOW On the TV you need to choose Limited on the PS3/4 .. it's that simple, you can also watch youtube, because you can't use both, it is just compability mode, you crash your black if you put both of them. I had a TV which could only be Limited without any way to change the TV options, but it couldn't show Full Range. so I just put Limited on everything . MadVR , PS3, Nvidia , so I won't have crashed black, if you can only run with Limited and it works right then your TV or device doesn't support Full RGB , it's simple enough .

Have you setup the Nvidia control panel for "fullscreen video" under Adjust desktop color settings because if not then it will select Auto and not give you full range.

Does this really work ? because I remember trying it, but maybe this effect the TV Black AUTO ? does anyone else changed it from AUTO to Full Screen Video ? what about the other settings there, what if you play a game, does it ok to keep it on Video ?

[AngelGraves13]

For example there is an issue with HDR and Dolby Vision if you manually change the signal the TV receive because if you set it Manually then the TV can't enter HDR mode, it needs to change from YCbcr 4:4:4 to 4:2:2 , and when you set it manually it Ycbcr 4:4:4 then it won't be able to change, and who want to change every time from mode to mode. not this is the only way you will get Full Range because if I try to set on the TV to AUTO it will use 16-235 , so I need to keep it on LOW. if I try to put from Nvidia like what I talked before on Manual and choose Full Range, all the desktop screen becomes crashed Black. if you check AVSForums, they also say, if you put LOW On the TV you need to choose Limited on the PS3/4 .. it's that simple, you can also watch youtube, because you can't use both, it is just compability mode, you crash your black if you put both of them. I had a TV which could only be Limited without any way to change the TV options, but it couldn't show Full Range. so I just put Limited on everything . MadVR , PS3, Nvidia , so I won't have crashed black, if you can only run with Limited and it works right then your TV or device doesn't support Full RGB , it's simple enough .



Does this really work ? because I remember trying it, but maybe this effect the TV Black AUTO ? does anyone else changed it from AUTO to Full Screen Video ? what about the other settings there, what if you play a game, does it ok to keep it on Video ?

On my Sony TV, if I leave it on Auto, my TV treats the signal like a PC input and doesn't allow me to change color temperature to Warm 1 or Warm 2 (which is needed for proper viewing). I'm also unable to apply any motion estimation (not that I do), so it's basically for minimal input lag. The black levels are also different on Auto, where everything looks washed out. Setting it to fullscreen videos basically allows full dynamic range.

[oddball]

Do you think we will ever get proper HDR switching on MadVR using AMD GPU's?

[oddball]

Hi, has anyone HDR with Polaris (RX4x0) working, with madvr automatic?
If yes, can you plz share your config.

Amd Driver Version and Settings
Lav version and Settings
MadVR Version and settings
used Player

Thx

Nope! It has never worked. I have to manually switch to HDR mode in Win10 settings and make sure fullscreen exclusive is unticked (undesirable for most playback). Then tick it and disable HDR mode after playback.

[austinminton]

For example there is an issue with HDR and Dolby Vision if you manually change the signal the TV receive because if you set it Manually then the TV can't enter HDR mode, it needs to change from YCbcr 4:4:4 to 4:2:2 , and when you set it manually it Ycbcr 4:4:4 then it won't be able to change, and who want to change every time from mode to mode. not this is the only way you will get Full Range because if I try to set on the TV to AUTO it will use 16-235 , so I need to keep it on LOW. if I try to put from Nvidia like what I talked before on Manual and choose Full Range, all the desktop screen becomes crashed Black. if you check AVSForums, they also say, if you put LOW On the TV you need to choose Limited on the PS3/4 .. it's that simple, you can also watch youtube, because you can't use both, it is just compability mode, you crash your black if you put both of them. I had a TV which could only be Limited without any way to change the TV options, but it couldn't show Full Range. so I just put Limited on everything . MadVR , PS3, Nvidia , so I won't have crashed black, if you can only run with Limited and it works right then your TV or device doesn't support Full RGB , it's simple enough .

Thanks, that makes complete sense now. Clears it all up. Sorry for full quote but I really couldn't edit anything out of it without losing valuable information.

[Asmodian]

Looks like 4K60p8bits RGB is not a valid HDR mode, and the GPU should not allow it instead of forcing it.

8-bit HDR10 works fine on my TV, Nvidia disallowing it would anger me.

However, 8-bit Dolby Vision HDR doesn't work for me, with similar results to your 8-bit HDR. :(

I wish HDR had better standards so different displays and drivers had the same behavior. :mad:

[Manni]

8-bit HDR10 works fine on my TV, Nvidia disallowing it would anger me.

However, 8-bit Dolby Vision HDR doesn't work for me, with similar results to your 8-bit HDR. :(

I wish HDR had better standards so different displays and drivers had the same behavior. :mad:

Please can you remind me your TV model that works in HDR10 RGB 8bits at 4K60p?

Thanks!

Re Dolby Vision, are you testing with a Dolby Vision source, a Dolby Vision display, and everything in between (AVR, switch, VP, etc) supporting Dolby Vision passthrough? Otherwise, it won't work.

[austinminton]

HDR10 8bit 4K60 RGB works for me too. I can easily verify its 4K60 HDR10 at 8 bits (using the TV menu). About the RGB, I have that set in nvidia control panel so assuming its outputting RGB, but I don't think I can easily verify that on the TV. Will dig into the menus to check that as well.

Its a Sony 75Z9D.

[madshi]

I am using DVBViewer latest Version.

i did not remove those files amd_ags_???.dll, both are in the madvr folder.(should i ?)

i have also try´d now without AVRm direct to TV but still the same no HDR.
Doesn't work. Nevever worked. Cleared out MadVR several times. Been through a few driver updates and now a change of GPU (RX 480 to RX Vega 56). Still the same issue.
I am guessing you are an Nvidia owner. I have yet to hear of anyone with an AMD GPU getting HDR working correctly in FSE nor auto switching to HDR when HDR is set to off in display settings.
I think I found the reason for the problems. Will hopefully be fixed in the next build.

Another Question, over testing i was seeing Travel 4K Channel on Astra who is HLG Testchanel (4K 50Hz BT2020, HLG) i guess there is no support for now. OSD did not show a sign of HDR.
HLG is not supported yet.

You're right, the players I use (MPC-BE, MPC-HC, JRiver MC) don't completely close. I had tried a workaround, adding the default 1080p71 mode to the list madVR can use, but it didn't work. Turns out madVR calls this rate 71, as does Windows, but Nvidia calls it 72. Once I added 1080p72, mode switching works fine. Doesn't solve the original problem, but I'm getting what I want.
For those "don't completely close" problem you could try to create a freeze report (Ctrl+Alt+Shift+Pause/Break). Maybe I can see where the media players are stuck. Please don't attach the freeze report to this forum. Instead upload it somewhere else and link to it here.

Another totally different problem: madVR never manages to optimize my custom rates. I follow the instructions, play a video at that resolution for 30 minutes or more, but when I click Optimize again I get the original popup, never the analysis results popup. I'm using a native driver for the monitor, using a GTX 1060 with the latest driver. EDID is read with no problem.
Did you create the custom mode with the madVR custom modes tab? Or did you use the Nvidia custom mode control panel? Currently measurements are only recorded if the custom mode was originally created by madVR's custom mode tab.

No difference at all between "let madvr decide" and "passthrough hdr".

Yes, if I toggle that option the picture dims or lights up.

I think my problem is that I'm not seeing the Wide Colour Gamut colours -I'm just seeing rec709 colours with hdr.

Just tested a 'Patriot Day' sample, and I'm getting the same problem. Many of the colours that are visible using the TV's own player (via usb) are not visible on PC with mpc-hc+madvr.

I also tried with everything set to 8 bit and no dithering in madvr, didn't make any difference.
I'm struggling to have a good idea of what the problem could be. If toggling the "send HDR metadata" switch results in a visible change in "passthrough HDR content to the display" mode, then obviously madVR is able to successfully switch your TV into HDR mode. In "passthrough" mode madVR simply outputs all pixels more or less untouched, so there's not so much that could go wrong on madVR's side.

The best explanation would be that your TV simply doesn't handle RGB HDR input signals correctly. But you said your Xbox when set to RGB looks fine, doesn't it? Are you 100% sure that your Xbox outputs RGB? Maybe it "secretly" switches to YCbCr when playing HDR content? Does your TV have an "info" screen which shows if it's receiving RGB or YCbCr, and if it's in SDR or HDR mode?

I tried the new D3D11 decoder on LAV (0.72.2.74). On a perfectly running setup of DXVA2 copyback, just changed it to D3D11 and left hardware device at automatic. MPC-HC (1.7.13-x64) now launches and madvr resolution change kicks in, but the video doesn't play at all. Just stays paused. Ctrl-J doesn't work. Even if I go into windowed from FSE, it stays paused and doesn't play. What am I missing please?
Can you please create a freeze report (Ctrl+Alt+Shift+Pause/Break)? Please don't attach is to this forum, but upload it somewhere else and then link to it here.

Oooh, screenshots in DAR with xysubfilter subs. TY madshi.
:)

@madshi - as requested.

https://drive.google.com/file/d/0B32qC2QOKOo3S3J5Q3pld2FYUjg/view?usp=sharing

this was created using JRiver MC23 64bit, but the 32bit version has the same issue: MVC3D playback does not switch to FSE. It does in MC22 without issue.
The problem is that in order to 3D playback, madVR automatically switches to 1080p23. However, MC23 stays at 4K resolution, and also tells madVR to render to 4K resolution. In order for madVR to switch into FSE mode, the madVR rendering window must match the display resolution. So this is a bug in MC23 which needs to be fixed by the MC23 devs.

Hey madshi, quick question regarding the Nvidia video output. Reading your first post, it seems that RGB is the way to go (no needless yuv to rgb internal conversion). However, now that HDR is here, being able to output 10bit 4k content is a must. Unfortunately, RGB 4k60@10bit isn't possible yet
IMHO stick to 8bit RGB, unless your TV doesn't handle 8bit RGB properly. Thanks to dithering, 8bit output is just fine, even for HDR. Of course 10bit would be better, but it is what it is, and IMHO 8bit RGB is the best compromise in this situation.

madshi, the new version started to close video files noticeably slower. It used to be almost instantly but now it takes several seconds when I exit the player or just close the video. It won't be a big problem, but the same delay also takes place on switching between subtitle tracks, which becomes inconvenient when I need to switch between them often. Can something be done about this?
Can you please create a couple of freeze reports (Ctrl+Alt+Shift+Pause/Break) while the player tried to exit? Please don't attach the freeze reports to this thread, but upload them somewhere else and link to it here.

in which case should I change (in device properties) from "pc levels 0-255" to "tv levels 16-235"? I set my Nvidia card as RGB limited (connected to my tv) and my Tv as limited (black level: low) but if I set in madvr to "tv levels 16-235" the image is washed. What am I doing wrong?
See FAQ in 2nd post of this thread.

There is another weird config: with 1080p50, 1080p30, 1080p29, 1080p25, 1080p24, 1080p23 I had 50.0Hz, instead of the more reasonable 29.97Hz!
It's questionable which is the best mode in this situation. Because madVR thinks deinterlacing might be necessary, it prefers 50Hz over 29.97Hz because if deinterlacing is needed, with 50Hz less frames would have to be dropped compared to 29.97Hz.

Here is the freeze report for when the player completely freezes.
https://pastebin.com/S3r9K4t3

But for some reason I just could not make it freeze again while in debug mode. I tried for 30 minutes straight.
That's what I feared. I may have to modify the way I handle native D3D11 decoding a bit to workaround this issue. For now if you get this problem, please use D3D11 copyback or some other decoder, as a temporary workaround.

Using MPC BE I get perfect sync for my display 23.976hz using madvr custom refresh rates using 10bit & 8bit

However,

Using DSplayer I only get perfect sync using 10bit. if I set madvr display output to 8bit, refresh rates is only 23.970. This results to frame drop every 3 minutes
Sounds weird. Not sure why that happens. Why not always using 10bit, then, though?

Alright, I managed to get it working better with:

madvr: limited
gpu: full
tv: limited

I've read that this is an acceptable config so if someone wants to confirm or deny that for me I'd appreciate it. It seems to be working.
Sounds good to me. See FAQ in the 2nd post of this thread.

For me it's

Madvr - 0-255
gpu - limited
Tv - Low which is 0-255

Everything seems fine , better than the 16-235 I had in MadVr on the old LED philips TV .
On my LED TV I had

Madvr- 16-235
gpu - limited
These are bad settings - unless you really have no other choice. See FAQ in 2nd post of this thread.

[madshi]

MadVR tends to crash when playing a HEVC video, using D3D11 (native / copy-back).
This does not happen using EVR.

Crash report: https://mega.nz/#!Ew8ymaqA!cq0nTDN6M5dkIWKVAyfHuXxNRADn5Fsy36k6ePHSaZM
Looks like a crash in the Intel GPU driver. You say this also occurs in D3D11 copyback mode? If so, then it's unlikely to be madVR's fault. The crash definitely is with D3D11 native decoding, though, which currently EVR doesn't support. It does look like a bug in the Intel GPU driver. So I'd suggest trying different GPU drivers.

If you also get crashes in copyback mode, can you please also upload a crash report for that?

The crash happens in the middle of playback? Or after you've done something, like seeking, stop/play etc?

You're using an outdated madVR build, though. I don't think updating to the latest build will help, but it might still be worth a try.

freeze videos (all formats) and player when this is in pause and after, move the seekbar when using D3D11.Works perfectly with native / copy-back
Can you please create a freeze report (Ctrl+Alt+Shift+Pause/Break)? Please don't attach it to this forum, but upload it somewhere else and then link to it here.

I wish madVR wouldn't hang every program I use it with. But that's too much to wish for.

Both ProgDVB and Potplayer hang regularly.
Then please create freeze reports for me (Ctrl+Alt+Shift+Pause/Break). Please don't attach them to this forum, but upload them elsewhere and link to them here.

I'm trying to let madvr measure video playback. But it is still displaying "not measured yet" in this video mode. I followed the four steps. What am I doing wrong?
Did you create the custom modes with the madVR custom mode tab? Or did you create them with the Nvidia/AMD/Intel custom mode tool? Currently madVR only records measurements if you created the custom mode with the madVR custom mode tab.

TV: sony ex700
graphics card: msi rx480
blueskyfrc version: v2.81
madvr version: 0.92.2 and 0.92.3
win 10

usually average stat is 12ms ,if I use madvr 0.92.2 , every 5- 10 seconds will burst into 20 ms, and then dropped frames, and turn off blueskyfrc on the normal, some people have encountered the same problem?
(madvr 0.92.1 will not)
Are you 100% sure that the problem does not occur with v0.92.1, but does occur with v0.92.2? I'm asking because the differences between the two versions are fairly small. If you're 100% sure, then could you please try this:

1) Please try using the madVR.ax/madVR64.ax files from v0.92.1 together with all the other files from v0.92.2. Does the problem still occur?

2) Please try using the madVR.ax/madVR64.ax files from v0.92.2 together with all the other files from v0.92.1. Does the problem still occur?

3) Please make sure you test this with SDR content, not HDR content.

4) If you're using the new LAV D3D11 decoder, please try with some other decoder, just to be safe it's not related to that.

I'm sorry if I'm confusing people, but it simply isn't always true that sending RGB results in less conversions (or rather, as you stated initially, that sending YCbCr results in one more conversion).

It depends on the display, and it doesn't have to have a "broken" RGB input to behave that way. Most displays with color/tint controls do not apply these controls on an RGB input. They convert to YCbCr, apply the controls, then convert back to RGB.

I'm not saying it's not possible to apply these controls in YCbCr, just that it's not the way many displays behave.

Whether it's better to have the display do this extra conversion because it's done internally, I couldn't say, but personally, I check each output option with chroma multiburst patterns and with my eyes. RGB isn't always the best option. It needs to be tested, unless color/tint are disabled with an RGB input, in that case you know there is no internal conversion.
It will never harm to double check and trust your eyes. And you're right that some (many?) TVs apply their controls in YCbCr, so they might do RGB -> YCbCr -> RGB with RGB input. However, a few arguments why I still think that RGB is *usually* the better choice:

1) Even if the TV internally converts RGB input to YCbCr, there will still not be any more conversions overall. Because if your HTPC outputs YCbCr, madVR will do YCbCr -> RGB. Then the GPU driver will do RGB -> YCbCr. Then the display will do YCbCr -> RGB. That sums up to 3 conversions. If your HTPC outputs RGB, madVR will do YCbCr -> RGB, the GPU driver will do nothing. The display will do RGB -> YCbCr and YCbCr -> RGB. So same number of 3 conversions overall. So making the HTPC output YCbCr will not reduce the overall number of conversions.

2) GPU drivers often do conversions in inferior quality. So it's usually better to avoid anything that requires the GPU drivers to apply any sort of conversion.

3) Even if the GPU driver does a perfect RGB -> YCbCr conversion, the display won't know for sure which matrix was used by the GPU driver for the RGB -> YCbCr output conversion. Ok, at 1080p it's likely to be BT.709. But what happens if you send 4K to the display? With 4K YCbCr input, will the display use BT.709 or BT.2020 matrix to convert the YCbCr input to RGB? And does that match what the GPU driver did? If not, colors will get screwed up. This potential problem can never occur when sending the TV RGB.

4) Even if the GPU driver does a perfect RGB -> YCbCr conversion, it either potentially adds banding artifacts (if no dithering is used), or at least increases the noise floor (if dithering is used). In theory this can also happen inside of the TV, but at least the TV's internal processing doesn't suffer from HDMI bandwidth limitations. E.g. with 4Kp60, if the GPU converts RGB -> YCbCr, either the GPU has to drop chroma to 4:2:2 (loss of chroma resolution), or it has to output 8bit (strong chance of added banding artifacts because the GPU driver probably won't apply dithering in this situation). If we send 8bit RGB to the TV, none of these problems will occur outside of the TV. Of course they could still occur inside of the TV's own processing circuits, but it's somewhat less likely there.

5) There's still a chance the TV might not do RGB -> YCbCr -> RGB, but keep everything in RGB. Some TVs might be able to perform color processing stuff in RGB. And even if they don't, I know for a fact that several (many?) TVs have a special "PC" or "low latency" mode in which all the color processing stuff is disabled, anyway. For some TV models (e.g. my Sony 4K LCD) this is also the only way to get 4:4:4 chroma support.

But as I said above, I'll never disagree with testing all options and trusting your eyes, at least when talking about experienced users like you who know what they need to look for.

Still, my recommendation stays with RGB as the most likely solution for best image quality. See also FAQ in 2nd post of this thread.

As I also said, I switch to HDR manually on the display (I disable the manufacturer's mode because it's poor and I apply my own BT2020/ST2084 calibration), so it's not "expecting" anything. As far as it's concerned, it's receiving SDR. And this works fine with everything except 4K60p 8bits from MadVR.

The issue occurs when MadVR is passing through HDR, but the display doesn't know/care whether it's SDR or HDR. There is no metadata sent to the display anyway, so that it doesn't switch to HDR automatically and applies its buggy implementation.
One thing that's confusing me is this: From what you've written now and in the past, I think you're using "passthrough" HDR mode in madVR, and you have "send metadata" disabled? If that's the case, why does the JVC go magenta? I understand that the JVC might go magenta if it switches into HDR mode with 8bit RGB. But it shouldn't switch into HDR mode in the first place, with your madVR config, should it? Or am I missing something?

The TV is being exclusively used for video/movies and absolutely nothing else.

However, none of the following work:

TV Full, NVIDIA Full, madVR Full: Extremely dark, like "Full" is being applied 3 times.
TV Limited, NVIDIA Limited, madVR Full: Looks like "Full" and not "Limited" in movies.
TV Limited, NVIDIA Full, madVR Limited: Looks too dark, like "Full is being applied 2 times.

The only one working is:

TV Limited, NVIDIA Limited, madVR Limited

Additionally, as before, for some reason the TV needs to be set to "Full" to provide a "Limited" range, and "Normal" provides a darker image - this applies in all cases.

I do not really understand what is wrong.
There must be something wrong. My best guess is that your Nvidia config is somehow to blame. In the Nvidia control panel, have you reset everything to "neutral" settings? No fancy stuff active like skin tone "enhancements", private Nvidia color settings etc? I'd also suggest you try the "madLevelsTweaker" utility. Maybe it will solve this issue for you.

Please can you remind me your TV model that works in HDR10 RGB 8bits at 4K60p?
Works fine on my Sony 55" 4K LCD display, too. Tested with both AMD and Nvidia GPUs. Unfortunately my Sony only says 3840x2160p59, it doesn't report the color format or bitdepth it's receiving, so I can't say for sure if the AMD/Nvidia GPUs are actually outputting RGB or not.

[Grimsdyke]

Mpc-be is active, potplayer is just a big complicated player...

Maybe, but it can play the DTS-HD MA track from PHANTASM (US Blu-Ray) while MPC-BE can not !

[huhn]

Maybe, but it can play the DTS-HD MA track from PHANTASM (US Blu-Ray) while MPC-BE can not !

very unlikely a problem with mpc-be...

[Asmodian]

Please can you remind me your TV model that works in HDR10 RGB 8bits at 4K60p?

LG OLED55C7P

Re Dolby Vision, are you testing with a Dolby Vision source, a Dolby Vision display, and everything in between (AVR, switch, VP, etc) supporting Dolby Vision passthrough? Otherwise, it won't work.

Dolby Vision works properly with 12 bit RGB and the TV displays when it goes into Dolby Vision or HDR10.

[dvd1]

restore default settings madVR but nothing D3D11 only D3D9
how to get D3D11?
no one can solve the problem?

[madshi]

You need to enable "use Direct3D 11 for presentation" and "present a frame for every VSync" in the "madVR\rendering\general settings".

[dvd1]

in the info screen ctrl + j can i understand when the GPU is at the limit?

[dvd1]

https://s26.postimg.org/9ml1a2lvd/Catturaefe5.png (https://postimages.org/)
it is now active

https://s26.postimg.org/enx0p6ipl/Catturazdffgrr.png (https://postimages.org/)

starting a 1080p disables D3D11 and the 1080p always starts in D3D9
madVR does not keep the D3D11 settings

[madshi]

Those screenshots are from complex profile setups. Does the same problem still occur with default settings without any profiles? Which media player are you using? E.g. Kodi's dsplayer may overwrite madVR settings, depending on how you've configured it.

The GPU is at the limit when the average rendering time gets near to the "frame" interval (e.g. 41.71ms for 23.976fps movies).

[dvd1]

Those screenshots are from complex profile setups. Does the same problem still occur with default settings without any profiles? Which media player are you using? E.g. Kodi's dsplayer may overwrite madVR settings, depending on how you've configured it.
yes, the problem also occurs with default settings and no profile. I use DSPlayer with kodi
The GPU is at the limit when the average rendering time gets near to the "frame" interval (e.g. 41.71ms for 23.976fps movies).
and when i have 50fps?

[Manni]

It will never harm to double check and trust your eyes. And you're right that some (many?) TVs apply their controls in YCbCr, so they might do RGB -> YCbCr -> RGB with RGB input. However, a few arguments why I still think that RGB is *usually* the better choice:

1) Even if the TV internally converts RGB input to YCbCr, there will still not be any more conversions overall. Because if your HTPC outputs YCbCr, madVR will do YCbCr -> RGB. Then the GPU driver will do RGB -> YCbCr. Then the display will do YCbCr -> RGB. That sums up to 3 conversions. If your HTPC outputs RGB, madVR will do YCbCr -> RGB, the GPU driver will do nothing. The display will do RGB -> YCbCr and YCbCr -> RGB. So same number of 3 conversions overall. So making the HTPC output YCbCr will not reduce the overall number of conversions.

2) GPU drivers often do conversions in inferior quality. So it's usually better to avoid anything that requires the GPU drivers to apply any sort of conversion.

3) Even if the GPU driver does a perfect RGB -> YCbCr conversion, the display won't know for sure which matrix was used by the GPU driver for the RGB -> YCbCr output conversion. Ok, at 1080p it's likely to be BT.709. But what happens if you send 4K to the display? With 4K YCbCr input, will the display use BT.709 or BT.2020 matrix to convert the YCbCr input to RGB? And does that match what the GPU driver did? If not, colors will get screwed up. This potential problem can never occur when sending the TV RGB.

4) Even if the GPU driver does a perfect RGB -> YCbCr conversion, it either potentially adds banding artifacts (if no dithering is used), or at least increases the noise floor (if dithering is used). In theory this can also happen inside of the TV, but at least the TV's internal processing doesn't suffer from HDMI bandwidth limitations. E.g. with 4Kp60, if the GPU converts RGB -> YCbCr, either the GPU has to drop chroma to 4:2:2 (loss of chroma resolution), or it has to output 8bit (strong chance of added banding artifacts because the GPU driver probably won't apply dithering in this situation). If we send 8bit RGB to the TV, none of these problems will occur outside of the TV. Of course they could still occur inside of the TV's own processing circuits, but it's somewhat less likely there.

5) There's still a chance the TV might not do RGB -> YCbCr -> RGB, but keep everything in RGB. Some TVs might be able to perform color processing stuff in RGB. And even if they don't, I know for a fact that several (many?) TVs have a special "PC" or "low latency" mode in which all the color processing stuff is disabled, anyway. For some TV models (e.g. my Sony 4K LCD) this is also the only way to get 4:4:4 chroma support.

But as I said above, I'll never disagree with testing all options and trusting your eyes, at least when talking about experienced users like you who know what they need to look for.

Still, my recommendation stays with RGB as the most likely solution for best image quality. See also FAQ in 2nd post of this thread.


Thanks a lot for taking the time to list these, these are far better reasons for outputting RGB than stating that it requires one less conversion than YCbCr. I agree 100% with the above, and with the fact that RGB is the best option most of the time. It is the option I am using myself with my current set-up.

Re 3, I always select the correct calibration manually given the poor HDR implementation in my display, so not an issue here, but I agree that with a display with a good HDR implementation that's another strong point for RGB.


One thing that's confusing me is this: From what you've written now and in the past, I think you're using "passthrough" HDR mode in madVR, and you have "send metadata" disabled? If that's the case, why does the JVC go magenta? I understand that the JVC might go magenta if it switches into HDR mode with 8bit RGB. But it shouldn't switch into HDR mode in the first place, with your madVR config, should it? Or am I missing something?


That's precisely why I was trying to find out, especially as Asmodian confirmed that HDR 4K60p RGB 8bits worked with his nVidia GPU on his display.

I do use HDR passthrough, but the metadata stops with the Vertex so that the display doesn't switch automatically to its own poor HDR implementation. So the metadata is only used so the Vertex can decode and display it, then the Vertex "Disables HDR" i.e. doesn't send any metadata. For the display, it is receiving SDR, not HDR. But I apply my own BT2020/ST2084 implementation (using an ST2084 gamma curve made with Arve's tool and a BT2020 calibration) manually.

I have tested this without anything in the way (direct connection from the GPU to the JVC) and I get exactly the same result, so it's not the AVR/Vertex.

When I say Magenta, you have to understand that it's not a calibration issue. It's as if the only color available was magenta. So I get a black and magenta picture, as you wouyld get a black and white picture. The screen isn't fully magenta, I can still read what is displayed on the desktop or I can watch the video, it's just black&magenta. So not a calibration issue, or a wrong SDR/HDR mode issue. It's just a completely corrupted picture.

It's not MadVR per se, when I send the desktop whith the OS HDR set to "off", all is fine. It just goes magenta if I set the OS HDR option to on, or if MadVR switches to HDR on the fly (as the OS HDR option is usually set to off).

I think that my display is unable to accept that picture format, and when it's sent it goes in that magenta mode.

What I don't understand is why it does that even when the Vertex kills the metadata, because in that case the display should think it's receiving SDR. But when in that mode, disabling HDR in the Vertex has no effect, the screen is magentified anyway.


Works fine on my Sony 55" 4K LCD display, too. Tested with both AMD and Nvidia GPUs. Unfortunately my Sony only says 3840x2160p59, it doesn't report the color format or bitdepth it's receiving, so I can't say for sure if the AMD/Nvidia GPUs are actually outputting RGB or not.

Thanks, I'll add it to the list of displays potentially accepting this.

LG OLED55C7P


Thanks, I'll add it to the list of displays accepting this.


Dolby Vision works properly with 12 bit RGB and the TV displays when it goes into Dolby Vision or HDR10.

Sorry, I should have said so, Dolby Vision needs at least 10bits, preferably 12bits because that's one of it's advantages over HDR10. It has a 1080p layer that allows to extend the HDR10 layer from 10bits to 12bits (with UHD Bluray). If streaming, then it needs 10bits I think, as I don't think streaming sends a dual layer or is able to send 12bits.

I wouldn't expect Dolby Vision to work in 8bits, that's probably something that Dolby would forbid as it would cause too much banding for them.

[madshi]

yes, the problem also occurs with default settings and no profile. I use DSPlayer with kodi
Then most probably your DSPlayer/kodi settings are at fault. DSPlayer can be configured to overwrite the madVR settings, or to not touch the madVR settings. It seems to me that currently DSPlayer is configured to overwrite your madVR settings in such a way that D3D11 is always deactivated. I'm not a DSPlayer expert, though. I'd suggest that you ask in the DSPlayer support forum how you can stop DSPlayer from disabling D3D11 for you.

and when i have 50fps?
The frame interval is shown in the Ctrl+J OSD. Look for "frame xxxx ms".

It's not MadVR per se, when I send the desktop whith the OS HDR set to "off", all is fine. It just goes magenta if I set the OS HDR option to on, or if MadVR switches to HDR on the fly (as the OS HDR option is usually set to off).

I think that my display is unable to accept that picture format, and when it's sent it goes in that magenta mode.

What I don't understand is why it does that even when the Vertex kills the metadata, because in that case the display should think it's receiving SDR. But when in that mode, disabling HDR in the Vertex has no effect, the screen is magentified anyway.
Have you tried unchecking the "send HDR metadata to the display" option, when you pick "passthrough HDR content to the display" in madVR? Does the JVC still go magenta?

[madshi]

madVR v0.92.4 released

http://madshi.net/madVR.zip

* fixed: HDR metadata transport didn't always work with AMD GPUs
* fixed: potential crash issue introduced in v0.92.0
* fixed: possible rendering slowdown issue introduced in v0.92.2
* fixed: custom mode warning windows sometimes appeared in background
* added logging to help find why custom mode measurements aren't recorded
* screenshotting now uses NGU High instead of Very High
* screenshotting now has a 5 second timeout instead of 2 seconds
* slightly modified user interface for Nvidia custom mode creation
Do any of you guys still have *NEW* problems that were introduced with v0.92.x and which you didn't have with v0.91.x? I'm mostly interested in fixing such new problems right now, to make sure that v0.92.x is at least not any worse compared to v0.91.x.

[Fabulist]

Have you setup the Nvidia control panel for "fullscreen video" under Adjust desktop color settings because if not then it will select Auto and not give you full range.

I do have it set on "Movie" mode but having it set on "Auto" works the same, I guess it does detect it correctly or makes little difference.

well not sure if you ever used a simple test pattern or if your screen is simply broken but "TV Limited, NVIDIA Limited, madVR Limited" is never ever be correct.

just to be sure what nvidia setting are you setting to limited there are some you simply don't use and leave at default.

How is it not correct and why it should not be correct? If you are going for "Limited" range why there should be one of these set at "Full" instead of "Limited" range?

The setting I am talking about is found under "Change resolution". The "Use default color settings" will provide the TV with RGB limited signal, where limited is "Limited" under "Output dynamic range". The "Use NVIDIA color settings" which lets you customize the output is the same as the default as long as I use RGB limited.

Also, the black crushing x7007 is mentioning is exactly what is happening to me, it is like you reapply "Full" range, it is really weird.


Are you on Windows 10 Creators Update by any chance?
I was running RGB Full on the whole "chain" without any issue previously and since updating to Windows 1703, RGB Full output is buggy on my 1050 Ti (whites are clipped and blacks are dark gray). I tried several drivers and full cleanup of driver files and registry, but it's always buggy.
I filed a bug report via NVIDIA driver survey page last week but haven't heard back yet, I hope they look into it because I'm stuck with RGB Limited until it's fixed. :(

I am using Creator's but I never had any issues with RGB Full or Limited on 2 different monitors and PCs* or my TV, especially with grayed out blacks.

Tested signal output from:
680
760
1080 Ti

*With a fresh install on every single Windows 10 update.

Have you tried a fresh install or DDU? If there are no mentions from others of this problem, maybe there is something else going on, I would try DDU (Display Driver Uninstaller) first and then a fresh install, I would never expect anything from NVIDIA's support, especially if it is not a widespread issue.


5) There's still a chance the TV might not do RGB -> YCbCr -> RGB, but keep everything in RGB. Some TVs might be able to perform color processing stuff in RGB. And even if they don't, I know for a fact that several (many?) TVs have a special "PC" or "low latency" mode in which all the color processing stuff is disabled, anyway. For some TV models (e.g. my Sony 4K LCD) this is also the only way to get 4:4:4 chroma support.

I do have such a mode on my TV, but is there a way to confirm whether this is also the only way for me to get 4:4:4 chroma support? Is it possible for me to verify this?


There must be something wrong. My best guess is that your Nvidia config is somehow to blame. In the Nvidia control panel, have you reset everything to "neutral" settings? No fancy stuff active like skin tone "enhancements", private Nvidia color settings etc? I'd also suggest you try the "madLevelsTweaker" utility. Maybe it will solve this issue for you.


My NVIDIA config has always worked like that for dynamic range as far as I can remember, there are no special tweaks and setting besides the ones that relate to games, and a default and clean installation works the same as it did multiple drivers before this one. Absolutely nothing affected dynamic range for better or worse.

Enhancements and video player tweaks are not activated anywhere on the control panel and all settings let the video player do its thing. Other such settings that exist on Intel's embedded GPUs I do not have since my processor does not have an embedded GPU, the only thing installed is the NVIDIA's graphic card.

The utility you are mentioning is for forcing "Full" range but for the "Adjust video color settings" section right? I have set this to "With the video player settings" instead of custom. Wouldn't forcing another "Full" range make things even worse considering I have black crushing blacks like x7007 mentioned?

[huhn]

How is it not correct and why it should not be correct? If you are going for "Limited" range why there should be one of these set at "Full" instead of "Limited" range?

https://forum.doom9.org/showthread.php?p=1271416#post1271416

GPU full means do nothing to the signal.
GPU limited means take the full range signal and make limited out of it. the GPU always thinks the input is full range even with madVR at limited.

[Manni]

Have you tried unchecking the "send HDR metadata to the display" option, when you pick "passthrough HDR content to the display" in madVR? Does the JVC still go magenta?

I tried, it doesn't make any difference. The only way to make it work with MadVR is to get MadVR to convert to SDR. Then it works fine.

As I said, it's not a metadata issue, the Vertex receives the metadata, decodes it, displays it on the OSD, then kills the metadata. The display never gets it.

As far as the display is concerned, it's always receiving SDR, I am the one deciding which calibration should be applied (SDR REc-709 or HDR BT2020).

[khanmein]

@madshi Thanks, now the flickering is disappeared on windowed mode + OSD enabled + pause mode. (v0.92.4)

Once you pause, there's a quick flicker still but not a big deal.

[steakhutzeee]

Using Kodi and its video rules I use xysubfilter for material filling the screen (1.33, 1.78 and 1.85) and vsfilter for 2.35 and 2.40 movies.

It helps that I tend to have movies in HD and SD material is mainly 4:3.Thanks :)

Filling your screen, you mean when you have no black bars?

I don't understand if there is difference between standard black bars, and bars that is "part" of the movie...

Btw, you mean xyVSfiler?

Inviato dal mio ASUS_Z00LD utilizzando Tapatalk

[ashlar42]

Thanks :)

Filling your screen, you mean when you have no black bars?

I don't understand if there is difference between standard black bars, and bars that is "part" of the movie...

Btw, you mean xyVSfiler?Yes, I mean xyVSfilter.

As for the other question, for what concerns me the main problem with xyVSfilter is its unability to render subs at target resolution but rendering them at video resolution.

This is a problem for SD sources. I use these rules:

<subs videoaspect="1.33|1.66|1.78" filter="xysubfilter" />
<subs videoaspect="1.85|2.20|2.35|2.40" filter="directvobsub_(auto-loading_version)" />

This way I have xysubfilter in case where resolution might be low (1.33, 1.66) or where the screen is filled (1.78) and xyVSfilter (DirectVobSub) where I need to be sure subs are moved to the bottom of the screen and where I mostly (99%) have HD sources and so rendering at video resolution does not constitute a problem.
I hope it's clear. If it isn't, PM me or write in the Kodi thread that's been opened recently.

[steakhutzeee]

Yes, I mean xyVSfilter.

As for the other question, for what concerns me the main problem with xyVSfilter is its unability to render subs at target resolution but rendering them at video resolution.

This is a problem for SD sources. I use these rules:




This way I have xysubfilter in case where resolution might be low (1.33, 1.66) or where the screen is filled (1.78) and xyVSfilter (DirectVobSub) where I need to be sure subs are moved to the bottom of the screen and where I mostly (99%) have HD sources and so rendering at video resolution does not constitute a problem.
I hope it's clear. If it isn't, PM me or write in the Kodi thread that's been opened recently.Thank you :)

I'm going to look at it asap :)
I use mpc be, you think it's the same?

I'm on a 1920*1080 monitor, so filling the monitor videos are the ones with 16:9 aspect ratio? I'm not so good at it [emoji14]
You think i've to edit something here for best use with my monitor?

https://s26.postimg.org/g7x9fn1rp/Clipboard01.jpg (https://postimg.org/image/g7x9fn1rp/)

Talking about VSFilter, i installed it, and selected it in MPC BE, enabled at preferred DirectVobSub(auto loading) in External Filters, but when loading a file i don't see any icon an it's not in the list of active filters. What i'm doing wrong? I've all x64. EDIT: Selecting DirectVobSub instead of the auto-loading version, icon appears and filter is loaded fine. But i've the exact output i've with XySubfilter, subs are not in the black bars.

Same result with the Internal Subtitle Renderer, subs are on the video, not below.

Inviato dal mio ASUS_Z00LD utilizzando Tapatalk

[Fabulist]

https://forum.doom9.org/showthread.php?p=1271416#post1271416

GPU full means do nothing to the signal.
GPU limited means take the full range signal and make limited out of it. the GPU always thinks the input is full range even with madVR at limited.

I understand that but why is it better to use a mix of dynamic ranges instead of having Limited on NVIDIA CP, Limited on madVR, and Limited on the TV assuming someone wants Limited as the end result. Why does it make more sense to have a mix of dynamic ranges like el Filou suggested? I do not understand this.

Having NVIDIA CP set to Full and madVR at Limited is what gives me as a final result "Full". If I change madVR or the TV to "Full" I will get blacks crushes further and further.

You are suggesting otherwise and I cannot identify the source of the problem.

[Manni]

Have you tried unchecking the "send HDR metadata to the display" option, when you pick "passthrough HDR content to the display" in madVR? Does the JVC still go magenta?

Apologies for my earlier answer regarding this, I thought I had tested this and it didn't make any difference, but I double checked just to be sure and if I disable "send HDR Metadata to the display" I'm able to display 4K60p 8bits HDR in RGB (the screen doesn't go magenta).

This makes more sense (I understand why you were confused), what doesn't is that this metadata (which I do send usually so it can be decoded by the Vertex) isn't supposed to go past the Vertex, and most of it doesn't as my display doesn't switch to HDR automatically. If the metadata was sent, it would switch. I'm going to discuss this with HD Fury.

Just to clarify, my normal MadVR config is HDR passthrough with Send HDR Metadata enabled (so the Vertex can read it and display it).

It's good to know that if I disable the metadata in MadVR, I can get 4K60p GRB 8bits to display properly on the display, but I shouldn't have to do this with the Vertex.

I'll keep you posted, thanks again for the suggestion.

I've re-tested with the latest MadVR build but I have no reason to think that it's the new build that caused this difference in behaviour.

One unrelated issue with MadVR: I have an NTSC DVD (Klute), ripped into DVD Folder, that doesn't render properly with MadVR. If I select EVR-CP, everything is fine (menus and film), but with MadVR the Warner Bros logo plays fine, then I only see the selecting line of the menu (not the menu options themselves), and no video at all (black screen) with audio when playing the film.

I've tried other PAL and NTSC DVDs and I haven't found other titles behaving like this. I kown that earlier versions of MadVR used to work because I watched it a few months ago with MadVR and it worked fine. I couldn't say when it broke.

[madshi]

The utility you are mentioning is for forcing "Full" range but for the "Adjust video color settings" section right? I have set this to "With the video player settings" instead of custom. Wouldn't forcing another "Full" range make things even worse considering I have black crushing blacks like x7007 mentioned?
Why don't you simply give it a try? Shouldn't cost you more than 10 minutes. Maybe it works, and you just giving it a try will save us all precious time. If it doesn't work, the madLevelsTweaker also allows you to undo the tweak. So no harm done in any case.

@madshi Thanks, now the flickering is disappeared on windowed mode + OSD enabled + pause mode. (v0.92.4)

Once you pause, there's a quick flicker still but not a big deal.
Good to hear, although I'm not sure why it's gone.

I understand that but why is it better to use a mix of dynamic ranges instead of having Limited on NVIDIA CP, Limited on madVR, and Limited on the TV assuming someone wants Limited as the end result. Why does it make more sense to have a mix of dynamic ranges like el Filou suggested? I do not understand this.
See FAQ in the 2nd post of this thread.

if I disable "send HDR Metadata to the display" I'm able to display 4K60p 8bits HDR in RGB (the screen doesn't go magenta).

This makes more sense (I understand why you were confused), what doesn't is that this metadata (which I do send usually so it can be decoded by the Vertex) isn't supposed to go past the Vertex, and most of it doesn't as my display doesn't switch to HDR automatically. If the metadata was sent, it would switch. I'm going to discuss this with HD Fury.

Just to clarify, my normal MadVR config is HDR passthrough with Send HDR Metadata enabled (so the Vertex can read it and display it).

It's good to know that if I disable the metadata in MadVR, I can get 4K60p GRB 8bits to display properly on the display, but I shouldn't have to do this with the Vertex.
You're probably already aware, but just in case: Of course you can use profiles to workaround this issue. You can send metadata for framerates lower than 59fps, and disable metadata for 59fps+.

Anyway. I'm not 100% sure if the issue is with the Vertex. It could be. But it could also be a bug with the Nvidia GPU. In theory, when the Nvidia GPU is in HDR mode, all that should be different should be that the HDMI signal says "PQ" transfer function, and some SMPTE 2086 metadata. The actual pixels values and format should stay the same. But maybe the Nvidia GPU "secretly" also changes the pixel format? Maybe the GPU thinks that 60fps is too much for your HDMI connection and thus switches to YCbCr 4:2:0 or 4:2:2, but still reports RGB to the display? Or something weird like that. I don't really know, just some wild thoughts. Just wanted to let you know this, so you don't put the blame to 100% on the Vertex. It could be the Vertex, or it could be the Nvidia GPU/driver.

FWIW, which "max pixel clock" does your EDID report? (See JVC identification tab in madVR.)

Edit: You also have an AVR between HTPC and JVC, right? That one could also play a role.

I have an NTSC DVD (Klute), ripped into DVD Folder, that doesn't render properly with MadVR. If I select EVR-CP, everything is fine (menus and film), but with MadVR the Warner Bros logo plays fine, then I only see the selecting line of the menu (not the menu options themselves), and no video at all (black screen) with audio when playing the film.

I've tried other PAL and NTSC DVDs and I haven't found other titles behaving like this. I kown that earlier versions of MadVR used to work because I watched it a few months ago with MadVR and it worked fine. I couldn't say when it broke.
A while ago nevcairiel modified the way LAV Video Decoder transports subtitles to madVR. LAV used to draw the subtitles directly on top of the video. But a while ago nevcairiel changed that to send the subtitles to me by using the new subtitle interface (also used by XySubFilter). The advantage of the new logic is that madVR has greater control. I had asked nevcairiel for this change, so that I could move subtitles into the active video rectangle, when using the auto black bar detection etc. My best guess is that this issue was introduced with this change in LAV Video Decoder.

It could be a bug in LAV or in madVR, it's hard to say for me. Can you upload a sample, so nevcairiel and I can both double check?

[Manni]

You're probably already aware, but just in case: Of course you can use profiles to workaround this issue. You can send metadata for framerates lower than 59fps, and disable metadata for 59fps+.


I'm using profiles for many things but I didn't think of doing so for that. Thanks for reminding me. The issue is for 30+ (it works fine up to 445Mhz, then the magenta bug kicks in but only with HDR, I go up to 595Mhz with SDR content without any issue).


Anyway. I'm not 100% sure if the issue is with the Vertex. It could be. But it could also be a bug with the Nvidia GPU. In theory, when the Nvidia GPU is in HDR mode, all that should be different should be that the HDMI signal says "PQ" transfer function, and some SMPTE 2086 metadata. The actual pixels values and format should stay the same. But maybe the Nvidia GPU "secretly" also changes the pixel format? Maybe the GPU thinks that 60fps is too much for your HDMI connection and thus switches to YCbCr 4:2:0 or 4:2:2, but still reports RGB to the display? Or something weird like that. I don't really know, just some wild thoughts. Just wanted to let you know this, so you don't put the blame to 100% on the Vertex. It could be the Vertex, or it could be the Nvidia GPU/driver.


Agreed, I'm not blaming the Vertex either, they are not causing this, but they should/might be able to correct it the way you do when I tick the "do not send HDR metadata" in MadVR, since there is a similar feature in the Vertex that works fine, except it seems in this occasion.


FWIW, which "max pixel clock" does your EDID report? (See JVC identification tab in madVR.)


600Mhz. It's not the JVC, it's the Denon X7200WA that holds the identification, but that doesn't make any difference. As I said, I can go up to 595Mhz in SDR (or in HDR if the metadata is disabled in MadVR), so not a bandwidth issue. All cables/AVR etc fully compliant.


Edit: You also have an AVR between HTPC and JVC, right? That one could also play a role.


As reported, I've tested this by connecting the GPU to the JVC directly, and the magenta bug occurs with a direct connection, so not due to anything in between.


A while ago nevcairiel modified the way LAV Video Decoder transports subtitles to madVR. LAV used to draw the subtitles directly on top of the video. But a while ago nevcairiel changed that to send the subtitles to me by using the new subtitle interface (also used by XySubFilter). The advantage of the new logic is that madVR has greater control. I had asked nevcairiel for this change, so that I could move subtitles into the active video rectangle, when using the auto black bar detection etc. My best guess is that this issue was introduced with this change in LAV Video Decoder.

It could be a bug in LAV or in madVR, it's hard to say for me. Can you upload a sample, so nevcairiel and I can both double check?

Thanks, it might be the reason. I'll email you a private link to a sample as soon as I've made it.

[nevcairiel]

Can you upload a sample, so nevcairiel and I can both double check?

Making a sample of the menu of a DVD is also relatively easy:
Just take all the files from the DVD, but leave out the VOB files for the main title (usually VTS_01_*.VOB, the set with all the 1GB files)

[mrmojo666]

madVR v0.92.4 released

http://madshi.net/madVR.zip

* fixed: HDR metadata transport didn't always work with AMD GPUs



seems it works! now AMD is switchng my tv to hdr.

Am I Dreming? :)

[el Filou]

Having NVIDIA CP set to Full and madVR at Limited is what gives me as a final result "Full". If I change madVR or the TV to "Full" I will get blacks crushes further and further.

You are suggesting otherwise and I cannot identify the source of the problem.If your TV supports RGB Full and madVR + GPU + TV are set to Full and you still get crushed blacks then it means your TV brightness setting is not correct.

I am using Creator's but I never had any issues with RGB Full or Limited on 2 different monitors and PCs* or my TV, especially with grayed out blacks.

Have you tried a fresh install or DDU? If there are no mentions from others of this problem, maybe there is something else going on, I would try DDU (Display Driver Uninstaller) first and then a fresh install, I would never expect anything from NVIDIA's support, especially if it is not a widespread issue.
I've tried DDU and clean install of several drivers (Edit: I've also tried madshi's NVIDIA levels tweaker but it has no effect). I wanted to avoid reinstalling Windows from scratch because that's the only thing that doesn't work right and it's clearly an NVIDIA problem and there's so much to reconfigure for HTPC use but that might be my only hope. :(

[madshi]

Agreed, I'm not blaming the Vertex either, they are not causing this, but they should/might be able to correct it the way you do when I tick the "do not send HDR metadata" in MadVR, since there is a similar feature in the Vertex that works fine, except it seems in this occasion.
The Vertex can remove the PQ flag and SMPTE 2086 metadata, but if the Nvidia GPU does more than that (e.g. actually send out YCbCr 4:2:0 pixels, but claim to send out RGB) then the Vertex won't help there.

The weird thing is that the issue only appears to apply to 60fps. Why is that? I find it hard to understand that, except if some of the parties involved change their behaviour because they believe the bandwidth is too high for HDMI. And since you said that directly connecting the HTPC to the JVC shows the same behaviour, it's most likely to be the GPU.

But then, why does 60fps HDR seem to work for everyone else (e.g. me)? I can only guess that your JVC's EDID block contains something that confuses the GPU, and that my EDID block is different. But I'm wildly speculating here...

seems it works! now AMD is switchng my tv to hdr.

Am I Dreming? :)
Finally!! :) It was working for me all the time, so I had a hard time understanding why it failed for everyone else...

[Manni]

Making a sample of the menu of a DVD is also relatively easy:
Just take all the files from the DVD, but leave out the VOB files for the main title (usually VTS_01_*.VOB, the set with all the 1GB files)

Will send this as well, Madshi will forward to you.

Re the RGB 8bits at 4K60p issue, I've created profiles for HDR (if fps >= 30 and srcheight > 1080 then don't send metadata, else send metadata).

Works great :)

[oddball]

At last HDR switching works (even in FSE)! I can stop posting now :)

Thanks for sorting it (eventually) Madshi! *BOWS*

[madshi]

Yey! :)

[cyber201]

Hi madshi, thanks for your work.
I have a question. Now with the latest version of madvr, latest nVidia driver (385.69) and latest Win10 CU the screen goes automatically in HDR mode or not?
Because I have win10 CU but with old nVidia driver to make HDR switch automatically.

Now the issue is resolved or is a Windows 10 and driver issue?

Thanks

[madshi]

It works for me, and as far as I've heard also for the other Nvidia users. On a purely technical level, the latest Nvidia drivers are not as good as the old drivers were for HDR switching, but I've managed to workaround the driver problems, so you shouldn't notice a difference.