madVR - high quality video renderer (GPU assisted)

[huhn]

read what reclock is...

it will be different on any PC anyway.

[pOpY]

Just a short comment while still having piles of commercial work on my desk:

Thanks to my great Nvidia driver contact, I managed to get a fix for 1080p23 timings into newer driver versions. So stock 1080p23 timings should be much better now with newer drivers, probably also for 3D. I know, the newest drivers come with their own problems, so many are still using older driver versions. But JFYI...

Thank, you for this great news.
Can you please tell us in which driver version this fix will be included?

Thank you
pOpY

[Manni]

Thank, you for this great news.
Can you please tell us in which driver version this fix will be included?


I have already reported that 397.93 brings a significant improvement for 3D vs previous versions. In 1080p23 3D, I get a frame repeat every 13 minutes vs one frame repeat every 3 minutes with previous drivers. I haven’t tested 1080p 2D as I have no use for it, but improvements might be there too. There might be further improvements in future drivers.

[pOpY]

I have already reported that 397.93 brings a significant improvement for 3D vs previous versions. In 1080p24 3D, I get a frame repeat every 13 minutes vs one frame repeat every 3 minutes with previous drivers. I haven’t tested 1080p 2D as I have no use for it, but improvements might be there too. There might be further improvements in future drivers.

thx for the hint.
will try the 397.93 driver.

[madjock]

I have already reported that 397.93 brings a significant improvement for 3D vs previous versions. In 1080p24 3D, I get a frame repeat every 13 minutes vs one frame repeat every 3 minutes with previous drivers. I haven’t tested 1080p 2D as I have no use for it, but improvements might be there too. There might be further improvements in future drivers.

Is there such a thing as 2D and 3D settings for drivers, as after I got good figures to setup Nvidia custom res, both work the same for me. Not bragging just didn't know they were different.

Only tried it with a HSBS Mkv so I am maybe missing something.

[Manni]

Is there such a thing as 2D and 3D settings for drivers, as after I got good figures to setup Nvidia custom res, both work the same for me. Not bragging just didn't know they were different.

Only tried it with a HSBS Mkv so I am maybe missing something.

I'm talking specifically about 3D framed packed, which is a different video mode (1080p23FP). If you use T/B or SbS, then it's the same video mode as 1080p 2D (but it's not full res 1080p 3D, only half res).

I didn't test 1080p23 2D because I never use it, I upscale everything to 4K23 and I get 1 frame drop every hour with MadVR custom refresh rate with all drivers versions, so happy with that.

[madjock]

I'm talking specifically about 3D framed packed, which is a different video mode (1080p23FP). If you use T/B or SbS, then it's the same video mode as 1080p 2D (but it's not full res 1080p 3D, only half res).

I didn't test 1080p23 2D because I never use it, I upscale everything to 4K23 and I get 1 frame drop every hour with MadVR custom refresh rate with all drivers versions, so happy with that.

Ah makes sense.

Well this is what fixed my refresh rates, and I tried every driver etc.

https://forum.redfox.bz/threads/how-to-achieve-perfect-23-976hz-24p-with-nvidia.72844/

[Manni]

Ah makes sense.

Well this is what fixed my refresh rates, and I tried every driver etc.

https://forum.redfox.bz/threads/how-to-achieve-perfect-23-976hz-24p-with-nvidia.72844/

This doesn’t work for 1080p23FP. NVidia’s control panel custom res and CRU don’t work in 3D modes.

In 2D, I get very good results with 4K23p and MadVR’s custom refresh rate, so there is nothing to fix. You should report if native 1080p23 (2D) is improved in 397.93, it might be.

[SweetLow]

see attached the beginning of the discussion :
It is NOT the beginning of discussion.

[madjock]

This doesn’t work for 1080p23FP. NVidia’s control panel custom res and CRU don’t work in 3D modes.

In 2D, I get very good results with 4K23p and MadVR’s custom refresh rate, so there is nothing to fix. You should report if native 1080p23 (2D) is improved in 397.93, it might be.

I was getting audio drop outs with the latest, also Madshis statement and the age of the new driver, plus no mention of any fixes for 23.976 in the release notes tell me it has not been implemented yet.

I am pretty sure it goes to 23,970 as they all do, and I think the custom was not saving, anyway I gave up and went back to 390,77 which worked out better for me. I also am unsure how Nvidia could fix the driver when all clocks have to be taken into consideration, hence how madVRs custom and a tweaked Nvidias one can work, as we know seeing a 23.976 dead in framerate does not mean you will not get frame drops.

[nevcairiel]

plus no mention of any fixes for 23.976 in the release notes tell me it has not been implemented yet.


Such things don't necessarily make it into changelogs.

[SweetLow]

Such things don't necessarily make it into changelogs.
Nobody likes to show his/her previous mistakes :)

[madjock]

Nobody likes to show his/her previous mistakes :)


