<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments for The Aperture Blog</title>
	<atom:link href="http://theapertureblog.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://theapertureblog.com</link>
	<description>Tips, Tricks, Tutorials and Presets for Aperture</description>
	<lastBuildDate>Sun, 19 Feb 2012 20:00:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Aperture 4? by Doug</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21689</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Sun, 19 Feb 2012 20:00:10 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21689</guid>
		<description>I will use App or LR, whichever comes up with a reliable solution to share images and data across a LAN for a small office.</description>
		<content:encoded><![CDATA[<p>I will use App or LR, whichever comes up with a reliable solution to share images and data across a LAN for a small office.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by ian</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21554</link>
		<dc:creator>ian</dc:creator>
		<pubDate>Thu, 16 Feb 2012 15:01:02 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21554</guid>
		<description>sorry one more thing that I am currently doing as I was writing this...

 When the client comes back with file #&#039;s as selects, I search the project for the # and then increase that files rating for final output. 

In Aperture you search the number, the one fie is presented then you have to select it to increase rating

In Lightroom you don&#039;t have to select it. you just hit your ratings.

a quibble I know but when you&#039;re doing 50 or so in a row, that extra mouse move really slows you down.</description>
		<content:encoded><![CDATA[<p>sorry one more thing that I am currently doing as I was writing this&#8230;</p>
<p> When the client comes back with file #&#8217;s as selects, I search the project for the # and then increase that files rating for final output. </p>
<p>In Aperture you search the number, the one fie is presented then you have to select it to increase rating</p>
<p>In Lightroom you don&#8217;t have to select it. you just hit your ratings.</p>
<p>a quibble I know but when you&#8217;re doing 50 or so in a row, that extra mouse move really slows you down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by ian</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21553</link>
		<dc:creator>ian</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21553</guid>
		<description>I&#039;d agree with everything said here. Just trying the LR ver 4 beta. As much as I loathe the UI of lightroom, better and faster quality output trumps any advantages in UI.

Oh and Mark Re outputs, you simply need to make various presets for the diff size, etc you need. Yes it&#039;s a different way of thinking than the big assed dialog presnted to you every export in LR, but hey that&#039;s the way Apple wants to do things, create presets.</description>
		<content:encoded><![CDATA[<p>I&#8217;d agree with everything said here. Just trying the LR ver 4 beta. As much as I loathe the UI of lightroom, better and faster quality output trumps any advantages in UI.</p>
<p>Oh and Mark Re outputs, you simply need to make various presets for the diff size, etc you need. Yes it&#8217;s a different way of thinking than the big assed dialog presnted to you every export in LR, but hey that&#8217;s the way Apple wants to do things, create presets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Viren Mohan</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21547</link>
		<dc:creator>Viren Mohan</dc:creator>
		<pubDate>Thu, 16 Feb 2012 11:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21547</guid>
		<description>I&#039;d love to see:

1. Metadata tags like in Photo Mechanic. For example, I could set my headline to equal {filename}{YYMMDD-HHMMSS}, or output filename to equal {filename}(color profile}. Many other applications, Photo Mechanic has nailed it down pat. LR is halfway there too.

2. Easier file/folder sync for referenced files. Helps clean up junk tiffs generated during stitching application.

3. Adjustment panel solo mode, like in Lightroom. Saves a ton of mouse clicks.

4. Keywording, renaming and metadata exactly like in LR. Having to batch operate files everytime is a bit tedious.

5. Copy and paste masks between adjustment bricks.

6. Fully with you on the vignette thingy, it is too basic.

7. Keystoning a la DXO Optics.

8. Color profiling ala DXO Optics - beats the pants off LR, IMHO. Film, and other digi manufacturers looks are easy to replicate.

9. LAB curves please, instead of just a luminance curve. Works magic for color separation, like in Iridient&#039;s raw developer.</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to see:</p>
<p>1. Metadata tags like in Photo Mechanic. For example, I could set my headline to equal {filename}{YYMMDD-HHMMSS}, or output filename to equal {filename}(color profile}. Many other applications, Photo Mechanic has nailed it down pat. LR is halfway there too.</p>
<p>2. Easier file/folder sync for referenced files. Helps clean up junk tiffs generated during stitching application.</p>
<p>3. Adjustment panel solo mode, like in Lightroom. Saves a ton of mouse clicks.</p>
<p>4. Keywording, renaming and metadata exactly like in LR. Having to batch operate files everytime is a bit tedious.</p>
<p>5. Copy and paste masks between adjustment bricks.</p>
<p>6. Fully with you on the vignette thingy, it is too basic.</p>
<p>7. Keystoning a la DXO Optics.</p>
<p>8. Color profiling ala DXO Optics &#8211; beats the pants off LR, IMHO. Film, and other digi manufacturers looks are easy to replicate.</p>
<p>9. LAB curves please, instead of just a luminance curve. Works magic for color separation, like in Iridient&#8217;s raw developer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Bill Montgomery</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21523</link>
		<dc:creator>Bill Montgomery</dc:creator>
		<pubDate>Wed, 15 Feb 2012 16:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21523</guid>
		<description>In addition to the features you&#039;ve described, I&#039;d like to see:
• Much improved pen pressure responsiveness for all brush-in adjustments
• A gradient tool
• A transform/distort tool that would allow me to slightly compress the width of a photo</description>
		<content:encoded><![CDATA[<p>In addition to the features you&#8217;ve described, I&#8217;d like to see:<br />
• Much improved pen pressure responsiveness for all brush-in adjustments<br />
• A gradient tool<br />
• A transform/distort tool that would allow me to slightly compress the width of a photo</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Noah Bershatsky</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21508</link>
		<dc:creator>Noah Bershatsky</dc:creator>
		<pubDate>Wed, 15 Feb 2012 01:57:40 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21508</guid>
		<description>Booooooo Hissssssss</description>
		<content:encoded><![CDATA[<p>Booooooo Hissssssss</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by alessandro amato</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21497</link>
		<dc:creator>alessandro amato</dc:creator>
		<pubDate>Tue, 14 Feb 2012 17:23:11 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21497</guid>
		<description>I wonder why nobody here has listed Aperture&#039;s slowness during editing as something to fix in the next release. Maybe you&#039;ve all got a new/fast mac (macbook pro or imac with the new intel chips and 8-16 Gb ram) ?

My main machine is a 2.66 ghz mac mini with 4gb ram and a solid state drive. It was fast and perfectly usable with Lightroom, but since I switched to Aperture it has become unacceptably slow even when doing very elementary processing (e.g. loupe view: takes literally seconds to load the 100% image, white balance, curve/levels).

I know, in the future I will get hold of a faster computer (when is the next generation of macminis arriving ?) but for now I have made the comparison between similar processes in lightroom and aperture and the first wins.</description>
		<content:encoded><![CDATA[<p>I wonder why nobody here has listed Aperture&#8217;s slowness during editing as something to fix in the next release. Maybe you&#8217;ve all got a new/fast mac (macbook pro or imac with the new intel chips and 8-16 Gb ram) ?</p>
<p>My main machine is a 2.66 ghz mac mini with 4gb ram and a solid state drive. It was fast and perfectly usable with Lightroom, but since I switched to Aperture it has become unacceptably slow even when doing very elementary processing (e.g. loupe view: takes literally seconds to load the 100% image, white balance, curve/levels).</p>
<p>I know, in the future I will get hold of a faster computer (when is the next generation of macminis arriving ?) but for now I have made the comparison between similar processes in lightroom and aperture and the first wins.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Thomas Fitzgerald</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21495</link>
		<dc:creator>Thomas Fitzgerald</dc:creator>
		<pubDate>Tue, 14 Feb 2012 15:46:46 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21495</guid>
		<description>I know. .... They have usually released stuff by now though (usually at lunch time GMT) but we can still hope :-)</description>
		<content:encoded><![CDATA[<p>I know. &#8230;. They have usually released stuff by now though (usually at lunch time GMT) but we can still hope <img src='http://theapertureblog.com/backend/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by rockaw</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21494</link>
		<dc:creator>rockaw</dc:creator>
		<pubDate>Tue, 14 Feb 2012 15:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21494</guid>
		<description>Aperture 2 released on 2nd tuesday in Feb. &#039;08
Aperture 3 released on 2nd tuesday in Feb. &#039;10

Today is the 2nd tuesday in Feb. &#039;12...</description>
		<content:encoded><![CDATA[<p>Aperture 2 released on 2nd tuesday in Feb. &#8217;08<br />
Aperture 3 released on 2nd tuesday in Feb. &#8217;10</p>
<p>Today is the 2nd tuesday in Feb. &#8217;12&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Ryfe</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21455</link>
		<dc:creator>Ryfe</dc:creator>
		<pubDate>Mon, 13 Feb 2012 15:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21455</guid>
		<description>Hello,
I agree with all you suggested! 
I would add 2 very important things to my point of view : 
Better use of geolocalisation. For the moment, the way A3 handles it is pretty poor + it&#039;s a pain to right the GPS info in the exifs
Better way of adding labels (for me, Photoshop Elements is just soooo much better and simple and user friendly
The way A3 handles time modification is too basic too (here again Photoshop Elements, witch is made for begginners is more powerful), particularly whan you have to synch various cameras on a journey with many time difference

Was my two cents</description>
		<content:encoded><![CDATA[<p>Hello,<br />
I agree with all you suggested!<br />
I would add 2 very important things to my point of view :<br />
Better use of geolocalisation. For the moment, the way A3 handles it is pretty poor + it&#8217;s a pain to right the GPS info in the exifs<br />
Better way of adding labels (for me, Photoshop Elements is just soooo much better and simple and user friendly<br />
The way A3 handles time modification is too basic too (here again Photoshop Elements, witch is made for begginners is more powerful), particularly whan you have to synch various cameras on a journey with many time difference</p>
<p>Was my two cents</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Henrique</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21308</link>
		<dc:creator>Henrique</dc:creator>
		<pubDate>Thu, 09 Feb 2012 02:32:48 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21308</guid>
		<description>They have the fix RAM usage. After Lion, Aperture 3, which used to run smooth, suddenly started taking forever (and finally crashing my Mac) when applying adjustments and retouches. I had to change Aperture to run in 32-bit to address that.</description>
		<content:encoded><![CDATA[<p>They have the fix RAM usage. After Lion, Aperture 3, which used to run smooth, suddenly started taking forever (and finally crashing my Mac) when applying adjustments and retouches. I had to change Aperture to run in 32-bit to address that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Video: Image Editing With Plug-ins in Aperture by Diego</title>
		<link>http://theapertureblog.com/2012/01/27/video-image-editing-with-plug-ins-in-aperture/comment-page-1/#comment-21307</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Thu, 09 Feb 2012 02:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1111#comment-21307</guid>
		<description>Thanks for the demo! It was quick and short and straight to the point! I have one question though: doesn&#039;t editing a picture with plugins end up generating a new Tiff file? Does that mean you end up with some 2 or 3 versions of each file? Wouldn&#039;t that end up taking a lot of disk space... I have just started using Aperture and my biggest pet peeve is that it does not do lens correctly directly on the RAW files.</description>
		<content:encoded><![CDATA[<p>Thanks for the demo! It was quick and short and straight to the point! I have one question though: doesn&#8217;t editing a picture with plugins end up generating a new Tiff file? Does that mean you end up with some 2 or 3 versions of each file? Wouldn&#8217;t that end up taking a lot of disk space&#8230; I have just started using Aperture and my biggest pet peeve is that it does not do lens correctly directly on the RAW files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Ralf</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21294</link>
		<dc:creator>Ralf</dc:creator>
		<pubDate>Wed, 08 Feb 2012 19:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21294</guid>
		<description>Additionally to the mentioned features, I&#039;d like to have improvals in keyword management. In detail:
-Keyword hierarchies with toggling inclusion or exclusion, nicknames and multilang support would be nice. (Example: Federal District with nickname Mexico City and multilang tags as Bundesbezirk, Distrito Federal etc., assigned to Mexico, which is assigned to North America).
-I&#039;d like to be able to assign keywords to different hierarchies. (Example: Dresden --&gt; Free State of Saxony --&gt; Federal Republic of Germany and Dresden --&gt; District of Dresden --&gt; German Democratic Republic)

For &quot;Places&quot;, I&#039;d like to be able to create own locations as polygons, not only circles. I&#039;d like to correct wrongly defined admin unit hierarchies and names.
For &quot;Faces&quot;, I propose an easier way to manage unnamed faces. It&#039;ll be nice to be able to mass-name faces selecting those and have drag-and-drop and/or naming facilities.</description>
		<content:encoded><![CDATA[<p>Additionally to the mentioned features, I&#8217;d like to have improvals in keyword management. In detail:<br />
-Keyword hierarchies with toggling inclusion or exclusion, nicknames and multilang support would be nice. (Example: Federal District with nickname Mexico City and multilang tags as Bundesbezirk, Distrito Federal etc., assigned to Mexico, which is assigned to North America).<br />
-I&#8217;d like to be able to assign keywords to different hierarchies. (Example: Dresden &#8211;&gt; Free State of Saxony &#8211;&gt; Federal Republic of Germany and Dresden &#8211;&gt; District of Dresden &#8211;&gt; German Democratic Republic)</p>
<p>For &#8220;Places&#8221;, I&#8217;d like to be able to create own locations as polygons, not only circles. I&#8217;d like to correct wrongly defined admin unit hierarchies and names.<br />
For &#8220;Faces&#8221;, I propose an easier way to manage unnamed faces. It&#8217;ll be nice to be able to mass-name faces selecting those and have drag-and-drop and/or naming facilities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Some Tips for Using a Film Scanner (or any Scanner) with Aperture by ianc</title>
		<link>http://theapertureblog.com/2012/01/04/some-tips-for-using-a-film-scanner-or-any-scanner-with-aperture/comment-page-1/#comment-21264</link>
		<dc:creator>ianc</dc:creator>
		<pubDate>Tue, 07 Feb 2012 15:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1091#comment-21264</guid>
		<description>Thanks for this. I found photographing my negatives with 3 bracket exposure using a macro lens gives me better results and tonal range than scanning them.</description>
		<content:encoded><![CDATA[<p>Thanks for this. I found photographing my negatives with 3 bracket exposure using a macro lens gives me better results and tonal range than scanning them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Mark</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21257</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 07 Feb 2012 13:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21257</guid>
		<description>It sounds to me like you should switch to Lightroom!

RAW conversion is the most important thing the program does.  If I though the conversions from ACR were better, I would be using Lightroom or Photoshop.

Better noise reduction would be great, but I would like something along the lines of Nik Dfine where I can apply different amounts of reduction to specific color ranges.  Being able to crank my NR sliders so far up that they turn the picture into mush doesn&#039;t really interest me.

The one thing I like from LR that I would love in Aperture are the extensive export options.  Aperture is really lacking here.  I export full size JPG, but for anything that needs to be resized, I export to TIFF, then resize and sharpen in Photoshop.

I would like the ability to copy the brush in/out strokes from one adjustment brick to another.  If I spend 10 minutes brushing in a precise mask for curves, I would like to be able to apply that same mask (or inverse) to levels, highlights &amp; shadows, etc.</description>
		<content:encoded><![CDATA[<p>It sounds to me like you should switch to Lightroom!</p>
<p>RAW conversion is the most important thing the program does.  If I though the conversions from ACR were better, I would be using Lightroom or Photoshop.</p>
<p>Better noise reduction would be great, but I would like something along the lines of Nik Dfine where I can apply different amounts of reduction to specific color ranges.  Being able to crank my NR sliders so far up that they turn the picture into mush doesn&#8217;t really interest me.</p>
<p>The one thing I like from LR that I would love in Aperture are the extensive export options.  Aperture is really lacking here.  I export full size JPG, but for anything that needs to be resized, I export to TIFF, then resize and sharpen in Photoshop.</p>
<p>I would like the ability to copy the brush in/out strokes from one adjustment brick to another.  If I spend 10 minutes brushing in a precise mask for curves, I would like to be able to apply that same mask (or inverse) to levels, highlights &amp; shadows, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Lars Broberg</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21256</link>
		<dc:creator>Lars Broberg</dc:creator>
		<pubDate>Tue, 07 Feb 2012 10:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21256</guid>
		<description>I would be happy if my camera was supported. Apple needs to step up with the RAW-support.  Seems I have to learn Lightroom or Capture one instead.</description>
		<content:encoded><![CDATA[<p>I would be happy if my camera was supported. Apple needs to step up with the RAW-support.  Seems I have to learn Lightroom or Capture one instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Michael</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21254</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 07 Feb 2012 09:08:57 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21254</guid>
		<description>For me the biggest thing on my list is for Apple to fix the bug with IPTC meta data. If I tag any picture with foreign or accented characters (such as ö, ä, and å) and then export and upload 
those pictures to my agency&#039;s picture bank all the foreign and accented characters become scrambled. 

It&#039;s something I&#039;ve reported on support forums and via feedback forms for over a year now. I&#039;m currently using an awful work around where I edit pictures in Aperture, export to Photo Mechanic, tag them and upload them. Not really ideal for half time at a sports event. 

So for me that is a big one, and a likely deal breaker if it&#039;s not addressed. 

Then in regards to my workflow a built in FTP would be amazing. If I got that along with them fixing the IPTC bugs I would immediately shave 15 minutes from my regular workflow. 

On top of those I&#039;d like to see some stuff from your list. Better RAW processing, better noise management would be very welcome. Also make all adjustments brush able, and improve general performance.</description>
		<content:encoded><![CDATA[<p>For me the biggest thing on my list is for Apple to fix the bug with IPTC meta data. If I tag any picture with foreign or accented characters (such as ö, ä, and å) and then export and upload<br />
those pictures to my agency&#8217;s picture bank all the foreign and accented characters become scrambled. </p>
<p>It&#8217;s something I&#8217;ve reported on support forums and via feedback forms for over a year now. I&#8217;m currently using an awful work around where I edit pictures in Aperture, export to Photo Mechanic, tag them and upload them. Not really ideal for half time at a sports event. </p>
<p>So for me that is a big one, and a likely deal breaker if it&#8217;s not addressed. </p>
<p>Then in regards to my workflow a built in FTP would be amazing. If I got that along with them fixing the IPTC bugs I would immediately shave 15 minutes from my regular workflow. </p>
<p>On top of those I&#8217;d like to see some stuff from your list. Better RAW processing, better noise management would be very welcome. Also make all adjustments brush able, and improve general performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Rolf Schmolling</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21249</link>
		<dc:creator>Rolf Schmolling</dc:creator>
		<pubDate>Tue, 07 Feb 2012 06:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21249</guid>
		<description>I wonder and (hope NOT) rthat this is Lion only… not going to put that beast on my MBP (early 2008)

Regards,

Rolf</description>
		<content:encoded><![CDATA[<p>I wonder and (hope NOT) rthat this is Lion only… not going to put that beast on my MBP (early 2008)</p>
<p>Regards,</p>
<p>Rolf</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Paul Perton</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21246</link>
		<dc:creator>Paul Perton</dc:creator>
		<pubDate>Tue, 07 Feb 2012 04:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21246</guid>
		<description>How about fixing the crop tool so that it doesn&#039;t de-select your image every time you move/change a crop?

And, while that really hard debugging is happening, it would be good to be able to define and save a custom crop - 3:1 for landscape use perhaps?</description>
		<content:encoded><![CDATA[<p>How about fixing the crop tool so that it doesn&#8217;t de-select your image every time you move/change a crop?</p>
<p>And, while that really hard debugging is happening, it would be good to be able to define and save a custom crop &#8211; 3:1 for landscape use perhaps?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Aperture 4? by Thomas Fitzgerald</title>
		<link>http://theapertureblog.com/2012/02/06/aperture-4/comment-page-1/#comment-21226</link>
		<dc:creator>Thomas Fitzgerald</dc:creator>
		<pubDate>Mon, 06 Feb 2012 22:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://theapertureblog.com/?p=1119#comment-21226</guid>
		<description>Oh, good point. I completely forgot about that.</description>
		<content:encoded><![CDATA[<p>Oh, good point. I completely forgot about that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

