- This topic has 200 replies, 40 voices, and was last updated 7 months, 2 weeks ago by
.
-
Posts
-
- Offline
I installed Display Cal on y mac m2 but it just crashed each time I tied to open it
@flatscan please create an issue ticket on https://www.github.com/eoyilmaz/displaycal-py3/issues
- Offline
Ok, I just did but there were so many I don’t have much faith ill get any help.
Thanks for trying.I installed DisplayCAL 3.9.15 (Installer) on Windows 11, but I have some problems with it:
– When trying to check the profile of my Eizo cs2420, which I calibrated with Color Navigator 7.
I run the measurement report, the program allows me to resize the measurement window, but when I run the verification the measurement window shrinks to the smallest size, ignoring the settings I had made on it before.– At the end of the measurement, it returns the verification report to me in HTML format. In this report, I see that the white point of my monitor is totally wrong.
Instead, if I use the function Tools > Report > “Report on Calibrated display Device”, it seems to work fine, in fact in this case the settings of the measurement window are maintained, and in the report the white point looks more correct.-If I try to make a measurement report for my second monitor “Dell u2515h,” the measurement window appears on this monitor, but when I start the measurement it returns to the primary monitor.
So I uninstalled this version of DisplayCAL and reinstalled the old 3.8.9.3.
In this version the measurement report seems to work as expected, also the measurement result returns good values for the white point.I am using the i1Display pro as a colorimeter.
Thank you for your time and effort, which you are giving to keep this fantastic Software alive.I apologize for my bad English.
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.-Newer CS2420 are WLED PFS phosphor, although you may have an older model which had worse QC and contrast.
-ColorNavigation has 2 sets of corrections for CS line & i1d3: default (matrix, hance non portabel and somehow innacurate), EDR/CCSS based on U2413 GB-LED (innacurate for your display). Get CS2731 EDR from Eizo APAC and replace it in “C:\ProgramData\EIZO\Sensor\i1DisplayProEDR” on EVERY APP UPDATE
-Current Windows DisplayCAL-p3 has an issue with HTML report and corrections. macOS runs fine. For testing whitepoint use tools/report/calibrated screen report. It will run a basic test and output results in console.
-DisplayCAL-py3 is making great advances for Win version but unless you have an i1Pro3 or some issue, stay in old DisplayCAL till most of issues are fixed. It’s going fast.
-Old DisplayCAL is measuring “AS COLOR NAVIGATOR”, not “good” or accurate because of the things explained above.Depending on each i1d3 firmware data you may or not get a huge improvement in white by using de CCSS/EDR with the actual SPD of newer CS2420, or get same white.
In my experience “default” value in color navigator for correction (“color managed”) give >3dE to i1Pro2/3 or i1d3 using proper EDR, but depends on colorimeter.
If going to use ColorNavigator + DisplayCAL use “no compensation” corection in ColorNavigator preferences and replace GB-LED EDR with WLED PFS one.
Patches EDRs for WLED PFS Eizos can be found on Lift Gamma Gain forums, Stuart Pointon.Please report any bugs, feature requests at http://www.github.com/eoyilmaz/displaycal-py3/issues
I don’t monitor posts at this forum…
Thanks, Vincent, I replaced the EDR file in Color navigator 7 with the one you suggested and did a new calibration.
Although the measurement report done with DIsplayCAL, using “Spectral: LCD PFS Phosphor WLED Panel” as a correction is good, I notice that the monitor now appears with a reddish color cast, this even in applications that are color managed.
If I compare side by side the cs2420 with my Dell u2515H, both calibrated with the same white point, it seems to me that the colors match much better with the profile created with the original EDR file. Obviously, I know that monitors have two different panels, but with the profile made with the original EDR, the difference between the two monitors was not as noticeable.
Could it be that my Eizo has a panel with an older technology?
Please report any bugs, feature requests at http://www.github.com/eoyilmaz/displaycal-py3/issues I don’t monitor posts at this forum…
Okay, I will do that tomorrow. Thank you.
Thanks, Vincent, I replaced the EDR file in Color navigator 7 with the one you suggested and did a new calibration.
Although the measurement report done with DIsplayCAL, using “Spectral: LCD PFS Phosphor WLED Panel” as a correction is good, I notice that the monitor now appears with a reddish color cast, ***this even in applications that are color managed***.
Color cast in white/grey?
Maybe your’s is older, hence a GB-LED. In that case, like if you has a CS2730 you’d keep RGphosphor EDR.
Maybe your i1d3 is an outlier, an unit where its firmware spectral sensivities do not match actual colorimetr behavior. Maybe you did it wrong: close CN7, replace EDR, open it, choose “no compensation” & recalibrate in CN7.
Maybe you are an outlier form generic model of std osbserver and PFS red peaks do not help to get metamers.
Without an spectrophotometer IF there is a visual mismatch … it’s guessing.Anyway if you trust that the color cast is real, because of the reasons explained above, restore old EDR.
OR, is there is always a visual cast, use ColorNavigator7 (or NEC’s , maybe Benq palete master ultimate too) post calibration adjustment. and remove color tint visually in white.Why?
Color managed apps (ICC profiles) DO NOT CARE AT ALL about whitepoint, they won’t do anything about it. We exclude here absolute colorimetric LUT3D like the typical ones in Resolve or madVR.If I compare side by side the cs2420 with my Dell u2515H, both calibrated with the same white point, it seems to me that the colors match much better with the profile created with the original EDR file. Obviously, I know that monitors have two different panels, but with the profile made with the original EDR, the difference between the two monitors was not as noticeable.
Difference between EDRs is mostly due to WP diferences. There won’t be gamma or huge “visual” primaries error in profile, just a white point color cast difference.
Could it be that my Eizo has a panel with an older technology?
Maybe, as you may see in DIsplayCAL colorimeter corrections and as I said before, some CS2420 units are GB-LED, some WLED PFS:
https://colorimetercorrections.displaycal.net/
(unless they were deleted you’ll find these 2 flavors for CS2420, you can plot SPD with ARgyllCMS specplot or DIsplayCAL “i” button in correction)Also ” LCD PFS Phosphor WLED family <PFS_Phosphor_Fa…ly_31Jan17.ccss>” or its equivalent EDR is not the same as Stuart Pointon or even “HP Z24x G2” bundled with DisplayCAL. PFS phsophor family is a colection of several PFS, some of the are just sRGB with a mix of primaries.
Stuart’s or “HP Z24x G2” bundled with DIsplayCAL or HP Dreamcolor HW cal solutions are samples of a WPLED PFS with near P3 red, near AdobeRGB green an typical blue led.
But they should not differ between them on most i1d3 units. Not the same but close.It may or may not be related, but I read that the Topaz post processing software crash on M2 Macs (only)
Unfortunately I can’t even install v16. Do I have to install anything else besides the window setup exe file? On the laptop, however, everything is fine with just the executable
Issues with the new displaycal go to the github issues places. https://www.github.com/eoyilmaz/displaycal-py3/issues . The developer is not working on issues on the old version and the old version issues are here. It is a new developer for the new version.
The old version works fine on Windows 10. Windows 11 is a lot more tricky with its auto color managment for SDR and HDR. It should be disabled. And it monitors is icc profiles different from windows 10.
Today, I also had the White Balance problem mentioned above. I fixed it by installing the older version found on this site.
Another thing I noticed (on Windows 11) is that while calibrating, I usually had a small YouTube window or other things open on the side. But I saw that the greys were sometimes flickering. In the report, I noticed that gamma sometimes jumped to 2.6 or 2.8.
Later, when I did the calibration without touching anything and with everything closed (using the old version), the gamma stayed stable at 2.2, with no problems, as shown in the report.
I wanted to share the issues I experienced so that others can be aware too.
Hello DisplayCAL Users,
I’m writing to you today with a special request regarding my upcoming application for a UK Global Talent Visa. This visa, designed for individuals with exceptional talent in their field, would allow me to continue developing and supporting DisplayCAL from the UK, ensuring its future growth and availability for everyone.
A crucial part of this application involves demonstrating the impact and value of my work, and there’s no better way to do this than through your direct experiences and feedback.
I would be incredibly grateful if you could share your testimonials about DisplayCAL at https://github.com/eoyilmaz/displaycal-py3/issues/581
Specifically, I’m interested in hearing:
- How has DisplayCAL benefited you? (e.g., improved color accuracy, solved specific workflow problems, saved you money, enhanced your creative output, etc.)
- What are your favorite features or aspects of DisplayCAL?
- How has DisplayCAL impacted your work or projects?
- Any specific success stories or “aha!” moments you’ve had with DisplayCAL.
Your honest and detailed feedback will be invaluable in showcasing the real-world impact of DisplayCAL and strengthening my visa application. Please feel free to write as much or as little as you like, but the more specific and descriptive you can be, the better!
Thank you so much for your continued support of DisplayCAL. It means a great deal to me to see how this project helps so many of you.
Best regards,
Erkan Ozgur Yilmaz
Ho installato la versione 3.9.17 e finalmente sono riuscito a far funzionare DisplayCal correttamente con un ridimensionamento del display del 200%, essenziale per la mia configurazione. Ho eseguito l’intero processo di profilazione e generazione di LUT e la verifica ha riportato risultati eccellenti su tutti i fronti (punto di bianco, gamma, gamut, ecc.).
Tuttavia, una volta caricata la LUT in JRiver utilizzando il motore di rendering JRVR, tutte le immagini mostravano una pronunciata dominante blu. Ho testato sia i formati .cube che .3dlut con risultati identici. Ho anche provato a eseguire l’intera catena di colori sia in Full (0–255) che in Limited (16–235), ma senza successo.
La mia catena di riproduzione è composta da un proiettore abbinato a una GPU Nvidia RTX3060. Con la precedente build v3.9.16, il tracciamento della scala di grigi era perfetto, ma gamma e temperatura colore erano meno accurati, probabilmente a causa del limite di ridimensionamento del 150% in vigore all’epoca. Per questo motivo ho deciso di ricalibrare e rigenerare la LUT.
Qualcuno ha riscontrato un problema simile o può indicarmi dove potrei aver sbagliato? Grazie in anticipo.
