Does anyone else think that the Smart Album/ filter search criteria Aperture/ Album Name does not work post upgrade to A3.3?
I used to use a rule against a Project containing many Albums to identify photos in that Project not yet in Albums (Aperture/ Album Name/ is empty). Since upgrading, that filter no longer works.
Steve
Ive always have found that some smart Albums stop working. But I just tossed them and made a new one and was back in business. 3.3 in terms of Smartfolders seem normal to me. Ill keep an eye on it though thanks for the warning.
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
Try rebuilding your database. See today’s post: Metadata Search Not Working? Rebuild Your Aperture Database.
@PhotoJoseph
— Have you signed up for the mailing list?
Crikey, this upgrade to A3.3 is proving to be a time-consuming and painful process. The initial upgrade seemed to work well once I got there, but then I had this metadata filtering issue, and trying to fix it has caused a world of exasperation.
Using my iMac, <70k image referenced library all on the iMac’s HHD, and a FW800 external drive for backups, this is my process to date.
1) Timemachine backup pre upgrade ~1hr; Carbon Copy image pre upgrade ~2hr
2) Upgrade (part of a multi-gigabyte software update from Apple) with Aperture and iPhoto Library upgrades ~2-3 hrs
3) Create new A3.3 Vault ~2 days!!!
4) Repair library trying to fix metadata search issues (but did not fix) ~2 hrs
5) Timemachine backup pre library rebuild (to fix metadata search) ~3hr; Carbon Copy image pre library rebuild ~3hr (should have deleted that old Vault first)
6) Aperture library rebuild as per “Metadata Search Not Working? Rebuild Your Aperture Database” ~2 hours
7) Following rebuild, FOUND THAT ALL REFERENCED IMAGES ARE DISCONNECTED, AND THAT A3 IS REPORTING THAT MY ‘MACINTOSH HD’ IS UNMOUNTED (offline) …
8) Shutting Aperture down now takes 10+ minutes as it ‘updates library’ each time
9) So a ‘restore permissions’ step too ~1 hr. That did nothing. Disk still unmounted.
10) Used disk utility to verify disk, and fix permissions (~1 hr). Fixed some things, but did not seem to be anything related to Aperture.
11) Tried a a ‘restore permissions’ step again. ~1 hr. No change … still broken.
12) Now resorting to the Create a new Library and import the old one trick. Created the new library, and imported a few images to test (as referenced). Test images seemed to work ok (HD is online). So now currently importing the lot ~ 5 hrs so far, and still going. I so hope it works.
Steve
If this was a competition then I won, I don’t count in hours but days lost. But it will be worth it to get back to a stable Database, DB, in aperture. ( some of the problems were my fault)
Maybe this is good that they did this 3.3 upgrade as a training for us when they deliver AP4.0. Hopefully our newly rebuilt DB/Lib will upgrade smoothly!
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
David
As i write this, my iMac is still flogging away with the import after 14 hrs, so I left it working.
And you know, I was having the same thought as you this morning as I trudged to the train. There’s bugs in this upgrade … Either Apple are crap at quality control, or it’s very complex behind the scenes and A3.3 is all about laying the groundwork for A4 [or third thought, they’re doing field testing with A3.3, and we’re the unpaid testers].
Still praying that this #**%}]] import works.
Steve
14 hrs is long for an import. Open Activity Monitor and see if Ap has red type stating not responding? Now sometimes Not Responding goes on and off so keep an eye on it. Guess I should of asked how many images are you importing? If there are thousands then it might be still working great if its from a camera card …not so much.
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
Well, my ordeal seems to be over (fingers heavily crossed). 14+ hours for the import of 69,084 images to the new library (finished whilst I was at work today).
Quick compare of library sizes:
> Old lib (A3.2.x) 57.78Gb
> Old lib post upgrade (A3.3) 113.79Gb
> New lib post import (A3.3): 119.2Mb at launch … started generating previews immediately, and stopped at 71.23Gb.
Lost all of the ‘Library Albums’ that were upgraded from A3.2.x … otherwise seems to be A3 as I knew it (with that drab UI).
Steve
Wow, that’s a really significant increase in size.