Ferris Wheel: 1/1250s f/8.0 ISO200 73mm -0.3ev, Canon 30D, Canon 70-200 f/2.8L IS

Here is what I am currently doing to manage photos on my MacBook and iMac. It's a simple one-way process.

When I import my photos onto the Macbook I do so as managed files so they go into the library. Then I'll cull, rate, keyword, or whatever I want to get done. I don't adjust much, since the screen is small and not as good as my iMac and I can't control the room illumination as well. I leave preview generation turned on for all projects in my library and set it to make half size images. This lets me quickly put together slide shows and skim through images in a flash.

Then when I'm done working on the laptop, I export the project to the desktop and rename the project in the library by adding "Exported" to the end. That's to remind me that I've already done the export and should not do any more editing.

To transfer the project to the iMac I either copy it across the network, or restart the laptop in Firewire target mode and use the Finder to drag the folder across and onto my iMac Aperture library.

Back on the MacBook I delete all the rejects by finding them with a smart album and pressing command delete and then relocate all the remaining project images to a temporary folder. I immediately delete the temporary folder, since I don't want the RAW images to remain on the Macbook, and rename the project again by removing "Exported" and adding "Previews".

So on the laptop I have previews that I can easily show, drag out to other apps, or email, and on the iMac I have the RAW files, the previews, and the project intact. On the laptop the images use up only about 1 MByte each with the thumbnails and previews, so it is pretty space-efficient.

Tags: Aperture, Workflow, Laptop

Fraser Speirs has blogged his experience keywording his photos:

So, finally, I’ve drawn together my thoughts about keywording in Aperture. My problem with keywording has always been more about “how can I make it easy enough that I will actually do it?”, rather than “what should the keywords be?”. I’ll explain my personal taste for both, though.

In particular he talks at length about the keyword bar at the bottom of the window:

The magic — if that’s what it is — is that these button sets give keyboard shortcuts to your keywords. The first nine keywords in any set get the shortcuts Option-1 through Option-9, although the set of keywords can be arbitrarily large (I think). The second insight, that I think few people have noticed, is that you can cycle through these button groups using the shortcuts Comma and Period. This makes for really fast navigation through keyword groups.

Tags: Aperture, Keywords, Workflow

James Duncan Davidson recounts how he recently shot ETech and eComm: 11,000 photos in total, and processed them all with Aperture.

Tags: Aperture, iPhoto, Workflow

A reader pointed out to me that the workflow described in Use Albums and Stacks To Manage Adjusted Images no longer works. Aperture 2.0 has changed the behavior of album picks so that creating a new album from non-pick images no longer automatically makes those images the album picks in the new album. Send feedback to Apple if you want the old behavior back.

Tags: Aperture, Bugs, Stacks, Album Picks, Workflow

Sometimes I have an image that I want to adjust to look like another in some way -- maybe the same brightness or color. This is easy to do because Aperture can display both at the same time and I can adjust one while using the other as a reference.

The first thing I do is press the S key to select Primary Only. This has no effect on adjustments (adjustments can be applied to only one image at time), but it does very conveniently make the currently selected image very obvious. Only the selected image has a white selection ring in this mode.

Here I have the upper image displayed as a reference and am adjusting the lower image:

This also works in full screen mode (F key) and with zoom on (Z key):

If I need to adjust two images at the same time, this is possible too. Clicking on an image changes the selection to that image and I make adjustments. This technique can be applied to as many images as I can cram on the screen.

Tags: Aperture, Adjustments, Workflow, Comparing

Missing from Aperture is the ability to attach notes and documents to images, albums, or projects. A partial way around this limitation is to create web journals in Aperture and associate them with the images they relate to.

To add notes to My Macworld 2008 project, I control-click the project and select New > Web Journal:

That creates an unnamed web journal inside the project which I then rename. A web journal consists of blocks of text and images arranged on individual pages, the idea being that each page is a single entry for a unit of time such as a day. In this case I'm just going to use one page.

I add text to the blank web journal by clicking the +T icon, or by dragging it to where I want a new entry. The green line shows where it will be placed:

Placeholder text appears and can be replaced with notes by overtyping:

There is a control at the top right that selects whether the text is used as a subtitle or as body text. I can also replace the site title and other placeholder text.

To add images to the web journal pages, I must first add them to the web journal image browser. I add images by option-clicking on a project or album so that two browsers are displayed together and then drag the images I want over to the web journal browser:

