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

<channel>
	<title>dual(ité) &#187; lightroom</title>
	<atom:link href="http://diode.tv/blog/tag/lightroom/feed/" rel="self" type="application/rss+xml" />
	<link>http://diode.tv/blog</link>
	<description></description>
	<lastBuildDate>Fri, 03 Sep 2010 15:42:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Re-evaluating LR3 vs Aperture 3</title>
		<link>http://diode.tv/blog/2010/08/13/re-evaluating-lr3-vs-aperture-3/</link>
		<comments>http://diode.tv/blog/2010/08/13/re-evaluating-lr3-vs-aperture-3/#comments</comments>
		<pubDate>Fri, 13 Aug 2010 14:54:31 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[feature]]></category>
		<category><![CDATA[gear]]></category>
		<category><![CDATA[adobe]]></category>
		<category><![CDATA[AP3]]></category>
		<category><![CDATA[aperture]]></category>
		<category><![CDATA[aperture 3]]></category>
		<category><![CDATA[aperture3]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[bugs]]></category>
		<category><![CDATA[comparison]]></category>
		<category><![CDATA[evaluation]]></category>
		<category><![CDATA[lightroom]]></category>
		<category><![CDATA[lightroom 3]]></category>
		<category><![CDATA[LR3]]></category>
		<category><![CDATA[noise reduction]]></category>
		<category><![CDATA[NR]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[problems]]></category>
		<category><![CDATA[RAW]]></category>
		<category><![CDATA[rendering]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[strengths]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[weaknesses]]></category>
		<category><![CDATA[workflow]]></category>

		<guid isPermaLink="false">http://diode.tv/blog/?p=1064</guid>
		<description><![CDATA[I just wrote a lengthy  post on the Aperture forum about my recent tribulations with Aperture. I thought I&#8217;d post it here. I also suggest you read the original thread if you&#8217;re interested. I couldn&#8217;t help but smile a little when I read your post. Great coverage btw. I smiled because I&#8217;ve just spent the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://diode.tv/blog/wp-content/uploads/2010/08/LR3AP3.jpg"><img class="alignnone size-large wp-image-1067" title="LR3AP3" src="http://diode.tv/blog/wp-content/uploads/2010/08/LR3AP3-950x573.jpg" alt="" width="950" height="573" /></a></p>
<p><em>I just wrote a lengthy  post on the Aperture forum about my recent tribulations with Aperture. I thought I&#8217;d post it h</em>ere<em>. I also suggest you read the </em><a href="http://discussions.apple.com/thread.jspa?threadID=2539445&amp;tstart=15" target="_blank"><em>original thread</em></a><em> if you&#8217;re interested.</em></p>
<p>I couldn&#8217;t help but smile a little when I read your <a href="http://discussions.apple.com/thread.jspa?threadID=2539445&amp;tstart=15" target="_blank">post</a>. Great coverage btw.</p>
<p>I smiled because I&#8217;ve just spent the past two weeks playing with the LR3 demo and going pretty much through the exact same odyssey &#8211; as well as coming to the same conclusions. In fact, your post was like a transcript of my own deep personal thoughts ;-)</p>
<p>I decided to thoroughly test LR3 *because* of Aperture. I needed to export a client&#8217;s session and Aperture refused to do it. Period. Kernel panics (!!!), hangs you name it: my edits were essentially trapped within the app with no way of getting them out. Since I didn&#8217;t have time to jerk around I downloaded LR3 and redid the entire session&#8217;s picks. Pretty good way to learn how to use an application fast. To my surprise, it worked. It worked well.</p>
<p>After the ordeal I managed to get Aperture running normally again (won&#8217;t go into details, you probably know the rebuild/preferences drill) but was now confronted with serious doubts about my choice of workflow. For the first time ever I contemplated a move to LR3.</p>
<p>Like you, I hate the UI. I hate the modules. I find the DAM and its entire display and philosophy ridiculous or confusing at best. But yes, the new Details brick is amazing. The Camera Calibration presets are a godsend &#8211; not a dealbreaker mind you, but seriously efficient. And the biggest advantage is still &#8211; to my surprise &#8211; speed. You get used real fast to being able to zoom into an image to check focus, NR or sharpening without having to wait 20 seconds or more. No matter how much processing you do to a photograph, zooming in and out is done in a blink. This was quite destabilizing coming from Aperture&#8217;s glacial image rendering.</p>
<p>So I sat down and began a series of tests. I edited all sorts of picks from my Aperture library to see where I could get with LR3 and compare. I imported the results back in AP3 to do side-by-side comparisons. Some of the results had me considering a workflow using both apps, with Aperture as the DAM and LR3 as a possible editor (sorry DLS!). I had opened Pandora&#8217;s Box.</p>
<p>I figured if I was going to change, might as well try what else was out there. So I downloaded Capture One. Then I downloaded CS5 (still using CS3). Capture One&#8217;s rendering was ok but didn&#8217;t do anything to sway me. CS5 was CS5 &#8211; bloated and messy. Played around with the new Context Aware Fill and realized it was nothing but a very bad Clone Tool (talk about hype). I went back to LR3 and did more testing.</p>
<p>With the +shiny new toy syndrome+ out of the way I began to notice kinks in LR3&#8242;s armour. It had a serious tendency to crash blacks into a weird posterized mess. My initial sense of getting better rendering was shaken by the fact that LR3 seemed inconsistent, with much depending on the type of image. I also realized how much I was missing the ability to add adjustment bricks beyond what was available in the built-in brushes.  To make a (too) long story short: I felt constrained.</p>
<p>Now, after over two weeks of going back and forth I&#8217;ve decided to stick with Aperture. It&#8217;s become obvious to me that LR is meant to be used along with Photoshop for anything beyond basic photo treatments. This makes perfect sense from Adobe&#8217;s business standpoint. I have nothing against Photoshop and use it all the time, but I like being able to stay within my main app.</p>
<p>Does LR3 sometimes do a better job? Yes. Same goes for Aperture. Does LR3&#8242;s built-in NR/sharpen and Lens Correction trump Aperture? Hell yes and I wish Apple would take notice. I&#8217;m using DFine, Sharpener Pro and PTLEns but would very much welcome not having to render TIFFs for those functions, to say nothing of the ability to go back and tweak.</p>
<p>But for my use Aperture is a better tool. And the good thing about all this is that in trying to replicate certain LR3 functions, I&#8217;ve found new ways of working with AP3 and have also revisited areas of my workflow.</p>
<p>The big caveat is still there though: Aperture 3 *needs to work*. Yesterday, after several days without any problems Aperture started crashing when applying a brushed curve to a certain picture. Just like that out of the blue. I had to repair the database &#8211; again. I lost time &#8211; again. It&#8217;s like this application has psychotic episodes. It&#8217;s just not acceptable. I send so many crash reports it&#8217;s not even funny. It&#8217;s also completely random which is even more infuriating.</p>
<p>So I&#8217;m like you. I&#8217;m back but with the knowledge that LR3 CAN work if Aperture fails on me. It&#8217;s not elegant, it&#8217;s cumbersome but it works.</p>
<p>Apple, you need to make Aperture 3 work. Every day.</p>
]]></content:encoded>
			<wfw:commentRss>http://diode.tv/blog/2010/08/13/re-evaluating-lr3-vs-aperture-3/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>the case of aperture and the stratocaster</title>
		<link>http://diode.tv/blog/2010/01/08/the-case-of-aperture-and-the-stratocaster/</link>
		<comments>http://diode.tv/blog/2010/01/08/the-case-of-aperture-and-the-stratocaster/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 17:22:37 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[aperture]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[gear]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[creativity]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[essay]]></category>
		<category><![CDATA[lightroom]]></category>
		<category><![CDATA[reflections]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://diode.tv/blog/?p=722</guid>
		<description><![CDATA[For the past year &#8211; and more so these past months &#8211; the debate has been raging around Aperture and Lightroom, mainly from AP2 users who feel abandoned by Apple. The silence surrounding a new version of the application has been deafening, forcing a lot of users into the arms of Adobe for many reasons [...]]]></description>
			<content:encoded><![CDATA[
<a href="http://diode.tv/blog/wp-content/gallery/news/strat.jpg" title="" class="shutterset_singlepic78" >
	<img class="ngg-singlepic" src="http://diode.tv/blog/wp-content/gallery/cache/78__480x360_strat.jpg" alt="strat" title="strat" />
</a>

<p>For the past year &#8211; and more so these past months &#8211; the debate has been raging around Aperture and Lightroom, mainly from AP2 users who feel <a href="http://theappleblog.com/2010/01/06/a-plea-for-a-significant-aperture-update/" target="_blank">abandoned by Apple</a>. The silence surrounding a new version of the application has been deafening, forcing a lot of users into the arms of Adobe for many reasons that have been discussed to death at this point. If you read this blog you know I&#8217;ll be sticking it out unless physically booted out of the Aperture camp.</p>
<p>There are a lot of technical reasons for my decision. I&#8217;ve mentioned them in other posts. But one thing that never seems to enter the debate is something less tangible: the fact that software can be an instrument in its own right.</p>
<h2>flugelhorn?</h2>
<p>I&#8217;m not talking about software as a tool mind you, but as an instrument. Like a violin, a piano or a… flugelhorn?<br />
You see, through all my experimentation with various incarnations of Lightroom one thing has always been quite clear: I get very different results than I do with Aperture. Some of it has to do with my varying comfort level between the two apps. And some of it is purely technical, differences between RAW converters and such. But I&#8217;ve also come to believe that software &#8211; creative software &#8211; has a footprint and flow that affect the output. Software has tone.<br />
I&#8217;m a <a href="http://itunes.apple.com/ca/album/black-glitter-diaries/id277014647" target="_blank">musician</a>. My guitar is a Fender Stratocaster. Everything about this instrument impacts what I do with it: the neck, the spacing betweens frets, how the body feels in my hands. All these design choices mould the way I use the guitar. In fact, over the years they&#8217;ve moulded the way I play guitar. I&#8217;m now convinced Aperture shapes my photography in pretty much the same way.<br />
In the great debate between Lightroom and Aperture we seem to forget that they each have a very specific signature. The philosophical differences in design, the choice of available effects and the way they&#8217;re applied all contribute to shaping pictures in a very distinct way. In my mind they&#8217;re not instantly interchangeable, as many seem to imply. This, I think, is why I&#8217;m having such a hard time contemplating a switch. I&#8217;m not so sure I want to change oils for water-colour, Strat for SG.</p>
<h2>the homogenous pool</h2>
<p>Why do we feel this need for one app to rule them all? If everyone uses a brush, isn&#8217;t there a case to be made for using a palette knife? Ok, it&#8217;s not as clear cut as that. These applications can obviously be twisted and turned in ways that can make them much closer to each other in the end. Plugins are certainly an equalizer. Same goes for round-tripping to external editors.</p>
<p>But right now I can&#8217;t help looking at my choice of Aperture as a plus, something that puts me in a particular mindset that&#8217;s philosophically different from a Lightroom user. I see my photography in another context, I use other tools that work in other ways, I interface with my work through another window. Interface as zeitgeist so to speak. I&#8217;m not trying to delude myself into being some sort of rebel soldier either &#8211; I&#8217;m simply contemplating my choice beyond keywords, metadata and organization.</p>
<h2>full of what?</h2>
<p>I know, maybe I&#8217;m full of it. Just rationalizing my decision to stick with Aperture. But perhaps I&#8217;m on to something. Perhaps software design has become a much more intricate part of our creative process than we give it credit for. Perhaps it impacts our vision and field of view as well.</p>
<p>And perhaps I can wait a little longer.</p>
]]></content:encoded>
			<wfw:commentRss>http://diode.tv/blog/2010/01/08/the-case-of-aperture-and-the-stratocaster/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>LR3 beta &#8211; a followup</title>
		<link>http://diode.tv/blog/2009/10/22/lr3-beta-a-followup/</link>
		<comments>http://diode.tv/blog/2009/10/22/lr3-beta-a-followup/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 14:47:32 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[aperture]]></category>
		<category><![CDATA[gear]]></category>
		<category><![CDATA[adobe]]></category>
		<category><![CDATA[aperture 3]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[lightroom]]></category>
		<category><![CDATA[opinion]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://diode.tv/blog/?p=616</guid>
		<description><![CDATA[Alright. I know it&#8217;s quick but I&#8217;ve just spent the past hour playing with the new LR3 beta and while all the core advantages from LR2 remain, it&#8217;s still no fun to work with. The interface is just as messy as before and most of the improvements &#8211; at least as far as I can [...]]]></description>
			<content:encoded><![CDATA[<p>Alright. I know it&#8217;s quick but I&#8217;ve just spent the past hour playing with the new LR3 beta and while all the core advantages from LR2 remain, it&#8217;s still no fun to work with. The interface is just as messy as before and most of the improvements &#8211; at least as far as I can tell right now &#8211; would warrant a big point update, not sure about a whole new version. I&#8217;m guessing there&#8217;s a bit of marketing going on (which is certainly fair game, don&#8217;t get me wrong).</p>
<p>What I DO like is the fact that they&#8217;re being totally open about the process, allowing photographers to use the new tools and decide what works for them. This makes making business decisions a lot easier than the limbo Apple currently forces us to live in.</p>
<p>Things I really like:</p>
<ul>
<li>The noise reduction and basic RAW rendering looks a lot better &#8211; way better than Aperture 2, which is a big deal.</li>
<li>Local edit tools seem more fluid &#8211; and the fact that they exist at all shames Aperture 2.</li>
<li>History, history, history.</li>
</ul>
<p>Not to beat a dead horse but I still don&#8217;t see myself switching to this app unless Apple drops the ball on AP3 or leaves us in the dark for another six months. Or three.</p>
<p>Oh! just give us something already will you?</p>
]]></content:encoded>
			<wfw:commentRss>http://diode.tv/blog/2009/10/22/lr3-beta-a-followup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LR3 beta 1</title>
		<link>http://diode.tv/blog/2009/10/22/lr3-beta-1/</link>
		<comments>http://diode.tv/blog/2009/10/22/lr3-beta-1/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 13:15:12 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[photography]]></category>
		<category><![CDATA[adobe]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[gear]]></category>
		<category><![CDATA[lightroom]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://diode.tv/blog/?p=611</guid>
		<description><![CDATA[Chris alerted me to it this morning in the comments: is this sad or what? Only bright side I can think of is the kick in the pants this is going to give Apple &#8211; if they care anything about our community and business. Some of the highlights of the new version according to Adobe [...]]]></description>
			<content:encoded><![CDATA[<p>Chris alerted me to it this morning in the comments: is this sad or what?<br />
Only bright side I can think of is the kick in the pants this is going to give Apple &#8211; if they care anything about our community and business.</p>
<p>Some of the highlights of the new version according to Adobe Labs:</p>
<ul style="list-style-type: disc; list-style-position: outside; list-style-image: initial; margin-left: 0.5em; padding-left: 1.5em; margin-top: 1em; margin-bottom: 1.35em;" type="disc">
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>Brand new performance architecture</strong>, building for the future of growing image libraries</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>State-of-the-art noise reduction</strong> to help you perfect your high ISO shots</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>Watermarking tool</strong> that helps you customize and protect your images with ease</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>Portable sharable slideshows with audio</strong>—designed to give you more flexibility and impact on how you choose to share your images, you can now save and export your slideshows as videos and include audio</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>Flexible customizable print package creation</strong> so your print package layouts are all your own</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>Film grain simulation</strong><strong> tool</strong> for enhancing your images to look as gritty as you want</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>New import handling</strong> designed to make importing streamlined and easy</li>
<li style="font-size: 1em; line-height: 1.35em; padding-bottom: 0.5em;"><strong>More flexible online publishing options</strong> so you can post your images online to certain online photo sharing sites directly from inside Lightroom 3 beta (may require third-party plug-ins)*</li>
</ul>
<p>Nothing earth-shattering but bread and butter features obviously geared to working photographers. I&#8217;ve downloaded the beta and will report back when I get a chance.</p>
<p>Btw, Adobe is again allowing this beta to be <a href="http://labs.adobe.com/technologies/lightroom3/" target="_blank">downloaded freely</a> by anyone and it doesn&#8217;t expire until April 2010. I&#8217;m guessing this strategy is paying off <strong>big time</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://diode.tv/blog/2009/10/22/lr3-beta-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Aperture 3 &#8211; Wishes. Expectations. Anticipation.</title>
		<link>http://diode.tv/blog/2009/08/10/aperture-3-wishes-and-expectations/</link>
		<comments>http://diode.tv/blog/2009/08/10/aperture-3-wishes-and-expectations/#comments</comments>
		<pubDate>Mon, 10 Aug 2009 19:01:49 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[aperture]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[gear]]></category>
		<category><![CDATA[adobe]]></category>
		<category><![CDATA[aperture 3]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[lightroom]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://diode.tv/blog/?p=490</guid>
		<description><![CDATA[Quick Recap When Apple unveiled Aperture in 2005, the photography landscape was in dire need of consolidation: the digital workflow was a hodge podge of various solutions combining RAW converters, editing software and asset management applications. Working with RAW files was unwieldy, involving conversions and file multiplication if you needed different versions of the same [...]]]></description>
			<content:encoded><![CDATA[
<a href="http://diode.tv/blog/wp-content/gallery/news/apgrab.jpg" title="" class="shutterset_singlepic26" >
	<img class="ngg-singlepic" src="http://diode.tv/blog/wp-content/gallery/cache/26_web20_480x360_apgrab.jpg" alt="apgrab" title="apgrab" />
</a>

<p><strong>Quick Recap<br />
<span style="font-weight: normal;">When Apple unveiled Aperture in 2005, the photography landscape was in dire need of consolidation: the digital workflow was a hodge podge of various solutions combining RAW converters, editing software and asset management applications. Working with RAW files was unwieldy, involving conversions and file multiplication if you needed different versions of the same picture. In a word, it was a mess. So it&#8217;s no surprise Aperture was greeted with a pretty high degree of excitement from the community. Unfortunately, version 1.0 suffered from several architectural problems which, combined with performance issues, marred an otherwise brilliant idea. As is often the case, execution proved difficult. </span></strong></p>
<p>But Apple listened and quickly updated the app with several free updates that not only squashed bugs, but also added major features &#8211; a sign that they were serious about the photography market. In less than a year Aperture went from 1.0 to the greatly enhanced 1.5, a version that felt more like a new version than a point upgrade. They also lowered the price and offered a rebate to early adopters.</p>
<p>Soon after the 1.5 release, Adobe offered a mac-only free beta of Lightroom seen by many as a reaction to Aperture. Clearly, the race was on.</p>
<p>The free beta release by Adobe was an odd move that showed a certain nervousness on their part. In fact, the free beta felt more like an alpha when first released. But Adobe&#8217;s public offering and transparency throughout the process paid off: it kept their competitor to Aperture in the public eye, staving off the perception that they were losing their crown to Apple. It also allowed them to gain a pool of users willing to wait out the beta period in exchange for free software. With beta 3 they added support for Windows, something Apple was obviously not interested in matching. And while LR lacked the spit and polish of Aperture, it clearly had the upper hand in performance and system requirements. When Lightroom 1.0 was finally released &#8211; at the same price point as Aperture &#8211; their application was already in the hands of many Adobe faithful as well as PC users who were ready for the only equivalent solution available on their platform.</p>
<p>Today both Aperture and Lightroom sit at version 2. And while the relative merits of both applications can spark endless debates, LR has clearly emerged as the juggernaut in terms of adoption. Adobe has introduced features like camera presets and non-destructive localized editing that trounce Aperture&#8217;s offering. The ball is now in Apple&#8217;s camp.</p>
<p><strong>A Love Affair</strong><br />
I have a love affair with Aperture. In fact I consider it to be a deciding factor in my decision to become a full-time photographer. I remember sitting at my computer with the Aperture demo, my pictures spread out across both screens and realizing: <em>man, that&#8217;s all I want to be doing</em>. So it comes as no surprise that I&#8217;m routing for Aperture to not only survive but thrive, evolve and prosper. I&#8217;ve tried LR2. It has amazing features. But I can&#8217;t stand it. And it&#8217;s not because of some deep-routed fear of change or some sort of apprehension when faced with new software &#8211; I&#8217;ve been using Photoshop for like fifteen years and have no problem whatsoever with learning applications. It just feels cramped. As if my photos are stuck in a box. Aperture makes my work look like a gallery display and for all the superficiality of that argument, it matters to me in the end. It affects both the way I perceive what I do and the enjoyment I get out of doing the work. I&#8217;m also much more at ease with its free mode workflow that allows me to jump in and out of different tasks within the same environment.</p>
<p>But Aperture 3 has to seriously rock.</p>
<p><strong>What now?<br />
</strong>I&#8217;ve stated many times how I believe Aperture 3 will be dependent on Snow Leopard&#8217;s radical new technologies. While many only see the upcoming OS as a mere refinement to Leopard, I see it as a sea change and a foundation for the next jump ahead in OS X software. I think Aperture 3 should be a flagship application. No, scrap that: I think it NEEDS to be a flagship application. I&#8217;m also pretty sure Apple knows this. They read the same data we do. They know how much LR is getting entrenched.</p>
<p>So what do I want in AP3? Here goes:</p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<ol>
<li><span style="font-weight: normal;"><strong>Non-destructive localized editing</strong><strong>: <span style="font-weight: normal;">I&#8217;ve invested a lot in Aperture. I use several plug-in packages (Nik and OnOne suites) that I believe add a lot to its basic possibilities. I have no problem relying on third-parties for these types of features any more than I have a problem using them in Photoshop &#8211; I don&#8217;t expect Aperture to give me every feature under the sun. But there is clearly a need for <em>non-destructive</em> localized editing. Please. I don&#8217;t want to create a TIFF file everytime I need to dodge and burn. This is basic, essential stuff.</span></strong></span></li>
<li><span style="font-weight: normal;"><strong>RAW presets</strong><strong>:</strong> Adobe has presets that closely emulate in-camera settings. This is essential. There&#8217;s nothing I hate more than seeing my photo thumbnails go from a great looking starting point to a ho-hum version as soon as I switch the Preview button off. Of course this will vary depending on the camera you use, but <a href="http://photo.rwboyer.com/2009/05/nikon-aperture-and-war-against-bit-twiddling/">Nikon decoding is pretty off the mark</a>, especially with blues. I know these settings are proprietary but if Adobe can get that close, Apple should get much closer as well.</span></li>
<li><span style="font-weight: normal;"><strong>Squash the bugs:</strong> There are a lot of annoying bugs throughout Aperture. If for instance I add pictures to an album with a custom sort, Aperture sometimes displays multiple duplicates of certain pics. The only remedy is to then sort the album by date &#8211; thereby losing the original sort order. It&#8217;s not a huge deal but before I found the solution I spent a pretty uncomfortable selection session with a client, trying to pretend nothing was wrong while pictures were multiplying before our eyes &#8211; not fun. This is one of many &#8211; failed exports, crashing and weird book creation tools are other great time wasters&#8230;</span></li>
<li><span style="font-weight: normal;"><strong>Speeeeed</strong>: This is obvious and yes, depends on the hardware in use. But the fact is Aperture gets slower as its database grows bigger. It&#8217;s much better in V2 but it&#8217;s still a problem. I have a library of a few gigabytes dedicated to a single client that launches in seconds and where anything I do just flies. Not so with my main library. Switching to referenced files helps (with a fast FW800 hard drive) but there&#8217;s clearly optimizing possible. I&#8217;m hoping SL helps in this regard.</span></li>
<li><span style="font-weight: normal;"><strong>Keyword hierarchies</strong>: I do stock photography and while the main agency I work with now does the keywording for me, I would still love being able to add multiple related keywords in one fell swoop. Anyone shooting stock needs this. Anyone looking for a quicker way to organize pictures needs this as well.</span></li>
<li><span style="font-weight: normal;"><strong>Sharpening on export</strong>: I get to sharpen in the print dialog, taking into account the size of the final print (as it should be). Why the hell can&#8217;t I get the same thing in the export dialog? Web exports need sharpening in relation to file size.</span></li>
<li><span style="font-weight: normal;"><strong>Consistent print dialog</strong>: Why does book printing use a different print dialog? The book tool is quirky but pretty useful for times when you need to do basic layouts, add text etc&#8230; But try to print and you get yet ANOTHER print dialog: no sharpening <span style="text-decoration: line-through;">and no colorsync management &#8211; which means bad color</span>. Huh?</span></li>
<li><span style="font-weight: normal;"><strong>Image presets</strong>: I use all the workarounds with Lift and Stamp but I&#8217;d really like to be able to save an entire adjustments setup &#8211; with custom preset categories if possible.</span></li>
</ol>
<p>Those are my basic wishes. Nothing earth shattering or even remotely original but getting these would make my work so much easier. Now of course there&#8217;s the dream wish: non-destructivre workflow and versioning when using plug-ins, the nirvana and holy grail of wishes&#8230;</p>
<p>Which features on that list am I expecting? <strong>1</strong> and <strong>2</strong>. In fact, in spite of my undying love for this app  I don&#8217;t think Aperture could survive another cycle without some implementation of those two features. And no, Faces wouldn&#8217;t make up for it.</p>
<p>What do you think?</p>
]]></content:encoded>
			<wfw:commentRss>http://diode.tv/blog/2009/08/10/aperture-3-wishes-and-expectations/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
	</channel>
</rss>
