<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Aperture vs. Lightroom Part three: Lightroom</title>
	<atom:link href="http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/</link>
	<description>@ robertwrightphoto.com</description>
	<lastBuildDate>Sat, 06 Mar 2010 15:36:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: me</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-667</link>
		<dc:creator>me</dc:creator>
		<pubDate>Mon, 21 May 2007 14:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-667</guid>
		<description>I have hacked my Aperture to do this, my concern was mainly what happens when Raw support finally arrives, one of two things,  there are two entries for M8 in the raw dictionary, and both appear, or there is only one, and any adjustments I have made to 4000+ images and counting suddenly become the wrong adjustments. So I left it alone for now. Thanks for the post.</description>
		<content:encoded><![CDATA[<p>I have hacked my Aperture to do this, my concern was mainly what happens when Raw support finally arrives, one of two things,  there are two entries for M8 in the raw dictionary, and both appear, or there is only one, and any adjustments I have made to 4000+ images and counting suddenly become the wrong adjustments. So I left it alone for now. Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: V</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-666</link>
		<dc:creator>V</dc:creator>
		<pubDate>Mon, 21 May 2007 12:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-666</guid>
		<description>Not sure if you are aware of this, but there is a &quot;hack&quot; available that adds M8 support to Aperture.

Here&#039;s how:

--------
Originally Posted by Eoin on Leica User forum:
--------

If you want to use Apple Aperture to process M8 DNG&#039;s you&#039;ll need to do the following.....

1. I downloaded the free Adobe DNG Converter app (ADC) from Adobe&#039;s website. Using The settings to use for the converter (available in the ADC&#039;s preferences) were:
JPEG Preview-&gt;None
Compression(Lossless) checked
Image Conversion Method-&gt;Preserve Raw Image
Original Raw File-&gt;Embed Original Raw File-&gt;unchecked
You&#039;ll also need to point to the source M8 DNG folder and where you want to output the Adobe DNG&#039;s to
2. If you try to import an Adobe converted M8 dng file into Aperture. It imports, but says that it is an unsupported image format. You&#039;ll need to do the following...
3. I started up my plist-editing application. I used PlistEdit Pro. You can download it as a free trial
4. In the finder, I navigated to
System/Library/Frameworks/ApplicationServices.framework/ Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/Raw.plist and copied (not moved) that file to the Desktop in case I made a mistake. I then opened the original file in its original location in PlistEdit Pro. You may have to unlock this file to allow you to save it depending on your security setup. To unlock right click and select get info, go to ownership and permissions and change from read only to read and write.
5. After opening in PlistEdit Pro I found the entry for the Nikon-D200 in the upper panel, highlighted it and clicked on duplicate. A new entry is created called Nikon-D200 2. If you click on the name and edit it to read Leica Camera AG-M8 Digital Camera, the name must be entered exactly as I have typed it here. It&#039;s probably easiest to cut and paste it
7. I saved the edited Raw.plist file in its original location, closed all my apps, started up Aperture, and imported the Adobe converted DNGs without a hitch.

What you will find is aperture is able to display and edit the Adobe converted DNG file like any other raw file. The only thing you may notice is the colour saturation will need to be increased slightly if you happen to like the what I consider over saturated C1 profile.
I find the conversions to be excellent and what&#039;s more I&#039;m enjoying being back within the Aperture workflow.</description>
		<content:encoded><![CDATA[<p>Not sure if you are aware of this, but there is a &#8220;hack&#8221; available that adds M8 support to Aperture.</p>
<p>Here&#8217;s how:</p>
<p>&#8212;&#8212;&#8211;<br />
Originally Posted by Eoin on Leica User forum:<br />
&#8212;&#8212;&#8211;</p>
<p>If you want to use Apple Aperture to process M8 DNG&#8217;s you&#8217;ll need to do the following&#8230;..</p>
<p>1. I downloaded the free Adobe DNG Converter app (ADC) from Adobe&#8217;s website. Using The settings to use for the converter (available in the ADC&#8217;s preferences) were:<br />
JPEG Preview-&gt;None<br />
Compression(Lossless) checked<br />
Image Conversion Method-&gt;Preserve Raw Image<br />
Original Raw File-&gt;Embed Original Raw File-&gt;unchecked<br />
You&#8217;ll also need to point to the source M8 DNG folder and where you want to output the Adobe DNG&#8217;s to<br />
2. If you try to import an Adobe converted M8 dng file into Aperture. It imports, but says that it is an unsupported image format. You&#8217;ll need to do the following&#8230;<br />
3. I started up my plist-editing application. I used PlistEdit Pro. You can download it as a free trial<br />
4. In the finder, I navigated to<br />
System/Library/Frameworks/ApplicationServices.framework/ Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/Raw.plist and copied (not moved) that file to the Desktop in case I made a mistake. I then opened the original file in its original location in PlistEdit Pro. You may have to unlock this file to allow you to save it depending on your security setup. To unlock right click and select get info, go to ownership and permissions and change from read only to read and write.<br />
5. After opening in PlistEdit Pro I found the entry for the Nikon-D200 in the upper panel, highlighted it and clicked on duplicate. A new entry is created called Nikon-D200 2. If you click on the name and edit it to read Leica Camera AG-M8 Digital Camera, the name must be entered exactly as I have typed it here. It&#8217;s probably easiest to cut and paste it<br />
7. I saved the edited Raw.plist file in its original location, closed all my apps, started up Aperture, and imported the Adobe converted DNGs without a hitch.</p>
<p>What you will find is aperture is able to display and edit the Adobe converted DNG file like any other raw file. The only thing you may notice is the colour saturation will need to be increased slightly if you happen to like the what I consider over saturated C1 profile.<br />
I find the conversions to be excellent and what&#8217;s more I&#8217;m enjoying being back within the Aperture workflow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: me</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-660</link>
		<dc:creator>me</dc:creator>
		<pubDate>Mon, 14 May 2007 00:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-660</guid>
		<description>There is, it is called LightboxXMP and it will let you write a sidecar and export it alongside an image.</description>
		<content:encoded><![CDATA[<p>There is, it is called LightboxXMP and it will let you write a sidecar and export it alongside an image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Iannelli</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-658</link>
		<dc:creator>Simon Iannelli</dc:creator>
		<pubDate>Sun, 13 May 2007 16:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-658</guid>
		<description>Well, I&#039;m not a stock user aswell, because I think my pictures are too important for me to be used without my control. I want to know what happens to/with them ;)

LR is able to write the metadata into RAWs (if the format supports it, otherwise it will write sidecar files). I prevent using applications who lock my pictures in. This is a reason why I don&#039;t use Aperture. Apple has the guidline that they never alter the RAWs (to prevent damage), because of that metadata can only be applied on export. Maybe there are thirdparty tools to write metadata into the files.</description>
		<content:encoded><![CDATA[<p>Well, I&#8217;m not a stock user aswell, because I think my pictures are too important for me to be used without my control. I want to know what happens to/with them <img src='http://www.robertwrightphoto.com/writing/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>LR is able to write the metadata into RAWs (if the format supports it, otherwise it will write sidecar files). I prevent using applications who lock my pictures in. This is a reason why I don&#8217;t use Aperture. Apple has the guidline that they never alter the RAWs (to prevent damage), because of that metadata can only be applied on export. Maybe there are thirdparty tools to write metadata into the files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: me</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-657</link>
		<dc:creator>me</dc:creator>
		<pubDate>Sun, 13 May 2007 15:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-657</guid>
		<description>This brings up a whole other issue, how Lr and Aperture treat metadata. As it is now, the captions and keywords are invisible to  Spotlight because neither program writes into the original raw file. There is a caveat, Lr will write into DNG files, like the M8 files, but so far, Spotlight cannot see into the M8 DNG&#039;s. So I don&#039;t know if the caption info is visible or not, we will have to wait for Apple to update it&#039;s raw support.
I agree, some caption data would be effective even if it is only available to the DAM, but the ability to &quot;find&quot; a photo presumes questions like &quot;I am looking for a photo of..&quot; which I have always had a hard time with. I would challenge you to write a caption for the photo at the head of this post. Other than location, is that caption useful? Usually I find I work on a series for a while, and then eventually I move on. What survives is a small group of pictures. The rest becomes chaff. So I guess I am not interested in becoming a librarian?</description>
		<content:encoded><![CDATA[<p>This brings up a whole other issue, how Lr and Aperture treat metadata. As it is now, the captions and keywords are invisible to  Spotlight because neither program writes into the original raw file. There is a caveat, Lr will write into DNG files, like the M8 files, but so far, Spotlight cannot see into the M8 DNG&#8217;s. So I don&#8217;t know if the caption info is visible or not, we will have to wait for Apple to update it&#8217;s raw support.<br />
I agree, some caption data would be effective even if it is only available to the DAM, but the ability to &#8220;find&#8221; a photo presumes questions like &#8220;I am looking for a photo of..&#8221; which I have always had a hard time with. I would challenge you to write a caption for the photo at the head of this post. Other than location, is that caption useful? Usually I find I work on a series for a while, and then eventually I move on. What survives is a small group of pictures. The rest becomes chaff. So I guess I am not interested in becoming a librarian?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Scheffler</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-656</link>
		<dc:creator>Ron Scheffler</dc:creator>
		<pubDate>Sun, 13 May 2007 14:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-656</guid>
		<description>Quote: or myself, I don’t usually bother with caption data.

Then you aren&#039;t helping yourself save time. A few minutes adding caption and keywords to a new project will save considerable time down the road when you&#039;re trying to find specific images. Even in a &quot;non-stock&quot; library.

It may also make the folder structure less relevant. I have to admit, I have not looked at Lightroom yet, so maybe it is important. 

Maybe your digital image library is manageable now, but in 5-10 years or later? Even with extremely tight editing you will end up with tens of thousands of images.

This is where DAM software comes into play. But you can get some of that functionality, and probably enough of it for simple image searches, even from Spotlight built into OSX. Other apps have incorporated Spotlight functionality, such as Photo Mechanic, which will open a contact sheet with all images found based on a keyword search. Quickly checking the specs for both Lightroom and Aperture, it appears they both support keyword searches (I would be surprised if they didn&#039;t). Even if it only takes you a minute to find an image, a keyword search will take a second or two... 

It also appears both Lightroom and Aperture are similar to DAM software in that they apply the caption/keyword to the database referencing the files rather than embedding directly into the image files. This is fine if you only plan to use one app for all of your organizing. While you can embed the metadata to images upon export from either app, it will mean that while files are within the Lightroom or Aperture system, they are essentially hidden from caption/keyword searches made by other apps and probably also Spotlight (Spotlight searches metadata embedded within files).

My point is that adding caption and keyword info has value, even if your current library is manageable without it.</description>
		<content:encoded><![CDATA[<p>Quote: or myself, I don’t usually bother with caption data.</p>
<p>Then you aren&#8217;t helping yourself save time. A few minutes adding caption and keywords to a new project will save considerable time down the road when you&#8217;re trying to find specific images. Even in a &#8220;non-stock&#8221; library.</p>
<p>It may also make the folder structure less relevant. I have to admit, I have not looked at Lightroom yet, so maybe it is important. </p>
<p>Maybe your digital image library is manageable now, but in 5-10 years or later? Even with extremely tight editing you will end up with tens of thousands of images.</p>
<p>This is where DAM software comes into play. But you can get some of that functionality, and probably enough of it for simple image searches, even from Spotlight built into OSX. Other apps have incorporated Spotlight functionality, such as Photo Mechanic, which will open a contact sheet with all images found based on a keyword search. Quickly checking the specs for both Lightroom and Aperture, it appears they both support keyword searches (I would be surprised if they didn&#8217;t). Even if it only takes you a minute to find an image, a keyword search will take a second or two&#8230; </p>
<p>It also appears both Lightroom and Aperture are similar to DAM software in that they apply the caption/keyword to the database referencing the files rather than embedding directly into the image files. This is fine if you only plan to use one app for all of your organizing. While you can embed the metadata to images upon export from either app, it will mean that while files are within the Lightroom or Aperture system, they are essentially hidden from caption/keyword searches made by other apps and probably also Spotlight (Spotlight searches metadata embedded within files).</p>
<p>My point is that adding caption and keyword info has value, even if your current library is manageable without it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-654</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sat, 12 May 2007 23:11:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-654</guid>
		<description>I can begin to see the wisdom of your approach, let the library be a monolithic structure of arbitrary shape, simple dates, BUT, use the IPTC to organize it through tags....which could be read by the DAM.

I think this can make sense if you have a lot of subjects, or perhaps are trying to ornanize a stock library. I am sure it works for you, and i like the non-reliance on proprietary software to do your organizing for you.

I gave up on stock a long time ago...</description>
		<content:encoded><![CDATA[<p>I can begin to see the wisdom of your approach, let the library be a monolithic structure of arbitrary shape, simple dates, BUT, use the IPTC to organize it through tags&#8230;.which could be read by the DAM.</p>
<p>I think this can make sense if you have a lot of subjects, or perhaps are trying to ornanize a stock library. I am sure it works for you, and i like the non-reliance on proprietary software to do your organizing for you.</p>
<p>I gave up on stock a long time ago&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Iannelli</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-653</link>
		<dc:creator>Simon Iannelli</dc:creator>
		<pubDate>Sat, 12 May 2007 20:22:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-653</guid>
		<description>I totally agree with you. I also ofter work more than a day on a particular project. The scheme based on the date splits my shots into days (or even months and years). But to put them together I use DAM-software. Because I think it is risky to rely on a proprietary DAM-software I organize the collections through tags. Like this I can easily switch to another application which can read IPTC without losing my collections in the folder structure. It would be nice if LR would allow to set up &quot;smart collections&quot; as aperture does.

Hope you understand what I mean. English isn&#039;t my first language.</description>
		<content:encoded><![CDATA[<p>I totally agree with you. I also ofter work more than a day on a particular project. The scheme based on the date splits my shots into days (or even months and years). But to put them together I use DAM-software. Because I think it is risky to rely on a proprietary DAM-software I organize the collections through tags. Like this I can easily switch to another application which can read IPTC without losing my collections in the folder structure. It would be nice if LR would allow to set up &#8220;smart collections&#8221; as aperture does.</p>
<p>Hope you understand what I mean. English isn&#8217;t my first language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-652</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sat, 12 May 2007 18:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-652</guid>
		<description>I am not sure what you are proposing, the caption data goes in the iptc yes, assuming I have caption data. For NYtimes jobs, it goes there. For myself, I don&#039;t usually bother with caption data.
But in terms of avoiding duplicate file names, I have never had a problem, and the likelyhood of two files ending up in the same folder with the same name seems low to me, plus there would be a finder warning should it occur.

I messed with renaming files in the beginning and was put off by the resulting string of numbers, it is just too confusing in the finder to look at a folder containing 2007_5_10_L10001xxx.DNG&#039;s over and over. So the original L1001xxx.dng is fine for me. Plus enclosing folders, year, month day, I really don&#039;t get as I said. 

Basically, I have street work which is ongoing, a gowanus project which is ongoing, some mall stuff which is stalled, and then jobs, unique to the client, plus just a random unflied folder for whatever stuff. But pretty much if I am shooting it is in one of these areas, so the date is irrelevent.

I think what i am avoiding saying outright is if you can only think to catalog your work by day, then maybe you need to spend some time thinking exactly what it is you are making? A way of catloging time?

We have lost the contact sheet in digital. Those indeed were numbered according to the year and successive rolls, ie 1991-125. But this was mainly because the images were anchored to rolls, cutting individual frames out was a no-no. Now, in digital, the &quot;frames&quot; are unanchored. There is no reason to keep them in shot-order. I know i am losing the pleasure of seeing how I was working on a particular shot to shot basis, and who knows, I might miss that ultimately. But the gain in seeing an idea build is worth it in my opinion.</description>
		<content:encoded><![CDATA[<p>I am not sure what you are proposing, the caption data goes in the iptc yes, assuming I have caption data. For NYtimes jobs, it goes there. For myself, I don&#8217;t usually bother with caption data.<br />
But in terms of avoiding duplicate file names, I have never had a problem, and the likelyhood of two files ending up in the same folder with the same name seems low to me, plus there would be a finder warning should it occur.</p>
<p>I messed with renaming files in the beginning and was put off by the resulting string of numbers, it is just too confusing in the finder to look at a folder containing 2007_5_10_L10001xxx.DNG&#8217;s over and over. So the original L1001xxx.dng is fine for me. Plus enclosing folders, year, month day, I really don&#8217;t get as I said. </p>
<p>Basically, I have street work which is ongoing, a gowanus project which is ongoing, some mall stuff which is stalled, and then jobs, unique to the client, plus just a random unflied folder for whatever stuff. But pretty much if I am shooting it is in one of these areas, so the date is irrelevent.</p>
<p>I think what i am avoiding saying outright is if you can only think to catalog your work by day, then maybe you need to spend some time thinking exactly what it is you are making? A way of catloging time?</p>
<p>We have lost the contact sheet in digital. Those indeed were numbered according to the year and successive rolls, ie 1991-125. But this was mainly because the images were anchored to rolls, cutting individual frames out was a no-no. Now, in digital, the &#8220;frames&#8221; are unanchored. There is no reason to keep them in shot-order. I know i am losing the pleasure of seeing how I was working on a particular shot to shot basis, and who knows, I might miss that ultimately. But the gain in seeing an idea build is worth it in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Iannelli</title>
		<link>http://www.robertwrightphoto.com/writing/photography/aperture-vs-lightroom-part-three-lightroom/comment-page-1/#comment-651</link>
		<dc:creator>Simon Iannelli</dc:creator>
		<pubDate>Sat, 12 May 2007 17:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertwrightphoto.com/writing/?p=73#comment-651</guid>
		<description>Don&#039;t you think that captioninformation should go into the metadata (IPTC) and not in the filename? Using the date + a unique term avoids duplicates. For example 2007/2007-05/2007-05-12/yourname-2007-05-12-001.ext

Simon</description>
		<content:encoded><![CDATA[<p>Don&#8217;t you think that captioninformation should go into the metadata (IPTC) and not in the filename? Using the date + a unique term avoids duplicates. For example 2007/2007-05/2007-05-12/yourname-2007-05-12-001.ext</p>
<p>Simon</p>
]]></content:encoded>
	</item>
</channel>
</rss>