Haha very true. If only there was such a thing as a cutdown HTPC driver, I remember when you used to get modified drivers years ago.

If only....

But you would think that something that has been broken so long and mentioned numerous times over the years on their forums would warrant a bit of fanfare, I think it may be trickier than a 1 fix for all so maybe not something that would get shouted about.

Most of the forum is about games crashing rather than frame rates nowadays though.

[Manni]

I was getting audio drop outs with the latest, also Madshis statement and the age of the new driver, plus no mention of any fixes for 23.976 in the release notes tell me it has not been implemented yet.

As I said, although there was significant improvement in 397.93 in 1080p23FP compared to previous drivers, there might be further improvements to come in future drivers. Madshi didn't say that he had *just* talked to his contact, and 397.93 is only one week old.

Audio dropouts have nothing to do with this. The refresh rate will cause video frames to be dropped/repeated if not close enough. If you have audio drops in native 1080p23 refresh rate, something else is seriously wrong in your config.

Anyway, you asked for some information, I provided some, so let's move on if you don't want to test for yourself. I'm sure someone who does use 1080p23 (2D) will test and report if there are improvements or not in 397.23. I wouldn't know as I haven't tested previous drivers for this, so I can't compare.

Such things don't necessarily make it into changelogs.

Exactly :)

The significant 1080p23FP improvement certainly didn't.

[sauma144]

Does it mean I can finally buy a new nvidia graphic card?

[madjock]

As I said, although there was significant improvement in 397.93 in 1080p23FP compared to previous drivers, there might be further improvements to come in future drivers. Madshi didn't say that he had *just* talked to his contact, and 397.93 is only one week old.

Audio dropouts have nothing to do with this. The refresh rate will cause video frames to be dropped/repeated if not close enough. If you have audio drops in native 1080p23 refresh rate, something else is seriously wrong in your config.

Anyway, you asked for some information, I provided some, so let's move on if you don't want to test for yourself. I'm sure someone who does use 1080p23 (2D) will test and report if there are improvements or not in 397.23. I wouldn't know as I haven't tested previous drivers for this, so I can't compare.



Exactly :)

The significant 1080p23FP improvement certainly didn't.


I obviously did try it myself when it came out days ago. The audio drop outs are due to the driver, no need to be so rude. Also if you did change to the new drivers, you surely had to create a new custom one yourself ?

https://forums.geforce.com/default/topic/1057223/?comment=5355083

[veggav]

Well, in the end I disabled the this device is calibrated and I believe I prefer this way.

I have one more question, when using NGU you have anti alias, soft, standard and sharp.
Is it correct to assume that NGU Anti-Alias is the less demanding option and NGU sharp is the most demanding one?

I mean are those related to picture quality? NGU Anti alias will give the "worst" (in quotes because as I can see the result is really good) and NGU sharp will give you the best one?

I'm using NGU standard because it seems more natural.

Also would that be considered true for the chroma upscaling.
I'm using starnd very high quality.
Is sharp very high quality more demanding?

[madjock]

Well, in the end I disabled the this device is calibrated and I believe I prefer this way.

I have one more question, when using NGU you have anti alias, soft, standard and sharp.
Is it correct to assume that NGU Anti-Alias is the less demanding option and NGU sharp is the most demanding one?

I mean are those related to picture quality? NGU Anti alias will give the "worst" (in quotes because as I can see the result is really good) and NGU sharp will give you the best one?

I'm using NGU standard because it seems more natural.

Also would that be considered true for the chroma upscaling.
I'm using starnd very high quality.
Is sharp very high quality more demanding?

Some good info in both these threads. Apologies if you have seen them already.

https://forum.kodi.tv/showthread.php?tid=259188&pid=2238958#pid2238958

https://forum.doom9.org/showthread.php?t=171787

[Clown shoes]

Afternoon folks,

