- This topic has 18 replies, 5 voices, and was last updated 2 years, 7 months ago by
.
-
Posts
-
I already bought a calibrite and returned it the same day when it made a horrible mess of my display…
Then I found out about this software, so I buy a used x-rite i1 display on ebay and try again.
This software is a bit better (the software from calibrite made my white balance super yellow and dark and washed out)
But, it still isn’t right… my resulting profile with DisplayCAL is closer to white balanced, but so washed out, so low contrast it’s by no stretch of the imagination “calibrated.”
I’ve worked in film for 15+ years… I’ve learned to calibrate monitors with color bars back in the day… I can calibrate my monitors better by eye even if it takes me making minor tweets over days… which is why I want to make this software work for me, I figure I can’t be perfect. But WTF is this?
I realize I might not be used to the resulting profile, but the results I’m getting are absolutely ridiculous… I know for a fact NO ONE will ever see the resulting video I export with this DisplayCAL profile the same as I am seeing it WITH it. I Use premiere pro, I can TELL that the GUI is NEVER meant to look the way it does with the displaycal profile, that alone proves my calibration is no where near correct… therefore it’s useless… it’s not correct, it completely undermines the point of calibrating.
What could I be doing wrong… every time I do this I get ultra low contrast, washed out everything, no blacks at all… is this a common problem?
Tristimulus colorimeters need to be corrected for each different display type in order to give an accurate result.
Please share the make and model of your monitor and the name, if any, of the correction you’re using.
A screenshot of your settings on the first tab of Displaycal would also help
I have a samsung 43″ CU7000.. i don’t know what you mean by what correction I’m using…
Also I don’t know what the point of screenshoting the settings on the first tab of Displaycal would be… show you the settings that DON’T work?
Pretty sure I have it set correctly on the first tab… which is why it NOT working is frustrating; am I supposed to set it to something counterintuitive to make this actually work?
Colorimeters use three filters, red, green and blue, to read the colours from a display. They do not read the absolute wavelength of light, or more accurately, the spectral power distribution. This means they cannot accurately distinguish between the different backlight and panel technologies. They need to be “corrected”, translating their readings into readings accurate for that panel type.
This translation is done in Displaycal with a CCSS file. This CCSS file is a set of absolute spectral power distribution readings taken with a high end spectroradiometer that characterize the display’s energy levels through the entire range of wavelengths emitted by the display.
Displaycal / Argyll has a whole host of these spectral readings for different display types. This is the second line tagged “correction” in the first tab of Displaycal. You need to select the appropriate correction.
Also I don’t know what the point of screenshoting the settings on the first tab of Displaycal would be… show you the settings that DON’T work?
To confirm that you’re NOT using a correction, which is why you’re having this problem. You’re using uncorrected readings.
Pretty sure I have it set correctly on the first tab…
No you haven’t.
As to which option you should choose, it’s not immediately apparent to me without doing a fair bit of searching for specifications on your device.
It seems to be an edge-lit VA panel, but specifications on this device are not very helpful and it doesn’t get a lot of technical reviews it seems, so hard to tell.
Maybe try with both the Spectral: RGB LED family and Spectral: White LED family set in the “corrections” dropdown and see whether you get a better result.
So I’ve tried this now and come to this conclusion…
So here’s why calibrating like this is objectively flawed… it simply doesn’t provide any consistent results… it’s not calibrating ANYTHING… thus how can it be used to “calibrate” more than one monitor? It can’t even calibrate ONE monitor.
The results seem mostly dependent on the initial manual white balance you must do pre calibration, which also seems to be where the overall contrast is set… the software doesn’t set contrast. It asks you to adjust the white balance until the three bars line up and it gives you a green go ahead… THAT point where they line up is already incorrect. Obviously too red on my monitor, the resulting calibration profile is NOT far off from where I started.
So again… HOW can this calibrate more than one monitor if it can’t produce a result on ONE monitor. It doesn’t know what D65 white is it seems.
When
So I’ve tried this now and come to this conclusion…
So here’s why calibrating like this is objectively flawed…
I would say that user (e.g.) knows nothing.
it simply doesn’t provide any consistent results… it’s not calibrating ANYTHING… thus how can it be used to “calibrate” more than one monitor? It can’t even calibrate ONE monitor.
The results seem mostly dependent on the initial manual white balance you must do pre calibration, which also seems to be where the overall contrast is set… the software doesn’t set contrast.
This reasures my previous statement.
It asks you to adjust the white balance until the three bars line up and it gives you a green go ahead… THAT point where they line up is already incorrect. Obviously too red on my monitor, the resulting calibration profile is NOT far off from where I started.
John D already explained how to do this.
The rest of your sentence is false since DisplayCAL or i1Profiler calibrated grey to whatever TRC you choose and matching the white you set as reference (numerical -once you had setiup your measurement device correctly- or visual -which seems that you had not tried)
GPU caibration software calibrates grey. That’ts its purpose. Then it measures display to see how it behaves after grey calibration. With that info (stord in an ICC profile) this o other software can do other things including colorspace simulation.
I’d start reading stuff to understand what that sentence means, then go back to calibration.So again… HOW can this calibrate more than one monitor if it can’t produce a result on ONE monitor. It doesn’t know what D65 white is it seems.
When
99% is user’ fault because it does not know what he is doing, does not read documentation and ask the same questions of hundreds before him for free
No, I’m objectively correct … if you can’t understand why it exposes what an amateur you are; even if you somehow get a result from this thing it doesn’t matter… it’s not effective.
I spent yesterday doing calibrations for hours; tried everything mentioned in this thred, then everything mentioned in youtube videos on the software. First of all, no setting no matter what calibrated the monitor correctly… thus the software DOES NOT CALIBRATE, it doesn’t know what the word calibrate means.
The problem is this… it comes down to the initial balance it asks you to do… whatever is done there sets the stage for the rest of that “calibration” which isn’t a calibration at all. I can by pass Nvida control panel and only use me menu settings to white balance… this results in a red tinted white, even when specifically selecting D65. Also without the graphics card control the contrast is over the top… the calibration doesn’t change that. So… onto using the Nvida to attempt to balance AND control the white balance since the “”””calibration””” doesn’t calibrate. Now I can dial in the contrast to whatever I want knowing the software won’t affect the contrast. You can also make the brightness either at the level they specify OR 4x times that… the meter stops reading it at a certain point. And ALSO because it doesn’t seem to detect contrast it doesn’t detect brightness changes DUE to changes in contrast (which I REALLY don’t understand, but we’ve established that the software doesn’t work). Here’s the smoking gun; eventually after being sick of the software thinking a red tinted white square is white, I set the white balance myself. R-G-B close to 0 (the software had me at -23 for blue or something and +16 for red, because it’s BROKEN) SO I just eyeball it… then calibrate ignoring the fact that the setup sees the white as too blue. Guess what… the final profile it generates is almost exactly the balance I DID MYSELF. Again… the software doesn’t calibrate ANYTHING.
If I get the energy to try again for another 6 hours maybe I’ll record what I do to explain to you people why calibration should not yield a completely different result every single time.
You are not supposed to touch anything color related in the GPU driver panel 🤦♂️😂
You are calibrating a TV with a “LCD White LED” panel type, it has 10 point white balance calibration plus color gamut calibration, when using DisplayCAL you want to adjust the 100% IRE inside the TV to match the desired white point and white level.
Ideally you should do the 10 point white balance calibration with HCFR plus a TPG and adjust the gamma, white level and white point at the hardware level, later you can create an ICC profile with DisplayCAL with everything set to “As measured”.I will not explain anything further because of the temper tantrums in your comments and also calling Vincent an “amateur”.
Be more civil next time.If you knew how to read you’d see that I uninstalled everything related to the GPU control panel.
You like these other two are obsessed with repeating technical specifications as if I don’t know them… I’m already a light year ahead of you telling you this thing DOES NOT WORK..I already gave you an explanation as to why even if you THINK it works, it still doesn’t. I am correct whether you realize it or not.
Trying to adjust the white balance through the Nvidia control panel in the first place just demonstrates how very little knowledge you have in the subject matter.
LOL… you literally CANNOT READ can you?
I’ll tell you again that when I did do that, it yielded a better result because it’s the only way to control the contrast… but again… you don’t read!
You also recommend using a program I’ve never heard of HCFR just to adjust the white balance… so you admit yourself Displaycal DOESN’T WORK… my entire point!!!!!!!
I didn’t say that, re-read the post slow and carefully.
Ideally you should do the 10 point white balance calibration with HCFR plus a TPG and adjust the gamma, white level and white point at the hardware level, later you can create an ICC profile with DisplayCAL with everything set to “As measured”.
are you trolling or a mental retard?
You corroborate EXACTLY my point, this software doesn’t work, doesn’t calibrate anything and at best leaves your white balance, contrast, and gamma where YOU set them.
It thinks white on my screen is RED… when I correct it and make the RGB closer to zero the resulting profile is closer to that neutral white which is actually closer to a blue than red… THUS, the software does NOTHING.
Why is that hard for you sycophantic nerds to admit? Let me try to give you a mental picture…
If the software ACTUALLY calibrated the screen… the white level would become the SAME in the end (D65 as specified) whether the screen was slightly red or slightly blue from the onset.
