Recent content by Epatcola

You can find hundreds of web references telling you: Or something similar. It isn't specific to inkjet printers. The color mixing bleed seems to usually be called 'ink bleed'. As for the OP I assume you are trying to drum up a bit more activity on the forum. An admirable idea which doesn't...

I had a quick look and saw 60 bytes sent for each button press. I expect those 60 bytes mostly contain 31 spectral measurements. I would look at spectral measurement values in ColorQC 2 at try to find that data in those 60 bytes. That said I don't think ColorQC is too painful to use. Trying to...

That would be much more complicated. I envisage a jig like this The CR30 is a loose fit in the jig main part. The collar around the CR30 is fixed. The jig lifts the CR30 by the collar, moves it to the next patch, lowers it to the target then drops some more to briefly press the CR30 button...

I see ConradH asking about CR30 communications on DPReview. I don't participate there. FYI the CR30 USB interface is just a serial port implemented with a CH340 USB -> serial chip. While connected you will see the CR30 in windows device manager under serial ports as "USB-SERIAL CH340". There...

A small, but, useful update to the target generators, ti3 generation script, and instructions.

And a few batch files named paper_sizexpatch_countxpatch_size to generate various targets on one or two sheets.

Yesterday I created an A5 target with 384 randomized 8mm patches. I printed it on half an A4 sheet of Epson Premium Glossy paper on an ET-7750. I measured the target this morning which took nearly 20 minutes. I am sure with practice and a bit more care that could be reduced. Aligning the rule...

I am using 8mm patches and the rule I designed so you only need to see a couple of patch 'joints' to align the rule. I have never had any ti3 files from chartread to look at. It appears the colprof needs the input RGB values (from the ti2 file) followed by measured values on each data line. I...

Today for the first time I printed and measured a target. The target was randomized and I couldn't generate a profile. I think the build_profile script is not doing the right thing. The patches are randomized on the sheet and the ti2 file has a SAMPLE_LOC to tell you where they are on the...

Something is messed up. I don't know what your .colors file is. I generated an A5 10mm patch target from your 228 ti1 file with this printtarg.exe -r -v -i 22 -p 148.492x210 -a1.25 -T360 -m3 "my 228-target" and got this Which doesn't look like your photos. The 4th patch (A4) in the ti1/ti2...

I have not tried generating a profile yet. I have an i1studio so I don't really need to. I bought the CR30 because it is cheap and interesting and could be convenient for spot reading. I was/am waiting for the scripts you guys are producing to be finished and stable then I will probably have a...

The target is straight out of printtarg. No need to edit. All you need is something that can print without color management and to scale obeying the 360DPI file resolution. I use Qimage. I played around some more with printtarg and -i22 is the best instrument setting for square patches. If you...

This targen -v -d2 -g 16 -f 486 test printtarg -r -v -i 22 -p A4 -a 1.2506 -T914.4 test produces 486 x 10mm square patches on an A4 sheet: The instrument type parameter seems to control the shape of the patches and peripheral annotations. The -a parameter scales the patch size. I didn't look...

Here is a collar and 300mm rule for 10mm square patches. Rule and collar on your 247 patch target scaled by forced printing at 518 dpi. Align the rule to the edge of the patches with notches central. Press the button and slide to the next notch. I can't see how that isn't faster and less...

I noticed the calibration cap has a serial number matching that which the device reports to the application. Our white calibration values differing shows the device has has a factory calibration for itself and associated calibration cap.