EIZO CG247x + Davinci Resolve

Home Forums Help and Support EIZO CG247x + Davinci Resolve

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #8423

    KolossPhilos
    Participant
    • Offline

    Hey Community!!

    i am a little confused….and a lil rookie so i have a few questions!

    I want to connect the CG via decklink mini monitor with resolve.

    So the CG247x is hardware calibrated right? (so i need to use the color navigator software to do this?)

    I’ve read a lot about the calibration thing…for my understanding if the monitor is hardware calibrated i dont need to do anyhting more that that right? or not?

    Others say they run the monitor in “native” mode and calibrate it via displaycal and davinci with a 3D LUT (but where then is the sense of having a hardware calibrated monitor?)

    so what way to go?

    1. Calibrate with Colornavigator  only?
    2. set the monitor to native and do a 3d LUT with displaycal within resolve?
    3. Hardware calibrate and then on top a displacal-resolve calibration?

    …so which path to take….can’t wait until i can afford a flanders ..but till then i really need your help! 🙂

    for what i’ve read the setting most ppl use are “Rec709, 2.4, 100cd/m2, Min Black Level” what do you think about that?

    most of the stuff i’m doing is for web tho….but i buy the monitor because i will be grading a documentary soon and i want it to be accurate.

    sorry for the noob questions but there is so much different information and opinions out there and its so difficult to get it as a rookie!

    thanks in advance

    Phil

    #8430

    Florian Höch
    Administrator
    • Offline

    Hi,

    so, you have the agony of choice. If you want to figure out which way to go, you could compare the accuracy of the two mentioned main approaches (ColorNavigator vs. native + DisplayCAL 3D LUT). I wouldn’t go the ColorNavigator + software 3D LUT on top route, as for profiling you want the monitor to be in its native gamut mode without any alterations.

    As this is a professional graphics display with a very linear IPS panel, you can probably reduce the amount of patches measured considerably (try the default 175 instead of the DisplayCAL Resolve preset default of around 1500, which is more aimed at TVs and their nonlinearities).

    “Rec709, 2.4, 100cd/m2, Min Black Level”

    If that’s related to ColorNavigator then I can’t comment because it is unclear to me if “2.4” means a “pure” power curve, Rec BT.1886, or something else entirely. Rec709 gamut and 100 cd/m2 sounds reasonable.

    #8436

    KolossPhilos
    Participant
    • Offline

    Hi Florian,

    thank you so much! really! My Monitor arrived today and i’ve tried it right away…

    turned out that the color navigator way seems to be blocked due it’s not showing up when i’ve connected the monitor via ultrasrudio mini monitor 🙂 but the native way sounds better anyways!

    tried it the fast way today with sRGB through DisplayCAL via Davinci for a actual project wich is meant for web to test.
    Is is ok to just use the sRGB preset end then go? sRGB is gamma 2.2 right?

    so…I like the result quite a lot! Seems to be less saturated on the eizo and the highs are a bit dull ..but maybe i just have to get usedd to the monitor…btw i also did a second calibration for the Video Monitor in GUI..worked well too even tho its a bit different (its a NEC PA2272w).

    For the REC709 Question …i don’t really know what i am talking about thats the thing 🙂
    I would just go with the resolve preset thats already in DisplayCAL? that says 1886… is that gamma 2.4?

    And in general… the ppl are saying that sRGB is equal to REC709…but it then has to be the REC709 with gamma 2.2 right?

    My near future Project will be sent to festivals for screening so the safest way to set up the project will be REC709 1886? and then convert it later to DCI or sth?

    #8439

    Florian Höch
    Administrator
    • Offline

    Is is ok to just use the sRGB preset end then go? sRGB is gamma 2.2 right?

    You’d need to make the right alterations (e.g. disable 1D calibration, enable 3D LUT), and keep in mind you cannot target the sRGB curve for a 3D LUT from the main GUI (but you probably wouldn’t want to do that anyway, Rec.1887 with a roughly 1000:1 contrast display is almost identical to the sRGB curve). It’s easier to start from the “3D LUT for Resolve” preset.

    I would just go with the resolve preset thats already in DisplayCAL? that says 1886… is that gamma 2.4?

    Rec.1886 uses an exponent of 2.4, but due to display contrast being taken into account, the end result is usually closer to an overall gamma of roughly 2.2 (but comes quicker out of black).

    And in general… the ppl are saying that sRGB is equal to REC709…but it then has to be the REC709 with gamma 2.2 right?

    sRGB uses the Rec709 primaries, and has a tone response that has an overall gamma of roughly 2.22, but comes quicker out of black than a pure power 2.2 curve would.

    My near future Project will be sent to festivals for screening so the safest way to set up the project will be REC709 1886? and then convert it later to DCI or sth?

    That sounds about right.

    #8445

    KolossPhilos
    Participant
    • Offline

    ok so i will skip this sRGB move and go with REC709 BT!

    I set the Eizo to Adobe RGB, Native Gammut, 120cd….
    calibrated today again with the REC.1886 preset and it looks good so far!

    Now the pictures are a little bit brighter/less contrasty than with sRGB and i can see more noise in the blacks…
    seems also to be less saturated than the sRGB? I’m just afraid that on sRGB devices it will look to saturated….

    watching the same pictures on the iphone its quite close now 🙂 … closer than the sRGB…and anything before i had done!

    another question…in resolve i have to set output colorspace but i just can find the following:
    REC709 (scene)
    REC709 2.2
    REC709 2.4

    so there isn’t anything saying “RC.1886″…is then the 2.2 version the right one as you pointed out that the 1886 results in roughly 2.2?

    hope we soon have all devices display DCI-P3…. 🙂

    #8446

    Florian Höch
    Administrator
    • Offline

    I’m just afraid that on sRGB devices it will look to saturated….

    There’s no such thing as “sRGB devices”. Most consumer displays are close, but all over the place. You can’t do anything about it.

    another question…in resolve i have to set output colorspace but i just can find the following:

    Sorry, not an Resolve expert. You may want to ask in Blackmagic Design forums.

    #8453

    KolossPhilos
    Participant
    • Offline

    for what i’ve experienced the last time is that apple devices have akind of reliable “calibration” and not totally all over the place.
    what i’ve read that they are using sRGB…. my tests today are that on the iphone the rolloff in the shadows is harder than on the eizo….

    i also read an article that they will maybe introduce DCI-p3 with the iPhone 7!

    thanks again man for your time! really brought some light in the dark!
    really impressed by DisplayCAL btw…shpuld have used it much earlier 🙂

    #8454

    Florian Höch
    Administrator
    • Offline

    for what i’ve experienced the last time is that apple devices have akind of reliable “calibration” and not totally all over the place.

    Yes, but not everyone has an Apple device.

    what i’ve read that they are using sRGB…. my tests today are that on the iphone the rolloff in the shadows is harder than on the eizo….

    They’re likely not using the sRGB response curve, but a gamma of around 2.2.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.

Log in or Register

Display Calibration and Characterization powered by ArgyllCMS