<?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/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>RB Design &#187; Adobe Lightroom</title>
	<atom:link href="http://photo.rwboyer.com/tag/adobe-lightroom/feed/" rel="self" type="application/rss+xml" />
	<link>http://photo.rwboyer.com</link>
	<description>All Things Photography</description>
	<lastBuildDate>Thu, 29 Jul 2010 01:21:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Aperture vs. Lightroom &#8211; File Management Again</title>
		<link>http://photo.rwboyer.com/2009/12/06/aperture-vs-lightroom/</link>
		<comments>http://photo.rwboyer.com/2009/12/06/aperture-vs-lightroom/#comments</comments>
		<pubDate>Sun, 06 Dec 2009 18:13:03 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Aperture vs Lightroom]]></category>
		<category><![CDATA[Apple Aperture]]></category>
		<category><![CDATA[Articles]]></category>
		<category><![CDATA[Adobe]]></category>
		<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Aperture]]></category>
		<category><![CDATA[Aperture vs. Lighroom]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[file management]]></category>
		<category><![CDATA[folder structure]]></category>
		<category><![CDATA[Organization]]></category>

		<guid isPermaLink="false">http://photo.rwboyer.com/?p=1414</guid>
		<description><![CDATA[Woooo Whooo, I received my very first question from an Aperture File Management eBook customer. Of course I answered his specific question ASAP but something that I touch on in the book crossed my mind as well that I thought people considering Aperture vs. Lightroom at this point may want to consider. Even a few [...]]]></description>
			<content:encoded><![CDATA[<p>Woooo Whooo, I received my very first question from an <a href="http://photo.rwboyer.com/aperture-ebooks/">Aperture File Management eBook</a> customer. Of course I answered his specific question ASAP but something that I touch on in the book crossed my mind as well that I thought people considering Aperture vs. Lightroom at this point may want to consider. Even a few of you Aperture old timers may find this a little interesting.</p>
<p>I have written about <a href="http://photo.rwboyer.com/2008/10/01/aperture2-vs-lightroom2-file-management/">Lightroom&#8217;s and Aperture&#8217;s comparative file management capabilities</a> before but I wanted to add a different perspective or twist to it. There are a lot of people that choose to use Lightroom over Aperture because they &#8220;like&#8221; that Lightroom&#8217;s only file organizational tool happens to be whatever manually created folder structure on their hard drive. Of course Aperture can do the exact same thing if that is all you want but Aperture can do so much more. Heck you can use Aperture to sort, select, categorize, arrange, and group images any way that you want and then&#8230;. TAHHH DAHHH &#8211; use the file relocate master functions in combination with the subfolder options to have Aperture automatically create just about any pristine folder structure with your images as you could possibly imagine. AUTOMATICALLY and error free.</p>
<p>Personally after using Aperture I would far prefer to import my images into Aperture no matter how big a mess my folder structure was. Organize them using all of the Aperture tools and metadata and then have Aperture create the exact folder structure I wanted on disk. Even if every single image I had was in one giant pile. Aperture can suck them in and create a pristine by date folder hierarchy in one import and one relocate. Fantastic.</p>
<p>Hell &#8211; If I had to use Lightroom I would probably buy Aperture for the sole purpose of automating and standardizing my on disk folder structure or reorganizing the whole thing if I change my mind. I actually find it laughable that Lightroom users are so adamantly against the way Aperture &#8220;deals with folders and files&#8221;. That is only because they have no idea how quickly and easily Aperture can create recreate, reorganize, sort sift, wash, iron, and dry any folder structure that anybody could possibly imagine with about three mouse clicks.</p>
<p>RB</p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2009/12/06/aperture-vs-lightroom/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Alternatives To The Mainstream</title>
		<link>http://photo.rwboyer.com/2009/04/09/alternatives-to-the-mainstream/</link>
		<comments>http://photo.rwboyer.com/2009/04/09/alternatives-to-the-mainstream/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 03:39:51 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Apple Aperture]]></category>
		<category><![CDATA[Articles]]></category>
		<category><![CDATA[General Photography]]></category>
		<category><![CDATA[ACDSee]]></category>
		<category><![CDATA[Aperture]]></category>
		<category><![CDATA[Aperture 2]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Lightroom 2]]></category>
		<category><![CDATA[Photo Mechanic]]></category>
		<category><![CDATA[work-flow]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://photo.rwboyer.com/?p=876</guid>
		<description><![CDATA[I am a little punch drunk from spending far too much time on reinventing the site with a bunch of new features so I thought I would take a little break and discuss a couple of products that serve as partial alternatives to the heavy hitters in the image work-flow field. The two players that [...]]]></description>
			<content:encoded><![CDATA[<p><a rel="lightbox" href="/wp-content/uploads/2009/04/Ex1.jpg"><img title="Ex1.jpg" src="/wp-content/uploads/2009/04/.thumbs/.Ex1.jpg" border="0" alt="Ex1.jpg" hspace="10" vspace="10" width="175" height="150" align="left" /></a></p>
<p>I am a little punch drunk from spending far too much time on reinventing the site with a bunch of new features so I thought I would take a little break and discuss a couple of products that serve as partial alternatives to the heavy hitters in the image work-flow field. The two players that come to mind would be Photo Mechanic and ACDSee Pro.</p>
<p>I don&#8217;t claim to be remotely proficient with either product in the way that I am with Aperture and Lightroom but I thought I would bring <span id="more-876"></span>them up for those that may be looking for an alternative as well as to pose the question of why one would want to go with one of those products. While I have an opinion on this &#8211; big surprise there &#8211; I am honestly interested in others thoughts, especially those that use other products or are considering it.</p>
<p>Photo Mechanic seemingly enjoys a devoted following among the Photojournalist crowd. They claim that it is fast, nothing faster, especially when reviewing RAW. The funny thing is that almost none of those shooters actually shoot RAW.Â PhotojournalistsÂ shoot JPG for what I consider an anachronistic hold out for something sort of like some sort of proof that the image is &#8220;real&#8221;. Yea I know that happens to be the deal right now but I suspect it will probably change. If anyone is interested in that thought process I would be happy to share it but let&#8217;s just say if I were a photojournalist I would most likely shoot RAW+JPG even if I HAD to deliver the out of camera JPG files.</p>
<p>Getting back on track, if speed is the issue I find it difficult to believe that there is any measurable performance difference between just about any work-flow software on modern equipment dealing with puny JPG files. So if the mission of the day is speed and modern hardware can chew through JPG files way faster than humans could possibly absorb them visually that would leave us with work-flow efficiency. Now don&#8217;t get me wrong, Photo Mechanic seems to be a fine piece of software for what it does but I prefer the flexibility andÂ substantialÂ additional function that both Aperture and Lightroom supply.</p>
<p>On to ACDSee. Windows only, similar but smaller feature set to Aperture and Lightroom, not free. Again a decent piece of software for a Windoze product but I am perplexed as to what would motivate someone to choose it over Lightroom or Aperture. It doesn&#8217;t seem to have the historical following that Photo Mechanic has so what is the attraction? Does it boil down to what photographers started with, what they are used to, or the desire to use something that other people don&#8217;t use?</p>
<p>I am not casting dispersions on either of the products that I mentioned, I am just curious as to the thought process and value proposition real or perceived that motivates the selection of either product over something like Lightroom or Aperture.</p>
<p>Thoughts?</p>
<p>RB</p>
<p>Ps. The image at the top is a screen shot of a JPG from my 4.1 megapixel D2H strait out of the camera with all image setting set to &#8220;normal&#8221; &#8211; who the heck needs more megapixels (at least for some things).</p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2009/04/09/alternatives-to-the-mainstream/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Aperture 2 vs. Lightroom 2 &#8211; Keywords</title>
		<link>http://photo.rwboyer.com/2008/11/25/aperture-2-vs-lightroom-2-keywords/</link>
		<comments>http://photo.rwboyer.com/2008/11/25/aperture-2-vs-lightroom-2-keywords/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 12:49:34 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Aperture vs Lightroom]]></category>
		<category><![CDATA[Aperture]]></category>
		<category><![CDATA[Aperture 2]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[hierarchy]]></category>
		<category><![CDATA[keyword]]></category>
		<category><![CDATA[Keyword Synonym]]></category>
		<category><![CDATA[Metadata]]></category>

		<guid isPermaLink="false">http://photo.rwboyer.com/?p=572</guid>
		<description><![CDATA[After much clamoring from loyal readers here is another installment of Aperture v. Lightroom round 9.7. I will try to tackle key-wording (is that a word now?) as quickly and painlessly as possible. First off some quick bottom line kinds of things and then some details. Both applications are so far and away better than [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/wp-content/uploads/2008/A2vLR2_Keywords.jpg"><img title="A2vLR2_Keywords.jpg" src="/wp-content/uploads/2008/.thumbs/.A2vLR2_Keywords.jpg" border="0" alt="A2vLR2_Keywords.jpg" hspace="10" vspace="10" width="150" height="94" align="left" /></a>After much clamoring from loyal readers here is another installment of Aperture v. Lightroom round 9.7. I will try to tackle key-wording (is that a word now?) as quickly and painlessly as possible. First off some quick bottom line kinds of things and then some details. Both applications are so far and away better than older tools that we won&#8217;t even bother to compare them. If you are using either of these and not tagging your images with keywords you should be ashamed of yourself or something. Aperture introduced some ground breaking features with it&#8217;s release way back before Lightroom was around. <span id="more-572"></span>The problem with Aperture is a &#8220;what have you done for me lately&#8221; kind of problem. Aperture hasn&#8217;t really added, fixed, or refined a whole lot in the keyword department since version 1. Lightroom on the other hand has taken all the really cool things that Aperture had and added a bunch of really useful goodies of it&#8217;s own. So the bottom line here is that Lightroom wins this one hand&#8217;s down at the moment. I know you were not expecting that to come from me if you have been reading along with this series, maybe I am just so enraged because after 354,891 requests by myself and other photographers Apple can&#8217;t seem to give us one little tiny freaking check-forking-box to include the entire keyword hierarchy when exporting image versions. Enough of that, here are some more details for those that may not use these every day.</p>
<p>First keyword hierarchies &#8211; both applications support creating and modifying hierarchies of keywords. For the uninitiated this is an awesomely powerful feature. You can put keywords like rose, petunia, chrysanthemum, etc, under the keyword &#8220;flower&#8221;, which you can then put under the keyword &#8220;plant&#8221;. By doing this if you tag an image with the keyword rose and only that keyword rose when you do a search for images with the keyword &#8220;plant&#8221; or &#8220;flower&#8221; that image that you tagged with &#8220;rose&#8221; will show up as well &#8211; get it? I cannot explain how useful this is, you really need to experience it yourself &#8211; for one thing it makes keywording your images about 3000 times faster and more effective. All you do is add really really specific keywords to your images and they inherent all the more general keywords above that specific keyword in the hierarchy. You don&#8217;t even have to bother thinking about it before you start keywording. Both applications allow you to manipulate and modify the keyword hierarchy anytime you want. Example &#8211; import a bunch of images of let&#8217;s say boats. add all the kinds of boats. Pearson, Hunter, O&#8217;Day, Hobie, whatever. When you are done if you don&#8217;t already have a general keyword boat just make one and maybe a sail keyword as well. Drag the sail under the boat keyword, then drag all of the specific kinds under sail &#8211; done now you can search on boat or sail and Lightroom/Aperture will find all of the boats you just tagged with the specific kind of boats &#8211; cool. That is where the similarity ends in terms of keyword hierarchies between Aperture and Lightroom. Aperture does all this wonderfulness withing Aperture itself but only embeds the specific keyword when you export images and choose to embed the metadata or create an XMP sidecar. You can do crazy stuff like running scripts that smash the entire hierarchy into each of your images based on the specific keywords but that sort of defeats the purpose. Lightroom on the other hand will export the entire hierarchy for each specific keyword, but wait there&#8217;s more, for each and every keyword Lightroom let&#8217;s you specify whether or not to include the parent keywords and&#8230;. whether to export it at all.</p>
<p>Comparing the ability to assign keywords both Aperture and Lightroom have similar features. You can pretty much type each keyword in and if it does not exist both applications keep track of that for you. You can select directly from a list that is searchable/filterable. Both applications allow you to copy assign keywords more than one at a time by using one image as the model and then applying those keywords to as many images as you want. Lightroom also allows you to assign a &#8220;shortcut&#8221; to a bunch of different and unrelated keywords, Aperture does not have this but personally I have found this useless.</p>
<p>Both applications allow you to import and export the whole keyword scheme, if you use more than one computer to do work this is absolutely essential. It also helps if you work with an agency that has standard keyword definitions or with a team of photographers. Aperture has the ability to lock the keywords in order to avoid unintentionally adding nonexistent keywords, Lightroom does not. This is really not a big deal given that the Lightroom interface promotes clicking buttons to add keywords vs. typing them. If you stick to consistency in your work-flow by clicking buttons when you intend on using an existing keyword and typing one when you intend on adding a new keyword you will be fine. Removing keywords is easy in both applications but the user interface to do this is better in Lightroom (that is Lightroom 1 &#8211; Aperture 98,767 on the UI front) I have no idea why Apple made this so bizarre in Aperture.</p>
<p>One last feature that Aperture does not have and Lightroom 2 introduced is keyword synonyms. This is the ability to associate a bunch of words with an &#8220;official keyword&#8221; that mean the same thing and are treated the same when searching. This is another amazing feature heck you can even put words in a different language here. Really good if you are a stock photographer and need to tag images with a million specifics that mean the same thing. Again you can tell Lightroom that the synonyms should be exported if you want &#8211; this is a huge deal &#8211; wake up Apple get your forkin&#8217; act together and stop giving Aperture users ridiculous things like &#8220;All Project&#8221; view so we can have a screen that looks like iPhoto isn&#8217;t that nice &#8211; give us the keyword features that Lightroom has &#8211; SOON.</p>
<p>The only thing that I can say about Aperture here is that again it wins in the user interface department with a couple of minor exceptions. Aperture is just elegant and pretty all the way around. Lightroom &#8211; especially the dialog boxes to manage some of the keyword functionality are clunky, cumbersome, and downright Windows 3.1&#8242;ish.</p>
<p>Score a big win for Adobe Lightroom 2 versus Apple Aperture 2 when it comes to keyword functionality.</p>
<p>RB</p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2008/11/25/aperture-2-vs-lightroom-2-keywords/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Aperture2 vs. Lightroom2 &#8211; Stacks</title>
		<link>http://photo.rwboyer.com/2008/10/04/aperture2-vs-lightroom2-stacks/</link>
		<comments>http://photo.rwboyer.com/2008/10/04/aperture2-vs-lightroom2-stacks/#comments</comments>
		<pubDate>Sun, 05 Oct 2008 00:38:49 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Aperture vs Lightroom]]></category>
		<category><![CDATA[Aperture]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Apple Aperture]]></category>
		<category><![CDATA[collections]]></category>
		<category><![CDATA[image stack]]></category>
		<category><![CDATA[stacks]]></category>
		<category><![CDATA[virtual copies]]></category>

		<guid isPermaLink="false">http://rwboyer.blogdns.com/?p=466</guid>
		<description><![CDATA[Stacks in Aperture2 and Lightroom2 are about the only feature that share some functionality and have the same name. Stacks are a way of grouping similar images together. The images can be various versions of the same image taken in the camera, virtual copies (as termed in LR), versions (same thing but Aperture term), or [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/wp-content/uploads/2008/A2vLR2_Stacks.jpg"><img title="A2vLR2_Stacks.jpg" src="/wp-content/uploads/2008/.thumbs/.A2vLR2_Stacks.jpg" border="0" alt="A2vLR2_Stacks.jpg" hspace="10" vspace="10" width="150" height="94" align="left" /></a>Stacks in Aperture2 and Lightroom2 are about the only feature that share some functionality and have the same name. Stacks are a way of grouping similar images together. The images can be various versions of the same image taken in the camera, virtual copies (as termed in LR), versions (same thing but Aperture term), or versions that were modified with an external editor/plug-in. Stacks have the same basic functionality in both applications and can more or less do similar jobs. The magic of stacks comes from their interaction with albums (Aperture) or collections (Lightroom). I will touch a little bit on albums/collections just because the function of images stacks are so closely related to these other features. I will also compare a bit of compare mode functionality as well mostly due to Apertures excellent &#8220;stack mode&#8221;.<span id="more-466"></span></p>
<p>First the similarities between Lightroom and Aperture. Both applications can group images together either manually or automatically by the date and time stamps on the original images. They both automatically put new versions/virtual copies in a stack with the original master image. You an move images &#8220;up&#8221; or &#8220;down&#8221; in a stack or move an image right to the top. Images at the top of the stack are the images that represent the stack when the stack is closed and there for provide an easy way to select only the images at the top of stacks when all stacks are closed.</p>
<p>The big difference between Aperture2 and Lightroom2 is that stacks are inherent and visible no matter where you are looking at an image in Aperture. When using Lightroom you only have access to stacks and the related stack functionality when looking at images in the library module and then only when clicked on a folder (the closest thing to an Aperture project) view. For instance if you drag an image in a stack into a collection that image shows up in the collection but there is no indication when viewing the collection that it is part of an image stack. There is no stack functionality at all when viewing a collection with one exception. If you create a new virtual copy or version of an image in a collection it will automatically be added to a stack with the original image when viewing that image in a folder. In aperture it is apparent that an image is in a stack no matter where you are looking at it, in an album, a smart album, the project, etc. This may not seem like a big deal but it is huge in terms of a streamlined work-flow. When combined with the functionality of &#8220;album picks&#8221; in Aperture, the ability for different images to show up at the top of a stack in every different album or album like thing is a huge time saver for creating and managing various versions of an image for different output purposes. Take for example the need for different image crops for standard paper sizes. In Aperture you can close all of your stacks, select all of them (or filter based on whatever criteria you want) create a new album with those. Hit one key to make a new version and then apply an 8&#215;10 crop to all of them at the same time. Just the act of doing this causes the new versions created in the context of the album to show up at the top of the stack in that album. Don&#8217;t get me wrong there are ways of accomplishing this in Lightroom with much less fanfare than the way we all used to do things like this but Aperture&#8217;s stacks/stack picks/album picks are major work-flow efficiency tools when used to their best advantage. The Light room equivalent is more like go to the folder, close all the stacks, select all images or filter/select all images, create virtual copies, create new collection, drag collection to collection set, select all images in collection, apply black and white preset. Not a big deal but here is the big deal but longer and clunkier.</p>
<p>The other thing that is different is what is almost a total lack of short cut keys to manipulate stacks in Lightroom. WTF, once you have some experience using an application and you are whizzing through your work-flow using short cut keys and one or two are missing for what you want/need to do it&#8217;s like hitting a brick wall going 90 mph. The same applies to the lack of short cut keys for Lightroom compare mode. If you get proficient using both Aperture2 compare features and Lightroom features you will feel like you are in slow motion, mouse move point, click, hell in Lightroom. Talking about compare features for a moment, Lightroom has a workable compare mode and just enough keys to make you want the ones it does not have. Lightroom also has absolutely no connection between it&#8217;s compare features and it&#8217;s stack features. The big missing key as compared to Aperture is the set compare item key. Don&#8217;t think this is a big deal? You should have seen the seizures and conniptions that the experienced Aperture users had when Apple removed not that key but the short cut that put you into compare mode and set the compare item at the same time due to newbie users accidently putting themselves in compare mode. The speed of compare mode, short cut keys and stack mode are deal breakers when comparing Aperture2 to Lightroom2 for a lot of people. Stack mode in Aperture2 is like compare mode but tied to image stacks. A summary is that the right/left arrow keys only move the candidate image within the stack, they won&#8217;t go beyond. The up/down arrow keys move from stack to stack. When changing stacks the &#8220;stack pick&#8221; or image at the top of the stack is automatically set to the compare images. Last but not least, ta da&#8230; there is a shortcut key/function that replaces the compare image with the candidate AND makes it the stack pick.</p>
<p>It&#8217;s also kind of nice to do a search or use a global smart album and know that an image that shows up is part of an image stack, in other words has other versions or similar shot variations. Even if the other version do not meet the search or smart album there is a grey box around the image along with a badge indicating the number of images in a stack that the image is a part of.</p>
<p>The bottom line stacks, compare mode, and their relationship to versions/virtual copies and collections/albums are workable in Lightroom and better than anything we had a few years ago but Aperture2 blows the living crap out of Lightroom2 when it comes to stack functionality when looked at in the context of an overall work-flow.</p>
<p>RB</p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2008/10/04/aperture2-vs-lightroom2-stacks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Aperture2 vs. Lightroom2 &#8211; Aperture Forum Post</title>
		<link>http://photo.rwboyer.com/2008/10/03/aperture2-vs-lightroom2-aperture-forum-post/</link>
		<comments>http://photo.rwboyer.com/2008/10/03/aperture2-vs-lightroom2-aperture-forum-post/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 03:06:24 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Aperture vs Lightroom]]></category>
		<category><![CDATA[Aperture]]></category>
		<category><![CDATA[Aperture 2]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Lightroom 2]]></category>

		<guid isPermaLink="false">http://rwboyer.blogdns.com/2008/10/419/</guid>
		<description><![CDATA[Thought some readers here would find my sarcastic but true response to a name redacted poster in the Aperture forum&#8217;s post regarding his switch to Lightroom. The really funny part was his response to this sadly Apple deleted it before I could grab it. Knew that would happen that is how you are able to [...]]]></description>
			<content:encoded><![CDATA[<p><span class="jive-quote-header">Thought some readers here would find my sarcastic but true response to a name redacted poster in the Aperture forum&#8217;s post regarding his switch to Lightroom. The really funny part was his response to this sadly Apple deleted it before I could grab it. Knew that would happen that is how you are able to enjoy this part. Original author in normal text &#8211; my caviler response in grey italic.</span></p>
<p>RB<span id="more-419"></span></p>
<p><em style="color: #e06666;">Name changed</em> wrote:</p>
<div class="jive-quote">well it was nice while it lasted, but Apple come on do you think nobody will try another software ?</p>
<p>I moved to Lightroom2, for the following reasons</p>
<p>1) Lightroom presets, finally i can select how i want a group of pictures to look like and replicate it later with 1 click</p></div>
<p><em style="color: #cccccc;">I use both applications both on almost a daily basis. If this is your number<br />
one reason to switch I see you switching back and forth and to and fro<br />
to just about anything that comes along. This functionality is<br />
replicated using other Aperture features in a heartbeat. Good luck<br />
saving a ton of time with this one.</em></p>
<div class="jive-quote">2)Keyword synonyms, I have finally have a meaningful hierarchy and synonyms included without moving a finger</div>
<p><em style="color: #cccccc;">Keyword synonyms are nice I totally agree that this is really cool -<br />
esp for multilingual photographers or publications. Bet you you will<br />
see Keyword functionality beefed up in the next Aperture release it&#8217;s<br />
been about the same since v1 (long before LR was even a glimmer in<br />
Adobe&#8217;s eye)<br />
</em></p>
<div class="jive-quote">3)working keywords. I can have my &#8220;work group&#8221;<br />
keywords like what agencies i submitted my images too, what were the<br />
sales etc. I can search and sort and create dynamic collections, but I<br />
can choose those to be exportable or not exportable. Apple if you<br />
position Aperture as &#8220;professional&#8221; software, give us tools that<br />
professionals can use</div>
<p><em style="color: #cccccc;">Aperture can do the same thing with one caveat that there are several<br />
scripts make work (namely putting the hierarchy in the exported version)<br />
</em></p>
<div class="jive-quote">4)Non destructible editing. I can mask, edit,<br />
correct, change exposure, sharpen, color, etc without creating a<br />
rendered file. I do not get a concept of Aperture plugins, why do i<br />
want to use or pay for plugins that render to a file? I want it in RAW,<br />
otherwise i have photoshop</div>
<p><em>&#8220;Non Destructable&#8221; is this a new technology that I missed or didn&#8217;t quite<br />
fathom. Anywho &#8211; the localized adjustments are nice and Aperture&#8217;s D+B<br />
plugin is a joke but not a deal breaker for most folk especially with<br />
tools like Viveza. and disk space is cheap anyway.<br />
</em></p>
<div class="jive-quote">5)D@mn databases are getting corrupted all<br />
the time. Apple get a note, use unique ID not visible to users, I don&#8217;t<br />
care if 2 files have the same name, make it work</div>
<p><em style="color: #cccccc;">I have 300,000+ images in my main library &#8211; no issues. Maybe it&#8217;s you<br />
or your hardware, or something. LR has a database &#8211; don&#8217;t count your<br />
chickens so fast.<br />
</em></p>
<div class="jive-quote">6)Better B&amp;W processing and NR</div>
<p>Agreed way better DNG support and the new camera profiles and profile<br />
tools that not many people even know are out there are a game changer -<br />
Apple needs to think about this and hopefully do something similar or<br />
better yet open up the RAW processing engine and let other people do it.</p>
<p><em style="color: #cccccc;">As for noise &#8211; get a D3 or D700 all noise reduction *****.</em></p>
<p><em style="color: #cccccc;"></em></p>
<div class="jive-quote">Overall I liked Aperture UI and features much better then Lightroom 1x,<br />
but when Lightroom 2.0 came out i gave it a try. The type of<br />
productivity increase i got is just incredible comparing to Aperture.<br />
The biggest &#8220;no go&#8221; for me was lack of support for second monitor and<br />
proper compare tools. With Lightroom 2 I have it all</p>
<p>Now minor but noticeable differences between Aperture and Lightroom</p>
<p>- Aperture database keeps getting corrupted (did i mention it before?)</p>
<p>- Aperture keeps crashing</p>
<p>- At about 50,000 images Aperture is barely usable with MacbookPro with 4GB ram</p>
<p>- You can not take your processing changes with you, Lightroom export those into XMl</p>
<p>There are much more things regarding support of new camera&#8217;s, support for bridge or CS, issues closed format</p>
<p>Overall I love Aperture look and feel and some functions, but if I need<br />
to process, keyword and render 100 pictures in 10 minutes from Studio<br />
shoot I choose lightroom</p>
<p>Bye bye</p>
<p>Have fun</p></div>
<p><em style="color: #cccccc;"></em><em>Bye</em><br />
We&#8217;ll miss you over here, can&#8217;t wait to see you in the LR forums. Have<br />
fun don&#8217;t worry about us idiots over here we&#8217;ll get along I hope<br />
without all of you wonderful contributions.</p>
<p><em style="color: #cccccc;">RB<br />
</em></p>
<p><em><span style="color: #cccccc;">Ps. 100 shots? Save your self some time spent in learning a new app use bridge or finder.<br />
</span></em></p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2008/10/03/aperture2-vs-lightroom2-aperture-forum-post/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Aperture 2 vs. Lightroom 2 &#8211; File Management</title>
		<link>http://photo.rwboyer.com/2008/10/01/aperture2-vs-lightroom2-file-management/</link>
		<comments>http://photo.rwboyer.com/2008/10/01/aperture2-vs-lightroom2-file-management/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 05:40:38 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Aperture vs Lightroom]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Apple Aperture]]></category>
		<category><![CDATA[master image]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://rwboyer.blogdns.com/2008/10/406/</guid>
		<description><![CDATA[Due to popular demand I will provide some additional detail to my previous Adobe Lightroom 2 versus Apple Aperture 2 article. Both of these applications are so rich in both functionality and the multitude of ways they can used to support a photographic work-flow it will take a serious of articles to even scratch the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/wp-content/uploads/2008/Lr2_File_Mgt.jpg"><img title="Lr2_File_Mgt.jpg" src="/wp-content/uploads/2008/.thumbs/.Lr2_File_Mgt.jpg" border="0" alt="Lr2_File_Mgt.jpg" hspace="10" vspace="10" width="150" height="94" align="left" /></a>Due to popular demand I will provide some additional detail to my previous Adobe Lightroom 2 versus Apple Aperture 2 article. Both of these applications are so rich in both functionality and the multitude of ways they can used to support a photographic work-flow it will take a serious of articles to even scratch the surface. So, no better place to start than the image file management capabilities. Most photographers adopting either one of these applications will not delve into this subject until way down the road and when they do they usually have about 1,000 questions that they NEED answers to right now.</p>
<p>Aperture gives you two different ways to manage your original &#8220;master&#8221; image files. The first way is the managed masters method. Using managed masters Aperture pretty much completely insulates you from having to manage your images files at all. Aperture imports the images into its Library and figures out where to put them for you. This is great for libraries that are not of a massive scale, like on your laptop. <span id="more-406"></span>Using managed masters pretty much frees you from having to make decisions about where to put the images that you download from your camera. One thing that I need to clear up about managed masters and the Aperture library is the unreasonable fear that a lot of photographers have about Aperture somehow squirlling their images away in some super secret, unintelligible, highly complicated, weirdo structure that is just waiting for the slightest breeze to blow for them to be lost and gone forever. Let me put you at ease right now, this is not the case. The Aperture library is pretty much a folder/directory with a special flag that makes it look like one big file when viewed in the Finder. Don&#8217;t believe me? Fire up a terminal (command line) window and cd to ~/Pictures and then do an ls on the &#8220;Aperture Library.aplibraryls&#8221;. Look Ma, I can see all the stuff in there. Yup, and guess what. Aperture automagically does the exact same thing you would probably do manually it creates another directory inside for each project and puts your original master images in there. I think it is hilarious how many people I see mirror the exact same structure on a single disk manually instead of letting Aperture do it for them for irrational fear of&#8230;.Nothing?</p>
<p>This brings us to the second way that Aperture gives you to manage your original master images. That way is using &#8220;referenced masters&#8221;. Using referenced masters allows you to put the original master images anywhere you like. The only really good reason to use referenced masters with Aperture is to allow you to use more than one drive to store your images. This is really simple, the interesting part is you don&#8217;t have to decide one way or the other. With Aperture you can mix and match both when you import and down the road. For example let&#8217;s say you only have one machine and it&#8217;s a laptop with one internal drive. You could easily have all of you active projects use managed masters and then use Aperture to relocate them as referenced masters onto an external HD that you leave behind. If you need them active again just use Aperture to consolidate them back into the library if you want. The big thing with Aperture and major difference to Lightroom is that Aperture pretty much abstracts file management from the rest of your work-flow. When you look at your projects and their organizational structure inside of Aperture you have no indication of where your files are, nor do you care. If you want to manage the location of your files there are a couple of functions that allow you to do this but it has nothing to do with the way that you organize your projects or images within Aperture. The important functions are Relocate Masters, Consolidate Masters, and Manage Referenced. Relocate moves your original master images file to wherever you specify, including from managed to referenced. Consolidate takes whatever masters you have selected and moves them from being referenced to being managed back inside the Aperture library, neatly into a corresponding folder to the project that they live in. Last but not least Manage allows you to do a ton of really powerful things like re-hook the images versions to referenced masters when you move them on purpose or by accident somewhere different. I am talking way different because if you just rename the folder they reside in Aperture deals with that automagically.</p>
<p>I have dropped a couple of hints so far about this but here is the deal, there does not have to be any relationship at all between what Aperture project an image lives in and where the corresponding original master image resides on disk. In fact if you wanted to some of the images can be managed masters, some can be referenced from a different HD, and some can be referenced from a DVD if you want. Not only that but you can select what ever images in any combination you want, a whole project, a couple of images in a project, the whole library, etc, and then use the file management functions that I described on that set. You don&#8217;t have to do this, you can get involved as much or as little as you would like to in where your images are stored and it has no bearing with how your projects within Aperture are organized.</p>
<p>The reason that I spent so much time on how Aperture does things is because it makes explaining how Lightroom does things really easy. In Lightroom your folder/directory structure is your project structure, end of story. The on disk location of your originals images and how they are divided between folders is the way they are organized in Lightroom. What disk and what folder they are in is in your face and not at all abstracted from you at all. The only thing that you can do is move the folder around as a whole with all of the images in it, even to another HD and then tell Lightroom what you did. The other thing that you can do is move images out of one folder to some other folder and then tell Lightroom where to find them but that changes the way that your project structure in Lightroom is organized. Bottom Line &#8211; Aperture original master image location and project structure are completely independent. In Lightroom original master image location is tied directly to project structure and organization. The way that Lightroom works is a very special case of the way Aperture can work.</p>
<p>A coupe of other minor things to note that can be considered file management. Both Lightroom and Aperture generate JPG preview images of RAW files that are imported. The previews allow you to view your images and perform metadata, organization related tasks, slide shows, etc. even when the RAW master files are &#8220;off-line&#8221;. Previews also help speed some things up in both applications when there is no need to render the RAW file over and over. Aperture gives you a finer degree of control over the size of the previews generated and when they are generated. You can generate them automatically or completely manually with Aperture. You can delete any subset of image previews that you would like. This comes in handy when using a replicated library approach to dealing with a portable version of your library.<br />
For the esoterically oriented Lightroom and Aperture handle things a bit differently when and if you shoot RAW+JPG. When you import RAW+JPG into Aperture it looks like you have only one image, the RAW file. Behind the scenes Aperture is managing both of these files as a sort of compound master images. By default you will be looking at and working on a version of the RAW file. To see the JPG version you will have to right click and choose &#8220;new version from master JPG&#8221;. In Lightroom the default is to alegidly use the JPG as some sort of preview but I have not seen any indication that this is happening and personally wouldn&#8217;t because that would probably be really confusing. Once they are imported into Lightroom it will never show you the JPG again but the image is politely labeled RAW+JPG. The other option in Lightroom is to set a global option to import them as two separate images in a stack.</p>
<p>Whew that was a long one but I thought it deserved to be tackled given how much confusion and misinformation is out there on the subject. My vote in terms of overall file management capability has to go to Aperture for overall flexibility and Lightroom for simplicity. Some photographers just like the comfort level of doing things the same way they always have in terms of organizing their files and like that the location of them is brutally apparent. I like the abstraction of image file location until I really want to be involved with it.</p>
<p>As always let me know if you have any questions or comments.</p>
<p>RB</p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2008/10/01/aperture2-vs-lightroom2-file-management/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Aperture 2 vs. Adobe Lightroom 2</title>
		<link>http://photo.rwboyer.com/2008/09/09/aperture-2-vs-adobe-lightroom-2/</link>
		<comments>http://photo.rwboyer.com/2008/09/09/aperture-2-vs-adobe-lightroom-2/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 02:22:08 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Aperture vs Lightroom]]></category>
		<category><![CDATA[Aperture 2]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[DNG]]></category>
		<category><![CDATA[organizational capabilities]]></category>
		<category><![CDATA[strengths and weaknesses]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://eb3fa958-0bdc-4d28-be5b-162c0b80022c</guid>
		<description><![CDATA[The answer to the question â€œwhat is better, Aperture or Lightroom?â€, as always, is&#8230;. It depends. I use both Aperture and Lightroom on a daily basis (as well as Nikon NX2, etc, etc) If I didnâ€™t need to know both of these products extremely well I would probably use Aperture 2 for my own photography [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/wp-content/uploads/FromIweb/aperture_fullscreen.jpg"><img title="aperture_fullscreen.jpg" src="/wp-content/uploads/FromIweb/.thumbs/.aperture_fullscreen.jpg" border="0" alt="aperture_fullscreen.jpg" hspace="10" vspace="10" width="150" height="94" align="left" /></a>The answer to the question â€œwhat is better, Aperture or Lightroom?â€, as always, is&#8230;. It depends. I use both Aperture and Lightroom on a daily basis (as well as Nikon NX2, etc, etc) If I didnâ€™t need to know both of these products extremely well I would probably use Aperture 2 for my own photography (Just letting you know what my bias is). The answer that I always give to my private clients as well as participants in any of my workshops is this &#8211; Once you know what your priorities in a tool are, pick one based on your needs. Both are light years ahead of managing and processing your digital images the way you may have back in the dark ages before either of them existed. Now I know thatâ€™s not at all helpful so here are the strengths of both in a nutshell:<br />
<span id="more-134"></span><br />
Aperture 2 pros:</p>
<ul>
<li> Way better organizational capabilities that are not at all tied to the underlying file/directory structure.</li>
<li> Completely do anything anywhere flexibility, you are not forced into a workflow in any way. If you want to bring up the adjustments HUD and monkey around with the colors while laying out a book, have at it.</li>
<li> In general a less cluttered and more flexible user interface but this may be a matter of taste.</li>
<li> Books &#8211; Aperture books are really, really, flexible, nice, cool, and, did I say wonderful. Not just the ones printed by Apple or just the templates supplied out of the box but the concept in general. If you take the time to figure Aperture books out you can make some really nice stuff really quick and have just about any service print it up. Too bad that there is virtually no documentation on how to really do advanced book things in Aperture. Almost anything is possible but also almost completely undocumented.</li>
<li> Stacks, stack mode, compare mode, full screen mode, stack picks, and album picks&#8230;..Uhhh if you donâ€™t really know Aperture than this means nothing to you so letâ€™s just say once you figure out how stacking, stack picks, etc work you can improve your productivity by about 1000% if you shoot a lot of images and you need to narrow it down to a few. If you shoot tons of images Aperture shines at streamlining your ability to get through them and end up with the best of the best extremely quickly compared to anything else including LR2</li>
<li> Customization. You can customize the user interface in ways that suit how you work, what metadata is displayed where, what keys do what, etc, etc, etc.</li>
<li> Keyword hierarchies once you understand them.</li>
</ul>
<p>Lightroom 2 pros:</p>
<ul>
<li> Local adjustments. No need to bounce your image out to an external editor to do really flexible non-destructive adjustments. Just make sure you have a really powerful machine to keep things speedy. Apertureâ€™s out of the box dodge and burn plug-in is a joke.</li>
<li> Way better standards support for metadata but still not perfect.</li>
<li> Better print module, especially the output specific sharpening and the like.</li>
<li> Adjustment presets.</li>
<li> Windows (yuck) and Mac OS X.</li>
<li> Fabulous DNG support (of course) and especially the camera model presets that emulate the manufacturerâ€™s RAW conversion or roll your own with free tools. See my preview <a href="http://photo.rwboyer.com/adobe-lightroom2-and-dng-camera-profiles/">here</a>.</li>
<li> Out of the box more flexible web delivery but only out of the box (if you have tons of time you can make aperture do some amazing stuff but not for most of us)</li>
<li> Better but not perfect integration with Photoshop CS 3</li>
<li> Keyword synonyms.</li>
<li> There are strong and weak points to the adjustment capabilities of both applications but overall I have to say LR2 nudges out Apertureâ€™s adjustments by a hair.</li>
</ul>
<p>Bottom line &#8211; Both applications are fabulous considering that neither of them existed just a few years ago. You canâ€™t really go way wrong with either choice. I have highlighted what I consider to be the strengths of each application. Trying to quantify which application in superior overall for every photographer is pointless. If you are curious about a head to head detailed comparison on any particular feature that is really important to you and your photography shoot me an <a href="mailto:rwboyer@mac.com">email</a> or leave a comment and I will be happy to let you know what my experience has been.</p>
<p>RB</p>
<p>Update: Do to a lot of requests on some more detail I have started a series of articles with more detailed comparisons. I will continue to update this as time permits.</p>
<p><a href="http://photo.rwboyer.com/2008/10/aperture2-vs-lightroom2-file-management/">Aperture2 vs. Lightroom2 &#8211; File Management</a></p>
<p><a href="http://photo.rwboyer.com/2008/10/aperture2-vs-lightroom2-stacks/">Aperture2 vs. Lightroom2 &#8211; Stacks</a></p>
<p><a href="http://photo.rwboyer.com/2008/10/aperture-2-vs-lightroom-2-adjustment-presets/">Aperture2 vs. Lightroom2 &#8211; Adjustment Presets</a></p>
<p><a href="http://photo.rwboyer.com/2008/11/aperture-2-vs-lightroom-2-keywords/">Aperture2 vs. Lightroom2 &#8211; Keywords</a></p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2008/09/09/aperture-2-vs-adobe-lightroom-2/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Adobe Lightroom2 and DNG camera profiles</title>
		<link>http://photo.rwboyer.com/2008/08/10/adobe-lightroom2-and-dng-camera-profiles/</link>
		<comments>http://photo.rwboyer.com/2008/08/10/adobe-lightroom2-and-dng-camera-profiles/#comments</comments>
		<pubDate>Sun, 10 Aug 2008 19:09:30 +0000</pubDate>
		<dc:creator>RB</dc:creator>
				<category><![CDATA[Adobe Lightroom]]></category>
		<category><![CDATA[Apple Aperture]]></category>
		<category><![CDATA[Articles]]></category>
		<category><![CDATA[Aperture 2]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[DNG]]></category>
		<category><![CDATA[Lightroom 2]]></category>
		<category><![CDATA[Nikon Capture NX2]]></category>
		<category><![CDATA[photoshop lightroom]]></category>

		<guid isPermaLink="false">http://fcc5fb29-76cc-4751-bdbc-03857842a72a</guid>
		<description><![CDATA[Let me start out by stating that I am an Aperture zealot. I jumped on board Aperture from day one and believe that the product&#8217;s introduction was revolutionary. Heck it kicked Adobe in the head and woke the digital media giant into understanding what photographers really need, hence Photoshop Lightroom and now the (if I [...]]]></description>
			<content:encoded><![CDATA[<p><a rel="lightbox" href="/wp-content/uploads/FromIweb/DSC_9396_NX2_PC_vivid.jpg"><img title="DSC_9396_NX2_PC_vivid.jpg" src="/wp-content/uploads/FromIweb/.thumbs/.DSC_9396_NX2_PC_vivid.jpg" border="0" alt="DSC_9396_NX2_PC_vivid.jpg" hspace="10" vspace="10" width="150" height="101" align="left" /></a>Let me start out by stating that I am an Aperture zealot. I jumped on board Aperture from day one and believe that the product&#8217;s introduction was revolutionary. Heck it kicked Adobe in the head and woke the digital media giant into understanding what photographers really need, hence Photoshop Lightroom and now the (if I must say so) excellent Lightroom2. I can forgive Apple for the lame plugin implementation of dodge and burn, I can forgive no multi-adjustment presets, even if they do seem idiotically easy to implement. What I am starting to question is the Aperture development team&#8217;s commitment to a  professional product. Maybe I will rant about that later, for now I just wanted to cover a new development that has been a minor annoyance for myself and other RAW shooters for a long time.<span id="more-136"></span></p>
<p>I will speak only from a Nikon shooter&#8217;s perspective but if you change the names the same kind of thing is true no matter what you happen to shoot. Once upon a time if you wanted your RAW processing to look like the JPGs produced by your camera with various in camera settings you really needed to use Nikon Capture, not a pretty piece of software but getting much better over the years. Still it is backwards and cumbersome compared to Aperture or Lightroom. With Adobe&#8217;s release of Lightroom2 in combination with ACR 4.5 and the beta of DNG camera profiles plus profiling software this is not true anymore.</p>
<p>I just got done downloading and doing a quick compare of Lightroom2 RAW conversions using the new DNG camera profiles versus Nikon Capture NX2 RAW conversions with â€œpicture controlâ€ settings with the same names and could not believe my eyes with respect to how close the conversions are. This is friggin&#8217; great if you happen to like the RAW conversions and in camera produced JPGs that your camera happens to make and want to use them as a starting point. Huge time saver compared to starting with the same old flat RAW conversion that Aperture makes and then tweaking it from there. This tweaking usually takes multiple adjustment blocks and is not quite the same for every single image (probably due to white balance). What&#8217;s more is that Adobe has a free DNG camera profile editor and instructions on how to make your own camera profiles. This is totally great if you like to do that sort of thing or happen to shoot RAW with a camera that happens not to be a Nikon or Canon, you are now not out in the cold anymore. I can imagine that some dedicated non Canon/Nikon shooters out there will produce a bunch of profiles for their companions, if not do it yourself.</p>
<p>You can find the new tools <a href="http://labs.adobe.com/wiki/index.php/DNG_Profiles">here</a> &lt;&#8212;&#8212;. I did a really quick comparison on the Nikon profiles for a D200 verses NX2. Check it out <a href="http://homepage.mac.com/rwboyer/NEF/">here</a> &lt;&#8212;&#8211;. The captions under the images represent the software and profile or Nikon â€œpicture controlâ€ name for the conversion. For beta software I really think that it&#8217;s amazing. If you are a RAW shooter and are still using the clunky camera manufacturer&#8217;s software because of the RAW tone curve and color characteristics you may want to rethink that or at least try it out for yourself. I know what you are thinking &#8211; &#8216;DNG conversions and all are a pain&#8217; but guess what, you don&#8217;t have to do anything, the camera profiles work without converting your native NEF&#8217;s or CR2&#8242;s or whatever, they just work.</p>
<p>There are plenty of things I really love about Aperture compared to other products but the brilliant implementation of local adjustments, keyword synonyms, truly useful output sharpening, and now camera RAW profiles are starting to make the grass look greener and much more saturated over there on the Lightroom2 side of the fence.</p>
<p>RB</p>
]]></content:encoded>
			<wfw:commentRss>http://photo.rwboyer.com/2008/08/10/adobe-lightroom2-and-dng-camera-profiles/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