In this case I am taking images from the MacWorld 2008 project, but they could come from anywhere in my library.

To make things easier, I can lock the viewer to the web journal browser:

This keeps the web journal displayed all the time even if I select album or project browsers and click on the images they contain.

Once I have some images in the web journal browser, I add them to my notes as illustrations by just dragging them in:

As well as living inside projects, web journals can also be stored in blue folders or brown folders. Although I can't have web journals inside albums or smart albums, I can name my web journals in such a way that they are easily associated with them.

While this technique does not allow documents to be stored with projects, I can still associate them. Using a copy of TextWrangler, I open a new file browser with option command N. Then I navigate to the document I want, in this case a Garageband file, and control-click:

By selecting Copy URL I have a URL that starts with file://. I paste that into my web journal. Later when I want to access the document I can copy and paste the URL into Safari. Safari will open the document if it can (for a movie for instance), or if it cannot will reveal it in the Finder. This technique works with folders as well. There is, unfortunately, no way to make the link clickable.

Tags: Aperture, Web Journals, Workflow

If you want to see how a crop will look in the final image but still play with it, set your workspace up like this:

After starting the crop with the C key, adjustments of the crop rectangle in the viewer are accompanied by thumbnail regeneration in the browser. Once it looks right, press A to finish. The same trick works in full screen mode:

Just make sure that the thumbnails are set to be visible all the time by setting the viewer mode to On:

Tags: Tips And Tricks, Aperture, Cropping, Workflow, Workspace, Thumbnails

Fraser Speirs (of FlickrExport fame) shares his Aperture workflow:

Someone asked me recently about how I work through my photographs after I shoot. When I go out to photograph, I shoot a lot - most people I go out with are usually surprised at the number of frames I produce. It’s not uncommon for me to take the kids to the park and come home with 150-300 images.I find that I can usually edit down 350 images to around 50 in 40-60 minutes and I thought I would share how I go about this.

He also has a more recent blog entry entitled When I Delete a Photo (almost never, basically). I have a different philosophy: I reject many photos and delete all the rejects about once a month.

Tags: Aperture, Workflow, Deleting, Renaming, Referenced

It's 2008 and I have imported Jan 1 photos but there is no 2008 blue folder under library like my previous years. These are not regular blue folders rather a double rectangle in blue with an asterisk in the bottem right corner. How is this created? Thanks. Great site!

Those are built-in smart albums and there is nothing you can do about them:

I never use them. If you find where they are defined and change them, then Aperture will put them back to their defaults. But you would think that 2008 would have been automatically created since it follows 2007. Every time, so far at least.

The fix is to make regular smart albums for years. I click on Library and create a new smart album like this:

By selecting the library first, the scope of this smart filter is the entire library. Renaming the new smart album and clicking on the magnifying glass gives me the filter dialog. Notice that the title says (Library), showing the scope. I could use the + pop-up top right to add a Date line to the filter and then set a range of dates:

But this is messy. Once the dates are entered they change to include the time and time zone. When I set up one for 2007 the filter did not find images I had shot during the last 8 hours of 2007. I am 8 hours behind UTC, so I assume that this filter works on UTC. Handy for those who require the same universal time comparison worldwide so that everyone agrees on when 2008 starts and ends, but not what I need.

So I go for the quick fix by selecting select EXIF from the + button top right and matching the Capture Year:

In both cases I select Ignore stack groupings in order to allow images inside stacks to be included.

Tags: Aperture, Q&A, Smart Albums, Library, Workflow, EXIF

Ever had this happen?

This project is full of duplicates. There are only 30 images I need to remove in this example, so I can do it by hand, but what if I had a thousand?

There are two ways to remove duplicates: find something that is common to all images in one set and filter on that, or find something that is common to each pair of images and use that to create a thumbnail arrangement that makes for easy selection.

An example of using the first method is to see if the duplicates exist because they were imported a second time. If this is the case then they have a separate import session and I can filter them and remove them. It's easy to check. I click on the filter button top right, select Import Session and see just two. I select one of the two import sessions to filter down to just one set of images:

Then I select all the images will command A and delete them with command delete. When I show all the images in the project, just one set is left.

If the duplicate images were imported together this does not work, so I need a different method of distinguishing them. For example, if one set of duplicates is a different size then I can filter on the EXIF data and use a condition such as Image Height Is Less Than to split them:

