madVR - high quality video renderer (GPU assisted)

[el Filou]

could be bandwidth issues, do you have your PC set as 4:2:0 10 bit as it should be? [...] unless your desktop is 4:4:4 full RGB which hdmi 2.0 spec cant handle in 4k HDR mode.Sorry but this needs to be corrected:
- HDMI 2.0 can handle 4K 10/12-bit 4:4:4, but only at 24 Hz. Which is fine for movies. Use 4:4:4 whenever you can if available.
- 4:2:0 output should never be used with a PC, there is just no point to it you massively lose in image quality, and madVR's high quality chroma processing is wasted.
- 4:2:2 is not as horrible as 4:2:0 but still madshi has repeatedly said that, if your display device supports it, using 8-bit 4:4:4 should be better than 10/12-bit 4:2:2 with madVR.

[Moo]

Billy Lynn’s UHD - 60FPS..

I just ordered this disc to experiment with 60FPS. And it’s rippable now too.
I currently run 4:4:4 8bit on all BD and UHD. I’ll be curious to see what happens with this first and only 60FPS disc.

First post! Long time lurker!

Are we expecting another MadVR build anytime soon. I’d like to get to .10, but not if a .11 is due out in a few days..

[el Filou]

Yep, I know about it, there are exceptions to every rule. :)
HDR nature documentaries would also probably be 60p.

Edit: .10 dates from last week, so I doubt .11 will be released in the coming days.

[ABDO]

madVR v0.92.10 released
But I wanted to give you the chance to test both approaches to see if running both separately might be better for images quality or not. So please do test that and report back.

realy great work, after some tests, RCA/NGU fusion work perfect, the only different is it a little bit strong, so we can use it with one Less degree than the Separated RCA, thank you madshi.

[oldpainlesskodi]

"Posted by madshi
madVR v0.92.10 released
But I wanted to give you the chance to test both approaches to see if running both separately might be better for images quality or not. So please do test that and report back."

I cant use fuse, as I get a lot of image smearing my end (even at 1), but after playing about with my settings, it might be down to the new changes with NGU Sharp, combined with the fuse algo.

K

GTX 1080 Strix with the latest drivers, everything scaled to 4k.

Update - the madvr settings in Kodi have been updated, so will investigate further to rule in or out if this was causing my issue.

[mclingo]

Sorry but this needs to be corrected:
- HDMI 2.0 can handle 4K 10/12-bit 4:4:4, but only at 24 Hz. Which is fine for movies. Use 4:4:4 whenever you can if available.
- 4:2:0 output should never be used with a PC, there is just no point to it you massively lose in image quality, and madVR's high quality chroma processing is wasted.
- 4:2:2 is not as horrible as 4:2:0 but still madshi has repeatedly said that, if your display device supports it, using 8-bit 4:4:4 should be better than 10/12-bit 4:2:2 with madVR.

yeah I know the specs, but I get minor drops outs sometimes and snow when I use it with deep colour turn on, on my TV. You also then have to faff about changing your colour space between movie playback and desktop use, this is a ball ache, the difference is reportedly minuscule so I dont think its worth it.

If like me you have mixture of 8 and 10 bit movies, 420 10 bit should be better than 444 8bit for a movies which are actually encoded in 10bit, there should be less colour banding and smoother graduations.

i've also done exhaustive testing myself with 444 va 420 and never once seen a difference on any content that I could spot, so for me convenience wins.

If someone wants to upload a real world clip where the difference is undeniable apparent then I may change my mind however.

[ryrynz]

Are we expecting another MadVR build anytime soon. I’d like to get to .10, but not if a .11 is due out in a few days..

.11 won't change anything much anyway and takes only a minute, might as well.

[Georgel]

cant you just use Print Scr key on your keyboard?

No. Not ever. That is the worst way to take a screenshot, what do you do from there, paste it? I want to take thousands of screenshots to make wallpapers, just imagine the time it would take to process it all...

