![]() ![]() Most of pixels composing the highlights above the "soft clipping" have now a better differenciation and the HDR effect will be more pronounced Use the new calculated clipping value instead of "the measured peak luminance". In another word, we are looking for the NITS level of the P=% Quantil for the pixels above "this display target nits" (in our example, 90% of the pixels above 300nits are below 600nits). When C/T=P=90%, then select accordingly the clipping value. C= cumulated number of pixel above 300nits sorted by increasing nits T= total number of pixels above "the display target nits" (in our example 300nits) This "P=percentage clipping value" (in our example 90%) would be used like this: I would propose to give the user a choice for setting "a dynamic clipping nits limit" in "percent" of the number of pixels above "this display target nits". But doing so, most of the pixels are compressed heavily in the process, for those few. So Madvr is compressing the pixels between 300nits to 1000nits in order to NOT clip ANY pixels, even it's only a few. What I have noticed is very often only a few pixels in the image are reaching this peak luminance (let's say 1000nits), but most of the highlights (let's say 90% of the pixel above 300nits) are still below 600nits. ![]() ![]() I am using the HDR to SDR shader math mapping with a 300nits target, with dynamic compression of the highlights up to the peak luminance of each image. I have been thinking lately while watching 4K HDR movies on my projector how to improve HDR "pop" on a low brightness projector.īelow my quoted old idea which you did not like for good reasons.īased on that feedback and my user experience, here here is my new idea: ![]() This will be new feature not a bug fixing. >Madshi says that Madvr follows SMPTE 2390 accuratly. >solution with clipping only a certain % of the brightest pixels through use of an histogramm? I see currently 4 improvement potential through the below discussion:ġ) Madvr could handle highlights even better through light clipping (no bug). The discussion has been going all over the place in avsforum lately. I hope that concentrating all the discussion and effort in one place should enable a faster solution. The next best choice at the moment is the Lumagen pro at the moment for 5000$++ but it does not enable dynamic HDR (yet) Madvr let you choose the "HDR strength" vs "Brightness" through a control called: "this display target nits". You can choose your target color gamut according to your display: REC2020, DCI-P3 D65, REc709 and even better a full 3DLUT calibration over thousand of points! (for example I choose DCI-P3 because my projector covers 100% of DCI) Madvr compress the highlight dynamically: so you get dynamic HDR ala "Dolby Vision or HDR10+. It makes every projector or TV compatible with HDR even if they were not initially "marketed" for that I am myself a very happy user with Madvr HDR to SDR ton Mapping and have been using it for months with a great projector which is officialy not compatible with HDR (Epson EH-LS10000). How to further improve the already great Madvr HDR to SDR Mapping with special focus on projector. Madvr HDR to SDR mapping: already great, soon even better for projector? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |