<?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: RAW deathmatch &#8211; Lightroom 3 vs DXO 6 vs Capture One 5 vs Bibble 5</title> <atom:link href="http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/feed/" rel="self" type="application/rss+xml" /><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/</link> <description>Design &#38; Photography Tutorials and Resources</description> <lastBuildDate>Fri, 05 Mar 2010 20:39:02 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Armand Niculescu</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-507</link> <dc:creator>Armand Niculescu</dc:creator> <pubDate>Tue, 23 Feb 2010 06:43:56 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-507</guid> <description>It&#039;s the color space of the image. Basically, it&#039;s about how a particular combination of red, green and blue values - e.g. (72, 88, 234) - will actually look or print. Most images use the so-called SRGB color space, which are the colors most monitors can display.Professional RAW processors and dSLR cameras have the option of using the &quot;Adobe RGB&quot; space, which is capable of representing more colors. This is usually intended for print, resulting in deeper colors. On screen, images shot in Adobe RGB may look unsaturated and dull.You can try enabling color management in ACD See Pro or you can convert images to SRGB in Photoshop (&lt;em&gt;Edit --&gt; Convert to Profile&lt;/em&gt;)</description> <content:encoded><![CDATA[<p>It&#8217;s the color space of the image. Basically, it&#8217;s about how a particular combination of red, green and blue values &#8211; e.g. (72, 88, 234) &#8211; will actually look or print. Most images use the so-called SRGB color space, which are the colors most monitors can display.</p><p>Professional RAW processors and dSLR cameras have the option of using the &#8220;Adobe RGB&#8221; space, which is capable of representing more colors. This is usually intended for print, resulting in deeper colors. On screen, images shot in Adobe RGB may look unsaturated and dull.</p><p>You can try enabling color management in ACD See Pro or you can convert images to SRGB in Photoshop (<em>Edit &#8211;> Convert to Profile</em>)</p> ]]></content:encoded> </item> <item><title>By: Igal</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-506</link> <dc:creator>Igal</dc:creator> <pubDate>Mon, 22 Feb 2010 19:18:26 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-506</guid> <description>Hello Armand,
I have had great pleasure reading your review.
I mainly shoot landscape and architecture.
Have been using Capture One Pro 5 with good results.
But I will now give DXO 6 a try.But, I seem to be having a very weird problem.
Jpeg&#039;s that I edit in Photoshop, and RAW files edited in C1 Pro look excellent in the programs.
But, when I open them in AcdSee pro 3, the look dull and borring.
What could be the problem?Thank you,
Igal.</description> <content:encoded><![CDATA[<p>Hello Armand,<br
/> I have had great pleasure reading your review.<br
/> I mainly shoot landscape and architecture.<br
/> Have been using Capture One Pro 5 with good results.<br
/> But I will now give DXO 6 a try.</p><p>But, I seem to be having a very weird problem.<br
/> Jpeg&#8217;s that I edit in Photoshop, and RAW files edited in C1 Pro look excellent in the programs.<br
/> But, when I open them in AcdSee pro 3, the look dull and borring.<br
/> What could be the problem?</p><p>Thank you,<br
/> Igal.</p> ]]></content:encoded> </item> <item><title>By: Nino Frewat</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-505</link> <dc:creator>Nino Frewat</dc:creator> <pubDate>Sun, 21 Feb 2010 10:16:34 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-505</guid> <description>Thank you very much for this informative review.
I have written one for Aperture 3 vs ACR (PSCS4) vs Capture 1, but it&#039;s not as detailed and scientific as yours:
http://alebaneseonline.wordpress.com/2010/02/20/comparing-the-three-raw-heavyweights/</description> <content:encoded><![CDATA[<p>Thank you very much for this informative review.<br
/> I have written one for Aperture 3 vs ACR (PSCS4) vs Capture 1, but it&#8217;s not as detailed and scientific as yours:<br
/> <a
href="http://alebaneseonline.wordpress.com/2010/02/20/comparing-the-three-raw-heavyweights/" rel="nofollow">http://alebaneseonline.wordpress.com/2010/02/20/comparing-the-three-raw-heavyweights/</a></p> ]]></content:encoded> </item> <item><title>By: Roger W</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-496</link> <dc:creator>Roger W</dc:creator> <pubDate>Sat, 13 Feb 2010 10:04:58 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-496</guid> <description>Hi Armand and thanks for your informative article.My comment has been touched on in a number of posts and is regarding workflow using different RAW converters to get the best out of each. Indeed you even partially answered the question when you proposed a DxO and LR workflow as:- &quot;Original RAW –&gt; process in DxO –&gt; export as DNG –&gt; Lightroom –&gt; TIFF/JPEG&quot;.I am lucky in having DxO, LR, C1 (which rarely gets used these days), Canon DPP (never gets used) and finally Photomatix for HDR images.I tend to use DxO when lens correction is important but process these with most of the other settings turned off. Then, because I like LR&#039;s cataloguing capabilities, bring it back into LR as a TIFF and do my final edits in Photoshop.It would be good to get feedback from you, or others, on the various components to use in a multi RAW processing environment. Indeed, for HDR images, I don&#039;t think I have found a good workflow that incorporates Photomatix as compromises have to be made.Thanks again,
Rog.</description> <content:encoded><![CDATA[<p>Hi Armand and thanks for your informative article.</p><p>My comment has been touched on in a number of posts and is regarding workflow using different RAW converters to get the best out of each. Indeed you even partially answered the question when you proposed a DxO and LR workflow as:- &#8220;Original RAW –&gt; process in DxO –&gt; export as DNG –&gt; Lightroom –&gt; TIFF/JPEG&#8221;.</p><p>I am lucky in having DxO, LR, C1 (which rarely gets used these days), Canon DPP (never gets used) and finally Photomatix for HDR images.</p><p>I tend to use DxO when lens correction is important but process these with most of the other settings turned off. Then, because I like LR&#8217;s cataloguing capabilities, bring it back into LR as a TIFF and do my final edits in Photoshop.</p><p>It would be good to get feedback from you, or others, on the various components to use in a multi RAW processing environment. Indeed, for HDR images, I don&#8217;t think I have found a good workflow that incorporates Photomatix as compromises have to be made.</p><p>Thanks again,<br
/> Rog.</p> ]]></content:encoded> </item> <item><title>By: Peter Kasbergen</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-493</link> <dc:creator>Peter Kasbergen</dc:creator> <pubDate>Mon, 08 Feb 2010 09:31:18 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-493</guid> <description>Very nice quality review! I have my own opinion on Image workflow software, which I have written down here: http://www.kasbergen.com/?p=35You basically did here what I left out: compare image quality with examples. Nice to see :-)</description> <content:encoded><![CDATA[<p>Very nice quality review! I have my own opinion on Image workflow software, which I have written down here: <a
href="http://www.kasbergen.com/?p=35" rel="nofollow">http://www.kasbergen.com/?p=35</a></p><p>You basically did here what I left out: compare image quality with examples. Nice to see <img
src='http://cdn.twin-pixels.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: Rick</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-477</link> <dc:creator>Rick</dc:creator> <pubDate>Sat, 23 Jan 2010 03:55:03 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-477</guid> <description>Excellent review.  I bought DxO 5 for the Mac recently, partly based on it having integration with Lightroom according to DxO.  Having problems exporting the raw file from Lightroom to DxO, I just learned from DxO support that if you change the file name in any way when importing from the camera card (as in Lightroom, Photo Mechanic, whatever), you cannot then export an image from Lightroom to DxO- it will not be able to find the original file if it is changed from the name the camera gave it on capture. This is not useful, as far as I am concerned: you have to keep the meaningless camera-generated name rather than changing it to something useful/recognizable?  While I like DxO, I will not change my workflow and give up renaming files.  So DxO has become pretty much a no-go for me, sad to say.</description> <content:encoded><![CDATA[<p>Excellent review.  I bought DxO 5 for the Mac recently, partly based on it having integration with Lightroom according to DxO.  Having problems exporting the raw file from Lightroom to DxO, I just learned from DxO support that if you change the file name in any way when importing from the camera card (as in Lightroom, Photo Mechanic, whatever), you cannot then export an image from Lightroom to DxO- it will not be able to find the original file if it is changed from the name the camera gave it on capture. This is not useful, as far as I am concerned: you have to keep the meaningless camera-generated name rather than changing it to something useful/recognizable?  While I like DxO, I will not change my workflow and give up renaming files.  So DxO has become pretty much a no-go for me, sad to say.</p> ]]></content:encoded> </item> <item><title>By: Daniel</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-476</link> <dc:creator>Daniel</dc:creator> <pubDate>Fri, 22 Jan 2010 21:35:48 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-476</guid> <description>Sorry if this is redundant, my browser closed the window while I was composing an earlier reply.It is sad that all the players in the digital imaging space were unable to come up with an open standard that supports everyone&#039;s requirements, present and future.  However, that day may eventually come as digital imaging evolves and matures.  Part of the reason is that these guys are in a race with each other to produce the best imaging products, good for us.  Supporting an open standard for workflow, image processing, image archiving will be critical.  We do not want to be locked in to a vendor set forever.   It is pretty incredible how far and how fast it has come from the days of the late 90s when 2MP noisy sensors were state of the art.  With processing and processing tuned to the imaging sensor, I expect significant future advances in the next years and decades.  You will also see different decisions about where to partition the processing - in-camera hardware or post processing software - which will affect the DNG choices.  I believe we are still in &quot;wild west&quot; days for a little while, early adopters beware.  Another of my concerns is around archival.  I store RAW, but all the post processing and corrections we do would ideally be reproducible 10-20 years from now, so whatever software workflow we decide on has to support the legacy all the way back.  Never mind what will happen to digital storage media and the readers/writers necessary.  In any case, there should be a good open DNG standard as soon as possible.I haven&#039;t used HDR much either, but I am getting a feel for it.  I am using it to go back and post process some older photos and have been able to bring out some details that I could not do any other way.  HDR is ideal for those inside cathedral shots where there is a lot of small scale detail, I also think they tuned the software to do well with sunsets with a lot of dramatic clouds and reflections from the underside of the clouds.  The lighthouse is the Portland Head Light in Cape Elizabeth Maine, which some estimate is the most photographed in the world.  We had just had a snowstorm which was winding down in the afternoon, just in time for the sunset.  Those conditions happen maybe once a year, so I don&#039;t think you will see too many shots like those.   I used HDR on those shots (bracket 5 or 7 spaced 1EV apart at 5fps) evident by the ghosts of the multiple exposures in the surf.  I did not do a lot of work on processing those shots, you can see spots from the snow and frozen sea spray stuck to the lens, horizon off horizontal, etc.  And I do admit they appear a little over-processed.  I am working on a few chosen ones to fix all those issues, however this will take significant time.</description> <content:encoded><![CDATA[<p>Sorry if this is redundant, my browser closed the window while I was composing an earlier reply.</p><p>It is sad that all the players in the digital imaging space were unable to come up with an open standard that supports everyone&#8217;s requirements, present and future.  However, that day may eventually come as digital imaging evolves and matures.  Part of the reason is that these guys are in a race with each other to produce the best imaging products, good for us.  Supporting an open standard for workflow, image processing, image archiving will be critical.  We do not want to be locked in to a vendor set forever.   It is pretty incredible how far and how fast it has come from the days of the late 90s when 2MP noisy sensors were state of the art.  With processing and processing tuned to the imaging sensor, I expect significant future advances in the next years and decades.  You will also see different decisions about where to partition the processing &#8211; in-camera hardware or post processing software &#8211; which will affect the DNG choices.  I believe we are still in &#8220;wild west&#8221; days for a little while, early adopters beware.  Another of my concerns is around archival.  I store RAW, but all the post processing and corrections we do would ideally be reproducible 10-20 years from now, so whatever software workflow we decide on has to support the legacy all the way back.  Never mind what will happen to digital storage media and the readers/writers necessary.  In any case, there should be a good open DNG standard as soon as possible.</p><p>I haven&#8217;t used HDR much either, but I am getting a feel for it.  I am using it to go back and post process some older photos and have been able to bring out some details that I could not do any other way.  HDR is ideal for those inside cathedral shots where there is a lot of small scale detail, I also think they tuned the software to do well with sunsets with a lot of dramatic clouds and reflections from the underside of the clouds.  The lighthouse is the Portland Head Light in Cape Elizabeth Maine, which some estimate is the most photographed in the world.  We had just had a snowstorm which was winding down in the afternoon, just in time for the sunset.  Those conditions happen maybe once a year, so I don&#8217;t think you will see too many shots like those.   I used HDR on those shots (bracket 5 or 7 spaced 1EV apart at 5fps) evident by the ghosts of the multiple exposures in the surf.  I did not do a lot of work on processing those shots, you can see spots from the snow and frozen sea spray stuck to the lens, horizon off horizontal, etc.  And I do admit they appear a little over-processed.  I am working on a few chosen ones to fix all those issues, however this will take significant time.</p> ]]></content:encoded> </item> <item><title>By: Armand Niculescu</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-472</link> <dc:creator>Armand Niculescu</dc:creator> <pubDate>Thu, 21 Jan 2010 06:19:35 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-472</guid> <description>Hi,
First, I &lt;em&gt;love&lt;/em&gt; that lighthouse.The DNG question is a tough one. I started using it around 2005 because my camera at the time was producing uncompressed RAWs and saving 33%-50% space when archiving the files wasn&#039;t too bad. I also thought DNG will get a wider support, if not from camera manufacturers directly, at least from all software makers. If you read between the lines of my article, you can guess I regret a little using just DNG, as I can&#039;t load my old images in DXO for example. The obvious answer is that we must lobby the camera makers and software companies to add support for DNG. Nowadays support for MP3, JPG or TIFF is taken for granted, that should b the case with DNG, instead of ARW, CRW, MRF, NEF, RAW to name just a few.Workflow, I&#039;m trying to do as much as possible in the RAW converter and yes, leave the 8bit-only operations last.HDR - I must admit I haven&#039;t worked extensively with it, I have a &lt;a href=&quot;http://www.twin-pixels.com/hdr-cathedral/&quot; rel=&quot;nofollow&quot;&gt;HDR cathedral&lt;/a&gt; and I agree it takes a lot of tweaking to get a convincing look.</description> <content:encoded><![CDATA[<p>Hi,<br
/> First, I <em>love</em> that lighthouse.</p><p>The DNG question is a tough one. I started using it around 2005 because my camera at the time was producing uncompressed RAWs and saving 33%-50% space when archiving the files wasn&#8217;t too bad. I also thought DNG will get a wider support, if not from camera manufacturers directly, at least from all software makers. If you read between the lines of my article, you can guess I regret a little using just DNG, as I can&#8217;t load my old images in DXO for example. The obvious answer is that we must lobby the camera makers and software companies to add support for DNG. Nowadays support for MP3, JPG or TIFF is taken for granted, that should b the case with DNG, instead of ARW, CRW, MRF, NEF, RAW to name just a few.</p><p>Workflow, I&#8217;m trying to do as much as possible in the RAW converter and yes, leave the 8bit-only operations last.</p><p>HDR &#8211; I must admit I haven&#8217;t worked extensively with it, I have a <a
href="http://www.twin-pixels.com/hdr-cathedral/" rel="nofollow">HDR cathedral</a> and I agree it takes a lot of tweaking to get a convincing look.</p> ]]></content:encoded> </item> <item><title>By: Daniel DeSimone</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-471</link> <dc:creator>Daniel DeSimone</dc:creator> <pubDate>Thu, 21 Jan 2010 00:54:28 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-471</guid> <description>Mr. NiculescuThank you for your review.I have been a very happy user of C1 standard until C1 5 Pro has come out.  As with many other posters, because of the price I am looking at alternatives.  I also have in the past year started shooting with wider angle (14-24 FX f2.8 + D700 Nikon), and recently started experimenting with HDR (decided on Photomatix, for now.  Best HDR is a very similar situation, each has its strength, no one does it all).  As you said, there is no one simple solution, DxO is absolutely unparalleled in optical correction.  I played with the optical correction in C1 Pro 5, but it is not up to the same standards.  I also have come to the same conclusion that Bibble takes the cake for noise reduction.My question is around workflow and the amount of database conversions.  My concern is that moving from NEF to DNG and/or TIFF-16 to TIFF, not to mention JPEG final output, and running those through each individual programs&#039; interpretations of those formats introduces noise.  For example, I have seen differing results in the quality of NEF processing between D200, D300 and D700 into C1 4.8, never mind conversions.  Another example is that some of the filters and plug ins can only run in 8-bit mode.  Is there an argument to get into DNG as quickly as possible and limit yourself to only using LR, PS and native plug-ins?   Second, should one also consider the order of operations such that anything that can only be done in 8-bit mode be done last?Finally, any comments on HDR?  My limited experience has shown that it has promise, but a long way to go before all the problems are overcome.  I have had success in bringing out detail in snow drifts simultaneously with jagged dark rocks that no amount of Highlight/Shadow in C1 or PS could come close to.  On the other hand, aligning 7 exposures with moving subjects creates problems, noise is added, but most significantly it creates more macro effects such as subtle glows and shadows around masses.Thanks again for your excellent review.</description> <content:encoded><![CDATA[<p>Mr. Niculescu</p><p>Thank you for your review.</p><p>I have been a very happy user of C1 standard until C1 5 Pro has come out.  As with many other posters, because of the price I am looking at alternatives.  I also have in the past year started shooting with wider angle (14-24 FX f2.8 + D700 Nikon), and recently started experimenting with HDR (decided on Photomatix, for now.  Best HDR is a very similar situation, each has its strength, no one does it all).  As you said, there is no one simple solution, DxO is absolutely unparalleled in optical correction.  I played with the optical correction in C1 Pro 5, but it is not up to the same standards.  I also have come to the same conclusion that Bibble takes the cake for noise reduction.</p><p>My question is around workflow and the amount of database conversions.  My concern is that moving from NEF to DNG and/or TIFF-16 to TIFF, not to mention JPEG final output, and running those through each individual programs&#8217; interpretations of those formats introduces noise.  For example, I have seen differing results in the quality of NEF processing between D200, D300 and D700 into C1 4.8, never mind conversions.  Another example is that some of the filters and plug ins can only run in 8-bit mode.  Is there an argument to get into DNG as quickly as possible and limit yourself to only using LR, PS and native plug-ins?   Second, should one also consider the order of operations such that anything that can only be done in 8-bit mode be done last?</p><p>Finally, any comments on HDR?  My limited experience has shown that it has promise, but a long way to go before all the problems are overcome.  I have had success in bringing out detail in snow drifts simultaneously with jagged dark rocks that no amount of Highlight/Shadow in C1 or PS could come close to.  On the other hand, aligning 7 exposures with moving subjects creates problems, noise is added, but most significantly it creates more macro effects such as subtle glows and shadows around masses.</p><p>Thanks again for your excellent review.</p> ]]></content:encoded> </item> <item><title>By: Ronald N. Tan</title><link>http://www.twin-pixels.com/lightroom-dxo-capture-one-bibble-5/#comment-463</link> <dc:creator>Ronald N. Tan</dc:creator> <pubDate>Sun, 10 Jan 2010 22:12:15 +0000</pubDate> <guid
isPermaLink="false">http://www.twin-pixels.com/?p=403#comment-463</guid> <description>How do you do Mr. Niculescu,Thank you for this delightful and an informative article on the RAW giants. LR and C1 are like like the Nikons and the Canons of the RAW just because of the money they have and the professional zealots heralding and serving as poster people.When I first started only two years ago, I started with ACR 4.x and ultimately purchased into the C1 PRO license (then 3.7.8) and have been loyally using C1 PRO since the second half of 2007. With LR 3 on the horizon, I am thinking of &quot;divorcing&quot; C1 and picking up LR 3 when it comes out--I am hoping LR 3 would have a lens correction module where it would look up its database of lenses similar to PTLens and voila!Then LR3 (Adobe) will really shine and I think they will win even more customers just because Adobe &gt;&gt; CaptureOne in regard to financial resources and programmers. Thank you for your time sir and I have an immense reverence for you and your work. Reading your article, I was compelled to try DXO Optics 6 and oh-my-goodness, its grotesque and unintuitive GUI turned me off.My ultimate wish is for the &quot;HDR&quot; Fill Light/Recovery of ACR to be integrated into C1 (still my de facto RAW)-it squashed C1&#039;s Fill Light and Recovery until kingdom come.Happy new year 2010 sir!Best in health,ronald n. tan</description> <content:encoded><![CDATA[<p>How do you do Mr. Niculescu,</p><p>Thank you for this delightful and an informative article on the RAW giants. LR and C1 are like like the Nikons and the Canons of the RAW just because of the money they have and the professional zealots heralding and serving as poster people.</p><p>When I first started only two years ago, I started with ACR 4.x and ultimately purchased into the C1 PRO license (then 3.7.8) and have been loyally using C1 PRO since the second half of 2007. With LR 3 on the horizon, I am thinking of &#8220;divorcing&#8221; C1 and picking up LR 3 when it comes out&#8211;I am hoping LR 3 would have a lens correction module where it would look up its database of lenses similar to PTLens and voila!</p><p>Then LR3 (Adobe) will really shine and I think they will win even more customers just because Adobe &gt;&gt; CaptureOne in regard to financial resources and programmers. Thank you for your time sir and I have an immense reverence for you and your work. Reading your article, I was compelled to try DXO Optics 6 and oh-my-goodness, its grotesque and unintuitive GUI turned me off.</p><p>My ultimate wish is for the &#8220;HDR&#8221; Fill Light/Recovery of ACR to be integrated into C1 (still my de facto RAW)-it squashed C1&#8217;s Fill Light and Recovery until kingdom come.</p><p>Happy new year 2010 sir!</p><p>Best in health,</p><p>ronald n. tan</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: box346.bluehost.com @ 2010-03-11 00:48:36 by W3 Total Cache -->