<?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: Gimp vs Photoshop</title>
	<atom:link href="http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/</link>
	<description>The Photography of Brian White</description>
	<lastBuildDate>Fri, 06 Jan 2012 22:09:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Choose The Best Between GIMP vs Photoshop &#8211; Comparison Between GIMP vs Photoshop &#8211; Selecting The Best Amongst Photoshop vs GIMP Adobe Photoshop Mac</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-33903</link>
		<dc:creator>Choose The Best Between GIMP vs Photoshop &#8211; Comparison Between GIMP vs Photoshop &#8211; Selecting The Best Amongst Photoshop vs GIMP Adobe Photoshop Mac</dc:creator>
		<pubDate>Tue, 18 Oct 2011 00:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-33903</guid>
		<description>[...] here for Related LinksGimp vs Photoshop   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] here for Related LinksGimp vs Photoshop   Share and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Lannuzel</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-6824</link>
		<dc:creator>Nicolas Lannuzel</dc:creator>
		<pubDate>Mon, 10 Dec 2007 08:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-6824</guid>
		<description>Hi,

Interesting website, good source of information, and I like your personal point of views too.

Regarding dcraw/ufraw, I&#039;ve been using UFraw since a while, and it give me excellent results. As far as I can see, the colors and brightness is exactly the same as the embedded JPG inside the RAW file. And under 100% zoom there&#039;s no moire or funny artifacts as some would fear. Details level is same as output from CaptureNX.

The only differences are:
  - Noise level, but that&#039;s because I&#039;m not using the wavelet noise reduction feature in UFraw; while the embedded JPG has already been &quot;denoised&quot; directly in the camera.
  - Sharpening: UFraw doesn&#039;t do any kind of sharpening (yet). It&#039;s not a concern for me, since I always scale down and sharpen a bit in Gimp just before saving as JPG but never before editing the picture.

In the case of my Nikon D80, the picture from UFraw also contains more pixels. It seems that the camera engine (or Nikon CaptureNX) trim the image a bit, in order to keep a 3:2 aspect ratio I presume. But those pixels are in the raw file, and UFraw will give them to you.


The key here is to use the right color profile for your camera. Without it, the picture is flat and dark. I found the profile for my camera on the UFRaw page, there&#039;s also a link to a site giving other profiles as well.

I like UFraw more than CaptureNX (that I was using before in a virtual machine running XP). It allows me to write custom shell scripts for downloading, resizing and tagging in F-Spot automatically using UFraw, Image magick and Exif Tools.

You can check the UFraw page here: http://ufraw.sourceforge.net/

Have fun!

Nicolas</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Interesting website, good source of information, and I like your personal point of views too.</p>
<p>Regarding dcraw/ufraw, I&#8217;ve been using UFraw since a while, and it give me excellent results. As far as I can see, the colors and brightness is exactly the same as the embedded JPG inside the RAW file. And under 100% zoom there&#8217;s no moire or funny artifacts as some would fear. Details level is same as output from CaptureNX.</p>
<p>The only differences are:<br />
  &#8211; Noise level, but that&#8217;s because I&#8217;m not using the wavelet noise reduction feature in UFraw; while the embedded JPG has already been &#8220;denoised&#8221; directly in the camera.<br />
  &#8211; Sharpening: UFraw doesn&#8217;t do any kind of sharpening (yet). It&#8217;s not a concern for me, since I always scale down and sharpen a bit in Gimp just before saving as JPG but never before editing the picture.</p>
