[Tool] ChromIQ – a macOS and Windows GUI for ArgyllCMS printer profiling (v4.3.0)

[jctay]

Thank you for your prompt response.

RGB Value Representation

.ti3 uses a different base from the norm. When viewing RGB values by hovering over the measured patch, I think the standard representation using a base of 256 (2⁸) is still preferable.

Thank you

 

[know]

Thank you for your prompt response.

RGB Value Representation

.ti3 uses a different base from the norm. When viewing RGB values by hovering over the measured patch, I think the standard representation using a base of 256 (2⁸) is still preferable.

Thank you

Thanks for giving feedback and suggestions

I think the info on hovering over a measurement already gives the 0 to 256 range for RGB values... See image below:

 

[itsab1989]

I have been awake for too long and will catch some sleep now. Claude keeps working on the requests from @ajaytanna and @jctay and when it finishes will release a new beta. I (or Knut if he is available before me) will post here when it is ready but you can also check yourself on GitHub or by using the update check in the current beta. See you later!

 

[jctay]

Thanks for giving feedback and suggestions

I think the info on hovering over a measurement already gives the 0 to 256 range for RGB values... See image below:

I revisited the issue, measured the Lab value, and confirmed the hovered data using the patch tool.

Everything is confirmed to be in good order.

Thank you

 

[itsab1989]

Good to hear. The new beta is ready. Maybe have a look:
https://github.com/itsab1989/ChromIQ/releases/tag/v4.3.3-beta.7

 

[jctay]

ChromIQ v.4.3.3-beta.7

The issue I previously reported regarding the strip and patch patterns has been resolved.
The program is now much more responsive than before.

 

[jctay]

Compatible Profiling Target

The patch layouts used by i1Profiler and ChromIQ differ. Attempts were made to rotate and mirror the target to achieve a layout that can be recognized by both applications, but this was unsuccessful.

The objective is to develop a common profiling target that is compatible with both i1Profiler and ChromIQ, allowing the same physical target to be used for profiling in both applications.

Any recommendations for achieving this?

 

[know]

ChromIQ Workflow Improvement Suggestion

Measurement Phase

Regular Recalibration: When using older-generation devices such as the i1Pro1, regular recalibration is required when measuring targets with large patch sizes.

Measurement Interruption: The current measurement process requires the measurement to be stopped, after which users can either save the partial data or abort the measurement.

Suggestion: Add a dedicated Recalibration button to allow users to easily trigger recalibration during the measurement process.

Thank you

Hi @jctay ,

The latest beta 7 should do what you want, but uses keyboard command, not a separate button:

"Calibrate during a measurement with K: Press K (k, K, or the K key on a Cyrillic layout) and the instrument takes a new calibration before the next strip or patch, without ending the measurement; afterwards the same strip or patch is offered again.

An optional Calibrate button can be switched on in Preferences ▸ Measurement (off by default); while a measurement runs it stands where the disabled Save as Defaults stands. K is on the keyboard help card, the printed card and every "Calibration complete" window. With ArgyllCMS chartread K does nothing"

Cheers,
Knut

 

[know]

Compatible Profiling Target

The patch layouts used by i1Profiler and ChromIQ differ. Attempts were made to rotate and mirror the target to achieve a layout that can be recognized by both applications, but this was unsuccessful.

The objective is to develop a common profiling target that is compatible with both i1Profiler and ChromIQ, allowing the same physical target to be used for profiling in both applications.

Any recommendations for achieving this?

We are looking into it... we have had this thought before, but it may have a lot of consequences and has not been the main focus till now... maybe this will come, but we are first looking into a consequence and feasibility study...

Cheers,
Knut

 

[ajaytanna]

@itsab1989 Thank you very much. Do catch up on your sleep and spend time with your family too. You more than deserve it.
The earlier errors with CMYK and .cal files have been resolved in 4.3.3 Beta.7, Also it is great to have the preventive message come up in a Calibration run if one tries to select any chart.
A new problem, perhaps because of this is now the chart will not be random even if random is selected. That setting is ignored completely (Calibration run only).
I am still a bit confused about the .cal part. Since my RIP cannot handle a linearization separately I have to do it in the profile. Is just creating a chart with the -K option (apply and embed) enough to be read and a profile created from it proper? or do i also have to apply the cal file in the "Calibration & Profiling" tab at the time of creating the profile?