View Full Version : madVR - high quality video renderer (GPU assisted)
ashlar42
17th June 2022, 03:04
QTGMC https://forum.doom9.org/showthread.php?t=174544
have a look at this.
and yes properly working hardware deint from all 3 major vender are very good and also close to free.
I am familiar with QTGMC, having used it for several interlaced encoding, to deinterlace source.
My reasoning was about real time solutions, though.
If CUVID doesn’t lead to chroma errors, I might use that for interlaced material.
Sunspark
17th June 2022, 03:14
madVR would just be 100% perfect for me if it had D3D11 native deinterlacing and black bar detection running on the GPU, it's really a shame it's never gonna happen. :(
Why not just run the deinterlaced stuff off the intel gpu which is already in many systems? You could have two players set up and switch between them.
flossy_cake
17th June 2022, 05:00
In those screenshots, the dxva2-native algo in your card is best. It has the sharpest text rendition and doesn't do stupid stuff like putting white pixels in the middle of the letters like O.
The closest match I could find was softcubic70:
https://i3.lensdump.com/i/tpXN0Z.png
I seem to like it as well, it's quite clean.
Bilateral old is even sharper though:
https://i.lensdump.com/i/tpXPqP.png
Plus it cleans up baked-in chroma artefacts in that Family Guy DVD to almost imperceptible levels.
For now I might go with softcubic70 as my default and then for sources with baked-in chroma problems tag them with [profile='bilateral old']
edit: Super-xbr at sharpness 25 seems pretty good as well:
https://i1.lensdump.com/i/tpXfYm.png
I tested on an i3 11154G4 11th gen , Irirs, Aver Aspire 5
Sort of impressed 720p > 1080p could max out chroma super-xbr(still fave look at Netflix logo) Super-xbr doubling with SSIM100 dowm with AR or Linear light. (Not Both)
lower quality could handle NGU low with compression artifact removal activated. Not bad for onboard Graphics.
This iwas with torther test. Prehistoric Planet Ep 1 when Trex wading through water and Dracula (TV serires) opening ep 4. (50hz)
I encountered a bug with With MadVR and Windows 11. With MadVR's automatic refresh rate swithing sometimes invokes tablet mode if even on laptop. Doesn't
happen if change through Intel Control Panel. Narrowed it down down to "TabletPostureFreCompleted" "ImeersiveShell" but deleteing just recreats itself. (No touch controls Win 11)
@Flossy
Going to be honest with you. Just use software mode :)
flossy_cake
17th June 2022, 06:53
@Flossy
Going to be honest with you. Just use software mode :)
Why do you say that -- have you had some video files which decoded wrongly or differently with DXVA2-CB?
I might make some more 4:2:0 test files in different codecs, resolutions and dynamic ranges to see if one of them trips up DXVA2 into doing something weird.
I used the latest version of XMediaRecode portable to create that 4:2:0 clip from the 4:4:4 one. It was very difficult to get all the settings right to make sure it preserved everything, but I learned a lot in the process.
huhn
17th June 2022, 07:16
what more do you need to see the chroma shift?
BTW you can just take madVR 159 FFMPEG and place it in madVR folder under fffmpeg and just press control+shift+alt+print done you will get an still image encoded at QP 1.
and there are no known issue with DXVA copyback and DXVA native also does not decode wrong it scales wrongly that are two very different things.
flossy_cake
17th June 2022, 08:06
I'm aware of the chroma shift with DXVA2-native and have never used it.
On the last page you were saying "DXVA pipeline changes the image negatively" and "DXVA processing in general has misalign chroma on nvidia" so I thought I should check if DXVA2-Copyback really gives the same image as CPU.
huhn
17th June 2022, 08:27
but DXVA2 CP doesn't use the DXVA2 pipeline it uses the software pipeline. the video processor here is the issue i tried to make that as clear as possible when i said decoding is bit perfect and followed up by the correct response that DXVA2 N will lower image quality but another follow up to make clear this is not a decoder issue it is a processing issue.
you can get a perfect DXVA2 native image too(i have not checked it and i will not life is to short for this) just look at mpcVR which just accepts the image as DXVA2 p010 or DXVA2 nv12 but this video renderer also supports D3D11 processing so you still get the full feature set with d3d11 native unlike with madVR.
flossy_cake
17th June 2022, 08:47
Ok thanks. I guess I'll continue to use DXVA2-CB until I find evidence of it misbehaving.
Screenshot for you guys xo
https://drive.google.com/file/d/1N5X2T-j7N5k3KP3CNSjMhiFcAGxBep4I/view
https://imgur.com/a/MM08vWe
[QUOTE=JNW;1970414]Screenshot for you guys xo
https://drive.google.com/file/d/1N5X2T-j7N5k3KP3CNSjMhiFcAGxBep4I/view
el Filou
17th June 2022, 16:25
@JNW what are we supposed to look for here?Why not just run the deinterlaced stuff off the intel gpu which is already in many systems? You could have two players set up and switch between them.I've got a very old system without an iGPU. I probably need to upgrade at some time in the near future but I'm looking for having to do less of config switching.
Maybe one of the new Intel dGPUs would be a good solution if their perf/watt is good with madVR and their DXVA2 pipeline still works fine.
bob88
17th June 2022, 17:10
Hello,
Could you please tell me if I have a video that is:
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU
and I play it via HDMI cable on a device which is:
"st-2084, hlg"
will I have any benefit from it being Dolby Vision or will it be the same as HDR10 via some kind of fallback method which MadVR will do? Or will it come out defective?
Because I tried playing it directly through my device via a USB stick and it came out defective pink skin. I dont have the proper HDMI cable yet and am waiting for delivery but want to know is it going to work out? Or should I avoid Dolby Version videos altogether?
Also my device info says dynamic metadata is not supported. Is it a problem if I still keep the "send HDR metadata to the display" check box on?
Thank you.
Sunspark
17th June 2022, 17:53
@flossy_cake I probably should have been more sober for the attempt, but this screenshot business.. I'm missing something here.. how exactly are you taking screenshots? MadVR won't let me set "encoded" as a custom resolution unless I deselect dxva2 if it is currently selected. That's fine for testing, but then it comes to taking the screenshot itself.. I only find a key to take a screenshot in the player itself.. madvr doesn't seem to have a dedicated key setting for it.. so does that mean it communicates to the player itself how it will receive the screenshot as a custom encoding?
flossy_cake
18th June 2022, 16:51
What's frustrating with this chroma DXVA2 thing on NVIDIA is for people who watch interlaced content, if you use GPU deinterlacing it will reintroduce chroma errors even if it was decoded correctly with software or copyback.
Even if "use DXVA chroma upscaling when doing DXVA deinterlacing" is unticked?
It seems we can also untick "use DXVA chroma upscaling when doing native DXVA decoding" to get around the DXVA2-Native chroma alignment issue. This (https://i3.lensdump.com/i/t7rSgK.png) was the result when unticked, which is obviously bilateral so the setting seems to be working.
@flossy_cake I probably should have been more sober for the attempt, but this screenshot business.. I'm missing something here.. how exactly are you taking screenshots? MadVR won't let me set "encoded" as a custom resolution unless I deselect dxva2 if it is currently selected. That's fine for testing, but then it comes to taking the screenshot itself.. I only find a key to take a screenshot in the player itself.. madvr doesn't seem to have a dedicated key setting for it.. so does that mean it communicates to the player itself how it will receive the screenshot as a custom encoding?
Yeah I was wondering that myself... I figured MadVR must have some kind of callback function from the media player, in my case MPC-HC pressing alt+i. On my system "encoded video size" is never greyed out and I am unable to make it greyed out even if I'm doing DXVA2-CB/N decoding and select DXVA scaling options.
Another way is to display the video in windowed mode and then in MPC-HC Video Size > Normal Size which gives me 1:1 pixel mapping by cropping and then just use the print screen key. Can scroll with Ctrl+ Numpad 8,2,4,6.
huhn
18th June 2022, 18:29
zoom 100 %
1 for minimal view.
followed by alt print.
strg +v
Sunspark
18th June 2022, 23:20
I took a bunch of screenshots.. but here are 4 of them in 1 image.. sorry that I didn't animate them. The red text on blue is also worth looking at, but I didn't include those here.
All 4 are DVXA2-Native decoded and presented using D3D9. GPU is Intel HD Graphics 6000.
Top left- DXVA Chroma, MadVR Renderer
Top right- DXVA Chroma, MPCVR Renderer
Bottom left- Mitchell-Netravali Anti-Ringing Chroma, MadVR
Bottom right- Bicubic 60 Anti-Ringing Chroma, MadVR
It's strange, but despite the difference in red in the mpcvr image, it doesn't look bad when actually playing. I wonder why the red is so different.
The difference between MN and BC60 is small, however I think MN is subjectively better in this class because it is "flatter" so it looks a little more cinematic on video content playback, and the colours aren't quite as "punchy"/contrasty as BC60. BC60 seems to have hotspots of brighter blue and lighter colours in the centre of letters like "o", this is more visible under the 800 magnification. I find the MN text easier to read.
I don't think Intel's implementation of DXVA chroma is bad. It's arguably good enough for most people.
https://dl.dropboxusercontent.com/s/z0bn27ae1tn25yf/madvrTLmpcvrTRMNBLBC60BR.png
This link below is the same image enlarged 800%
https://dl.dropboxusercontent.com/s/6578xhfshfvpvno/madvrTLmpcvrTRMNBLBC60BR800.png
flossy_cake
19th June 2022, 04:08
It's strange, but despite the difference in red in the mpcvr image, it doesn't look bad when actually playing. I wonder why the red is so different.
Probably different tonemapping from HDR to SDR screenshot.
Intel6000 vs GTX1070
https://i3.lensdump.com/i/t7V6Rb.png
My take: 1070 is a little "cleaner" but is shifted to the right so that disqualifies it for me. I can get the same look with MadVR's softcubic70 without the shift, so I've got no reason to use DXVA2-N.
Another thing is what looks "clean" from close up just looks "soft" from a distance.
I might do some power consumption tests with DXVA2-N vs DXVA2-CB both with MadVR chroma.
Sunspark
19th June 2022, 05:17
Thanks for animating it. At first glance the 1070 looks fine, but when you see it popping back and forth, you can really see that it's almost like they placed a blur filter after the initial rendering. Shocking that a graphics company like NVIDIA could trip over their feet like this, and for years apparently.
You can still use the DXVA2-Native decoding, as long as you don't use the chroma or image scaling which is easy enough to set with every directshow renderer.
So where power consumption comes into play, this is tricky.. mpcvr has lower power consumption than madvr by a lot, but it's dxva all the way unless you disable dxva scaling in the filter options.. in which case it will use shaders instead.. but the only option there is catmull-rom (bicubic 50, and I don't know if they do anti-ringing or not). I didn't test the power consumption of the shaders. I think they are working on adding more. Maybe you could test this.
Madvr power consumption.. I was taking notes on that for my stuff.. it's tricky.. there's a lot of output paths.. d3d9 overlay, d3d9 exclusive, d3d11 exclusive, d3d9 windowed, d3d11 windowed, (each of these 2x, because you have old path which is backbuffers and new path which is frames in advance) so there are in total nine different output paths to check the power on against 4 different decoders (software, cb, dxva2 native, d3d11) so 36 combinations. You can't use DXVA scaling in D3D11 presentation, it will use bilinear for image scaling, but using dxva2 as the decoder works just fine with d3d11 for presentation. I'm using d3d9 overlay, but it's not actually the best power consumption, it's actually twice the gpu load of some of the other paths, but I am using it because I was doing extensive testing of a panning movement segment and found that this particular setting was "smoother" in motion than others. Was really tough, because in a regular window it was smooth, but as soon as it goes fullscreen it's not as smooth anymore and it's not related to the refresh rate, it's something to do with the compositor. So, I can have less power consumption if I use dxva2-cb because it uses half the gpu load with overlay but it won't be as smooth looking as when native is used. The extra conversion work madvr has to do has some kind of beneficial quirk that makes it smoother on this hardware.
d3d9 overlay w/ copyback, d3d11 presentation windowed and exclusive w/ d3d11 decoding used the least power for me. This is for madvr chroma scaling not dxva scaling. All the rest used more power. Nvidia will be different.
GPU-Z is good for viewing gpu load.
huhn
19th June 2022, 07:09
even if you don't scale chroma with DXVA native it will still move the image. this is a basic problem with madVR and DXVA processing using a an NVIDIA card.
mpcVR will move the chroma to but only if also some kind of DXVA processing is used.
flossy_cake
19th June 2022, 10:31
even if you don't scale chroma with DXVA native it will still move the image. this is a basic problem with madVR and DXVA processing using a an NVIDIA card.
mpcVR will move the chroma to but only if also some kind of DXVA processing is used.
Forgot to check that combination (DXVA2-native decode + MadVR chroma) and it appears to be shifted even worse -- diagonally down and to the right.
https://i2.lensdump.com/i/t7qJUm.png
https://i3.lensdump.com/i/t7qVZi.png
I was doing extensive testing of a panning movement segment and found that this particular setting was "smoother" in motion than others. Was really tough, because in a regular window it was smooth, but as soon as it goes fullscreen it's not as smooth anymore and it's not related to the refresh rate, it's something to do with the compositor.
Not sure if it's related, but I recently solved a long standing issue with dwm stutter on Windows 7 by adding this regkey
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM\Schedule]
"FrameRateMin"=dword:000000c8
(c8=200fps)
Sunspark
19th June 2022, 17:49
flossy_cake, well that's it for NVIDIA then. For MadVR in LAV video settings, hardware decoder to use either "None","DXVA2 (copy-back)" or "D3D11" (not Automatic in drop-down to force copy-back) and for MPCVR uncheck the first 4 boxes in the "DXVA2 and D3D11 video processor" group which will force shader processing instead since huhn indicated native decoding would still work just not the processing.
That should simplify power testing a bit.
I wonder why one of the big tech sites never embarrassed NVIDIA over this. One would think this would be great marketing for AMD.
huhn
19th June 2022, 19:44
i guess it is better to not tell you about amd...
bob88
26th June 2022, 00:24
Hello,
Please help me get HDR working with MPC-HC and madVR.
I have all the required hardware and am running Windows 11 with an HDMI hooked up to an HDR movie projector. Widows HDR checkbox is on.
Here is the info that I get:
https://i.ibb.co/0YbWXVN/Untit1led.png (https://ibb.co/0YbWXVN)
As far as I understand BT.2020 is being converted to DCI-P3. Why? Why does it not remain at BT.2020?
Also why is it rendered at 8 bit when I have set madVR like this:
https://i.ibb.co/R3tW9Mr/11.png (https://ibb.co/R3tW9Mr)
and the projector should work at 10bit:
https://i.ibb.co/nbhtzSK/2222.png (https://ibb.co/nbhtzSK)
and the movie is also 10bit:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 42 min
Bit rate : 16.9 Mb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.115
Stream size : 12.1 GiB (71%)
Title :
Writing library : x265 2.8+54-79c76e42cb28:[Windows][GCC 7.3.1][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=16 / numa-pools=24,24,24,24 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x1600 / interlace=0 / total-frames=0 / level-idc=51 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / repeat-headers / annexb / aud / hrd / info / hash=0 / no-temporal-layers / no-open-gop / min-keyint=1 / keyint=24 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / radl=0 / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=3 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / no-sao / no-sao-non-deblock / rd=3 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=16.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=160000 / vbv-bufsize=160000 / vbv-init=0.9 / crf-max=0.0 / crf-min=0.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=1 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50) / max-cll=1000,986 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / opt-qp-pps / opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / hdr / hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-mv-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primar : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Le : 986 cd/m2
Also on a sidenote, is there a way to convert SDR movies to HDR via a filter. I have pixel shader pack for MPC-HC. It has filters that are BT.709 to BT.601 but there is no BT.709 to BT.2020... Know where I can get one?
Thank you.
varekai
26th June 2022, 09:20
@bob88
Be quick and edit out this: Title : ***
bob88
26th June 2022, 12:05
@bob88
Be quick and edit out this: Title : ***
haha! thanks...
any ideas on the HDR thing?
please guys help me. I am tortured by this for weeks... :(
Alexkral
26th June 2022, 19:01
About the color conversion:
https://forum.doom9.org/showthread.php?p=1840255#post1840255
bob88
26th June 2022, 20:11
About the color conversion:
https://forum.doom9.org/showthread.php?p=1840255#post1840255
Thank you for replying.
So from what I understand regardless of the DCI-P3 thing its working properly.
The post also talked about some calibration which I had not done. I set it up like this but Im not sure it makes a difference. Is this proper:
https://i.ibb.co/Yt8pdvT/Screenshot-2022-06-26-220254.png (https://ibb.co/Yt8pdvT)
Also do I need to do anything with this:
https://i.ibb.co/7GQpCtq/Screenshot-2022-06-26-220358.png (https://ibb.co/7GQpCtq)
And what does this do?
https://i.ibb.co/h77hN8j/Screenshot-2022-06-26-220554.png (https://ibb.co/h77hN8j)
Alexkral
27th June 2022, 01:01
For HDR passthrough these settings are not used, so there is no difference between specifying them as you do, or disabling calibration.
Gamma processing is also for SDR output, and is usually not needed.
"disable desktop composition" disables Aero on Vista and Windows 7.
bob88
27th June 2022, 10:40
For HDR passthrough these settings are not used, so there is no difference between specifying them as you do, or disabling calibration.
Gamma processing is also for SDR output, and is usually not needed.
"disable desktop composition" disables Aero on Vista and Windows 7.
Ah ok!
Well after further testing I can confirm that regardless of it saying "-> DCI-P3" HDR is working! YAY! :D
Thank you for your help.
The only question I remain with is is there anywhere I can find a BT709 to BT2020 hlsl filter which I can use in MPC-HC? If anyone knows where I can find it I would love to try it out.
Thanks!
huhn
27th June 2022, 12:09
device-> "device name" -> calibration -> this display is already...
set it to bt 709 and it will turn everything to bt 709 except HDR passthrough which needs bt 2020 to be send at all times.
bob88
27th June 2022, 14:48
device-> "device name" -> calibration -> this display is already...
set it to bt 709 and it will turn everything to bt 709 except HDR passthrough which needs bt 2020 to be send at all times.
Ah Ok I understand how that works. But perhaps you did not get my question. I want to turn BT709 movies to BT2020 via an MPC-HC shader.
I have a pixel shader pack for MPC which has a BT601 to BT709 shader.
I am looking for the next step...
But since I dont understand how the whole thing works perhaps using such a shader is pointless and it will not turn my SDR movies to HDR... so tell me if my request is dumb.
huhn
27th June 2022, 15:41
you set that setting to bt 2020 and that's what will happen.
and no this will not turn it to HDR because HDR is not bt 2020 that's a gamut.
clsid
27th June 2022, 19:06
Disable HDR in Windows, and let madVR turn it on only when needed.
You can not turn SDR video into HDR.
Siso
27th June 2022, 19:14
Disable HDR in Windows, and let madVR turn it on only when needed.
You can not turn SDR video into HDR.
Very well said.
70MM
29th June 2022, 03:14
Would some of the experts here who use 113 mind sharing their HDR to SDR settings page please?
Im curious why many untick most boxes and others have most ticked, can you explain the reasons please?
SirMaster
29th June 2022, 18:23
Would some of the experts here who use 113 mind sharing their HDR to SDR settings page please?
Im curious why many untick most boxes and others have most ticked, can you explain the reasons please?
This is what I use on my projector that is about 85 nit peak white.
https://nicko88.com/misc/madVR%20settings/05%20-%20hdr.png
I quite like the effect of putting a lower peak nits and using the no compression limit to compensate. This helps increase the effect and the effective range of contrast recovery while still using a lower strength curve option.
Sunspark
29th June 2022, 19:30
I was checking something with ShowRenderSteps and there is a line that says chroma 4:2:0 -> 4:2:2.
I do not have full understanding of this.. my display is 4:4:4 (verified) and I have made the observation that if I deselect the 4:2:0 and 4:2:2 rows in LAV it does not label or use the chroma upscaling algorithm and the HUD appears as "h264, 8 bit, 4:2:0 -> RGB32, 8 bit, RGB". What am I missing here?
Ideally, chroma would upscale to 4:4:4 if possible.
huhn
29th June 2022, 21:24
when a simple scaler is used madVR does seem to do 420->422 then 422->444 so you can ignore the line. there is no issue here.
if you disable output formats and lav send RGB then you can not upscale chroma because there is no chroma.
nothing of this has anything to do with what your device does or what madVR outputs. madVR output is RGB always,
djsolidsnake86
30th June 2022, 12:19
i don't understand if is better use d3d11 or dxva copy in lav filter?
huhn
30th June 2022, 13:06
both have the same quality.
d3d11 is faster but quite a number of features don't work.
a copyback decoder is slower but all features work.
el Filou
30th June 2022, 16:18
This is what I use on my projector that is about 85 nit peak white. https://nicko88.com/misc/madVR%20settings/05%20-%20hdr.png I quite like the effect of putting a lower peak nits and using the no compression limit to compensate. This helps increase the effect and the effective range of contrast recovery while still using a lower strength curve option.But you're wasting 35 nits of your projector's dynamic range by doing that.
madshi has stated numerous times in the AVS thread it's a bad idea to not set the peak nits setting to the actual real peak nits you have. It's better to set the real peak nits and use other settings to get an image you like.
Sunspark
30th June 2022, 16:56
both have the same quality.
d3d11 is faster but quite a number of features don't work.
a copyback decoder is slower but all features work.
Power consumption will vary depending on your system. For example, on mine using madvr overlay mode with dxva2-native will cause fan whine due to the increased load caused by the need to convert the texture format to another format. Paradoxically, copy-back will have less load in this circumstance because it is not doing a conversion even though there is more bus traffic.
Only way to tell other than hearing the fan, is to use something like gpu-z to see the load in various configurations, and also how much CPU is being used for any given combination.
SirMaster
30th June 2022, 17:46
But you're wasting 35 nits of your projector's dynamic range by doing that.
madshi has stated numerous times in the AVS thread it's a bad idea to not set the peak nits setting to the actual real peak nits you have. It's better to set the real peak nits and use other settings to get an image you like.
Other settings like what exactly?
I have been using madVR for over a decade and madVR tone-mapping for as long as it's existed in madVR.
I have experimented with all the settings for hundreds of hours and these are the settings that I like the look of the most.
Setting the DLP lower makes the highlights brighter. And setting NCL > DLP stretches out the dynamic range.
Also I love HSTM, but it's not active above DPL. Setting DPL lower allows HSTM to be active lower and I like what that's doing to the darker scenes. If only we could just activate HSTM for the entire range.
To me, with these settings the image subjectively has more dynamic range than with a higher DLP rather than less.
I have another preset with 85 nits set for DPL, and I toggle it all the time, but I never prefer it over my other settings.
I can take a screenshot comparison tonight to show what I mean about why I like my settings.
70MM
30th June 2022, 22:39
Many thanks for your explanation SirMaster, I for one would love to see your comparison screenshot.
What I find difficult for begginers is there are so many settings in HDR to SDR that one needs to be really competent to know, or see what works best.
All some of us can do is to listen to experienced users like SirMaster and try their settings.
huhn
30th June 2022, 23:18
the options are mostly for testing not for actual use. they where never meant to stay like this.
if you want your system to work properly i would suggest to avoid beta versions.
there are known flicker issue(mostly fixed as far as i know in the newest betas) and other not yet removed issues.
Funny thing Ive never ever seen any flicker issue.....So do you think the Tone mapping on the JVC projectors is any better than using 113?
Alexkral
1st July 2022, 08:44
@el Filou
I do this most of the time with my lcd display. The result is expanded to the actual peak nits, so there is no wasted dynamic range.
@SirMaster
I'm curious how this actually works. The "no compression limit" parameter seems to mean that the content remains untouched below it. To achieve this, it's not possible to use a display peak luminance equal to 50. So it seems to me that in this situation, a display peak luminance above that is chosen (say at 150 nits), which guarantees that content below the compression limit is not actually compressed. But then the result must be scaled down to 50 nits, and this final result is expanded to 85 nits by your projector.
For brighter highlights, the original BT.2390 roll-off would be much simpler if it were available.
Edit: I don't know how the result can be scaled down, unless what is sent is not in the full range [0,1]. Can you check if setting a display peak nits higher makes the result different with the rest of your settings? I would say that in this situation it is not used at all.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.