<p>In the case of my Nikon D80, the picture from UFraw also contains more pixels. It seems that the camera engine (or Nikon CaptureNX) trim the image a bit, in order to keep a 3:2 aspect ratio I presume. But those pixels are in the raw file, and UFraw will give them to you.</p>
<p>The key here is to use the right color profile for your camera. Without it, the picture is flat and dark. I found the profile for my camera on the UFRaw page, there&#8217;s also a link to a site giving other profiles as well.</p>
<p>I like UFraw more than CaptureNX (that I was using before in a virtual machine running XP). It allows me to write custom shell scripts for downloading, resizing and tagging in F-Spot automatically using UFraw, Image magick and Exif Tools.</p>
<p>You can check the UFraw page here: <a href="http://ufraw.sourceforge.net/" rel="nofollow">http://ufraw.sourceforge.net/</a></p>
<p>Have fun!</p>
<p>Nicolas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WickedBlog &#187; Blog Archive &#187; Open Source Gems: Graphics 2-D Manipulation and Replacement for Illustrator and Paint Shop Pro</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-203</link>
		<dc:creator>WickedBlog &#187; Blog Archive &#187; Open Source Gems: Graphics 2-D Manipulation and Replacement for Illustrator and Paint Shop Pro</dc:creator>
		<pubDate>Thu, 22 Mar 2007 10:52:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-203</guid>
		<description>[...] Illustrator user now, and you want to read a great review on the comparisons between the two, visit Brian White&#8217;s Review of The Gimp vs. Illustrator to determine if you can go with the current version of The Gimp, or if you need to wait until [...]</description>
		<content:encoded><![CDATA[<p>[...] Illustrator user now, and you want to read a great review on the comparisons between the two, visit Brian White&#8217;s Review of The Gimp vs. Illustrator to determine if you can go with the current version of The Gimp, or if you need to wait until [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian White</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-36</link>
		<dc:creator>Brian White</dc:creator>
		<pubDate>Thu, 11 Jan 2007 07:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-36</guid>
		<description>It isn&#039;t so much that Gimp can&#039;t do RAW/NEF is that it supports only 8-bits per channel.  Since one of the benefits of the RAW formats in greater color depth (usually 12 bits per channel), these extra four bits are dropped after the conversion.

If the RAW converter can do the adjustment you need, such as adjusting the &quot;levels&quot; or &quot;curves&quot; before reduction to 8 bits, then this is sufficient and Gimp is fully capable for all the other touch-ups.

When I tried &quot;dcraw&quot; for conversion in to Gimp, I was disappointed.  It could convert the image data, but it did not apply the correct white balance or noise reduction that had been set in the camera.  The JPEG was of much higher quality and a better starting point.  I&#039;ll have to try &quot;ufraw&quot; sometime.</description>
		<content:encoded><![CDATA[<p>It isn&#8217;t so much that Gimp can&#8217;t do RAW/NEF is that it supports only 8-bits per channel.  Since one of the benefits of the RAW formats in greater color depth (usually 12 bits per channel), these extra four bits are dropped after the conversion.</p>
<p>If the RAW converter can do the adjustment you need, such as adjusting the &#8220;levels&#8221; or &#8220;curves&#8221; before reduction to 8 bits, then this is sufficient and Gimp is fully capable for all the other touch-ups.</p>
<p>When I tried &#8220;dcraw&#8221; for conversion in to Gimp, I was disappointed.  It could convert the image data, but it did not apply the correct white balance or noise reduction that had been set in the camera.  The JPEG was of much higher quality and a better starting point.  I&#8217;ll have to try &#8220;ufraw&#8221; sometime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Codrington</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-35</link>
		<dc:creator>Andrew Codrington</dc:creator>
		<pubDate>Thu, 11 Jan 2007 06:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-35</guid>
		<description>Hey Brian,
You mentioned GIMP not having RAW support. I saw a mention somewhere a while ago about UFRaw (http://ufraw.sourceforge.net/). I&#039;ve downloaded and installed it with no injuries.

It seems to work with GIMP, and supports our NEF files - but I have almost no clue what I&#039;m doing.

I&#039;d be interested in your take on it if you get a chance!

I&#039;m sold on the utility of RAW for special cases, but don&#039;t want to waste time fighting with software that doesn&#039;t do it justice.

Enjoy Zurich!

Andrew</description>
		<content:encoded><![CDATA[<p>Hey Brian,<br />
You mentioned GIMP not having RAW support. I saw a mention somewhere a while ago about UFRaw (<a href="http://ufraw.sourceforge.net/" rel="nofollow">http://ufraw.sourceforge.net/</a>). I&#8217;ve downloaded and installed it with no injuries.</p>
<p>It seems to work with GIMP, and supports our NEF files &#8211; but I have almost no clue what I&#8217;m doing.</p>
<p>I&#8217;d be interested in your take on it if you get a chance!</p>
<p>I&#8217;m sold on the utility of RAW for special cases, but don&#8217;t want to waste time fighting with software that doesn&#8217;t do it justice.</p>
<p>Enjoy Zurich!</p>
<p>Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-33</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Thu, 14 Dec 2006 19:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-33</guid>
		<description>If I&#039;m not mistaken, gimp will be getting (basic) ICC profile support in 2.4, which should be out fairly soon. Shame about V3 being so far off, but at least their new image processing layer is actually being developed agian...</description>
		<content:encoded><![CDATA[<p>If I&#8217;m not mistaken, gimp will be getting (basic) ICC profile support in 2.4, which should be out fairly soon. Shame about V3 being so far off, but at least their new image processing layer is actually being developed agian&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-32</link>
		<dc:creator>Guest</dc:creator>
		<pubDate>Mon, 11 Dec 2006 19:09:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-32</guid>
		<description>One more thing:
Photoshop is troublesome if you have an outdated machine (4-6 years and not upgraded since then :p), many of the filters give me the messages &quot;Not enough memory&quot; etc.. I have never(ever) had any message like that with Gimp, everything is just perfect. :)

Why spend money on something don&#039;t really need? Go for Gimp! ;)</description>
		<content:encoded><![CDATA[<p>One more thing:<br />
Photoshop is troublesome if you have an outdated machine (4-6 years and not upgraded since then :p), many of the filters give me the messages &#8220;Not enough memory&#8221; etc.. I have never(ever) had any message like that with Gimp, everything is just perfect. <img src='http://www.backgroundexposure.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Why spend money on something don&#8217;t really need? Go for Gimp! <img src='http://www.backgroundexposure.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian White</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-17</link>
		<dc:creator>Brian White</dc:creator>
		<pubDate>Thu, 23 Nov 2006 15:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-17</guid>
		<description>I know of CiniPaint (formally, FilmGimp, I believe) but haven&#039;t used it.  From what I&#039;ve read, it more suited towards the editing of multiple film frames that of individual photos.  How does it&#039;s tool/feature set compare to that of Gimp itself?</description>
		<content:encoded><![CDATA[<p>I know of CiniPaint (formally, FilmGimp, I believe) but haven&#8217;t used it.  From what I&#8217;ve read, it more suited towards the editing of multiple film frames that of individual photos.  How does it&#8217;s tool/feature set compare to that of Gimp itself?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Weller</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-16</link>
		<dc:creator>Alan Weller</dc:creator>
		<pubDate>Thu, 23 Nov 2006 13:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-16</guid>
		<description>Cinepaint, derived from the Gimp has 32 bit colour support as well as ICC colour profile support. It also works on low end equipment as it uses the GTK 1 library. I still use The Gimp but am keeping an eye on Cinepaint development. There is a new version on the horizon which will use the lightweight FLTK library.</description>
		<content:encoded><![CDATA[<p>Cinepaint, derived from the Gimp has 32 bit colour support as well as ICC colour profile support. It also works on low end equipment as it uses the GTK 1 library. I still use The Gimp but am keeping an eye on Cinepaint development. There is a new version on the horizon which will use the lightweight FLTK library.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian White</title>
		<link>http://www.backgroundexposure.com/blog/2006/11/gimp-vs-photoshop/comment-page-1/#comment-14</link>
		<dc:creator>Brian White</dc:creator>
		<pubDate>Tue, 21 Nov 2006 02:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.backgroundexposure.com/blog/index.php/2006/11/15/gimp-vs-photoshop/#comment-14</guid>
		<description>I did that at a sunset (&lt;a href=&quot;http://www.backgroundexposure.com/blog/index.php/2006/11/06/art-and-the-technician/&quot; rel=&quot;nofollow&quot;&gt;Art and the Technician&lt;/a&gt;) for those very reasons.  It took four exposures and some careful blending to make everything look balanced.  I guess because I&#039;m keeping it in XCF (Gimp native format) I have the full range of information anyway.</description>
		<content:encoded><![CDATA[<p>I did that at a sunset (<a href="http://www.backgroundexposure.com/blog/index.php/2006/11/06/art-and-the-technician/" rel="nofollow">Art and the Technician</a>) for those very reasons.  It took four exposures and some careful blending to make everything look balanced.  I guess because I&#8217;m keeping it in XCF (Gimp native format) I have the full range of information anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

