Aperture 3 - They screwed up an Import Command!
It boggles my mind why the Apple engineers would choose to make a change in the way an import command worked for YEARS under Aperture 2, but they've done it! Here's the message I just sent to Aperture Feedback:
Why did you change the way "Import/Folders As Projects" works??
I've been an Aperture user for years. One of the things I loved about the program is it lets ME be in control of how I organize my photos. For years, I've been using Aperture's "Import/Folders As Projects" command to automatically create Albums (that match an existing subfolder name in Finder) within existing projects. Now, under Aperture 3, the command doesn't work that way anymore! Here's how it has changed...
Under Aperture 2 the command worked two ways:
1) If I HIGHLIGHT (single click) on "Library" or "Projects & Albums" and then select Import/Folders As Projects, and then pick a folder full of photos, Aperture 2 would created a PROJECT with the exact same name as the folder I picked and import the photos into the new project.
2) If I were to, instead, HIGHLIGHT (single click) on an EXISTING project name in the Inspector, and then select Import/Folders As Projects, and pick a folder full of photos, Aperture 2 would created a new ALBUM within the EXISTING project name. That new Album's name would exactly match the name of the original folder that I picked (the one with the photos in it).
Under Aperture 3, it doesn't matter what I click on or highlight, Aperture 3 will ONLY work with method #1 above. Aperture 3 will ONLY allow you to create a new PROJECT, regardless if you've highlighted an EXISTING project or not.
WHY DID APPLE CHANGE THIS?
This change completely screws up the way I've been cataloging my photos for years. Now, to continue to properly recreate the same hierarchical Project/Album arrangement that matches the Folder/Subfolder organization on my dedicated hard drive for photos, I have to MANUALLY create a new Album (one at a time), name it, and then manually import just a single subfolder's worth of photos into it. I have to do this manually for EACH subfolder of photos as I add new subfolders of photos to my dedicated photo drive.
Using #2 above (in Aperture 2), I could have two dozen subfolders on my dedicated photo drive and import them ALL with one single command and Aperture 2 would automatically create Album's that matched the subfolder names.
Needless to say, I used the feature a LOT. I would sometimes shoot a full MONTH worth of photos before I would import them into Aperture. I'd have as many as 30 subfolders to import as Albums. Now, I have to do each one manually one at a time.
This is VERY annoying! It boggles my mind why the engineers decided to change it! I realize the command says "Folders As PROJECTS" but, from day one (of Aperture 2), it worked the way I describe above. In fact, I learned about this feature at one of the Aperture 2 Tour Seminars.
PLEASE FIX THIS ASAP! This is serious enough that it should warrant an immediate bug fix update. Without a fix, Apple has just created a dramatic amount of extra work for me when I have a multi-day shoot!
HELP!!!!
Mark
Why did you change the way "Import/Folders As Projects" works??
I've been an Aperture user for years. One of the things I loved about the program is it lets ME be in control of how I organize my photos. For years, I've been using Aperture's "Import/Folders As Projects" command to automatically create Albums (that match an existing subfolder name in Finder) within existing projects. Now, under Aperture 3, the command doesn't work that way anymore! Here's how it has changed...
Under Aperture 2 the command worked two ways:
1) If I HIGHLIGHT (single click) on "Library" or "Projects & Albums" and then select Import/Folders As Projects, and then pick a folder full of photos, Aperture 2 would created a PROJECT with the exact same name as the folder I picked and import the photos into the new project.
2) If I were to, instead, HIGHLIGHT (single click) on an EXISTING project name in the Inspector, and then select Import/Folders As Projects, and pick a folder full of photos, Aperture 2 would created a new ALBUM within the EXISTING project name. That new Album's name would exactly match the name of the original folder that I picked (the one with the photos in it).
Under Aperture 3, it doesn't matter what I click on or highlight, Aperture 3 will ONLY work with method #1 above. Aperture 3 will ONLY allow you to create a new PROJECT, regardless if you've highlighted an EXISTING project or not.
WHY DID APPLE CHANGE THIS?
This change completely screws up the way I've been cataloging my photos for years. Now, to continue to properly recreate the same hierarchical Project/Album arrangement that matches the Folder/Subfolder organization on my dedicated hard drive for photos, I have to MANUALLY create a new Album (one at a time), name it, and then manually import just a single subfolder's worth of photos into it. I have to do this manually for EACH subfolder of photos as I add new subfolders of photos to my dedicated photo drive.
Using #2 above (in Aperture 2), I could have two dozen subfolders on my dedicated photo drive and import them ALL with one single command and Aperture 2 would automatically create Album's that matched the subfolder names.
Needless to say, I used the feature a LOT. I would sometimes shoot a full MONTH worth of photos before I would import them into Aperture. I'd have as many as 30 subfolders to import as Albums. Now, I have to do each one manually one at a time.
This is VERY annoying! It boggles my mind why the engineers decided to change it! I realize the command says "Folders As PROJECTS" but, from day one (of Aperture 2), it worked the way I describe above. In fact, I learned about this feature at one of the Aperture 2 Tour Seminars.
PLEASE FIX THIS ASAP! This is serious enough that it should warrant an immediate bug fix update. Without a fix, Apple has just created a dramatic amount of extra work for me when I have a multi-day shoot!
HELP!!!!
Mark
32GB iPhone 3GS, Mac Pro 2.6, MB Pro 2.2, Aluminum iMac 2.4, Mini 2.0 Core 2 Duo, Mac OS X (10.6.2)