To use the second method, that of pairing up the duplicates, the sort order must use an image property that is the same for each duplicate, such as image date, caption, file name, or possibly file size. It depends on where the images came from as to what is available and what will work. The list view can be useful for doing this because it can sort on a much wider variety of image data than the grid view.

Once sorted, and assuming that every image has the same number of duplicates (all have one duplicate in my example), I arrange the display to show the duplicates in rows:

To select the ones that I want to remove, I simply click and drag a selection rectangle from the top to the bottom on the left-hand column:

Once selected, I press command delete to remove them. Just marking them with a keyword or as rejects are other options open to me. It depends how certain I am that I want them removed permanently and right now.

Another way I can get rid of duplicates is to hide them in stacks. This works only if the images have their image dates intact. I select all the images and go to Stack > Autostack. By addjusting the slider on the autostack HUD, the images are paired:

I close all the stacks with option semicolon and the problem has been hidden. If I later want to delete the duplicates, I can open all the stacks and adjust the width of the grid view to show one stack per row. Then I drag a selection rectangle across the right-hand images to select the images and delete them.

Having the duplicates in a stack like this also lets me mark one set. Selecting all the closed stacks and adding a keyword will only apply the keyword to the pick. If I subsequently unstack the images, I can then use that keyword to filter and remove the duplicates.

Tags: Aperture, Duplicates, Workflow, Deleting

If your workflow involves stacking before keywording then you have probably found that the keywording part is either inefficient or incomplete. Adding keywords to a closed stack only adds to the pick, so those non-picks remain without metadata.

There are consequences to this. For example, if I change the pick after keywording, the new pick (and hence the stack) no longer has the keywords:

The water keyword will not find the pick and so will not find the stack. And unless I specifically select to ignore stacks, any smart album that filters on the water keyword will fail to find this image.

The choice I have is either to live with this behavior, or keyword every image in the stack when I do the keywording. But how to keyword every image in a stack without going crazy?

The obvious way is to select the pick, click the number to open the stack, then click drag, click drag each keyword to each image:

This is very slow and error-prone. A faster way, but still with too many keypresses, is to open the stack and select all the images in the stack at once with command E. Then each keyword can be dragged over from the HUD just once to apply it to all the images:

I can apply multiple keywords at the same time by command-clicking on them and then dragging, saving even more time. And if the keyword buttons are set up on the keyword bar at the bottom of the window, I can press them or their keyboard equivalents to quickly apply commonly-used metadata.

I actually use an even faster way that goes straight to the next stack and opens it all in one step. First I select the top image in the project or album, then press option page down. That single key-press seeks forward to the next stack, opens it, and selects all the images it contains. Now I simply add keywords to all the images in the stack, as before. I press option page down again to go to the next stack and repeat. Once done, I close all the stacks with option semicolon.

Option page down also works in list view, but in list view the images are to small to be recognizable.

The option page-down method for dealing with stacks skips all the intervening unstacked images and that can be inconvenient. I have to go back over my images picking out the ones that are not in stacks among those that are in order to keyword them. I can make this a little easier by sorting the display by Keywords:

Once I do that, all the non-keyworded images are together at the bottom of the browser ready for keywording.

Tags: Keywords, Aperture, Stacks, Workflow

Ken Huth has published ApertureCast number 11: Workflow part 2: Six Ways To Edit on his HuthPhoto media page. Ken publishes an image-enhanced Aperture podcast every month or so.

Tags: Podcast, Aperture, Workflow

[Update: Aperture 2.0 kills this workflow dead. Apple has changed the behavior of album picks so that creating a new album from non-pick images no longer automatically makes those images the album picks in the new album. Send feedback to Apple if you want the old behavior back]

This article shows a powerful technique for managing adjustments to large numbers of images. It brings together stacks and albums and shows how they can be used as part of an efficient workflow. It was prompted by a posting on the Apple message boards for Aperture:

Here's the conundrum: I have 800 event photos in an Aperture project. I stamp adjustments to all of them. So, now I have 800 stacks, each with a master RAW image and an adjusted version. In each stack, the unadjusted master is the default pick. If the stacks are closed and I Export Versions, I get 800 JPEGs rendered from the unadjusted masters. If I open all stacks, select all, and Export Versions, I get 1,600 JPEGs rendered from both the masters and the versions. How in **** do I select the 800 adjusted versions for export without having to command-click on each one? Is there no way to automatically export just the versions?

