<?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:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Aperture Tip &#8211; Autostack</title>
	<atom:link href="http://photo.rwboyer.com/2009/12/16/aperture-tip-autostack/feed/" rel="self" type="application/rss+xml" />
	<link>http://photo.rwboyer.com/2009/12/16/aperture-tip-autostack/</link>
	<description>All Things Photography</description>
	<lastBuildDate>Thu, 29 Jul 2010 19:24:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: RB</title>
		<link>http://photo.rwboyer.com/2009/12/16/aperture-tip-autostack/comment-page-1/#comment-9208</link>
		<dc:creator>RB</dc:creator>
		<pubDate>Sun, 03 Jan 2010 02:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://photo.rwboyer.com/?p=1452#comment-9208</guid>
		<description>Tony - I would say that the two problems are related but are not aperture/image specific they are a general issue with that drive or some sort of data corruption issue that goes beyond what Aperture is trying to read - if a simple copy is causing issues nothing else is going to work either.

RB

Ps. Forgot to mention I always format my drives HFS vs. FAT32 for a lot of reasons - I have had horrible issues with FAT32 drives w/ OSX - esp in the write departments.</description>
		<content:encoded><![CDATA[<p>Tony &#8211; I would say that the two problems are related but are not aperture/image specific they are a general issue with that drive or some sort of data corruption issue that goes beyond what Aperture is trying to read &#8211; if a simple copy is causing issues nothing else is going to work either.</p>
<p>RB</p>
<p>Ps. Forgot to mention I always format my drives HFS vs. FAT32 for a lot of reasons &#8211; I have had horrible issues with FAT32 drives w/ OSX &#8211; esp in the write departments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tony.</title>
		<link>http://photo.rwboyer.com/2009/12/16/aperture-tip-autostack/comment-page-1/#comment-9201</link>
		<dc:creator>tony.</dc:creator>
		<pubDate>Sat, 02 Jan 2010 23:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://photo.rwboyer.com/?p=1452#comment-9201</guid>
		<description>Thanks for the fast response!  

The largest project looks to be 2400 images (unstacked).  Its family and travel photos grouped by year.  

I&#039;m using a LaCie 500gb drive with a firewire 800 connection.  

Today I found a new problem.  I tried making a copy of the library by simply dragging it to my other external Seagate drive.  The copy failed with a finder error-36.  This seems to be a common problem without solution.  

I&#039;ve checked the library for consistency... rebuilt the database.... tried repairing the external driver, all without success in creating a backup copy.  

Now I&#039;m in the process of exporting projects and re-importing into a new library one by one attempting to locate the offending image/file.  

Maybe this has something to do with the viewer freezing?</description>
		<content:encoded><![CDATA[<p>Thanks for the fast response!  </p>
<p>The largest project looks to be 2400 images (unstacked).  Its family and travel photos grouped by year.  </p>
<p>I&#8217;m using a LaCie 500gb drive with a firewire 800 connection.  </p>
<p>Today I found a new problem.  I tried making a copy of the library by simply dragging it to my other external Seagate drive.  The copy failed with a finder error-36.  This seems to be a common problem without solution.  </p>
<p>I&#8217;ve checked the library for consistency&#8230; rebuilt the database&#8230;. tried repairing the external driver, all without success in creating a backup copy.  </p>
<p>Now I&#8217;m in the process of exporting projects and re-importing into a new library one by one attempting to locate the offending image/file.  </p>
<p>Maybe this has something to do with the viewer freezing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RB</title>
		<link>http://photo.rwboyer.com/2009/12/16/aperture-tip-autostack/comment-page-1/#comment-9178</link>
		<dc:creator>RB</dc:creator>
		<pubDate>Sat, 02 Jan 2010 03:15:36 +0000</pubDate>
		<guid isPermaLink="false">http://photo.rwboyer.com/?p=1452#comment-9178</guid>
		<description>This could be a number of things - the fact that Aperture freezes and needs to be restarted is a concern. The very first thing I need to understand is how many images are in a project - not an album but the actual project sizes. Less than 1000 images more than 5000 images. Just some idea.

Just want to make sure that you don;t have gargantuan projects. Then you should take a look at the drive itself - some external drives cause OSX to throw fits - check for reports of your drive on-line to see if others have issues with it. Lastly if the drive is going to sleep that can sometimes cause extremely long delays when it fires back up.

RB</description>
		<content:encoded><![CDATA[<p>This could be a number of things &#8211; the fact that Aperture freezes and needs to be restarted is a concern. The very first thing I need to understand is how many images are in a project &#8211; not an album but the actual project sizes. Less than 1000 images more than 5000 images. Just some idea.</p>
<p>Just want to make sure that you don;t have gargantuan projects. Then you should take a look at the drive itself &#8211; some external drives cause OSX to throw fits &#8211; check for reports of your drive on-line to see if others have issues with it. Lastly if the drive is going to sleep that can sometimes cause extremely long delays when it fires back up.</p>
<p>RB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tony.</title>
		<link>http://photo.rwboyer.com/2009/12/16/aperture-tip-autostack/comment-page-1/#comment-9173</link>
		<dc:creator>tony.</dc:creator>
		<pubDate>Sat, 02 Jan 2010 00:21:37 +0000</pubDate>
		<guid isPermaLink="false">http://photo.rwboyer.com/?p=1452#comment-9173</guid>
		<description>I like the idea you present, but its giving me fits in practice.  

I&#039;m using a MacBook pro with 3GB of ram ( a mid-07 vintage machine) with an external LaCie drive attached via firewire 800 ports.  I&#039;m migrating about 15,000 pictures from iPhoto to Aperture.  I&#039;m using managed images, so they are all in Aperture.... about 54gb worth now.  When using the stack mode to compare stacked images I frequently have the viewer freeze.... Aperture simply refuses to move to the next stack of images or to the next image for comparison.  I ultimately have to quit Aperture and start again.

Any idea what may be driving this performance problem?  I&#039;ve turned off all previews which helped some.  I&#039;m at a loss of what else I need to do.  I&#039;m also not clear if the issue is memory, disk space or the connection speed with the external drive.

Any help is welcome.</description>
		<content:encoded><![CDATA[<p>I like the idea you present, but its giving me fits in practice.  </p>
<p>I&#8217;m using a MacBook pro with 3GB of ram ( a mid-07 vintage machine) with an external LaCie drive attached via firewire 800 ports.  I&#8217;m migrating about 15,000 pictures from iPhoto to Aperture.  I&#8217;m using managed images, so they are all in Aperture&#8230;. about 54gb worth now.  When using the stack mode to compare stacked images I frequently have the viewer freeze&#8230;. Aperture simply refuses to move to the next stack of images or to the next image for comparison.  I ultimately have to quit Aperture and start again.</p>
<p>Any idea what may be driving this performance problem?  I&#8217;ve turned off all previews which helped some.  I&#8217;m at a loss of what else I need to do.  I&#8217;m also not clear if the issue is memory, disk space or the connection speed with the external drive.</p>
<p>Any help is welcome.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
