Linux Tools for Professional Photography
An accurate monitor is vital for working with color photos. Professionals use a device called a colorimeter to measure the actual computer display and create an ICC profile that then is used by the OS to reproduce colors faithfully. Unfortunately, I am aware of no Linux drivers that support any of these devices. Even if you could get a monitor profile, The GIMP does not support using one for monitor display. Certainly, this is one feature in The GIMP I sorely miss. In fact, The GIMP bug #78265 documents the problem; hopefully, we will have this feature soon. In the meantime, we will do the best we can by carefully adjusting the monitor manually, using the controls built in to most quality monitors:
Set the monitor white point to 6,500K. This provides more yellow than the 9,300K that most monitors ship with, but it is much easier for your eyes to see correct color, which is why it's the industry standard recommendation.
Increase the monitor contrast to 100% and adjust the brightness until you can see most of the B Black Level strip in Norman Koren's excellent calibration chart, shown in Figure 3.
Adjust the display gamma using the gamma strip of Figure 3. To read the chart, squint your eyes until you can't discern the horizontal lines and find the location where the gray tone is the same across the strip; this is your current gamma. Adjust the display gamma using xgamma until the gamma is 2.2, the industry default.
Now adjust the separate R, G and B controls to make the gray of the target as neutral as possible. Use an image such as the color calibration chart, shown in Figure 3, to help adjust the monitor color balance. By focusing on the skin tones as well as neutral gray tones, you should be able to eliminate any gross color imbalances.
In addition to a well-adjusted monitor, a consistent lighting environment is critical for accurate color viewing. Dim light is best, and by lighting your room with 5,000K daylight-balanced compact fluorescents, the white of a piece of paper should look very close to the white on your display. ISO 12646 goes into great depth on providing further guidelines on ambient viewing conditions. Bright colors in your environment alter your color perception, so watch out for brightly colored nearby walls, as well as bright backgrounds and colored windows in your Linux environment. My Linux desktop uses a plain gray background and black and white window decorations.
Now that we have a reasonably correct monitor and viewing environment, we can turn our focus to scanning. Both SANE and VueScan are excellent Linux solutions for scanning, I have chosen to use VueScan primarily because it's the same software I use on the Mac. Whichever scanning software you choose, it's important always to use the same software settings. This is vital for correct color, as the ICC profile we are about to create is valid only for the color settings used when making it. In order to make a scanner profile, it's necessary to have a known quantity to scan, called a color calibration target. The target I use is the Q-60 Color Input Target made by Kodak, and it is available from many high-end photo stores. Scan the target using your preferred scanning software; remember to save your settings, and always use the same settings moving forward.
Creating an ICC from this scan is made possible by the LProf profiling tools, available from the Little CMS Web site (see on-line Resources). Run kmeasurementool and open the scan. Go to the Options tab and select the correct pick template for the target used, in this case the Kodak column picker. Go back to the image tab and resize the green target outline. Once the little squares are lined up with the color patches in the scan, select Pick and then Save IT8 sheet. Now use kscannerprofiler to create a custom ICC profile for your scanner by first selecting the correct target vendor and batch ID. Each target comes with a date identifying the batch. Open the IT8 sheet file created above and enter an output profile filename for your ICC profile, then press GO. This ICC profile now can be used to interpret the color space of the scanner.
Now that we have profiled our scanner, we can scan an actual transparency. When scanning, it's helpful to know the true optical resolution of the scanner. Scanning at the maximum optical resolution captures as much detail as possible without making your file too large. When saving the file, use the TIFF format for best results as it is a lossless format.
After scanning the transparency, the resulting TIFF file's color space is that of the scanner. I want to convert this color space to a working color space to do my image editing. A popular working color space is the Adobe 1998, a profile of which can be obtained from the Adobe Web site. Apply the scanner profile using tifficc, which is part of the Little CMS package, by running tifficc -i scanner.icc -o Adobe1998.icc scan.tiff scan_working.tiff, which converts the scanned TIFF image to our working color space.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide