novideo_srgb: GPU-side LUT-Matrix-LUT calibration

Home Forums General Discussion novideo_srgb: GPU-side LUT-Matrix-LUT calibration

Viewing 15 posts - 106 through 120 (of 135 total)
  • Author
    Posts
  • #139972

    Vincent
    Participant
    • Offline

    No if “madVR xxxxxxxx” or “AW xxxxxx” were made at native gamut.

    #139973

    S Simeonov
    Participant
    • Offline

    No if “madVR xxxxxxxx” or “AW xxxxxx” were made at native gamut.

    They were made at native gamut dci-p3.

    #139974

    Vincent
    Participant
    • Offline

    Then those setting are wrong. I’m not a native english speaker, but “from Rec709 to “simulated colorspace by novideo_sRGB”” does not seem so difficult to understand.

    #139975

    S Simeonov
    Participant
    • Offline

    Then those setting are wrong. I’m not a native english speaker, but “from Rec709 to “simulated colorspace by novideo_sRGB”” does not seem so difficult to understand.

    There is no way to keep novideo_srgb turned on, and watching a movie in madvr with 3dlut made specifically for madvr, it becomes a dark and desaturated mess. The correct way would be, for novideo_srgb to turn off automatically when madvr is detected, just how diplaycal profile loader works.

    • This reply was modified 5 months, 2 weeks ago by S Simeonov.
    #139977

    Vincent
    Participant
    • Offline

    Then those setting are wrong. I’m not a native english speaker, but “from Rec709 to “simulated colorspace by novideo_sRGB”” does not seem so difficult to understand.

    There is no way to keep novideo_srgb turned on, and watching a movie in madvr with 3dlut made specifically for madvr, it becomes a dark and desaturated mess.

    Because you are doing it wrong, you are chaining 2 color transforms that asume (each one) taht display behavior has native , and that is true only for one of them.

    It’s 100% user’s fault.

    The correct way would be, for novideo_srgb to turn off automatically when madvr is detected, just how diplaycal profile loader works.

    The correct way would be using a LUT3D on madVR that reencodes “from Rec709 to “simulated colorspace by novideo_sRGB””, and that’s what you are not doing.

    Then you apply an AMD driver, novideo sRGB or DWMLUT it is applied globally. Like if uyou had HW calibration capabilities on your display, hence all apps using that group [swoftware simulation + display] must acknowledge current status of that group.

    #139978

    S Simeonov
    Participant
    • Offline

    I’ve tried that too, same result. “simulated colorspace by novideo_sRGB” is srgb.

    • This reply was modified 5 months, 2 weeks ago by S Simeonov.
    • This reply was modified 5 months, 2 weeks ago by S Simeonov.
    #139983

    Vincent
    Participant
    • Offline

    Then such LUT3D won’t desaturate… it can’t (rec709 -> sRGB), unless you had not assigned it to Rec709 slot in madvr lut3d config and that is user’s fault.

    #139984

    S Simeonov
    Participant
    • Offline

    The 3dlut is in the correct slot.

    #139985

    Vincent
    Participant
    • Offline

    Then it cannot desaturate and the claims are false.

    #139986

    S Simeonov
    Participant
    • Offline

    For the 3dlut in madvr to work, it needs the windows calibration disabled.

    #140246

    zunderholz
    Participant
    • Offline

    novideo_srgb added support for “L* EOTF”. What is this?

    https://github.com/ledoge/novideo_srgb/releases/tag/v4.1

    #140251

    Vincent
    Participant
    • Offline

    A gamma value that results in something like visually equal distances between a grey and another. It has a gamma that starts low, 1.x and then rises to 2.x. It’s like sRGB TRC but more extreme.

    #140266

    noiremk2
    Participant
    • Offline

    Just to make sure, I have novideo_srgb going still.

    For my generic icc profile in windows, should I be using a generic synthetic gamma 2.2 profile generated by displaycal, or the stock srgb one?

    I just wanted to verify, since I’m calibrated for gamma 2.2 offset 50%, and I’m not sure if setting it to srgb or gamma2.2 is more correct when selecting a synthetic profile.

    #140270

    Vincent
    Participant
    • Offline

    This is the old disccussion about if sRGB content is meant to be displayed on g2.2 or if you must honor color management definitions : display behavior = display profile. I like the second one.

    #140276

    Old Man
    Participant
    • Offline

    Shouldn’t you profile the display and use that?

Viewing 15 posts - 106 through 120 (of 135 total)

You must be logged in to reply to this topic.

Log in or Register

Display Calibration and Characterization powered by ArgyllCMS