Possibility to convert csv-file with only L*A*B* values into a ArgyllCMS ti3 file

[x64]

I have the CR30-ti3-Dispensary ready for you on GitHub, make sure to read the readme carefully but using it is pretty straightforward. The default colorprof configuration is set to the preference you shared yesterday. Let me know your results/feedback and star my project on GitHub if you are satisfied.

 

[pharmacist]

many thanks for all the work @x64 : I wil give it a try with another type of paper of which I already have profile made for a side by side comparison to see if the CR30 colorimeter is a feasible alternative for a poor man's printer profiling solution costing only about € 70.-. For this I have do some test to compare thos profile side by side in prints.

 

[x64]

The main concern I have is that the presets primarily assume an A-type (tungsten) illuminant for most devices (per ti3 spec: "All instruments except the Spectrocam are assumed to have an 'A' type illuminant"). None of the stock entries explicitly use an LED illuminant, making me think it is unsupported.

But given how close the icc created with the CSV measurements is to the i1Pro1 icc, and we feed the spectral data to omit the SPD model, I think it is feasable.

 

[pharmacist]

The i1Pro3 and the SpyderPrint4 use LED illuminant AFAIK.

 

[x64]

The i1Pro3 and the SpyderPrint4 use LED illuminant AFAIK.

You are right! I used the ti3 documentation as a reference but it doesn't list those and is outdated.

 

[x64]

I re-initiated the github repo because there was a fatal flaw in the configuration (wrong file names). Now you can verify the functionality immediately after downloading by simply running build_profile.py and generating the example ti3 and icc. Nothing else changed, so you can keep using the scripts you downloaded earlier. Just thought I'd mention it because I versioned back to 0.1.0, for future updates you can follow the versioning.

 

[pharmacist]

Hi @x64 : I am a noob using python because for me it is a bit cryptic how to type in the commands to start the py file.

I tried this, but it does not seem to work:

Enlightment much appreciated.....

Meanwhile I will print the target (both the CR30 and the i1Pro version) again on a totally different kind of paper (the previous was Calumet matte photo paper) which is a cheap glossy cast paper and this time on the ET-8550 to see if the magic is still there. First I will generate the profile using my i1Pro1 and save this as a comparison profile for a later side by side comparison with the CR30 read target.

As you can see the same layout order in both the small patch (with space bars) for the i1Pro and the large patch CR30 colorimeter target.

 

[pharmacist]

OK found how to type in with python, but unfortunately the computer says NOOOO:

 

[pharmacist]

So here is the new data set: including a profile made with the i1pro1 for the Action Glossy paper (Epson ET-8550) and the csv file containing the data scanned with the CR30 with the same paper/printer combination:

Maybe @x64 you can have a look at and see what the problem exactly is.

 

[x64]

I forgot there are some caveats with python on windows, but I think you should be able to run the scripts.

The build_profile.py script is meant to be the main entry point. This script uses the profile_config.ini arguments to run the cr30_to_ti3.py directly, so you do not have to provide arguments for running the conversion.

You could run it standalone, and works fine, but you have to provide it specific arguments for your input/output files, otherwise it tries to find and use example files (that do not exist anymore, testprofile v2.csv is a old filename, my bad).

There might be additional issues with the ArgyllCMS installation, but that should not influence the CSV conversion.

To rule things out, first download the latest release from github. Remove previously downloaded versions. After extracting it, navigate the terminal to the src directory (you did that correctly looking at the screenshots).

Then simply run: "python3 build_profile.py".

With the latest release, all example files are in the correct location (this is defined in the config), and should run and deliver at least the output_example.ti3 to the output directory.