Search results

I would recommend just trying it, remember the last block where you had both random order AND empty values, we assumed it was the random order but might as well just be the latter. You can experiment yourself by just editing the header of a ti3 file and generate a low quality profile real quick...

OK, that view will make solving the hardware problem with your P900, confirmed by the firmware nozzle check print very difficult for you.

It is pointless and wasteful to continue diagnosing with software printing long as your FIRMWARE printing has obvious problems. The prints you get from QTR are meaningless for diagnostic. It is like you are trying to diagnose an car engine problem by looking at how the wheels are spinning, while...

Looking at your nozzle check you definitely have a hardware problem. Yellow has some issues, no vivid magenta coming through, and instead some cyan leaks through the vivid magenta channel. The nozzle check is pretty 'raw', done by the firmware. So before investigating software, the nozzle check...

Nice, that looks pretty good, If you fork from the main repo and push a PR I'll take a look and release it. If you are interested in further development (e.g. wrapping more argyll systems, data visualization, further input support/conversions) I can make you a collaborator.

I'm not sure if the random order is causing it, because with our interpretation it is not 'random' (e.g. index 1 on ti2 = index 1 on csv = index 1 on ti3). I'd try without the empty data first, then try the non random order. If the order is causing it, I'm sure we can find a workaround so you...

Comparing that ti2 and csv to the files we used to design the converter I notice some obvious problems/differences: -You used random order -Your 247 csv has a lot of empty data, see the fields populated with 0 across the file...

Something with the gamut mapping the source ICC, when running colorprof with no mapping (no -S/-s) I can create an ICC with that dataset (although it does not look correct). I'm not sure what that target looks like, is there enough dark patches for contrast? the issue is mostly low contrast in...

Hi Mohamed, I found a procedure for you to try on the HP support forums that solves a similar problem on different HP printers. However the setup cartridges have a unique function, HP claims that they are designed to do a first calibration. Using different cartridges for this task might give...

I just finalized 0.2.1 with a lot of improvements and simplification. The workflow and output remains the same but will not decide anymore what data to pass to the ti3: it simply takes all data you provided in the CSV. We now also take some header items from the ti2 and include them in the ti3...

Here is the profile generated with the ti2 and CSV of the 228-target set you shared before. This is not the action glossy set because that one didn't include a ti2.

That's the thing, "testprofile v2.csv" is hardcoded in "cr30_to_ti3.py" and is only used when running cr30_to_ti3.py directly without adding --csv, --ti1, and --out arguments (what you did), but when running build_profile.py the config gets used instead. I patched that in version 0.1.1 to avoid...

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...

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...

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

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...

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...

First results looking good! I'm noticing some difference between the 1iPro1 and CR30 results. Not sure if this is an undesirable offset caused by our process, or just instrument measurement difference. I'm going to clean up the script and prepare it for upload today. Any simple convenience...

Yes that works too, if you can get all sets across ti1 ti2 and csv uniform (set 1 = 1 = 1, etc) that would make things a lot easier.

Yep that works now, before you rescan, the last remaining step is that the csv needs unique per-patch names that we can match to SAMPLE_LOC of the .ti2 (e.g. A1, B2 etc.). Right now I'm just matching the closest values but that is not accurate or reliable. I noticed from the screenshots that...