<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: GNOME Color Manager Progress</title>
	<atom:link href="http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/</link>
	<description>Blog about geeky stuff</description>
	<lastBuildDate>Sun, 29 Jan 2012 09:38:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: dielpThitledy</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3367</link>
		<dc:creator>dielpThitledy</dc:creator>
		<pubDate>Tue, 24 Nov 2009 22:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3367</guid>
		<description>Lots of of folks blog about this topic but you wrote down some true words.</description>
		<content:encoded><![CDATA[<p>Lots of of folks blog about this topic but you wrote down some true words.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milan Knizek</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3344</link>
		<dc:creator>Milan Knizek</dc:creator>
		<pubDate>Mon, 16 Nov 2009 16:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3344</guid>
		<description>Do you know any software working on linux, which would be able to get the data about ICC profile from the display (or at least the hardware profile selected by a button on the display)? I recall someone mentioned on argyllcms list that the &quot;communication protocol&quot; is rather proprietary.

I have a Samsung XL20 and any time I switch the mode, I have to load the appropriate profile in gnome again.</description>
		<content:encoded><![CDATA[<p>Do you know any software working on linux, which would be able to get the data about ICC profile from the display (or at least the hardware profile selected by a button on the display)? I recall someone mentioned on argyllcms list that the &#8220;communication protocol&#8221; is rather proprietary.</p>
<p>I have a Samsung XL20 and any time I switch the mode, I have to load the appropriate profile in gnome again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: prokoudine</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3269</link>
		<dc:creator>prokoudine</dc:creator>
		<pubDate>Wed, 04 Nov 2009 21:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3269</guid>
		<description>BTW, I wonder if you could as far as merging and extending DDC/CI functionality from existing library and GNOME applet. Newer wide gamut displays store ICC profiles in their own LUT. Supporting them would be really awesome.</description>
		<content:encoded><![CDATA[<p>BTW, I wonder if you could as far as merging and extending DDC/CI functionality from existing library and GNOME applet. Newer wide gamut displays store ICC profiles in their own LUT. Supporting them would be really awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pascal de Bruijn</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3266</link>
		<dc:creator>Pascal de Bruijn</dc:creator>
		<pubDate>Tue, 03 Nov 2009 18:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3266</guid>
		<description>I have experimental Ubuntu Karmic packages available at my PPA:

https://launchpad.net/~pmjdebruijn/+archive/ppa/+packages</description>
		<content:encoded><![CDATA[<p>I have experimental Ubuntu Karmic packages available at my PPA:</p>
<p><a href="https://launchpad.net/~pmjdebruijn/+archive/ppa/+packages" rel="nofollow">https://launchpad.net/~pmjdebruijn/+archive/ppa/+packages</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: prokoudine</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3265</link>
		<dc:creator>prokoudine</dc:creator>
		<pubDate>Tue, 03 Nov 2009 15:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3265</guid>
		<description>But the point is, you don&#039;t have to scrap :) You can support Oyranos later, just keep it in mind ;)</description>
		<content:encoded><![CDATA[<p>But the point is, you don&#8217;t have to scrap <img src='http://blogs.gnome.org/hughsie/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':)' class='wp-smiley' />  You can support Oyranos later, just keep it in mind <img src='http://blogs.gnome.org/hughsie/wp-content/mu-plugins/tango-smilies/tango/face-wink.png' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3264</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 03 Nov 2009 11:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3264</guid>
		<description>This work seems awesome; thank you for doing it.

A suggestion to make it a little more &quot;Just Works&quot;: for the benefit of people without color calibration hardware, how about remembering the color calibration information, indexing it by the monitor&#039;s EDID information, optionally uploading that to a central site, and using that information as part of the wizard if you don&#039;t have the hardware?  &quot;You don&#039;t have color calibration hardware attached.  However, your monitor (vendor &quot;FOO&quot; model 1234) has color calibration data available in our database.  Would you like to use that color calibration data?&quot;  Or, if you don&#039;t want to assume based on attached color calibration hardware, offer the choice: &quot;Measure color calibration data using attached calibration hardware &gt;&quot; or &quot;Use known color calibration data for monitor vendor and model &gt;&quot;, with each option disabled when not available (preferably with an explanatory sentence below it, &quot;No color calibration hardware attached&quot; and &quot;No known color calibration data for monitor with vendor &#039;FOO&#039; and model 1234 not known&quot;, respectively).

You can get the monitor&#039;s EDID information from the xrandr property &quot;EDID_DATA&quot;, though that means you have to parse it yourself; however, since you only want the vendor and model out of it, that should prove easy enough.</description>
		<content:encoded><![CDATA[<p>This work seems awesome; thank you for doing it.</p>
<p>A suggestion to make it a little more &#8220;Just Works&#8221;: for the benefit of people without color calibration hardware, how about remembering the color calibration information, indexing it by the monitor&#8217;s EDID information, optionally uploading that to a central site, and using that information as part of the wizard if you don&#8217;t have the hardware?  &#8220;You don&#8217;t have color calibration hardware attached.  However, your monitor (vendor &#8220;FOO&#8221; model 1234) has color calibration data available in our database.  Would you like to use that color calibration data?&#8221;  Or, if you don&#8217;t want to assume based on attached color calibration hardware, offer the choice: &#8220;Measure color calibration data using attached calibration hardware &gt;&#8221; or &#8220;Use known color calibration data for monitor vendor and model &gt;&#8221;, with each option disabled when not available (preferably with an explanatory sentence below it, &#8220;No color calibration hardware attached&#8221; and &#8220;No known color calibration data for monitor with vendor &#8216;FOO&#8217; and model 1234 not known&#8221;, respectively).</p>
<p>You can get the monitor&#8217;s EDID information from the xrandr property &#8220;EDID_DATA&#8221;, though that means you have to parse it yourself; however, since you only want the vendor and model out of it, that should prove easy enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3263</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Tue, 03 Nov 2009 08:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3263</guid>
		<description>Sure, there are loads of other devices, made by several other companies. Just check the ArgyllCMS website for a list of supported devices. I&#039;m pretty sure Pantone are actually just giving their name to the Huey, as you can actually buy a Huey from other makers too.
You can, to some extent, profile a screen using visual indicators, but this will only give you a rough reading without doing hundreds of manual tests. Also, the black level and gamma of an LCD screen changes quite a lot based on the viewing angle, and so profiling &quot;by eye&quot; is actually really hard to do.</description>
		<content:encoded><![CDATA[<p>Sure, there are loads of other devices, made by several other companies. Just check the ArgyllCMS website for a list of supported devices. I&#8217;m pretty sure Pantone are actually just giving their name to the Huey, as you can actually buy a Huey from other makers too.<br />
You can, to some extent, profile a screen using visual indicators, but this will only give you a rough reading without doing hundreds of manual tests. Also, the black level and gamma of an LCD screen changes quite a lot based on the viewing angle, and so profiling &#8220;by eye&#8221; is actually really hard to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicu</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3260</link>
		<dc:creator>nicu</dc:creator>
		<pubDate>Tue, 03 Nov 2009 08:39:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3260</guid>
		<description>I understand 50$ is a relatively small sum (well, to buy it in my country will add a lot to it, but this is a different story), however Pantone is a *really evil* company (for example they snubbed the GIMP folks when those tried to wind a way to collaborate) and me, as probably many other FLOSS people, would find uncomfortable to give any money to them.

Isn&#039;t possible to calibrate the screen without dedicated hardware? I remember some Windows calibration tools (available on the display&#039;s drivers disks) there you can do the job only with software, by choosing colors and shades of gray.</description>
		<content:encoded><![CDATA[<p>I understand 50$ is a relatively small sum (well, to buy it in my country will add a lot to it, but this is a different story), however Pantone is a *really evil* company (for example they snubbed the GIMP folks when those tried to wind a way to collaborate) and me, as probably many other FLOSS people, would find uncomfortable to give any money to them.</p>
<p>Isn&#8217;t possible to calibrate the screen without dedicated hardware? I remember some Windows calibration tools (available on the display&#8217;s drivers disks) there you can do the job only with software, by choosing colors and shades of gray.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3252</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Mon, 02 Nov 2009 23:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3252</guid>
		<description>commit c661be0f100af2fe75191c2159c1daeb22a31601
Author: Richard Hughes 
Date:   Mon Nov 2 23:50:05 2009 +0000
    Don&#039;t crash when the EDID data is not available</description>
		<content:encoded><![CDATA[<p>commit c661be0f100af2fe75191c2159c1daeb22a31601<br />
Author: Richard Hughes<br />
Date:   Mon Nov 2 23:50:05 2009 +0000<br />
    Don&#8217;t crash when the EDID data is not available</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/comment-page-1/#comment-3251</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Mon, 02 Nov 2009 23:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=425#comment-3251</guid>
		<description>I thought about integrating it with gnome display caplet, but I think in the long run gcm should manage printer, scanner and camera profiles too, where integrating it with the display capplet makes little sense. Calibrating a monitor is just one link of the chain in a digital work-flow.

As for a donate button, it&#039;s very kind of you. I get employed by Red Hat to work on cool stuff, so I don&#039;t think it&#039;s required to send donations. If you really want to buy me something, amazon (UK) vouchers are probably the way to go. Thanks!</description>
		<content:encoded><![CDATA[<p>I thought about integrating it with gnome display caplet, but I think in the long run gcm should manage printer, scanner and camera profiles too, where integrating it with the display capplet makes little sense. Calibrating a monitor is just one link of the chain in a digital work-flow.</p>
<p>As for a donate button, it&#8217;s very kind of you. I get employed by Red Hat to work on cool stuff, so I don&#8217;t think it&#8217;s required to send donations. If you really want to buy me something, amazon (UK) vouchers are probably the way to go. Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/hughsie/2009/11/02/gnome-color-manager-progress/feed/ ) in 1.19104 seconds, on Feb 12th, 2012 at 5:25 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 6:25 am UTC -->
