<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Get Colormanaged &#187; introduction</title>
	<atom:link href="http://www.getcolormanaged.com/category/general/introduction/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.getcolormanaged.com</link>
	<description>Blog about Colormanagement and Image Editing</description>
	<lastBuildDate>Fri, 11 Nov 2011 16:09:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Pixels per inch for web</title>
		<link>http://www.getcolormanaged.com/general/introduction/ppi/</link>
		<comments>http://www.getcolormanaged.com/general/introduction/ppi/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 17:10:36 +0000</pubDate>
		<dc:creator>René</dc:creator>
				<category><![CDATA[Photoshop]]></category>
		<category><![CDATA[introduction]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[dpi]]></category>
		<category><![CDATA[PhotoshopCS4]]></category>
		<category><![CDATA[ppi]]></category>
		<category><![CDATA[Save for web]]></category>

		<guid isPermaLink="false">http://www.getcolormanaged.com/?p=447</guid>
		<description><![CDATA[What is the significance? Simply put? Nothing. Well, if that were all I had to say on the subject, this would have to be my shortest blogpost ever&#8230; Okay, a bit more info then: A lot of first time DSLR users are concerned that their shiny new camera delivers files that are &#8220;only&#8221; 72dpi, while [...]]]></description>
			<content:encoded><![CDATA[<h3>What is the significance?</h3>
<p>Simply put? Nothing.<br />
Well, if that were all I had to say on the subject, this would have to be my shortest blogpost ever&#8230; Okay, a bit more info then:<br />
A lot of first time DSLR users are concerned that their shiny new camera delivers files that are &#8220;only&#8221; 72dpi, while their old point and shoot delivered 300dpi files. Why is this concern unwarranted? Surely 300 is more then 72, and more is better, right?</p>
<h3>Wrong</h3>
<p>The old <del>wisdom</del> saying is that &#8220;300dpi is for printing and 72dpi is for screen&#8221;.<br />
There are a few things wrong with that.<br />
First and foremost, the term &#8220;dpi&#8221; stands for <strong>dots</strong> <strong>p</strong>er <strong>i</strong>nch. In a digital file there are no dots, only <em>pixels</em>. So the correct term is <strong>pixels</strong> <strong>p</strong>er <strong>i</strong>nch (ppi).<br />
Also, 72ppi originated as it was the resolution of an <em>ancient</em> Mac monitor. Current monitors have a much higher pixel density: My old 12&#8243; PowerbookG4 for instance has a screen resolution of about 100ppi. Most current screens are somewhere between 80 and 120ppi.<br />
<span id="more-447"></span></p>
<h3>Do the math&#8230;</h3>
<p>for <em>your</em> screen: Simply measure width and height and divide the number of pixels by the measured values&#8230; <strong><em>Tip</em></strong>: Once you found the figure for your screen, be sure to enter it in the PSCS4 preferences under &#8220;Units and Rulers, Screen resolution&#8221;: That way, the &#8220;Zoom, Print size&#8221; will show an accurate sized preview.<br />
So, is a 300ppi file better then a 72ppi file?</p>
<h3>No difference</h3>
<p>If you hadn&#8217;t gathered as much from the above, for display on screen, only the <strong>display you&#8217;re using</strong> will determine the &#8220;resolution&#8221;.<br />
So, a file that contains for instance 500&#215;750 pixels will be displayed at a different size (in inches, centimeters, or whatever you prefer), depending on the screen you&#8217;re using to view it. The arbitrary ppi figure set in the file has <em>no</em> relevance <em>whatsoever</em>.</p>
<p>To illustrate that, here is an example: Each file is 500&#215;750 pixels. One is 72ppi, the other 300ppi. </p>
<p><img title="500x750 pixels, 300ppi" src="http://www.getcolormanaged.com/images/Blog/ppi/rhd_20091212_EHBO_0065_300.jpg" alt="500x750 pixels, 300ppi" /><br />
<img title="500x750 pixels, 72ppi" src="http://www.getcolormanaged.com/images/Blog/ppi/rhd_20091212_EHBO_0065_72.jpg" alt="500x750 pixels, 72ppi" /> </p>
<p>Notice the difference? No? That&#8217;s because <em>there <strong>isn&#8217;t</strong> any</em>.</p>
<h3>Why use it then?</h3>
<p>Because you <em>have to</em> put something in the box: There is <em>no way</em> that Photoshop will allow you to <em>not</em> fill in a value. However, what you put in there is pretty arbitrary. Use whatever you like basically for display on screen.<br />
I prefer to use 300ppi for general use, since then the &#8220;image size&#8221; dialog box will quickly tell me about how large I can <em>print</em> an image at decent quality. For web, I mostly use 72ppi (unless I forget) since, well, that&#8217;s what some people expect&#8230;</p>
<p>Some more reading: <a href="http://www.scantips.com/no72dpi.html" onclick="urchinTracker('/outgoing/www.scantips.com/no72dpi.html?referer=');">here</a></p>
   ]]></content:encoded>
			<wfw:commentRss>http://www.getcolormanaged.com/general/introduction/ppi/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Photoshop CS4 Color Settings</title>
		<link>http://www.getcolormanaged.com/color-management/pscolorsettings/</link>
		<comments>http://www.getcolormanaged.com/color-management/pscolorsettings/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 22:15:21 +0000</pubDate>
		<dc:creator>René</dc:creator>
				<category><![CDATA[Color Management]]></category>
		<category><![CDATA[Photoshop]]></category>
		<category><![CDATA[introduction]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[PhotoshopCS4]]></category>
		<category><![CDATA[WYSIWYG]]></category>

		<guid isPermaLink="false">http://www.getcolormanaged.com/?p=407</guid>
		<description><![CDATA[Once, and for all Never thought I&#8217;d blog about something as individual as PS Color Settings&#8230; Then again, there is so much conflicting, incomplete or downright inaccurate info on the web, I thought it might be time to set the record straight. Individual First of: Like more things in photography life there is no &#8220;Magic [...]]]></description>
			<content:encoded><![CDATA[<h3>Once, and for all</h3>
<p>Never thought I&#8217;d blog about something as individual as PS Color Settings&#8230; Then again, there is so much conflicting, incomplete or downright inaccurate info on the web, I thought it might be time to set the record straight.</p>
<h3>Individual</h3>
<p>First of: Like more things in <span style="text-decoration: line-through;">photography</span> life<em> there is no</em> &#8220;Magic Bullet&#8221;. If that&#8217;s what you are looking for, better get used to this idea: You need a basic understanding of Color Management.<br />
On the bright side: The settings in the Color Settings dialog box affect a number of things. However, unless done <em>totally</em> wrong, how your images are displayed is <em>not</em> one of those things.</p>
<h3>Settings nobody should use</h3>
<p>There is no &#8220;Magic Bullet&#8221;, but there is a &#8220;one size fits no-one&#8221;: The setting called &#8220;Monitor Color&#8221;.<br />
<span id="more-407"></span><br />
<a title="'Monitor Color'. Don't ever use it." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/Monitorcolor.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/Monitorcolor.jpg" alt="'Monitor Color'. Don't ever use it." /></a></p>
<p>What does it do? Let&#8217;s go through the main problems step by step:</p>
<p>It sets your <em>monitor profile</em> as default working space. So every time you <a href="http://www.getcolormanaged.com/color-management/cmintro/">calibrate your monitor</a> (you do that regularly, right?) your default working space changes. <em>And</em> your default working space is limited to your monitors gamut. Not good if you are on a laptop for instance.<br />
One additional problem is that <em>equal values for R, G and B might <strong>not</strong> give a neutral gray</em>. And there are other problems.</p>
<p>One of those problems is, that it sets all color management policies to &#8220;off&#8221;. Note that, contrary to popular belief, <em>setting &#8220;monitor profile&#8221; does <strong>not</strong></em> turn off color management altogether: The one good thing in all this mess is that you are presented with this dialogue box when opening an image <em>with an embedded profile</em>:</p>
<p><a title="Profile Mismatch. So there is some colormanagement going on." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/Mismatch.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/Mismatch.jpg" alt="Profile Mismatch. So there is some colormanagement going on." /></a></p>
<h3>Damage</h3>
<p>The damage you can do here is very real:<br />
If you tick the top option (&#8220;Use the embedded profile&#8221;), no damage is done. The image will be shown correct, and all data is retained. Not bad at all.<br />
If you pick option #2 (&#8220;Convert to working space&#8221;), <em>irreversible damage</em> is done: The pixels in the image will be converted (changed!) to your monitor profile. Color <em>numbers</em> are converted (so colors will display correctly), <em>but all colors out of your monitors gamut will be <strong>clipped</strong></em>. Poof! Gone. Forever.<br />
If you pick option #3 (&#8220;Discard the embedded profile&#8221;), at least you won&#8217;t be damaging the file on import as in option #2 (it&#8217;s reversible by assigning the correct profile). <em>But you will not be seeing the image correctly</em>. So any &#8220;color correction&#8221; you do will be <em>incorrect</em>. The fact that the color numbers aren&#8217;t changed is a moot point because of this: What you see definitely will <em>not</em> be what others see.</p>
<h3>Other problems</h3>
<p>Yet another problem is that, even if you use embedded profiles, you will get no warning when you copy-paste an image into a new document (which by default will not have an embedded profile), or into an image with a different working space: The colors will change. See option #3 above.</p>
<p>So, I see no reason for <em>anyone</em> to use it. Not even web designers. Yes, I know that lots of browsers are not color managed. However, there are not lots of people using your screen, are there?<br />
The only reason to <em>temporarily</em> set it, is when you need to check whether Photoshop is using the correct monitor profile.</p>
<h3>Better</h3>
<p>Just about any of the other &#8220;presets&#8221; is better. These presets are grouped in a few categories. When you scroll trough them, you might notice a few things:</p>
<p>There are settings for Europe and North America. And in every region there are 3 settings: for &#8220;General Purpose&#8221;, &#8220;Prepress&#8221; and &#8220;Web/Internet&#8221;. When you tick &#8220;more options&#8221; Japan appears, which has the same trio but adds &#8220;Color For Newspaper&#8221; and &#8220;Japan Magazine Advertisement Color&#8221;. There also appear a few other &#8220;international&#8221; presets.</p>
<p>Rather then going into each one in depth, I&#8217;ll generally explain some differences and possible pitfalls: They are &#8220;presets&#8221;, but IMO none is perfect. You can use them as a <em>starting point</em> however.<br />
I start of with &#8220;more options&#8221; unchecked. And the screenshots are for the European presets. However, the comments I give are the same for the other localisations.</p>
<h3>General Purpose</h3>
<p><a title="'General Purpose'. It isn't all that general." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/GeneralPurpose.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/GeneralPurpose.jpg" alt="'General Purpose'. It isn't all that general." /></a></p>
<p>It <em>Isn&#8217;t</em>. It&#8217;s really that simple. Like I said: There&#8217;s no magic bullet.<br />
Main drawback is that you get no warning <em>whatsoever</em> for profile mismatches: When you open two images in a different working space, and paste one into the other, colors will be converted. Which, as said, is irreversible and might give irreversible damage. If I&#8217;m going to <em>damage my image, I <strong>damn well want to be notified</strong>.</em></p>
<h3>Prepress</h3>
<p><a title="'Prepress'. Quite okay actually." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/PrePress.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/PrePress.jpg" alt="'Prepress'. Quite okay actually." /></a></p>
<p>Is quite a decent choice if you are doing prepress work. Profiles are preserved, you are warned when you get a mismatch, and reasonable profiles are chosen for CMYK, gray and spot. (depending on the area you chose, CMYK and dot gain are different.) Then again, if you are doing prepress work, I&#8217;d hope that you know enough about color management that you don&#8217;t need to read my thoughts on it&#8230;</p>
<h3>Web/Internet</h3>
<p><a title="'Web/Internet'. For limited use." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/Web.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/Web.jpg" alt="'Web/Internet'. For limited use." /></a></p>
<p>This is the <em>only</em> preset where converting to working space might make sense in my opinion: If you are just doing work for internet, <em>anything</em> should be sRGB. If you have to ask why: Read my <a href="http://www.getcolormanaged.com/color-management/saveforweb/">blogpost</a> on the subject. Then again, I&#8217;d like a warning if an image has no embedded profile: In some cases it might be because someone screwed up. This is largely a personal preference however.</p>
<h3>Other presets</h3>
<p>Are &#8220;more of the same&#8221; (two other Japanese presets only differ in CMYK, gray and spot from Japan Prepress2). The &#8220;Phase One&#8221; workflow is the odd one out: It sets a gray profile of Gray Gamma 2.2 which is quite sensible. Then again, the CMYK profile is &#8220;Euro-Catalog&#8221;, which I never need.<br />
The other options (Colorsync (mac only), PS5) are <span style="text-decoration: line-through;">obsolete</span> legacy.</p>
<h3>Create your own</h3>
<p>Since everybody&#8217;s needs are different, it makes sense to make your own preset then, doesn&#8217;t it? Sure! But you need to know what each setting does. Some things are pretty straight forward, others not so much.</p>
<h3>Default working spaces: RGB</h3>
<p>Pretty much up to personal preference. The question &#8220;what RGB color space is best&#8221; I&#8217;ll leave be for now. Use whatever working space you use in your raw converter of choice. Two points I do want to make: If you don&#8217;t understand color management, do yourself a favor and <em>use sRGB as a working space <strong>everywhere</strong></em>. On the other hand, if you are using a wide gamut color space (anything larger then AdobeRGB) <em>do so in 16 bit per channel only!</em><br />
Settings <em>never</em> to use are AppleRGB, ColorMatchRGB or GenericRGB. These are based on monitors that went the way of the dodo&#8230;</p>
<h3>CMYK and others</h3>
<p>For CMYK working space: Most people won&#8217;t ever print something on an offset press, so won&#8217;t ever be needing CMYK. When you do need it, make sure the printer tells you what profile to use, and set that as the default: It has some impact further down the road in PSCS4.<br />
Don&#8217;t ever use GenericCMYK or one of the &#8220;old&#8221; Photoshop CMYK settings here: No good reason to. When in doubt, you probably won&#8217;t ever need it, so pick the &#8220;default&#8221; for your region.<br />
Same goes for Gray and Spot working space. If you do a lot of grayscale images for web, gamma 2.2 is the best setting. If you print them to a specific Offsetpress and you know what dot gain to use, by all means do. But in that case you probably wouldn&#8217;t be reading this article&#8230; For same reasons as above <em>never, ever</em> use Gamma 1.8. It&#8217;s obsolete.</p>
<h3>Policies and Notifications</h3>
<p>Choose &#8220;Preserve Embedded Profiles&#8221;, unless as explained above, you are a web designer <em>and have thought about the subject a bit</em>.<br />
I don&#8217;t see the need to tick the &#8220;Profile mismatch: Ask when opening&#8221; box, since I edit images from a known source, and the embedded profiles are what they are for a reason. So YMMV. I <em>do</em> tick the &#8220;Ask when pasting&#8221; and &#8220;missing profiles&#8221; boxes. The first because I want to be notified if an image profile is converted, the second because if there is no profile embedded, someone screwed up.</p>
<p><a title="'Profile Mismatch': Are you sure you want to convert without checking for clipping that might occur?" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/Mismatch2.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/Mismatch2.jpg" alt="'Profile Mismatch': Are you sure you want to convert without checking for clipping that might occur?" /></a><br />
Note that if you choose &#8220;Discard the embedded profile (do not color manage)&#8221; here, the image will be shown <em>as if it had the default working space embedded</em>. This has the same effect as assigning your default working space: The image won&#8217;t display accurate, but it is reversible (by assigning the proper profile).</p>
<p><a title="'Missing Profile': It's likely that someone screwed up." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/Missing.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/Missing.jpg" alt="'Missing Profile': It's likely that someone screwed up." /></a></p>
<p>Another note <em>(a big one)</em> is that <em>PS somehow <strong>doesn&#8217;t</strong> display this warning when <strong>pasting</strong> an image without profile into a document with an embedded color space</em>! Colors <em>will</em> change.</p>
<h3>Advanced: Conversion options</h3>
<p>Engine: Leave at &#8220;Adobe (ACE)&#8221;. It&#8217;s the best choice, and if you have a specific reason why you would want to use another, you would not need my advice.<br />
Rendering intent: Either perceptual or relative colorimetric for photographic images. Which is best will depend on the image. Not that this setting matters much: This is the rendering intent used by default when you go Image &gt; Convert to profile (where you can change it in the dialog box) and it is used when going Image &gt; Mode &gt; CMYK for instance (which I would strongly advise against, since it offers no preview and no direct control)<br />
The description says it all:</p>
<p><a title="Description of Black Point Compensation" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/bpc.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/bpc.jpg" alt="Description of Black Point Compensation" /></a></p>
<p><em>Always</em> tick &#8220;Use Black point compensation&#8221; and also &#8220;Use Dither&#8221;: It makes banding or posterization much less likely.<br />
The last option &#8220;Compensate for Screen -referred profiles&#8221; is only important if you make documents for Adobe After Effects. In that case: Tick it. Otherwise: Tick it as well, since it won&#8217;t matter then.</p>
<h3>Advanced, but not to be used</h3>
<p>&#8220;Desaturate Monitor Colors By&#8221; and &#8220;Blend RGB Colors Using Gamma&#8221;: Easy: Don&#8217;t tick those. They are not meant for photographers. Again: Read the description:</p>
<p><a title="Description of 'Desaturate Monitor Colors By'" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/desatMonitorcolor.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/desatMonitorcolor.jpg" alt="Description of 'Desaturate Monitor Colors By'" /></a></p>
<h3>Possible pitfalls</h3>
<p>As already mentioned, the settings set in the &#8220;Conversion options&#8221; will be used when changing from one color space to the next by going Image &gt; Mode. <em>So <strong>do not</strong> go there.</em> Use Edit &gt; Convert to profile instead. Yes you can also use it to convert from RGB to CMYK&#8230;</p>
<p><a title="Convert from RGB to CMYK profile" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/convertToProfile.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/convertToProfile.jpg" alt="Convert from RGB to CMYK profile" /></a></p>
<p>Another, less well known fact, is that the default profile is what determines the values in the info palette (Color picker) for anything but the color space the image is in. So if you use a CMYK or grayscale color picker on  an RGB image, the readout will be for your <em>current default</em> CMYK or gray working space!</p>
<p><a title="Readout of the info palette is dependant upon Color Settings" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/ColorPicker.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/ColorPicker.jpg" alt="Readout of the info palette is dependant upon Color Settings" /></a></p>
<p>Another of the <span style="text-decoration: line-through;">stupid</span> less-then-brilliant decisions on Adobes part was to have the Select &gt; Color Range &gt; Out of Gamut selection be based on the default CMYK working space. Makes no sense whatsoever and makes the tool all but unusable for anyone who prints at home, but there it is&#8230;<br />
Here is an sRGB image, softproofed for my Epson R2880, using glossy paper. The Gamut warning is on and shows no out of gamut colors. Notice the selection?</p>
<p><a title="'Select Color Range &gt; Out of Gamut' is based upon default CMYK Working Space. Stupid." href="http://www.getcolormanaged.com/images/Blog/ColorSettings/ColorRange.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt; float: left;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/ColorRange.jpg" alt="'Select Color Range &gt; Out of Gamut' is based upon default CMYK Working Space. Stupid." /></a></p>
<h3>Conclusion</h3>
<p>After reading this, you should know enough about the subject to create your own settings. After you did, save them as your own preset. It might also be a good idea to add a description.<br />
Here&#8217;s mine:</p>
<p><a title="My settings" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/Description.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/Description.jpg" alt="My settings" /></a></p>
<p><a title="My settings" href="http://www.getcolormanaged.com/images/Blog/ColorSettings/MySettings.jpg" rel="lightbox[407]"><img style="margin: 10px 10px 10px 0pt;" src="http://www.getcolormanaged.com/images/Blog/ColorSettings/tmb/MySettings.jpg" alt="My settings" /></a></p>
   ]]></content:encoded>
			<wfw:commentRss>http://www.getcolormanaged.com/color-management/pscolorsettings/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Color management</title>
		<link>http://www.getcolormanaged.com/color-management/cmintro/</link>
		<comments>http://www.getcolormanaged.com/color-management/cmintro/#comments</comments>
		<pubDate>Sun, 02 Aug 2009 16:46:02 +0000</pubDate>
		<dc:creator>René</dc:creator>
				<category><![CDATA[Color Management]]></category>
		<category><![CDATA[introduction]]></category>
		<category><![CDATA[WYSIWYG]]></category>

		<guid isPermaLink="false">http://www.getcolormanaged.com/?p=136</guid>
		<description><![CDATA[An introduction In the &#8220;analog&#8221; days, it used to be simple: You had a slide looking like you wanted, and that was a fixed reference point. So it was &#8220;somebody else&#8217;s problem&#8221; to make a print that matched the slide: WYSIWYG. Simple. Or at least: Not your responsibility. Negatives were a bit more complicated, but [...]]]></description>
			<content:encoded><![CDATA[<h3>An introduction</h3>
<p>In the &#8220;analog&#8221; days, it used to be simple: You had a slide looking like you wanted, and that was a fixed reference point. So it was &#8220;<a href="http://hitchhikers.wikia.com/wiki/Somebody_Else%27s_Problem_field" onclick="urchinTracker('/outgoing/hitchhikers.wikia.com/wiki/Somebody_Else_27s_Problem_field?referer=');">somebody else&#8217;s problem</a>&#8221; to make a print that matched the slide: WYSIWYG. Simple. Or at least: Not your responsibility. Negatives were a bit more complicated, but still: S.E.P.</p>
<p>Nowadays, you&#8217;ll have a file that looks good on <em><strong>your</strong> screen</em>. Since you probably don&#8217;t want to lug your computer and monitor with you anytime you want to make a print, only to be able to show what you think the print <em>should</em> look like, how do you manage to get a print that looks like the image on your screen?</p>
<h3>The keyword</h3>
<p>&#8230;of course, is &#8220;manage&#8221;. As in: <em>Color manage</em>: &#8220;Out of the box&#8221; every monitor will display an image different. Ever seen a store with 20 televisions in a row? All TVs looking different? Same will be the case with computer monitors if you don&#8217;t take countermeasures.<br />
While the TVs pretty much boil down to &#8220;personal preference&#8221;, with digital imaging it&#8217;s about <em><strong>accuracy</strong></em>.<br />
<span id="more-136"></span></p>
<h3>How to be accurate?</h3>
<p>That <em>is</em> your responsibility: You need to make sure your display looks the same as everybody else&#8217;s. To do that you <em>calibrate</em> and <em>profile</em> it: Calibration makes sure your screen is at a fixed state. Profiling creates an .icc profile and makes sure a certain color is displayed exactly <em>so</em>. The best way to do this, is to use a hardware device, such as for instance <a href="http://spyder.datacolor.com/product-mc.php" onclick="urchinTracker('/outgoing/spyder.datacolor.com/product-mc.php?referer=');">Spyder3</a>, <a href="http://www.xrite.com/product_overview.aspx?ID=788" onclick="urchinTracker('/outgoing/www.xrite.com/product_overview.aspx?ID=788&amp;referer=');">iOne Display</a> or <a href="http://www.xrite.com/product_overview.aspx?ID=1114" onclick="urchinTracker('/outgoing/www.xrite.com/product_overview.aspx?ID=1114&amp;referer=');">ColorMunki</a>.</p>
<h3>The managing</h3>
<p>&#8230;of the colors is then done by your (color managed) software, such as Photoshop for instance.<br />
It looks at the images .icc profile and at your display profile, and does a conversion between the two. Thus making sure that the colors are shown as they should.</p>
<h3>The beauty of it</h3>
<p>&#8230;is that the printer also <del>has</del> should have a calibrated screen, so will see the image exactly as you do. So he can see what he <em>should</em> get. If he then also correctly uses the software to print color managed, you&#8217;ll get a print that&#8217;s as close to the view on screen as possible. In fact, in that case it&#8217;s even easier then it used to be in the analog days!</p>
<p>Only remaining difference is caused by the fact that your screen is a device <em>emitting</em> light, while the print is <em>reflecting</em> light, and the fact that there are some colors that can be displayed but simply cannot be printed (and vice-versa).<br />
That&#8217;s where softproofing comes in&#8230; But more on that in a future blog post.</p>
   ]]></content:encoded>
			<wfw:commentRss>http://www.getcolormanaged.com/color-management/cmintro/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://www.getcolormanaged.com/color-management/hello-world/</link>
		<comments>http://www.getcolormanaged.com/color-management/hello-world/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 08:58:50 +0000</pubDate>
		<dc:creator>René</dc:creator>
				<category><![CDATA[Color Management]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[introduction]]></category>

		<guid isPermaLink="false">http://www.getcolormanaged.com/WP/?p=1</guid>
		<description><![CDATA[First blog post. Ever. At least, on my own blog (to be). I&#8217;ve commented a fair bit on other people&#8217;s blogs, when the subject was Colormanagement, and someone presented wrong facts. For instance if it was recommended to set Photoshop to use &#8220;Monitor color&#8221; as working space, since then anything would look the same in [...]]]></description>
			<content:encoded><![CDATA[<h3>First blog post.</h3>
<p>Ever.</p>
<p>At least, on my own blog (to be).<br />
I&#8217;ve commented a fair bit on other people&#8217;s blogs, when the subject was Colormanagement, and someone presented wrong facts. For instance if it was recommended to set Photoshop to use &#8220;Monitor color&#8221; as working space, since then anything would look the same in Photoshop and the (not color managed) browser. Color management just went right out the window, as well as any chance at consistency&#8230;</p>
<p>Therefore, I believe this to be *bad* advice, so often I&#8217;d comment something along those lines, or sent the poster an email. I can&#8217;t stand misinformation. I&#8217;m kinda funny that way.</p>
<p>Because I&#8217;m kinda funny in other ways as well, I also like to <em>know how stuff works</em>. (And if possible, also <em>why</em>)<br />
That sometimes leads to hours of searching as to <em>why</em> something doesn&#8217;t work as expected, instead of just accepting the fact and get on with what you were doing&#8230; So probably not the best practice, both for your social life, and in the business kind of way. For the last, I couldn&#8217;t care less, and my social life is okay, thanks very much. Also, it <del>is satisfying my curiosity</del> has the added advantage of getting to understand the problem better, which gives an advantage when you engage other (peoples) &#8220;irrational&#8221; problems.</p>
<h3>So, what to expect here then?</h3>
<p>I have no idea yet. I don&#8217;t even know if it&#8217;s going to be a regularly updated blog, or more &#8220;website-like, static&#8221; approach. I&#8217;m not completely without a clue however:</p>
<p>First, I plan to post a few simple posts on the &#8220;how and why&#8221; of color management. Just to cover the basics. I&#8217;ve posted the same (or similar) on <a href="http://photography-on-the.net/forum/showthread.php?t=707058" onclick="urchinTracker('/outgoing/photography-on-the.net/forum/showthread.php?t=707058&amp;referer=');">POTN</a>.</p>
<p>Incidentally, that forum is probably what inspired me to start all this: I started a thread there a few years back about color problems. Due to my lack of organisation, limited knowledge at the time (and not locking the thread), it became what was lately accurately referred to, a &#8220;Huge meandering thread&#8221;. This blog is my penance, and an effort to bring some order to that chaos.</p>
<p>Later on (when I get comfortable with blogging), I&#8217;ll probably also post solutions whenever I encounter a problem (For instance: PSCS4 seems to have a bug regarding color managed printing, looking in to that as I have time to spare, I&#8217;m using PSCS2 until then)</p>
<p>I sincerely hope that later posts gain in structure compared to this one, and also are a bit more relevant. But this is at least better then the default &#8220;Welcome&#8221; post by WordPress&#8230; (And there&#8217;s no-one around to see it anyway).</p>
   ]]></content:encoded>
			<wfw:commentRss>http://www.getcolormanaged.com/color-management/hello-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