The only approach I've found is to select the versions and make them the picks in their stacks, one by one. Then I can close the stacks, select all, and Export Versions. This is painfully time-consuming. I can't even just select the versions one by one and then batch promote them to pick status. I not only have to select the versions one by one, but I also have to promote them one by one. Argh! Am I missing something here? Please help.

Here is a project with some images that I am going to adjust. There could be thousands: the workflow is the same.

Before I start adjusting I select the three images I want to work with and create new versions by pressing option V:

This creates duplicates of the three and puts each duplicate into a stack with the original as the pick. This is where the difficulty lies as the person with the problem found. Since those new versions are in stacks but are not the pick then Aperture will not use the adjusted version for exports.

To turn this to my advantage (without clicking anywhere else so that the duplicates are still selected) I control click one of the new versions and select New From Selection > Album:

Pressing command L has the same effect. The new album is created and displayed and I can rename it to something meaningful, such as Adjusted:

The new album shows the stacks just as the project did, but this time there are check marks on the duplicates showing that these are the album picks:

An album pick is the image that will be on the top of the stack for this album only. Look what happens when I close all the stacks with option semicolon:

Just the album picks are left showing. That's the preparation complete. I have an album which will show me all the new versions, so no changes to the original project are needed. Now I adjust the images. For this example the changes are rather radical, so the difference is obvious:

I could have adjusted just one image and used lift and stamp to process thousands.

Selecting the original project shows that the adjusted versions are still in the stacks, and are not the picks as they are in the album:

Closing the project stacks will show me the originals. Closing the album stacks will show me the adjusted images. So by selecting either the project images or the album images I can choose which I export, print, or continue to process.

This technique can be used any number of times with any number of selections and albums and should be part of your standard workflow.

Tags: Aperture, Stacks, Album Picks, Adjustments, Workflow

I am a photographer and travel to various "Locations." I am having a workflow problem with Aperture and image storage. It seems to me that there is probably an easy fix either in Aperture or in modifying my workflow but the Apple discussion group is unable to grasp my problem. One kind responder pointed me to your site and so perhaps you would allow me to ask my question. While traveling I download from the camera to my laptop MacBook Pro each day. Dependent upon opportunities I sometimes need to download from the SD cards directly to a Wolverine battery operated hard drive while continuing to shoot. I then copy from the Wolverine to my MB Pro at the end of the day. I use Aperture to rate, cull, add keywords, put into projects etc etc. As the laptop's hard drive is too small to store all of my images i usually need to make additional DVD backups of my images and erase the files from my laptop. This is where the problem starts.

After I erase the master files the images and ratings etc still appear in Aperture but of course the images show as off line. Upon returning home I copy all of my images onto my eSATA hard drives (from DVD or from Wolverine). Now I want to have Aperture look for the master images on the eSATA drive and re connect, but cannot figure out how to do this. The only solution I have so far is to re do the rating, culling, keywords etc referencing the images on the eSATA drive and erase the older versions. This besides being time consuming is for me fraught with peril. My administrative skills are almost non existent.

You can reconnect the copied masters with the Referenced File Manager. I have an article that describes how to do this called Burning Masters To DVD and The Referenced File Manager. However, you can make all of this workflow faster and less perilous by working with complete projects rather than individual masters. And you won't have to go near the Referenced File Manager to do it.

As you import images into the Aperture library on your laptop, make the projects fairly small. Do your rating and sorting. When your laptop is too full, export these projects a few at a time.

You can check that the projects look OK by dropping them onto an open TextWrangler document and seeing if the expected files are present:

Looks good to me. Also check the size of the project in the Finder as a sanity check:

My project has 18 images of about 2.5MB each, so that looks right.

Burn as many as will fit onto a DVD, verify the DVD, and then delete the project in the Aperture library and empty the trash. Emptying the trash is necessary because the deleted masters in the projects will be moved there. Repeat with all the projects you want to move. You'll have to come up with a foolproof scheme for naming these projects so there is no chance of deleting the wrong thing.

Now when you get back into the office, just import the projects into Aperture's library. That's it. Mount the DVD and drag the projects to the library:

If you trust that the keywords coming in with the projects are well-behaved (ie match the scheme you are using, have the correct spelling etc.) then before importing the projects, unlock the keyword HUD by bringing it up with shift H and clicking the lock icon. This will give the newly-imported images the same keywords are are already used in the library. If you leave the keyword HUD locked, the imported keywords will be added to a separate keyword hierarchy called Imported Keywords and have to be merged later.

