TI1, TI2, CSV and printtarg target files for SpyderPrint Targets

[knowing]

OK, I tried to scan the targets but unfortunately the same error happens:

View attachment 17971

I will try to read every row and save the file and see how the profile is generated.

Hi @pharmacist ,
I am still pondering on what could be wrong with the ti1 files for the images and have not yet found an answer. I was wondering if you could tell me the steps you take when you take the example ti1 file that my script read_image_patch_colors generates (modified to get 975 patches) until you start reading with chartread?

I have a lot of open questions in my mind because I do not understand your process:

• You use the ti1 file with printtarg and make a tif file.
• Then you do something to the image to make your printscreen, which has colors that seem duller on the image?
• Is that image (the printscreen image) that you print for scanning with the colorimeter?
• When that image is changed from the original colors, are you also creating a ti2 file that matches the colors in the printscreen?
• Which ti2 file are you using as input to chartread? The one generated from printtarg, or another ti2 file that is adapted to the printscreen image?
• Did you use the latest ti1 file from the example folder "A4-Expert Target Plus Grays (1 page - 975 patches)-SS" when making your i1 image? Or did you use an old one, and just copying the second table in the new ti1 file? I ask because I did several fixes on the last script that might have had some effect on the ordering of the til1 list colors. If you give me the ti1 file you use I could compare them to check.

Could you upload any files that you make at every step, so I could investigate further?

Sidenote:
In the printing industry, the term "printscreen" generally refers to screen printing (also known as silkscreen printing or serigraphy). I assumed it is something like this you are doing, but it dawned on me that you might just refer to the "print screen" button on the keyboard, but that should not create such bland colors compared to the original images I posted earlier. Which is why I assumed some other process done here.

Also, you attached this image earlier, with an error from Qimage:

I assume this is coming from the image that you create from printtarg? Is printtarg embeding an icc profile on the image generated that is corrupted?
When I search for this error message: "Qimage has encountered a corrupted or incompatible ICC profile while processing the file:"
Google AI is instructing to try to strip or convert the color profile on the image to sRGB in photoshop or GIMP etc (save with or without profile).
Have you opened this image in photoshop or other software to see if the same error is there, or if the error is removed if you remove any profile or save the image with sRGB profile?

If you have that image it would be interesting to look at it. I do not get any similar error when opening images from printtarg that was generated using the ti1 files made by my script.

I would really appreciate your input to understand what is happening here.

Thanks,
K

 

[Epatcola]

Also, you attached this image earlier, with an error from Qimage:
View attachment 18008

Qimage had what I consider to be a bug or at best a useless error message. I don't know if it got fixed in the current version. If the Job Profile | Printer Profile drop down contains an icc profile Qimage attempts to read it even when OFF is selected in the drop down.

If that profile is missing you get this error message implying there is something wrong with the profile in the file you are printing.

 

[knowing]

Qimage had what I consider to be a bug or at best a useless error message. I don't know if it got fixed in the current version. If the Job Profile | Printer Profile drop down contains an icc profile Qimage attempts to read it even when OFF is selected in the drop down.

If that profile is missing you get this error message implying there is something wrong with the profile in the file you are printing.

Thanks for letting us know