I am extremely selective in the previews that I have Aperture generate. For the most part it consists of my top rated images and maybe some other stuff that I use regularly. If you have read some of my work-flow posts or file management eBooks you should know how to control Aperture previews in a lot of different ways. I thought I would share something that I found obvious but surprised a friend of mine the other day when he saw me doing it. The first thing is that...
I am not yet a huge fan of the web as a presentation medium for my photography. No I am not old fashioned and I didn’t say that I was not a fan of digital presentation. For some reason I just am not a huge fan of web galleries, online portfolios and the like. As you may have noticed I don’t have a bunch of galleries posted. When it comes to presenting my photographs you can probably tell if you have read more than two posts on my blog...
Well, not really seven, it’s just a title that I like to use pertaining to a couple of things that you can do that really bog down Aperture’s performance. After some encouragement from a new found iFriend Michael I have decided to wade into the murky and treacherous waters of managing performance in Aperture. To kick things off I thought that I would highlight the obvious (or not). Just one little “your mileage may vary” type of disclaimer first – remember that this kind of stuff is highly variable...
If you have been using Aperture for more than a little while, especially on a laptop you may be struggling with storage space issues. Referenced masters to the rescue – sort of. For the readers not familiar with referenced masters a brief review is in order. With Aperture there are two options for storing the image files that you import. Option one – the default – is called managed masters. Using managed masters Aperture copies your precious original image files into it’s mysterious secret abyss never to be seen...