The big advantage of using projects to move images around is that they are self-contained. They include all the masters, versions, keywords, ratings, albums, adjustments, and everything else needed to work instantly as soon as they are put back into the library. They even contain thumbnails, so you won't have to wait for them to be regenerated once you are back in the office.

Tags: Aperture, Q&A, Masters, Laptop, Workflow, Projects, Reconnecting

Now that all of my old images and their metadata have been prepared and transferred from iView to Aperture, one step remains: clean up. Cleaning up comprises applying ratings, merging keywords, and converting data in other fields to keywords.

Before describing this process, some advice on performance. I discovered that by doing the right thing I could speed up some operations with Aperture up by a factor of more than a thousand. Yes really. The key advice is this:

If at all possible, don't have any images or thumbnails visible when you change metadata!

I found that doing some things like changing and editing keywords in the keyword HUD with a filter active that used that metadata took an hour rather than a second (I have 20,000 images in my library). Aperture was going through serious contortions with SQL and string handling during this time and eating real memory at a rate of about 50k a second (a memory leak?). Once I figured what was going on, I created an empty project and selected that each time I wanted to make changes to the keyword hierarchy.

Of course it is not always possible to have images not showing or filtered, but whenever messing with keywords, it is worth remembering.

Apply Ratings
To apply ratings (these were brought over as keywords from iView) I filter on the blue folder called iView that contains all of my projects with the imported images. Since all of my one star images have the keyword onestar, I filter on onestar, select all the images in the browser with command A and press the + key to give them a rating of one star. This takes a while because there are many one star images. Then (bearing in mind the performance tip above) I delete the onestar keyword from the Imported Keyword section of the keyword HUD.

I repeat this for the twostar and threestar keywords and the ratings are now done.

Convert People Keywords
Next I convert my people keywords. I have imported name keywords from iView that all start with a lower-case letter so I can distinguish them from the existing ones. To convert these is easy. After selecting my empty project and unlocking the keyword HUD I double-click on "steve" in the keyword list and change it to "Steve". That elicits this warning:

Once done, I drag the Steve keyword onto its containing keyword in my "master" hierarchy. In this case that keyword is Family under People:

I get another warning and then this warning:

Accepting the offer to merge the keywords leaves my imported images with the same keyword as those already in my library and ensures that they have the same hierarchy too.

I repeat this for each person until I am done.

Convert All Other Metadata
There is still more metadata to convert. Annoture maps iView metadata fields to IPTC fields. For instance Location in iView becomes Sub-location in Aperture. So I have to work through each IPTC field, identify all the possible values, filter by each of those values, select the images, and add or apply keywords appropriately.

This is not as hard as it seems. By adding the appropriate fields to the List - Expanded metadata view and browsing my images in list view I can sort them by these fields:


For Albuquerque I create a new keyword United States > New Mexico > Albuquerque, select all of the images with Albuquerque in the Sub-location field (in the list view with click at the top and shift click at the bottom of the range), and then apply the new Albuquerque keyword. See Metadata Views for more information on setting this display up.

Once I have worked all the way down the Sub-location column and repeated this for each different word used in that field I can clear the field. The easiest way to do this is to select all of the images I have imported (and processed), press shift command B to bring up the batch change dialog and set it up like this:

By selecting Replace and checking the box next to Sub-location I choose to clear that field on all selected images. I press OK and then move to the next field.

Delete The Old Folder Hierarchy
Finally I am done, and all that remains is to delete my old folder hierarchy. It is now empty of course. I left it in place because in the second step (importing) iView still needs the hierarchy in place to allow filtering by folder. Now it is no longer needed.

That's It
I am sure that others will have a different story to tell about moving from iView to Aperture. Please let me know your own experience so I can improve this article.

Tags: Aperture, iView, Workflow, Keywords

I have been busy moving all my old photos that were cataloged with iView into Aperture. It has taken a while to work through all the issues and get the workflow straight, but the result is exactly what I wanted: all the images with their metadata transferred. To transfer the metadata I used Annoture, Adam Tow's utility. Special thanks go to Adam for modifying his utility to work around some of the problems I found with my old image files.

Since there is a lot of detail to this process I am presenting what I found as three separate articles covering the three distinct steps needed: preparation, importing, and clean up. This article covers preparation. There are three things that need preparation: the images, the iView catalog, and Aperture.

