@janos666 pointed out that I have to upgrade from v3.8
So, it's on the 3dlut tub, other formats are available beside of madvr in the dropdown.

No, it doesn't, only 33x33x33 is available.
But since other formats have different cube sizes (included 17 as well), can you add support for 17 points Cube as well for LG OLED format?

Thank you!

I have a Samsung Q80R 82” can I have any tips for calibraton Sdr and Hdr? I can use displaycal or calman for manual calibration. i want to have the best quality and if possibile create also a 3d lut for Madvr Hdr to Sdr as I had before on my projector.

Thanks.

I have observed a strange behavior and I am trying to understand it before I go ahead and profile my JVC RS500 projector and create 3dLUTs for MadVR. Maybe, someone can help me understand what is going on?

The problem happens as I try to adjust the 100% white, 6500K whitepoint.

The probe is an i1. It is fixed on a tripod and it never moves between readings.

First, I adjust my PJ to D65 with the i1 connected to my laptop, running Chromapure3, displaying a 100% BT709 white field from AVSHD and played through Madvr. In madvr, I have chosen "disable calibration controls for this device". Madvr reports matrix BT709 and primaries BT709. I manage to get CP3 to report a corrected color temp of 6456K, deltaE 0.5, so, I am happy! (image1)

But, after that, I open DisplayCal and start profiling my display. Same i1 probe, no correction file. When the display adjustment window shows up before profiling starts, madTPG displays its full 100% white pattern, and the resulting reading is a lot different: color temp is reported to be 6752K? and the RGB bars, of course, show there is way too much blue. (image 2)

Why such a difference? I am trying hard to find out what I am doing wrong.

Since I will be watching my movies through madVR, I believe the white 100% displayed by madVR and read through Chromapure 3 is the white I will see when watching a movie. But why Displaycal reports a white so much different? I am just trying to understand and start my profiling with a correctly adjusted D65...!

Attached Thumbnails

   

You say i1 meter, but do you mean like the i1Display Pro colorimeter? Are you using the same colorimeter correction between ChromaPure and DisplayCAL?

Are you using the madVR test pattern generator (madTPG) for DisplayCAL? You probably should be as that's what you need to use when generating a 3DLUT for madVR anyways.

Please don't go by color temperature. 6500K can vary between a cyan and a magenta tint and still be 6500K. Michael Chen (MichaelTLV here) demonstrated that years ago. Use the proper CIE x,y coordinates for D65 instead.

Thanks a lot for your inputs.

I am using the i1 pro2. I will try to use madTGP as the pattern generator for Chromapure3 and report back.

As for the color temp being inaccurate in Kelvins, the two pics I have attached also show that the color coordinates differ (x=0,313 and y=0.330 as reported by chromapure, deltaE 0.5 versus x=3085 y=0.3275 deltaE 2.5 as reported by DisplayCAL). Maybe the difference between those two color temps is not significant?

What “Mode” did you select in DisplayCAL? Does it correspond to the setting in ChromaPure?

Correct Colour Temperature is a “necessary but not sufficient condition”. IOW, 6500K may not be D65, but 6752K is definitely not D65.

Finally getting around to creating these correction files. Do I create them with both meters in position or does it do one and then the other?

Makes no difference as long as the projector doesn’t drift while you swap the meters. Note that meter should be warmed up for about half hour, and should be aimed at the same part of the screen, typically the centre.

Is it ok to have the meter up to 3’ away from the screen?

The distance is not an issue as long as you can make sure the meter is aimed at the pattern.

Hi, to isolate the problem, display manually from your TV USB for example a white patch from AVSHD (or from an external player you have) and then measure that patch from ChromaPure and from DisplayCAL.

Doing this you will find out if the difference is related with the meter operation.

Currently have DCI filter in place on my NX9 and thus have madvr set to calibrated to DCI-P3.
I plan to take the filter out (use HDR color mode). What should I change the calibrated to setting in madvr to? Should it be BT2020?

Yes, BT2020 unless you make a color profile with autocal that is DCI-P3 gamut without the wide color filter.

Is that preferred?
If so, how do you do that?

I get 72 nits with DCI filter in place but 93 nits when in HDR color mode (no filter) but if I can somehow preserve the extra color and keep the brightness that would be great.

Heh, well the wide filter is precisely what lowers the light output, so of course you cannot have wider color without it. If that were possible why don't you think they would have done that in the first place?

Is it preferred? It's only really preferred if you are calibrating with a 3DLUT as it seems to give a better result while using fewer patterns with DCI-P3 rather than BT.2020 gamut.

You do it with autocal in the create color profile section.

Finally completed this. Have the two files generated. Is there any way that I can test to ensure that both devices measure the exact same now?

I've attached screenshot of the variance result. Was it just marginally off the mark or way off the mark?

Attached Thumbnails

 

Well we don't know what it was before correction. That is showing the i1 Pro 2 readings vs. the corrected i1D3 readings.

That already shows that they both measure very closely now, at worst 0.0602 dE for blue.

Got it. Good point. Thanks a ton

So now in the future when you wont have the i1 Pro 2, to touch up your calibration you can redo gamma with the Spyder, and then for color, you can use your corrected i1D3 with HCFR and use autocal custom gamma editor to edit 12-point white balance which you can touch up your greyscale and color temp with.

Awesome, thanks very much and that saves me buying an i1pro2.

I'll probably do one more full calibration with my Spyder and i1pro2 while I have it since my hours on bulb are now at 250 (was 130 when I first calibrated it).

Then hopefully I'll just do it as you explain when I reach 600 hrs or so.

Do you think that's a good approach (i.e. do you think my bulb at 250 is pretty much settled in)?

Yeah probably for the most part.

Tried using the ccmx file (DisplayCal correction matrix) I created in HCFR and I could not get it to load (i.e. display in that little HCFR dropdown). I copied the file to multiple HCFR folders but nothing.

Any ideas?

The file goes in: C:\Users\"username"\AppData\Roaming\ArgyllCMS

Then you should see it in the Display Type dropdown in the ArgyII Meter Property page in HCFR, usually at the bottom of the list.

Is there a place where you can rent the high end calibrators?

Hello everyone !

I'm trying to generate a 3DLUT for HDR content to HDR display with MadVR using tone map using external 3DLUT.

When using DisplayCal with madvr HDR settings, there are 2 things I need to get a confirmation please :
-first, when it launch MadTPG, I cannot select HDR. "Your display doesnt seem to be HDR capable". When I use Windows display settings to activate HDR, TV switch to HDR, and MadTPG is indeed with HDR button active. Is it the normal way to do it ?
-second, with the interactive display adjustement, what cd/m² should I aim ? In SDR I set it to 150cd/m², but what about HDR ?! TV get a lot brighter as soon as it switch to HDR mode, so I guess I have to set it way up more ? (by default it's around 290)

Beside that, after generating the 3DLUT, and set it on MadVR, when I watch HDR content my TV does NOT switch to HDR. If I set up MadVR to HDR passtrought, TV switch correctly. It seems the 3DLUT mess the HDR metadata ?

Complete configuration :
-Philips 854OLED
-GTX 1050Ti
-GeForce 441.41
-Windows 10 1903
-i1 displaypro
-MadVR 0.92.17
-DisplayCal 3.8.9.1

DisplayCal is setup with the "Process HDR Content", not "Convert HDR content to SDR". I can put all other settings but can't see how it could be related (and I did not setup anything special from default config exept 720 peak nits)

My guess is, it's related to MadTPG that cannot switch to HDR by itself ?

Thanks a lot for your help !

edit : the problem comes from madvr 0.92.17, it's working as intended with 0.92.16 !