There's something I've been meaning to ask that's probably a stupid question, but does anyone know what the difference between setting 'disable calibration controls for this display' vs 'this display is already calibrated' ?

If I've already calibrated my display then I'm not quite sure what the purpose of the second option is?

EDIT:

My bad, I think I've already worked it out. 'Disable calibration' presumes a pure power curve of 2.2 as opposed to 'this display is already calibrated' which allows me to set the curve which in my case will be 2.4 for a BT1886 set up.

Have I got that right?

[Warner306]

Afternoon folks,

There's something I've been meaning to ask that's probably a stupid question, but does anyone know what the difference between setting 'disable calibration controls for this display' vs 'this display is already calibrated' ?

If I've already calibrated my display then I'm not quite sure what the purpose of the second option is?

EDIT:

My bad, I think I've already worked it out. 'Disable calibration' presumes a pure power curve of 2.2 as opposed to 'this display is already calibrated' which allows me to set the curve which in my case will be 2.4 for a BT1886 set up.

Have I got that right?

Disable calibration defaults to BT.709 with a pure power curve 2.20. The gamma setting is only important if you enabled gamma processing. Most people are watching SDR content at BT.709, so this choice is not overly important.

[Warner306]

Well, in the end I disabled the this device is calibrated and I believe I prefer this way.

I have one more question, when using NGU you have anti alias, soft, standard and sharp.
Is it correct to assume that NGU Anti-Alias is the less demanding option and NGU sharp is the most demanding one?

I mean are those related to picture quality? NGU Anti alias will give the "worst" (in quotes because as I can see the result is really good) and NGU sharp will give you the best one?

I'm using NGU standard because it seems more natural.

Also would that be considered true for the chroma upscaling.
I'm using starnd very high quality.
Is sharp very high quality more demanding?

Look at the images posted in the Kodi thread. They will give you a better idea of what each NGU algorithm looks like.

I've settled on NGU Anti-Alias for chroma upscaling and NGU Sharp for image doubling. The chroma layer is soft and doesn't always look good when oversharpened. And the luma layer is sharp and can benefit more from sharp upscaling. That's been my observation when looking at upscaled still images of both.

[Betroz]

NGU Anti-Alias is just excellent for upscaling 480p video to 1080p! Love it! :)

[Asmodian]

I agree for SD to HD/UHD I love NGU AA.

I agree with Warner306 for upscaling HD content.

[Manni]

I obviously did try it myself when it came out days ago. The audio drop outs are due to the driver, no need to be so rude. Also if you did change to the new drivers, you surely had to create a new custom one yourself ?


Your post was confusing and I didn't realize that you had tested 397.93. I thought you were saying you wouldn't bother testing because the change wasn't in the release notes. Sorry if I misread. Also you mentioned audio drop outs, which suggests issues beyond a minor refresh rate mismatch in 1080p23, though it might be hardware-specific.

When I change drivers I simply create a custom refresh mode using MadVR using the EDID/CTA settings, it takes seconds and gives me near perfect playback (one frame drop every hour or so) at least in 4K23, including with 397.93. No audio drop outs here.

I don't test 1080p23 because I have no use for it (except in 3D frame packed) and I have since reverted to 385.28 due to the many issues I experience here with 39x.x.

[BetA13]

hy all,

i have a problem setting up MADVR for a friend and need some help :)

The System is:
Windows 7 64bit
GTX 1080 mini @ 378.78 Driver
Asus 10bit Monitor 4k HDR (if needed i will ask the exact name)

MPC HC, LAV Filters and MadVR are all Up to Date.
DirectX is installed and all the stuff...

Problem:

In Madvr i set USE D3D11 - In OSD it shows D3D9
I set 10Bit in Monitor settings in MadVR - It uses only 8Bit..

I cant figure out whats wrong and why it isnt working...It should say or use d3d11 but it doesnt..And d3d11 is also a must if you wanna use 10bit if i understand correctly..

Also scaling algos dont sem to work, its like it doesnt use teh settings i set.
The madvr folder is in c:/programFiles and teh madvr folder has access rights..

And the Render Queue doesnt fill up..its hanging at 1-2..All other queues are fine..

any help would be great.. THX..

Beta

[huhn]

what player is used some player save settings differently.

[Clown shoes]

Disable calibration defaults to BT.709 with a pure power curve 2.20. The gamma setting is only important if you enabled gamma processing. Most people are watching SDR content at BT.709, so this choice is not overly important.

Why is the gamma setting only important if you are enabling gamma processing?

If my display is calibrated with a 2.4 curve and MadVR is expecting 2.2 is that not going to cause an issue with the way gamma is displayed?

[huhn]

no because if you have calibrated your display to gamma 2.4 it will display an not gamma altered images as gamma 2.4.

[Clown shoes]

no because if you have calibrated your display to gamma 2.4 it will display an not gamma altered images as gamma 2.4.

So I'm now confused. What is the purpose of this gamma setting then?

So it makes no difference if I select disable calibration controls?

[BetA13]

what player is used some player save settings differently.

MediaPlayer CLassic HC 64bit.
Settings are stored as .ini and the settings do save in the player since it keeps everything.

The Problem is that MadVR doesnt do what i set in the options of MadVR..

The Player is fine from what i can tell..

[huhn]

So I'm now confused. What is the purpose of this gamma setting then?

So it makes no difference if I select disable calibration controls?
it is there to change the gamma.
it's very simple how should madVR change the gamme if it doesn't know the gamma of your screen?

if you use gamma processing and want a gamma of 2.0 it has to get to that gamma different if the display is gamma 2.2 or 2.4.

BetA13 mpc.hc doesn't use different settings.

[Clown shoes]

it is there to change the gamma.
it's very simple how should madVR change the gamme if it doesn't know the gamma of your screen?

if you use gamma processing and want a gamma of 2.0 it has to get to that gamma different if the display is gamma 2.2 or 2.4.

BetA13 mpc.hc doesn't use different settings.

Ok I think I understand.

So let's say I have a TV that has a 2.4 power curve and I would like perhaps a daytime setting of 2.2 without having to play with my TV controls, I could set MadVR to Rec709 with a 2.4 power curve and then set 2.2 under gamma processing to get my desired result. Is that about right?

If I just want to leave it as 2.4 I could simply select 'disable calibration controls for this display' bearing in mind that I could not use gamma processing as it will presume my display is 2.2. Is that also correct?

[BetA13]

?!?!?!?!?!?

ummm, i think we dont understand each other :)

MPC HC works fine..
LAV FIlters also do theyr job.

Madvr also works...
BUT, if i try to change some settings IN MADVR, like : use Direct3D 11 for presentation (WIndows 7 and newer) , the Madvr OSD still shows that its using D3D9 even doh i did set it to use D3D11...

It is exactly set up as mine wich i use on my PC..Here D3D11 works and is showed in teh OSD..

i never encoutered such problem, and i installed and setup Madvr for a lot of friends in teh past, where i never came across such problem.

cheers

[huhn]

Ok I think I understand.

So let's say I have a TV that has a 2.4 power curve and I would like perhaps a daytime setting of 2.2 without having to play with my TV controls, I could set MadVR to Rec709 with a 2.4 power curve and then set 2.2 under gamma processing to get my desired result. Is that about right?[]
yes.
If I just want to leave it as 2.4 I could simply select 'disable calibration controls for this display' bearing in mind that I could not use gamma processing as it will presume my display is 2.2. Is that also correct?[/QUOTE]
no...
just tell madVR it is 2.4 and you can easily get 2.4 and 2.2. if you want gamma 2.2 you have to tell madVR that your screen is 2.4.

@BetA13 i said MPC-HC shouldn't be the problem and i don't know why it is happening sorry.

[madjock]

Your post was confusing and I didn't realize that you had tested 397.93. I thought you were saying you wouldn't bother testing because the change wasn't in the release notes. Sorry if I misread. Also you mentioned audio drop outs, which suggests issues beyond a minor refresh rate mismatch in 1080p23, though it might be hardware-specific.

When I change drivers I simply create a custom refresh mode using MadVR using the EDID/CTA settings, it takes seconds and gives me near perfect playback (one frame drop every hour or so) at least in 4K23, including with 397.93. No audio drop outs here.

I don't test 1080p23 because I have no use for it (except in 3D frame packed) and I have since reverted to 385.28 due to the many issues I experience here with 39x.x.

No problems. I would have thought that if the latest driver had made any difference the EDID settings would still have seen an improvement. To be honest apart from the drivers showing 23.976 instead of 23.970 or 23.971 I am unsure how they can fix it for all.

Other than it being a sort of auto custom res I don't know how they can fix it.