Prepare Images and Folders

The first step in preparation is to back up my old images. I use spare space on a Firewire drive for this. Backing everything up leaves me an escape route in case I run into a bug or problem I cannot fix, or simply mess everything up by making an error.

Next I make sure that all the images and folders are not write-protected. Write-protected images and folders will cause problems later when I want to remove them. By selecting the top-level folder and hitting command-I I can check the permissions:

That needs fixing. I click the pop-up, change it to Read and Write and then click the disclosure triangle to see the details:

Clicking on Apply to enclosed items will propagate the changes down to all the folders and files.

Importing files that have no extension into Aperture can cause problems, so the next exercise is to make sure every file has one. To do that I go through each folder in turn in list view, sorting by type, and dragging anything that either has no extension or a JPG extension to a folder on the desktop. Then I run this Automator action on that folder:

This adds .jpg to anything that does not already have it. Then I drag the renamed images back to the folder they came from. This breaks the link between iView and the renamed images, but that is OK. Annoture can be set up to deal with that.

Then I look for files with names containing forward slash (/) characters. These will cause problems with metadata transfer later on, so I rename them in iView (so that iView knows the new name -- Annoture will not help me here).

Finally I remove all foreign files from the folders I am going to import images from: sounds files, movies, text files, anything that might confuse or upset the process.

Prepare the iView Catalog

I will be using Annoture to move metadata from iView to Aperture. It works well, but it is not magic. There are some things it cannot do, and some things that it can do will make for extra work in Aperture that I can reduce by doing some of the work in iView.

The basic philosophy is to change all the metadata types that could have multiple entries for one image into multiple keywords and then move that metadata into Aperture.

First I make a back up my iView catalog. I can now fritz with the metadata as much as I like before moving it over to Aperture.

Then I add a new keyword iviewimport, select all the images in my iView catalog, and apply that keyword to them. This step will let me be assured that metadata for all images has been transferred. If any image in Aperture that came from my old images does not have the iviewimport keyword, then Annoture did not move the metadata for some reason (it could be missing from my iView catalog for instance).

In iVew I have all my people listed under the People category. In Aperture I use keywords. So the next step is to create a keyword for each person in iView. The keywords I create are all lower-case: bob, not Bob. I do this so that the new keywords will not get confused with the existing keywords in Aperture. I will convert all the bob keywords to Bob keywords later. To apply the new keywords, I select that person in the People list, select all of the images that include that person, and drag them to the new keyword.

Then I rename all my iView keywords so that they start with a lower-case letter. The reason for this is that I have several keywords in Aperture that are the same except for their hierarchy. I have Content > Water and also Blog > Water. Another more realistic example would be Color > Orange and Fruit > Orange. When the metadata is transferred from iView to Aperture, Aperture makes a random choice between the available keywords if there is more than one match. So anything tagged with Water in iView will end up either as Content > Water or Blog > Water and have to be sorted out manually. But if I change all the Water keywords to water in iView this will not occur and everything will get the naked water keyword.

Lastly I convert all my labels to keywords. Because hitting number keys is so convenient, I, like a lot of people, have used the labels for rating images instead of the Rating category. But since ratings don't transfer in Annoture I need to convert these to keywords and then deal with them in Aperture. It's the same system as for people. This time the keywords I create are onestar, twostars etc., all lower-case again.

Prepare my Aperture Library

First I make a back up of my Aperture library. A simple copy will work.

Next I create new projects. I will work on one chunk of images at a time by creating projects in Aperture and filling each with images from my old folder hierarchy. A project will typically be a year or a month of images, depending on how many photos I was taking at the time. For some images, such as scans of old photos, I will have a different structure. I put all of those new, empty, projects into a hierarchy of blue folders with one at the top called iView.

I don't want my existing Aperture keywords to be modified, so I make sure the keyword HUD is locked. That is done by clicking the small lock on the keyword HUD (shift H).

This ensures that the keywords that come in with the imports are put into the Import Keywords part of the keyword HUD.

That's all the preparation done. Next is importing.

Tags: iView, Aperture, Workflow

O'Reilly Digital Media has two more podcasts up now. Bill Frakes talks about workflow (24m) (recorded on location and has level problems) in one, and Sal Soghoian talks about automation (14m) in the other.

Tags: Podcast, Workflow, Interview