Use F5 in MPC-BE or MPC-HC. (Also there's a screenshot submenu in MadVR config.)

Thank you! This is exactly what I was looking for! That submenu is lovely, but it didn't say what key to use!

it depends on what you tell madVR about your display.
with passthrough it is most likely assume your TV will handle BT 2020 and will use that automaticly.
but it all comes down to your settings under calibration


depends on your video player for MPC-hc is is F5. unlike print screen it should "always" work.

Thank you, F5 is what I was looking for!

@madshi - Amazing work man. That screenshot was the last thing I really needed to make this work the way I wanted it to!!! Loving it!:D

[x7007]

Or bad GPU memory, other renderers might not show the same issues. I have often had memory issues that only showed up in one or two applications. They can be access pattern dependent and strange. It could be something else too, of course, but we really don't have enough information to do more than guess. I doubt a madVR setting could help. :(

I have watched a reasonable amount of UHD HDR blurays at this point (I have been buying them based on DeUHD's supported disc list :o) with madVR, Windows 10 1709, and current Nvidia drivers (currently 388.59). I have to manually turn HDR on and off in Windows but otherwise everything seems to work correctly.

It can't be memory errors . everything else works fine.

2 movies I tried The Dark Tower 2017 HDR and The Hitman Bodyguard 2017 HDR , both with dark scene had white dots the same exact place, there are no errors , there are no BSOD, this card works fine. what I am trying to find if it could be something else. what could it be if it's driver and not program , because it happens both Potplayer and MPC-HC with MadVR

[ryrynz]

the only different is it a little bit strong, so we can use it with one Less degree than the Separated RCA.

Can someone else confirm this? That really shouldn't be the case?

[arrgh]

but : why does the studdering only happen if I actually activate D3D11; if I deactivate it than I still get 3D but without studdering?

yes, I did post freeze reports, but you came to the conclusion that madVR is mostly gone already and you can not pinpoint a reason, why MPC-BE should hang.

Software setup : intel grahics driver 15.45.21.4821; LAV *.83 (nightly; with D3D11 as HW decoder); madVR *.10; mpc-be *.3181

http://www.bilder-upload.eu/thumb/a5d857-1513473326.jpg (http://www.bilder-upload.eu/show.php?file=a5d857-1513473326.jpg)

with this setup I have realized that 40-50% of my MVC-mkv do work smoothly, which is already a big success (here also the Player can be closed in a normal way);

but the second half shows mostly only a black screen; sometimes audio works, sometimes not; sometimes the player hangs after a short time (~30s); but always (whether it hangs or not) the player can only be closed via the Task-Manager;
since the working/not-working files are muxed over several years I would exclude a muxing problem...

here a statistics of such a file... the rendering times are extraordinary

http://www.bilder-upload.eu/thumb/a9b017-1513473928.jpg (http://www.bilder-upload.eu/show.php?file=a9b017-1513473928.jpg)

@madshi: I will send you via pm a link to 2 small 1 min samples, one working, one not; maybe you can identify what the difference is...; I will also send this to @Nevcairel, since I'm not sure where the problem really is...

[Georgel]

@madshi - is there any way you can give us control over how the screenshots are saved? I'd really love for them to be saved as PNG files, and to have control over the type of JPG they are saved as.

[huhn]

that's up to the player mpc-hc can do png.

@arrgh the file doesn't get decoded in real time. i wonder if it get's decoded at all.

[huhn]

It can't be memory errors . everything else works fine.

2 movies I tried The Dark Tower 2017 HDR and The Hitman Bodyguard 2017 HDR , both with dark scene had white dots the same exact place, there are no errors , there are no BSOD, this card works fine. what I am trying to find if it could be something else. what could it be if it's driver and not program , because it happens both Potplayer and MPC-HC with MadVR

a PC doesn't instantly crash if the Vram is corrupted it can work pretty much "fine".
i still haven seen a screen or if it is even shown on a screen shoot at all.

[Georgel]

So I'd love to have either PNG or level 12 JPG instead of what level is being used - that would really complete the thing I want to use it for.

How can one set what file type is saved, and at what level? Really need it now.

[huhn]

file -> save image (it not hidden or something) or alt+i.
the setting used there is used for f5 too.

[Moo]

Question about installing new versions. Can I just drop my old ‘settings’ file right into the newly installed folder structure? That’s how I’ve always done it. Is there a better/proper way?

[cork_OS]

Question about installing new versions. Can I just drop my old ‘settings’ file right into the newly installed folder structure? That’s how I’ve always done it. Is there a better/proper way?
I always just overwrite old madVR files with new build.

[mclingo]

hi, could really do with a final answer on this if anyone knows for sure, is 3D MVC possible without FSE on AMD cards or not, I know it is on NVIDIA.

Any chance you could finally put this to bed MADSHI?

[Clammerz]

If like me you have mixture of 8 and 10 bit movies, 420 10 bit should be better than 444 8bit for a movies which are actually encoded in 10bit, there should be less colour banding and smoother graduations.

This is not true. While a 10bit file is generally good depending on the encoder, 10bit output to the display is a crapshoot. MadVR outputting 8bit with high quality dithering can outperform a TV's processing engine (or graphics card drivers which may downsample behind the scenes) which may display banding with 10bit output.

You then go on to say that personally for yourself you don't see a difference and that is fine. But you shouldn't say "should be better" without qualifying so as not to confuse users which may not know the details behind the scenes.

Regarding your 3D issue, perhaps you should post about it on the bugtracker for a detailed record of the problem.

[Georgel]

file -> save image (it not hidden or something) or alt+i.
the setting used there is used for f5 too.

Thank you! This is lovely, I had no idea we could do this!

https://i.imgur.com/ch0ZGUc.png
(Default settings in MPC-HC)
Like huhn said, Alt+I lets you set whatever file type you want.

Thank you!

[mclingo]

This is not true. While a 10bit file is generally good depending on the encoder, 10bit output to the display is a crapshoot. MadVR outputting 8bit with high quality dithering can outperform a TV's processing engine (or graphics card drivers which may downsample behind the scenes) which may display banding with 10bit output.

You then go on to say that personally for yourself you don't see a difference and that is fine. But you shouldn't say "should be better" without qualifying so as not to confuse users which may not know the details behind the scenes.

Regarding your 3D issue, perhaps you should post about it on the bugtracker for a detailed record of the problem.

What you are essentially saying there is that people who think they are getting 10 bit might not be due to some background processing they might not be aware of and if this is the case then 8 bit + dithering will be better - well thats obvious isnt it.

Those with a true 10 bit panel and the ability to sent 10 bit to it will have the better picture though wont they as dithering is filling in data thats already there on 10 bit.


My 3D is working, I just have the well documented FES problems so I want to stop using it, I cant get 3d MVC to work without FES, I just want to know if i'm wasting my time trying to get it to work as it just doesnt work without FES.

[huhn]

what the difference between 10 bit and 8 bit? noise level
dithering is effecting the lowest bits the bit witch are already all over the place thanks to encoding and again are altered thanks to chroma scaling and YCbCr -> RGB conversation.
so now you go and do RGB dither it to 10 bit and makes the lowest bit more inaccurate give it the GPU that go and convert it to YCbCr down scale it to half the resolution 4:2:0 (yes it has half the resolution of RGB) and hopefully dither it yet again which again adds noise to the lowest bits.

but now the real fun guess what a display has to do to display an image. well it needs RGB guess what it is doing yet again...

RGB 8 bit shines most with TVs that properly support 4:4:4 and on these TVs chroma scaler have a bigger impact on the image.

RGB 8 bit can give you a more refined image while high bit deep can give you less dither noise with madVR and for not properly dithering renderer less banding.

[Manni]

what the difference between 10 bit and 8 bit? noise level
dithering is effecting the lowest bits the bit witch are already all over the place thanks to encoding and again are altered thanks to chroma scaling and YCbCr -> RGB conversation.
so now you go and do RGB dither it to 10 bit and makes the lowest bit more inaccurate give it the GPU that go and convert it to YCbCr down scale it to half the resolution 4:2:0 (yes it has half the resolution of RGB) and hopefully dither it yet again which again adds noise to the lowest bits.

but now the real fun guess what a display has to do to display an image. well it needs RGB guess what it is doing yet again...

RGB 8 bit shines most with TVs that properly support 4:4:4 and on these TVs chroma scaler have a bigger impact on the image.

RGB 8 bit can give you a more refined image while high bit deep can give you less dither noise with madVR and for not properly dithering renderer less banding.

This might be true with SDR, not with HDR. ST2084 needs at least 10bits in order to not produce any banding, especially in dark/bright areas, although it's more important in the content than for rendering.

My display is 12bits from end to end (input to panels) and 10bits output produces a better result than 8bits, especially in HDR. This is with my nVidia set to 4K23 RGB Full 12bits 4:4:4, as per my sig below.

[huhn]

and no you don't need 10 bit for HDR with no question at all nearly all TV out there have a 8 bit panel and no banding problems.
ST2084 is created so it creates less banding in the signal but pixel doesn't work like this. pixel are run pretty much the same with SDR or HDR because the pixel are changing there brightness with the number of transistors active for each sub pixel.

the problem with the real bit deep of panels is so bit that it is close to impossibile to test a panels bit deep with signal because a 8 FRC looks so close to a real 10 bit panel that the human eye and measurement device can't easily see the difference. test are so bad that even a VG248QE a clear 6 bit panel gets 8 bit a rtings even the specs say it is 6 bit... (and obviously visible to me with test pattern not real content)

and AFAIK there is no 12 bit panel on the market at all (professional screens are 10 bit too)and a very limited number of 10 bit panels.

if that'S the result you get feel free to sick to it.

[Manni]

and no you don't need 10 bit for HDR with no question at all nearly all TV out there have a 8 bit panel and no banding problems.
ST2084 is created so it creates less banding in the signal but pixel doesn't work like this. pixel are run pretty much the same with SDR or HDR because the pixel are changing there brightness with the number of transistors active for each sub pixel.

the problem with the real bit deep of panels is so bit that it is close to impossibile to test a panels bit deep with signal because a 8 FRC looks so close to a real 10 bit panel that the human eye and measurement device can't easily see the difference. test are so bad that even a VG248QE a clear 6 bit panel gets 8 bit a rtings even the specs say it is 6 bit... (and obviously visible to me with test pattern not real content)

and AFAIK there is no 12 bit panel on the market at all (professional screens are 10 bit too)and a very limited number of 10 bit panels.

if that'S the result you get feel free to sick to it.

The 2015+ JVC projectors have been confirmed to handle 12bits from the input to the panels. I don't care about flat panels so no idea if it exists for TVs or not.

[Asmodian]

This might be true with SDR, not with HDR. ST2084 needs at least 10bits in order to not produce any banding, especially in dark/bright areas, although it's more important in the content than for rendering.

The 2015+ JVC projectors have been confirmed to handle 12bits from the input to the panels. I don't care about flat panels so no idea if it exists for TVs or not.

You still do not need a >8-bit output for displaying HDR content without banding if you have high quality dithering. 8-bit output is a little nosier but that noise is very subtle. Keep 10-bit output from madVR and 12-bit from the GPU but don't expect it to make a significant difference.

Can you tell the difference between 8-bit and 10-bit from madVR with ordered dithering enabled (with the GPU and projector settings the same)?

[mclingo]

ok, so if there is no point using 10 bit do people recommend we all drop back to 8 bit and deploy 4:4:4 full RGB on our TV, how will this effect the playback of 10 bit HDR material?

[ryrynz]

Manni calm down on your excessive quoting. If you're replying directly after a post there's no need to quote.

[Asmodian]

It gets a lot more complicated when you bring GPU drivers and TVs into it. Some need 10 bit input to trigger their HDR modes, in that case you need the GPU to output 10+ bits.

The point is that being unable to get madVR to output 10-bit is fine for image quality, even if you are watching 10 bit HDR, and 8 bit RGB or YCbCr 4:4:4 is better than 10 bit YCbCr 4:2:2 or 4:2:0 unless your TV isn't good with RGB or 4:4:4 input (e.g. does its internal processing in 4:2:2).

[huhn]

The 2015+ JVC projectors have been confirmed to handle 12bits from the input to the panels. I don't care about flat panels so no idea if it exists for TVs or not.

ok, so if there is no point using 10 bit do people recommend we all drop back to 8 bit and deploy 4:4:4 full RGB on our TV, how will this effect the playback of 10 bit HDR material?

i can't remember but if i'm not mistaken AMD needs 10 bit for what ever reason or it will not send HDR.

so it is your choice if you go 4:2:2 10 bit or RGB 8 bit for 60 HZ which will be double dithered(and i tested the amd dithering to 6 bit is is pretty much random dithering not bad but not good too 10->8 bit should be the same but hard to test because it looks very similar)

windows 10 HDR shoudl work at 8 bit even with AMD cards.
The 2015+ JVC projectors have been confirmed to handle 12bits from the input to the panels. I don't care about flat panels so no idea if it exists for TVs or not.

it's hard to find a screen that doesn't support 12 bit input even TV from 2012 and older can do this easily.
and i wonder how people confirm stuff like this...

[mitchmalibu]

It's frankly not that difficult to test for yourself ... I watched a few HDR movies in 4:4:4 12bits and RGB 8bit, and frankly, without using comparison shots, I wouldn't be able to see any difference on a 2016 LG 4k OLED panel. 8bit RGB with a custom resolution to avoid frame drop seems like the better alternative from what I personally tried.
What madshi and others said makes sense : better reduce the number of conversions and drop down the bitdepth than try to push for max bitdepth and induce who knows how many post processing treatments on which you don't have any control.
Now, if only Nvidia gave us the possibility to make proper custom resolutions other than 8bit RGB ... :)

[Manni]

You still do not need a >8-bit output for displaying HDR content without banding if you have high quality dithering. 8-bit output is a little nosier but that noise is very subtle. Keep 10-bit output from madVR and 12-bit from the GPU but don't expect it to make a significant difference.

Can you tell the difference between 8-bit and 10-bit from madVR with ordered dithering enabled (with the GPU and projector settings the same)?

I don't want to dither if I don't have to. So yes, I prefer to keep 10bits output over 12bits GPU for 10bits HDR playback |(except for 60p where the driver drops automatically to 8bits). I don't see why I should add some noise when I don't have to.

I remember testing a while ago and the difference was subtle, but it was there for 10bits HDR content. When I tried to see a difference with bluray content (8bits SDR), I couldn't see any difference between 8bits and 10bits. I don't have the time to do more pixel peeping just because some prefer to watch HDR 10bits content dithered to 8bits.

I want as close as the "pure direct" equivalent as I can get :). I do agree though that it's not the end of the world if you drop to 8bits, but I want the same PQ as my standalone player (or better) with MadVR, not worse.