As far as the audio side on the latest ones, it has happened on a couple of them recently, the AVR does not flash as though its dropping, but something happens, I also saw a few others mention it. I am like you I do not play games, so I am after stability and reliability so quite happy to roll back.

[veggav]

My head is spinning with so much knowledge you guys are providing.

I took Warner360's advice and I'm using chroma with NGU AA and upscaling with NGU sharp.

Now one thing I don't understand is this:
The new windows 10 update shows the HDR setting along with WCG setting. Toggle this to enable HDR and WCG on and off.

But on the Nvidia side of drivers I can only choose RGB and YPbPr.
If I'm not mistaken HDR is YPbPr 10bits, right?

Ok, so if the HDR toggle is OFF, and I'm playing a movie in full screen windowed mode, and my display is at 2160p23 and on the Nvidia side it set to let application control colors, so I guess it might be YPbPr 4:4:4 in this scenario DCI is impossible, correct?

I mean WCG and DCI are the same thing?

Let's say windows is using desktop at 60hz 4:4:4 without chroma subsampling.
This is still BT709, yes? Or can you output DCI colors in 4:4:4 mode?

My head is spinning also because windows desktop seems undersaturated if BT709 is set on my TV but icons looks ok if I set DCI mode.
When I was playing a movie with calibration disabled on MadVR everything looked oversaturated with BT709 but looked ok with DCI.

So I believe I don't understand all this properly.

[el Filou]

BUT, if i try to change some settings IN MADVR, like : use Direct3D 11 for presentation (WIndows 7 and newer) , the Madvr OSD still shows that its using D3D9 even doh i did set it to use D3D11...Try this temporary workaround: delete madVR's folder in Program Files, then recreate it without giving the user write access rights. madVR should then only use the registry to store settings. Try and see if it 'remembers' your settings that way.
Other temporary workaround: try reinstalling madVR in folder %LOCALAPPDATA% or in %ProgramData% and see if it remembers the settings. If it does then there's a problem with the write access to Program Files.

[Warner306]

?!?!?!?!?!?

ummm, i think we dont understand each other :)

MPC HC works fine..
LAV FIlters also do theyr job.

Madvr also works...
BUT, if i try to change some settings IN MADVR, like : use Direct3D 11 for presentation (WIndows 7 and newer) , the Madvr OSD still shows that its using D3D9 even doh i did set it to use D3D11...

It is exactly set up as mine wich i use on my PC..Here D3D11 works and is showed in teh OSD..

i never encoutered such problem, and i installed and setup Madvr for a lot of friends in teh past, where i never came across such problem.

cheers

The driver your friend is using is probably a few years old. I would try upgrading it. I'm pretty sure it doesn't support HDR passthrough. I don't know if it would bring D3D11 back.

[Warner306]

My head is spinning also because windows desktop seems undersaturated if BT709 is set on my TV but icons looks ok if I set DCI mode.
When I was playing a movie with calibration disabled on MadVR everything looked oversaturated with BT709 but looked ok with DCI.

So I believe I don't understand all this properly.

Nvidia and madVR will ignore the Windows color settings, as long as you turned off HDR and WCG. You should keep the desktop at RGB Full at all times. Set 60 Hz to 8-bit RGB. Select each of the playback refresh rates (30 Hz and below) and set them to RGB 12-bits and save.

madVR will determine what color gamut is sent to the GPU based on the source and what is set in calibration.

The only caveat with this setup is that you'll have to use fullscreen exclusive mode with 4K content to get HDR10 passthrough to work due to a driver issue. Or, you could just output everything at 8-bits in windowed mode.

[el Filou]

The driver your friend is using is probably a few years old.378.78 is only 15 months old. :) While this is pretty old for gaming, it should be fine for madVR.

[Warner306]

378.78 is only 15 months old. :) While this is pretty old for gaming, it should be fine for madVR.

Fair enough. That driver still might have issues with HDR compatibility.

[Warner306]

Some information on AACS 2.1, which is now out for Sony movies Fury and Patriot:

