{"id":8570,"date":"2013-07-07T22:07:34","date_gmt":"2013-07-08T02:07:34","guid":{"rendered":"http:\/\/scruss.com\/blog\/?p=8570"},"modified":"2013-07-21T11:57:33","modified_gmt":"2013-07-21T15:57:33","slug":"a-mostly-colour-managed-workflow-for-linux-for-not-too-many","status":"publish","type":"post","link":"https:\/\/scruss.com\/blog\/2013\/07\/07\/a-mostly-colour-managed-workflow-for-linux-for-not-too-many\/","title":{"rendered":"A (mostly) colour-managed workflow for Linux for not too many $$$"},"content":{"rendered":"

Colour management is good. It means that what I see on the screen is what you meant it to look like, and anything I make with a colour-managed workflow you’ll see in the colours I meant it to have. (Mostly<\/em>.) You can spend a lot of money to do this professionally, but you can also get most of the benefits for about $125, if you’re prepared to do some fiddly stuff.<\/p>\n

The most important part is calibrating your display. Hughski’s ColorHug<\/a> (which I’ve mentioned before<\/a>) is as close to plug-and-play as you’ll get: plug it in, and the colour management software pops up with prompts on what to do next. Attach the ColorHug to the screen (with the newly supplied stretchy band), let it burble away for 10\u00e2\u20ac\u201c20 minutes, and the next time you log in, colours will be just right.<\/p>\n

Calibrating the scanner on my Epson WorkForce WF-7520<\/a> was much more work, and the process could use optimization. To calibrate any scanner, you need a physical colour target<\/a> to scan and compare against reference data. The cheapest place to get these (unless there was one in the box with your scanner) is Wolf Faust’s Affordable IT 8.7 (ISO 12641) Scanner Colour Calibration Targets<\/a>. If there are a bunch of likeminded folk in your area, it’s definitely worth clubbing together on a group buy to save on shipping. It’s also less work for Wolf, since he doesn’t have to send out so many little packages.<\/p>\n

(I’ve known of Wolf Faust since my Amiga days. He produced the most glorious drivers<\/a> for Canon printers, and Jeff Walker produced the camera-ready copy for JAM<\/a> using Wolf’s code. While Macs had the high end DTP sewn up back then, you could do amazing things on a budget with an Amiga.<\/em>)<\/p>\n

\"colour<\/a>The target comes packed in a protective sleeve, and along with a CD-R containing the calibration data which matches the print run of the target. Wolf makes a lot of targets for OEMs, and cost savings from his volume clients allow him to sell to individuals cheaply.<\/p>\n

Scanning the thing without introducing automatic image corrections was the hard part. I found that my scanner had two drivers (epson2<\/a> and epkowa<\/a>), the latter of which claimed to support 48-bit scanning. Unfortunately, it only supports 24-bit, like the epson2 driver, so whichever I chose was moot. I used the scanimage<\/a> command line tool to make the scan:<\/p>\n

scanimage --mode Color -x 175 -y 125 --format=tiff --resolution 300 > Epson-Workforce_WF-7520-WFaust-R1.tiff<\/pre>\n
which looks, when reduced down to web resolution, a bit like this:<\/p>\n
\"Epson-Workforce_WF-7520-WFaust-R1\"<\/a>It looks a lot darker than the physical target, so it’s clear that the scanner needs calibrating. To do this, you need two tools from the Argyll Colour Management System<\/a>. The first creates a text representation of the scanned target’s colour patches:<\/p>\n
scanin -v Epson-Workforce_WF-7520-WFaust-R1.tiff \/usr\/share\/color\/argyll\/ref\/it8.cht IT87\/r130227.txt diag.tiff<\/pre>\n
The result is a smallish text file<\/a> Epson-Workforce_WF-7520-WFaust-R1.ti3<\/span> which needs one more step to make a standard ICC profile<\/a>:<\/p>\n
colprof -A Epson -M 'Workforce WF-7520' -D 'WFaust R1' -ax -qm Epson-Workforce_WF-7520-WFaust-R1<\/pre>\n
I didn’t quite need to add that much metadata, but I could, so I did. The resultant ICC file can be used to apply colour calibrations to scanned images. Here’s the target scan, corrected:<\/p>\n
\"Epson-Workforce_WF-7520-WFaust-R1-corrected\"<\/p>\n
(I’ve made this a mouseover with the original image, so you can see the difference. Also, yes, there is<\/em> a greasy thumb-print on my scanner glass near the bottom right, thank you so much for noticing.)<\/p>\n
I used tifficc<\/span> from the\u00c2\u00a0Little CMS<\/a> package to apply the colour correction:<\/p>\n
tifficc -v -i Epson-Workforce_WF-7520-WFaust-R1.icc Epson-Workforce_WF-7520-WFaust-R1.tiff Epson-Workforce_WF-7520-WFaust-R1-corrected.tiff<\/pre>\n
There are probably many easier, quicker ways of doing this, but this was the first thing I found that worked.<\/p>\n
To show you a real example, here’s an un-retouched scan of the cover of Algrove Publishing<\/a>‘s book \u00e2\u20ac\u0153All the Knots You Need<\/a>\u00e2\u20ac\u009d, scanned at 75 dpi. Mouseover to see the corrected version:<\/p>\n
\"all-the-knots-you-need_algrove\"<\/p>\n
(Incidentally, there are two old but well-linked programs that are out there that purport to do scanner calibration:\u00c2\u00a0Scarse<\/a> and LPROF<\/a>. Don’t use them!<\/strong><\/span> They’re really hard to build on modern systems, and the Argyll tools work well.<\/em>)<\/p>\n
The last part of my workflow that remains uncalibrated is my printer. I could make a target with Argyll, print it, scan it, colour correct it, then use that as the input to colprof<\/span> as above. I’m suspecting the results would be mediocre, as my scanner’s bit depth isn’t great, and I’d have to do this process for every paper and print setting combination. I’d also have to work out what magic CUPS<\/a> does and compensate. Maybe later, but not yet.<\/p>\n","protected":false},"excerpt":{"rendered":"
Colour management is good. It means that what I see on the screen is what you meant it to look like, and anything I make with a colour-managed workflow you’ll see in the colours I meant it to have. (Mostly.) You can spend a lot of money to do this professionally, but you can also […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[7,11],"tags":[2679,2681,2680,2687,2682,270,2683,807,2685,808,305,2684],"class_list":["post-8570","post","type-post","status-publish","format-standard","hentry","category-computers-suck","category-photo","tag-argyll","tag-cms","tag-icc","tag-instagram","tag-lcms","tag-linux","tag-sane","tag-scan","tag-target","tag-tiff","tag-ubuntu","tag-wolf_faust"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pQNZZ-2ee","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts\/8570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/comments?post=8570"}],"version-history":[{"count":10,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts\/8570\/revisions"}],"predecessor-version":[{"id":8585,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts\/8570\/revisions\/8585"}],"wp:attachment":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/media?parent=8570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/categories?post=8570"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/tags?post=8570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}