[Asmodian]

We are not saying we prefer dithering 8 bit to 10 bit, only that no one can tell the difference all else being equal. :p

The point is only that you should not sacrifice anything for 10 bit output, not that 8 bit output is better.

Edit: And you always have to dither, you simply dither to 10 bit or 12 bit instead of dithering to 8 bit.

[Manni]

i can't remember but if i'm not mistaken AMD needs 10 bit for what ever reason or it will not send HDR.

so it is your choice if you go 4:2:2 10 bit or RGB 8 bit for 60 HZ which will be double dithered(and i tested the amd dithering to 6 bit is is pretty much random dithering not bad but not good too 10->8 bit should be the same but hard to test because it looks very similar)

windows 10 HDR shoudl work at 8 bit even with AMD cards.


it's hard to find a screen that doesn't support 12 bit input even TV from 2012 and older can do this easily.
and i wonder how people confirm stuff like this...

I don't know about AMD, I have nVidia 1080ti (see my sig). It's perfectly possible to send 8bits or 12bits to get HDR with nVidia. It is not possible to use 4:2:2 10bits with nVidia. It's 8bits or 12bits.

Therefore there is no need to use 4:2:2 with nVidia. I use 12bits 4:4:4 for 99.99% of films, and 8bits 4:4:4 for the odd 60p film such as Billy Lynn.

