- This topic has 37 replies, 10 voices, and was last updated 5 months ago by
.
-
Posts
-
Using clean install off Windows 10 worked, but maybe 2x slower, than with 2.3.1, and with 3000+ test chart displaycal showed another error at the end. So in my opinion, 3.0.1 to slow with displaycal.
Using clean install off Windows 10 worked, but maybe 2x slower, than with 2.3.1, and with 3000+ test chart displaycal showed another error at the end. So in my opinion, 3.0.1 to slow with displaycal.
What colorimeter do you have? And is argyll 2.3.1 really faster than 3.0.1?
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.i1 Display PRO, with 2.3.1 3400+ test chart about 1,5 h, 3.0.1 3400+ test charts 3h+.
Oh my…I guess I’ll downgrade to 2.3.1 when it is time to re-calbrite the monitor.
Thank you for your feedback.
From Argyll v3.0.0 changelog:
Changed i1d3 driver to cope with Rev. B “0x83” error robustly. This should fix any issues measuring low level Red only patch values on OLED displays, but with slower measurements when this occurs.
Hi, Everyone— very new here and very new to DisplayCal. I’m receiving the same error since updating to ArgyllCMS v3.0.1:
Error – new_disprd failed with ‘Instrument Access Failed’
I’ve tried various different settings, including the default Gamma 2.2, but it seems I receive the error across all configurations.
I’ve been looking for a way to revert to a previous version of ArgyllCMS, as I hadn’t encountered the issue prior to updating. I read in an older thread that one could copy the download link and change the version number to access prior releases, but that doesn’t appear to work, as the current link doesn’t contain a version number: https://www.argyllcms.com/downloadmac.html
Any help you might offer would be greatly appreciated!
System specs:
iMac 5K Retina
Mac OS Ventura 13.6 (22G120)
Radeon Pro 580 8GB
64 GB 2400 MHz DDR4
BMD Ultrastudio 4K Mini
Dell Ultrasharp U3223QE (as reference monitor through HDMI)
Resolve 18.6.2 (Build 2)Many thanks,
-Tony
edit: pasted the correct ArgyllCMS download link
System specs:
iMac 5K Retina
Mac OS Ventura 13.6 (22G120)
Radeon Pro 580 8GB
64 GB 2400 MHz DDR4
BMD Ultrastudio 4K Mini
Dell Ultrasharp U3223QE (as reference monitor through HDMI)
Resolve 18.6.2 (Build 2)Until ArgyllCMS errors are fixed or you find a link to previous ArgyllCMS versions for mac, use Xrite/Calibrite tool (better use i1Profiler since those new dells are very likely to be PFS phosphor LED backlight and latest calibrite app lacks of them even if they label a correction with that name it is not):
Plug Dell to imac output
Calibrate & create a “TABLE” (XYZLUT equivalent) profile, ICC v2 in i1Profiler (better use that if compatible with newer colorimeters).
Create a “.cube” LUT3D using DisplyCAL LUT3D creator or commandline collink, and DO NOT USE abs colorimetric since i1Profiler used to create profiles with PCS white (D50) + CHAD and in previous versions LUT3D creator or colling seem to ignore CHAD. Use colrimetric relative = preserve Dell display white point. Remember to apply VCGT in LUT3D creator. Source Rec709 gamma 2.4 black output 100%, destination your TABLE ICC profile, relatve colormetric, apply VCGT.
plug back Dell to your 4k mini
Go to resolve, place LUT3D on the folder as in DisplayCAL resolve for mac, configure LUT3D and test itThis assumes that imacs ouput to dell won’t do anything very bad so behavior though your 4k mini will be almost equal. This is a guess, so test how it behaves.
Vincent,
A huge thanks for your reply. The detail is very much appreciated. I’ll follow your roadmap and let you know how it goes.
From a Time Machine backup, I retrieved the last LUT3D I had created for Resolve. My concern was that the luminance was too high, at 176.9 cd/m2.
I had assumed DisplayCal would set the target luminance to 100 cd/m2, but as I mentioned, I’m a rookie and that was a rookie mistake.
Other than that, from what I can tell from the report, things looked mostly good. I’ll attach the report below.
Again, many thanks for the detailed response, and for taking the time to help out.
Vincent,
A huge thanks for your reply. The detail is very much appreciated. I’ll follow your roadmap and let you know how it goes.
From a Time Machine backup, I retrieved the last LUT3D I had created for Resolve. My concern was that the luminance was too high, at 176.9 cd/m2.
On a well behaved display lowering brightness does not change WP so since you are using a SDR LUT3D (which is relative to luminance) lowering brightess till you hit target value (100nit?) would solve your issue
On not so well behaved display lowering brightness after calibration may result in some xy drift for whietpoint. Measure it.
I had assumed DisplayCal would set the target luminance to 100 cd/m2, but as I mentioned, I’m a rookie and that was a rookie mistake.
DisplayCAL has no DDC/CI control, user must change RGB gains for white xy and brightness settings for luminance
Other than that, from what I can tell from the report, things looked mostly good. I’ll attach the report below.
Again, many thanks for the detailed response, and for taking the time to help out.
Seems fine, but if you lower OSD bightness WP may drift a little. Do it & test. If it bothers you ypu’ll need to redo.
On a well behaved display lowering brightness does not change WP so since you are using a SDR LUT3D (which is relative to luminance) lowering brightess till you hit target value (100nit?) would solve your issue
On not so well behaved display lowering brightness after calibration may result in some xy drift for whietpoint. Measure it.
DisplayCAL has no DDC/CI control, user must change RGB gains for white xy and brightness settings for luminance
Seems fine, but if you lower OSD bightness WP may drift a little. Do it & test. If it bothers you you’ll need to redo.
Vincent,
Again, can’t say how much I appreciate your help.
I was able to locate v2.3.1 in a system backup. Reinstalled, and was able to calibrate my primary and reference Displays with no issues.
It looks like Graeme has released v3.0.2. Now that I once again have access to a version that’s stable for my system, I may do some tests with the new release.
Still learning how to read the reports. Things look good, but there does appear to be some variance in the RGB Gray Balance, as well as some slight shifts with green in the Gamut a*b* report.
I didn’t use Iterative Gray Balance by setting the Tone Curve to Rec.1886 in the Calibration tab for this attempt, as the instructions in the wiki said it normally isn’t needed. Perhaps it is in my case?
Attaching the report below if you’re interested in taking a look.
Hope you’re well!
Argyll v3.0.2 at the and off calibration, clena windows 10 install, no problems with 2.3.1.
Oh dear… I thought 3.0.2 will be ok, I guess I was wrong.
Argyll v3.0.2 at the and off calibration, clena windows 10 install, no problems with 2.3.1.
report to argyllcms mailllist
