János Tóth F.

  • That’s also interesting, I haven’t thought of that before: why would the (global!) EZ-ADJUST menu become inactive if we only (!) modify a single (!) preset? 🙂

    In other worlds, when you touch the 1DLUT of a picture mode, that picture mode effectively switches to an imaginary “Native” EZ-ADJUST white point preset which is the same as if you man…[Read more]

  • 3. What I noticed during experimenting:
    – there’s no factory 3dlut by default?
    — Technicolor preset has factory 1dlut, I uploaded a unity 3dlut to it and it looked the same as Ciname Home preset (that we can’t modify)
    – the unity 1dlut results in different color temperature (even when user 3dlut is present):
    — open up the menu and take a look at t…

    [Read more]

  • >How come the DV would only use bt.709 data? It doesn’t make any sense.

    In DV mode, the DV chip shall be allowed to handle all the 3D color mapping (dynamic metadata based tone mapping and color space conversion), so any such processing should be bypassed in the TV’s processor. It looks like it was more convenient for LG to leave these steps (…[Read more]

  • I forgot to add: it would be nice to implement that matrix calibration method. CalMAN always uploads a 3DLUT (even when it’s done by running the numbers though a matrix to fill the cube). I am interested to see how a 1DLUT calibration + a real matrix behaves compared to a 1DLUT calibration + a 3DLUT filled from a matrix in HDR10 mode where the…[Read more]

  •  

    On the other hand the amount of near-black flashing wasn’t noticeably higher to me, so maybe the dithering and different subpixel usage are not totally coupled.  I’ll take a closer look at the subpixel usage and take some photos maybe.

    Calman also sets some additional flags if you tell it you have a 2019 model (it doesn’t actually check that t…

    [Read more]

  • I think it was said the C9 models came out-of-the box with a firmware that had the new tone map, the one introduced to C8 with 4.10.31, but I think there was no need to increase Brightness above 50 to raise out of black like it happened to many on the C8.

    I read some speculation that 240Hz (120+120 flicker) BFI was pulled from the 2019 firmware…[Read more]

  • @stoma

    Yes, it’s possible the dithering became more visible on that certain shade of color as the tone response drifted with different LUTs (new factory or fresh custom).

    I think this line is meant to be visible and it’s at least 2 pixels tall (exactly 2 lines on my current 1080p display, could be 4 in 2160p). It’s informative, you can sill see…[Read more]

  • If someone has a 2019 set it would be interesting to check if they behave the same way.

    I played around a bit with the parameters passed to the start calibration command, but they don’t seem to make any difference either way.  Further ideas on that front are welcome (I was actually hoping that they control the near black dithering behaviour, bu…

    [Read more]

  • @janos-toth-f,  Only writing the 1D LUT is supposed to disable the new dithering algorithm.

    The blocking flag should flip during the firmware update if you altered the 1DLUT before you updated the firmware (to a version with the new dithering from a version with old dithering) and it should be cleared if you re-calibrate with the new firmware.…[Read more]

  • @josh-2, Ted recommend to do the measurements while the TV calibration is disabled. This means: enable calibration -> reset the LUT you will upload later -> disable calibration -> take measurements & create LUT -> enable calibration -> upload LUT -> disable calibration -> take measurements for  verification.

    You can’t do this in HDR10 though (and…[Read more]

  • I hope this helps:

    0: Set your PC to Full Range RGB output. Set the TV to HDMI Black Level: High. Set the Contrast to 100 (yes, 100 for SDR as well). (Optionally use YCC and Low if you want to try correcting any internal processing errors with the LUTs).

    0/b: Figure out the OLED Light values you want after calibration by measuring 100% white in…[Read more]

  • I had a chance to take a closer look at the LUT behaviour in Dolby Vision mode on the C8.

    Both the 1D LUT and 3D LUT can be used, but the 3D LUT data which is used is the one marked BT709_3D_LUT_DATA and NOT the one marked BT2020_3D_LUT_DATA as one might expect.

    That’s nice. 🙂

    That DV 3DLUT shouldn’t necessarily target Rec2020 (even when used…[Read more]

  • Yes, agreed that it is not needed to profile in DV  bypass mode, as opposed to just doing it in HDR10 bypass mode as you are suggesting.  I was arguing rather that it would be useful to be able to send test patterns in standard DV mode to validate the calibration procedure at the end.

    Ah! Well, I guess it’s enough to validate a few patches (some g…[Read more]

  • Even in HDR10/HLG mode, sending the static HDR metadata (this can also be done by playing an HDR10 movie on a PC and putting the player to the background) is only half of the story. You also have put the TV into calibration mode where the tone-mapping is bypassed. And, of course, you also wish to fill the hardware LUT with neutral data before…[Read more]

  • Alright thanks.  Is it possible/foreseen to be able to export a 1d LUT from DisplayCal in cube format as well?

    It’s probably redundant for SDR because the 3DLUT does a really good care of the grayscale inmy experiments.

    I am not sure about HDR10/HLG unless you plan to convert the 1DLUT from dispcal results (the .cal 1DLUT file created by an…[Read more]

  • Ah, I finally managed to figure out how to use CalMAN for DisplayCAL generated 3DLUT upload: what it expects in the .3dl (header and data) depends on it’s own patter generator setting which is “TV 16-235” by default (restored every time it’s re-launched or a template re-loaded). After setting that to “PC 0-255” it’s happy with 0-255->0-255 Kodak…[Read more]

  • I wrote down the steps of experimental LG HDR10 hardware calibration with DisplayCAL here: https://www.avsforum.com/forum/139-display-calibration/2962814-2018-lg-oled-calibration-user-settings-no-price-talk-91.html#post58839958

    There is no way of validating the 3DLUT alone in HDR mode after the hardware upload (because the math based PQ->gamma2.2…[Read more]

  • I did a quick test: created a 3DLUT from the measurements of the SDR Game mode with Rec2020 and gamma 2.2 as targets and uploaded it to the HDR Game mode with CalMAN. Aside from some obvious black-crush it seems mostly fine. I think this could actually work. (But I would obviously need to measure the HDR mode and sort this limited/full range thing…[Read more]

  • @stama – Ah, sorry. I forgot I failed with HDMI Black = High because the “expand built-in patterns to PC levels” option works with the built-in pattern window (as I later found out) but not with madTPG (and I used the latter when I gave up with the full range setup).

    I assumed HDR10 uses a different 3DLUT (an actual 3×3 matrix) but it’s Ted who…[Read more]

  • Well, the CalMAN GUI DDC window shows me a 3DLUT table explorer with 64 as the starting point as 0% (the values are in percentage), then 96 at >0%, etc (as the header goes).

    I remember reading somewhere that 64 is mapped to 0 but that comment (as least what I recall from it) didn’t explain what that means (conversion or simply that “64 means 0…[Read more]

  • Load More

Display Calibration and Characterization powered by ArgyllCMS