I did tell you that it was not only the input but all the chain up to the panels that was 12bits. I don't have the reference here but it has been confirmed. It wasn't the case for the pre-2015 JVCs, which had 12bits inputs but 10bits panels.

We are not saying we prefer dithering 8 bit to 10 bit, only that no one can tell the difference all else being equal. :p

The point is only that you should not sacrifice anything for 10 bit output, not that 8 bit output is better.

Edit: And you always have to dither, you simply dither to 10 bit or 12 bit instead of dithering to 8 bit.

I am not sacrificing anything, so I don't see why I should use 8bits. And yes, I meant that I don't want to dither to 8bits if I don't have to, I thought the context would make it clear given that we have already discussed many times that MadVR's output is in 16bits before dithering.

I suggest we discuss this again when you have been able to compare 8bits vs 10bits output on native 10/12bits panels. Until then, I'm out. :)

[Oguignant]

Hi guys, question... Is there any way that when Madvr automatically changes to 23hz also change the bit depth to 12 bits? with the old Nvidia drivers I could do it. Is there any other software that I can use in Windows 10 and combine it with Madvr or run independently from Madvr?

Thks

[Asmodian]

I am not sacrificing anything, so I don't see why I should use 8bits.

You should not. If you don't have to sacrifice anything use 10 bit, of course. :p

I suggest we discuss this again when you have been able to compare 8bits vs 10bits output on native 10/12bits panels. Until then, I'm out. :)

I am using a 2017 LG OLED, which is native 10 bit. :rolleyes:

[Oguignant]

I am using a 2017 LG OLED, which is native 10 bit. :rolleyes:

I have LG OLED 2017 too. These panels are 10 or 12 bits?

[Asmodian]

10 bit

[Oguignant]

10 bit

I thought it was 12 bits because it supported dolby vision

[huhn]

there are 8 bit panels that can do dolby vision.

LG never confirmed more than 10 bit internal processing. they even featured this as a new "thing".

WRGB OLED can't be properly compared anyway it needs heavy processing to even get an image on the screen and if the sub pixel are really run with 10 bpc that would mean this screen has 40 bpp.

[Oguignant]

Hi guys, question... Is there any way that when Madvr automatically changes to 23hz also change the bit depth to 12 bits? with the old Nvidia drivers I could do it. Is there any other software that I can use in Windows 10 and combine it with Madvr or run independently from Madvr?

Thks

Nothing about this?

[edcrfv94]

In case you guys wonder how NGU Sharp compares to mpv's latest FSRCNN(X), here's a little comparison:

Blu-Ray screenshot (http://madVR.com/doom9/spiritedAway/HiRes.png)
downscaled (PNG) (http://madVR.com/doom9/spiritedAway/LowRes.png) | (JPG, 100 quality) (http://madVR.com/doom9/spiritedAway/LowRes.jpg)
latest FSRCNN32 (http://madVR.com/doom9/spiritedAway/FSRCNN32.png)
latest FSRCNNX32 (http://madVR.com/doom9/spiritedAway/FSRCNNX32.png)
NGU Sharp - High (http://madVR.com/doom9/spiritedAway/NGUSharpHigh.png)
NGU Sharp - Very High (http://madVR.com/doom9/spiritedAway/NGUSharpVeryHigh.png)

To make things as fair as possible I've downscaled the image with Bicubic/Catrom, which is exactly what FSRCNN and FSRCNNX were trained for.

Here are benchmark numbers, for 720p doubling:

Nvidia 1070:
FSRCNN16: 15.270 ms
FSRCNNX16: 26.397 ms
FSRCNN32: 46.290 ms
FSRCNNX32: ? (estimated: 80.021 ms)
NGU-Sharp High: 3.940 ms
NGU-Sharp Very High: 11.800 ms

AMD 560:
FSRCNN16: 14.289 ms
FSRCNNX16: 24.412 ms
FSRCNN32: 45.235 ms
FSRCNNX32: ? (estimated: 77.282 ms)
NGU-Sharp High: 12.970 ms
NGU-Sharp Very High: 37.100 ms

These are very weird benchmark results, to say the least. We know that NGU doesn't run as well as it should on AMD Polaris GPUs. But FSRCNN(X) running (ever so slighty) faster on my AMD 560 than on my Nvidia 1070 is just plain weird.

Look well, very expect NGU can be used at AviSynth also can NGU use for Deinterlacers to replace nnedi3(QTGMC)?

[Asmodian]

Not yet, NGU is currently only in madVR.

[petran79]

on W10 suddenly there is tearing in Full Screen mode, even with Exclusive Mode enabled. Doesnt happen with EVR (Potplayer) or VLC.
If I disable DX11 renderer in Madvr and switch to Fullscreen, screen becomes black with sound on the background. Player freezes and I have to kill the app via taskmanager.
Using Nvidia gtx1060 and gsync monitor

I even clean reinstalled the drivers

[mclingo]

People managing to get 10bit / 12 bit on FULL RGB 4:4:4, are you using monitors rather than TV/HDMI/ Receivers?, when I choose 4:4:4 full RGB I lose both the 12 bit and 10 bit options in my AMD control Panel suggesting its just not possible to get 10/12 BIT FULL RGB on current HDMI specs.

[Manni]

Hi guys, question... Is there any way that when Madvr automatically changes to 23hz also change the bit depth to 12 bits? with the old Nvidia drivers I could do it. Is there any other software that I can use in Windows 10 and combine it with Madvr or run independently from Madvr?

Thks

With Windows 10 you need to use 385.28. Select 4K23p, 12bits, RGB full, 4:4:4, apply. Then if the content goes above 30p, the driver will automatically switch to 4K60p 8bits 4:4:4, which is what you want. It doesn't work the other way around.

People managing to get 10bit / 12 bit on FULL RGB 4:4:4, are you using monitors rather than TV/HDMI/ Receivers?, when I choose 4:4:4 full RGB I lose both the 12 bit and 10 bit options in my AMD control Panel suggesting its just not possible to get 10/12 BIT FULL RGB on current HDMI specs.

No idea about AMD, for nVidia see above. I'm using a JVC projector and have no issue to get what's in my sig, at least at 23-30p.

[mclingo]

With Windows 10 you need to use 385.28. Select 4K23p, 12bits, RGB full, 4:4:4, apply. Then if the content goes above 30p, the driver will automatically switch to 4K60p 8bits 4:4:4, which is what you want. It doesn't work the other way around.



No idea about AMD, for nVidia see above. I'm using a JVC projector and have no issue to get what's in my sig, at least at 23-30p.

My TV is a 10 bit panel but I can only select 10bit in 420 mode, when I put my TV in 444 full RGB 10bit is missing.

Although i've not tried it for a while and there have been a few firmware updates, might try it again.

[Clammerz]

I suggest we discuss this again when you have been able to compare 8bits vs 10bits output on native 10/12bits panels. Until then, I'm out. :)

I don't think this topic was particularly relevant for you since you know exactly what your video pipeline is doing.

By "I don't want to dither if I don't have to", I assume you mean "dither further than I have to", since you'll need to dither down to 10bit from MadVR's higher internal representation.
But it's those kinds of wordings that made me bring this topic up in the first place. If someone were to assume "10bits, great. Just like my input" as the take away message, they could be dithering more than needed because something in their pipeline downconverted along the way.

It was more a cautionary mention rather than "everyone needs to not do this", but I think it got a little muddled along the way. Oops.

[Manni]

My TV is a 10 bit panel but I can only select 10bit in 420 mode, when I put my TV in 444 full RGB 10bit is missing.

Although i've not tried it for a while and there have been a few firmware updates, might try it again.

Your TV might have a 10.2gb HDMI max bandwidth, or your cables might not be good enough to pass through more than that. Make sure you select 23p when trying any chroma/bit depth combination, in order to make sure you don't cause a bandwidth issue (or at least you limit it).