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

[knowing]

Now I understand why you asked again, sorry. I see that my file name was not reflecting that it had Plus Grays. I also found some manual copy paste errors, so I upload the files again here (and on previous message), now named "A4-Expert Target Plus Grays (2 pages - 989 patches)-i1".

Sorry for the confusion. I hope it now works for your i1. I will update all the other example targets too in a new release soon.

Cheers,
K

 

[pharmacist]

Is it possible to upload the bare patch set with only 729 + 234 Extended grays patches (ti1 file with 963 patches in total) without the extra black and white patches up to 989 patches ? The reason I want to play with printtarg to obtain an optimal placement of the patches.

 

[knowing]

Is it possible to upload the bare patch set with only 729 + 234 Extended grays patches (ti1 file with 963 patches in total) without the extra black and white patches up to 989 patches ? The reason I want to play with printtarg to obtain an optimal placement of the patches.

I will upload all of the examples soon. The one I gave you is the 729 + 238 grays = 967. The last 22 lines with black and white you can remove as you wish, then you have the original patches in sequence.

Cheers,
K

 

[pharmacist]

There is something very strange with the ti1 files: it generates greenish space bars when I choose the -b argument in printtarg (not real white/black). it doesn't make sense to me and removing the last patches in your ti1 file still generates those extra black patches....I will wait.

 

[knowing]

There is something very strange with the ti1 files: it generates greenish space bars when I choose the -b argument in printtarg (not real white/black). it doesn't make sense to me and removing the last patches in your ti1 file still generates those extra black patches....I will wait.

Yes, I noticed that too. That is something related to the printtarg command. I have not found that anything is wrong with the ti1 files, but it is not impossible that some tag-name is missing, that is the cause for that. This requires some playing around with tags.

I see some other ti1 files that have made target file with black and white spacers, and the one I am looking at has these tags:
WHITE_COLOR_PATCHES "2"
BLACK_COLOR_PATCHES "4"
COMP_GREY_STEPS "32"
NEUTRAL_STEPS "48"
MULTI_DIM_BCC_STEPS "2"
OFPS_PATCHES "235"


I currently do not make them. You could try to insert them and see if it makes a difference.


Aaahh... I just noticed. The first time you sent me files, then your tiff had proper black and white, but that time I manually added these:
WHITE_COLOR_PATCHES "6"
BLACK_COLOR_PATCHES "7"

If you can add them into your ti1 file (do a search and count how many of them there are) and confirm if this fixes the issue, then I will automate creating these tags in the code.

Appreciate your help

Cheers,
K

 

[knowing]

Hi All,
I have now made a new release with lots of fixes and changes.

Download from:
https://soul-traveller.github.io/read_image_patch_colors/

Unfortunately, I am very desperate for time, so I will not maintain this code much. I also removed several printarg target examples, as it was too much to maintain. Those that are interested in making new targets have more than enough info to play around to create variations.

@pharmacist :
I have updated the code to dynamically crate tags for

WHITE_COLOR_PATCHES
BLACK_COLOR_PATCHES
NEUTRAL_STEPS

All example files are now updated and XYZ / LAB data uses ArgyllCMS xccilu for better accuracy.

Hope this fixes the issues

Cheers,
K

 

[knowing]

Hi All,
I have now made a new release with lots of fixes and changes.

Download from:
https://soul-traveller.github.io/read_image_patch_colors/

Unfortunately, I am very desperate for time, so I will not maintain this code much. I also removed several printarg target examples, as it was too much to maintain. Those that are interested in making new targets have more than enough info to play around to create variations.

@pharmacist :
I have updated the code to dynamically crate tags for

WHITE_COLOR_PATCHES
BLACK_COLOR_PATCHES
NEUTRAL_STEPS

All example files are now updated and XYZ / LAB data uses ArgyllCMS xccilu for better accuracy.

Hope this fixes the issues

Cheers,
K

I made a small update release with:
- Added support for calculating SINGLE_DIM_STEPS for ti1 files.
- Update of documentation

Cheers,
K

 

[knowing]

I made a small update release with:
- Added support for calculating SINGLE_DIM_STEPS for ti1 files.
- Update of documentation

Cheers,
K

Hi all,
I made a new small release, version 1.5.4, fixing non functional mirroring and rotation function, and improving documentation.

@pharmacist , did you manage to use the target you were making with the example files successfully?

Thanks for any feedback.

Cheers,
K

 

[pharmacist]

I am still trying to create a good divison of your new 975-target and I get this using the following command:

printtarg -v -ii1 -a0.9 -A0.85 -b -r -P -T360 -M10 -p180x297 975-chart

So I get a equally divided patch count per page and later I can use the stretch option to create a true A4 sheet (making the patches slightly thicker).

What I am concerned is the strange green empty patches on the second page (row on the right: bottom green patches). Normally I should get white patches when generating those empty patches. Not sure how this will interfere with the chartread command (will it be registered as empty patch or as real colour ?). Maybe I should PS to color those patches into true white. Another strange thing: the -b (black and white) argument should only give black and white space bars between patches and I see now greenish and black space bars....There is something very strange happening.

So it will become like this:

 

[knowing]

I am still trying to create a good divison of your new 975-target and I get this using the following command:

printtarg -v -ii1 -a0.9 -A0.85 -b -r -P -T360 -M10 -p180x297 975-chart

So I get a equally divided patch count per page and later I can use the stretch option to create a true A4 sheet (making the patches slightly thicker).

What I am concerned is the strange green empty patches on the second page (row on the right: bottom green patches). Normally I should get white patches when generating those empty patches. Not sure how this will interfere with the chartread command (will it be registered as empty patch or as real colour ?). Maybe I should PS to color those patches into true white. Another strange thing: the -b (black and white) argument should only give black and white space bars between patches and I see now greenish and black space bars....There is something very strange happening.

Thanks for showing how you create your target
This is obviously something with printtarg, which I also have seen. I would add patches for the last row to fill those green patches that are empty, but then the patch count will no longer be 975, if that was your aim to keep the same count. th original two charts have 967, so the the last 8 black and white I added to get perfect fit on two pages for the -iSS (SpectroScan) target type in my examples. Strange that it is so hard to get that perfect fit with the same number of patches for i1.

Did you try the latest chart example created with the script? I wondered if there would be any change using those ti1 files, with regards to the green spaces, as they now have these tags generated automatically:
WHITE_COLOR_PATCHES "13"
BLACK_COLOR_PATCHES "14"
COMP_GREY_STEPS "38"
SINGLE_DIM_STEPS "9"

I attach the two examples here, one for SS (1 page 975 patches) and one for i1 (2 pages 989 patches). I added those extra patches to fill the end row.

I tried your command with the latest attached generated ti1 file, but I had to modify to 988 patches to get a perfect fit on the page.

printtarg -v -ii1 -b -r -P -a0.9 -A0.85 -T360 -M10 -p180x297 "A4-Expert Target Plus Grays (2 pages - 988 patches)-i1"

This was the result:

As you can see, there is still the green spacers.

I don't think I can make those go away, unless someone finds out why printtarg make those. Not sure the ti1 files I have generated are the cause.

Cheers,
K