Huge Delta E – BenQ PD2700U

Home Forums Help and Support Huge Delta E – BenQ PD2700U

Viewing 11 posts - 31 through 41 (of 41 total)
  • Author
    Posts
  • #37938

    Bastien
    Participant
    • Offline

    Ok I will try to do some new profiling tests later this week or next week.

    Thank you for your feedback !

    • This reply was modified 2 months ago by Bastien.
    #37969

    Bastien
    Participant
    • Offline

    Hi @Vincent !

    I follow up on this topic since my last tests within a bran new project with 0 node correction applied.

    Image pipeline : MacBook Pro – Thunderbolt 3 – UltraStudio 4K Mini (via Resolve) – HDMI – BenQ PD2700U
    Target calibration : Rec.709, Gamma 2.4, 100cd/m2

    Following the settings attached below, below are listed the steps I have followed :

    1. Set the BenQ monitor to Gamma 2.4 in its menu settings;
    2. Start the profiling via DisplayCal threw Resolve and adjust the RGB and luminance values via the monitor menu settings;
    3. Generate a 3D LUT targeting Rec.709 Gamma 2.4;
    4. Import the 3D LUT in Resolve as a viewing monitor lookup table;
    5. Verify the calibration via DisplayCal threw Resolve;
    6. Check the measurement report generated by DisplayCal.

    I still find the incorrect results in the reds as you can see in the measurement report attached below…

    Thank you again for you support !

    • This reply was modified 1 month, 3 weeks ago by Bastien.
    Attachments:
    You must be logged in to view attached files.
    #37978

    Vincent
    Participant
    • Offline

    That means that there is some weird behavior in the whole chain as a “single object” [UltraStudio 4K Mini – PD2700U HDMI input limited] that cannot be captured with your current resolution of the 3d mesh of XYZLUT profile. There is nothing more to do unless your deck link card+ resolve can take video data (limited) expand to full in a reliable way, send full thorugh decklink and make teh benq work in full. I cannot help you with that last task because IDNK that decklink capabilities.

    I’ll  say that it is HDMI limited input the culprit, but you’d need further testing with a raspi or a pc, feeding limited input signal data and checking vs full range side to side.

    #37979

    Bastien
    Participant
    • Offline

    I have set the I/O device to send full level and the monitor to display full level.

    After doing another calibration, the measurement report is pretty much the same.

    • This reply was modified 1 month, 3 weeks ago by Bastien.
    Attachments:
    You must be logged in to view attached files.
    #37982

    Vincent
    Participant
    • Offline

    I said that ago: before attempting to validate a LUT3D you must ensure that display matches native gamut profile (LUT3D is a transformation from one profile to another). Otherwise you won’t know if you did someting wrong and you are wasting time.
    If lastest profile is verified with same errors it measn that profile does not match display. Also contrast has drop significatively… which points to user error in the configuration of the devices.

    • This reply was modified 1 month, 3 weeks ago by Vincent.
    #37984

    Bastien
    Participant
    • Offline

    Measurement report 1
    Display vs display (no simulation)
    Video range (monitor + I/O box)

    Attachments:
    You must be logged in to view attached files.
    #37986

    Bastien
    Participant
    • Offline

    Measurement report 2
    Display vs display (no simulation)
    Full range (monitor + I/O box)

    Attachments:
    You must be logged in to view attached files.
    #37993

    Bastien
    Participant
    • Offline

    Hi !

    I have found that setting up the “output levels” to Full range in the “Display & instrument window” for profiling gives me better results using Video or Full range in the [monitor + I/O box] pipeline :

    Measurement report 1 — 2022-12-05 13/27/11
    3D LUT in Resolve as a viewing monitor lookup table
    Display vs Rec.709 Gamma 2.4 (simulation)
    Video range (monitor + I/O box)

    Measurement report 2 — 2022-12-04 22/46/38
    3D LUT in Resolve as a viewing monitor lookup table
    Display vs Rec.709 Gamma 2.4 (simulation)
    Full range (monitor + I/O box)

    Do you find anything positive in those results @Vincent ?

    Thank you again for your support !

    Attachments:
    You must be logged in to view attached files.
    #38040

    Vincent
    Participant
    • Offline

    both show colorspace desaturation vs predicted. Maybe you shoudl as Blackmagoc to assist you in tde IO box configuration since it seems the one that is messing the pipeline

    #38041

    Bastien
    Participant
    • Offline

    Thank you for your feedback Vincent !

    I have asked Blackmagic about this. Hope they will be able to provide support to my case.

    BTW, if it can help, here is an access to my workflow, settings and image pipeline :
    https://app.milanote.com/1P43C31xxzvjg4?p=8He5MuhLdo8

    • This reply was modified 1 month, 2 weeks ago by Bastien.
    • This reply was modified 1 month, 2 weeks ago by Bastien.
    #38054

    Bastien
    Participant
    • Offline

    both show colorspace desaturation vs predicted. Maybe you shoudl as Blackmagoc to assist you in tde IO box configuration since it seems the one that is messing the pipeline

    Don’t you think the result is close enough according to the ∆E results ?
    The colorspace desaturation seem to be quite limited if not imperceptible to the naked eye.

Viewing 11 posts - 31 through 41 (of 41 total)

You must be logged in to reply to this topic.

Log in or Register

Display Calibration and Characterization powered by ArgyllCMS