AACS 2.1 and Disc Ripping (http://www.avsforum.com/forum/26-home-theater-computers/2364113-guide-building-4k-htpc-madvr-35.html#post56281916)

AACS 2.x and madVR go hand-in-hand these days. Hopefully, this link is permissible here...

[veggav]

Nvidia and madVR will ignore the Windows color settings, as long as you turned off HDR and WCG. You should keep the desktop at RGB Full at all times. Set 60 Hz to 8-bit RGB. Select each of the playback refresh rates (30 Hz and below) and set them to RGB 12-bits and save.

madVR will determine what color gamut is sent to the GPU based on the source and what is set in calibration.

The only caveat with this setup is that you'll have to use fullscreen exclusive mode with 4K content to get HDR10 passthrough to work due to a driver issue. Or, you could just output everything at 8-bits in windowed mode.

How do you "save"? I've set Use Nvidia Color settings with 60hz with 8 bit RGB Full.
Than I switched to every refresh under 30hz and selected YPbPr 4:2:2 and 10bits, limited, and applied.
But whenever I toggle the refresh in Nvidia control panel it keeps the last used color setting.

HDR is still working tough.

Also MadVR shows primaries as BT2020 in HDR mode and -> DCI-P3.
This means it's converting BT2020 to DCI? I tried to set calibration to BT2020 and disable calibration but this still shows in the OSD.

Is that a normal behavior?

[Warner306]

How do you "save"? I've set Use Nvidia Color settings with 60hz with 8 bit RGB Full.
Than I switched to every refresh under 30hz and selected YPbPr 4:2:2 and 10bits, limited, and applied.
But whenever I toggle the refresh in Nvidia control panel it keeps the last used color setting.

HDR is still working tough.

Also MadVR shows primaries as BT2020 in HDR mode and -> DCI-P3.
This means it's converting BT2020 to DCI? I tried to set calibration to BT2020 and disable calibration but this still shows in the OSD.

Is that a normal behavior?

I said set everything to 12-bit RGB Full, not Y'CbCr 4:2:2. You don't want the GPU to do a range conversion from RGB to Y'CbCr before reaching the display. You should select the resolution, apply RGB 12-bit and save. The other way to do it is to play a video and go back to the GPU control panel and make the change and save. You don't have to select the refresh rate a second time after doing this.

The primaries are DCI-P3 but they are in a BT.2020 container. That's all that is saying. There is no conversion.

[Georgel]

Seems that my issues were because I was using algotihms that were too aggressive somehow...

BTW, I think some bugs might have been caused by windows updates as well.

[veggav]

I said set everything to 12-bit RGB Full, not Y'CbCr 4:2:2. You don't want the GPU to do a range conversion from RGB to Y'CbCr before reaching the display. You should select the resolution, apply RGB 12-bit and save. The other way to do it is to play a video and go back to the GPU control panel and make the change and save. You don't have to select the refresh rate a second time after doing this.

The primaries are DCI-P3 but they are in a BT.2020 container. That's all that is saying. There is no conversion.

Playing the video worked after changing the setting per refresh, set everything to RGB 12Bit Full here.

Thank you, Warner, for your patience explaining those basic features for me.

[Warner306]

Playing the video worked after changing the setting per refresh, set everything to RGB 12Bit Full here.

Thank you, Warner, for your patience explaining those basic features for me.

Great. You can confirm 12-bit RGB is working by visiting the GPU control panel during playback. Some drivers have had issues retaining these settings, but it should be fine.

[suanm]

Nvidia and madVR will ignore the Windows color settings, as long as you turned off HDR and WCG. You should keep the desktop at RGB Full at all times. Set 60 Hz to 8-bit RGB. Select each of the playback refresh rates (30 Hz and below) and set them to RGB 12-bits and save.

madVR will determine what color gamut is sent to the GPU based on the source and what is set in calibration.

The only caveat with this setup is that you'll have to use fullscreen exclusive mode with 4K content to get HDR10 passthrough to work due to a driver issue. Or, you could just output everything at 8-bits in windowed mode.

Are you sure to have to use fullscreen exclusive mode with 4K UHD content so as to get HDR10 pass through normally to work due to a driver issue?
No wonder my cpu usage is so high,even close to 100% at one time in windowed mode when i play 4K UHD movies with HDR10 special effects trying to use the 'passthrough' feature.i don't know whether the high usage of cpu is related to the windowed mode or not?

[huhn]

with nvidia card you currently need FSE for 10 bit.

madVR only really uses the CPU with copyback decoding.
there are some HDR features that can use the CPU. FSE or windowed has nothing todo with that.

[suanm]

What's FSE? HDR passthrough feature should not depend on cpu in theory,i think.Because cpu doesn't natively decode HDR10 contents,cpu sends only HDR10 contents to the display or TV set which is in charge of decoding HDR10 contents.