Wrong keywords assigned since Aperture 3.2.3 ?

Update: It is the same problem on my iMac, OS 10.7.3

Hello Frank,

so it's pi-day today! 😎

Thank you for your quick response. I really appreciate it. In a new library the "Stock Categories" work fine, but none of my predefined keyword button sets. They don't even assign wrong keywords - just dead. It is the same on iMac and MBP.

Regards

Léonie

What is wrong with Apple. Aperture become more and more unstable and contains more bugs. That's my opinion.

Murphy's Laws - never change a running system. 😝

But then you'll never get any bugs fixed ...

Hate to have to report this but I just tried it on my production library with added keywords and it works ok for me. 😟

Thank you, Frank, that is good news actually.

Since both my Lion Systems are acting up, I am right now installing the Aperture update on ny SL-MBP.

Does it happen from the Keywords Control bar at the bottom of the screen also or just from the menu? What about the keyboard shortcuts, do they mess up also?

Button Sets, keybord shortcuts, menu entries - all the same 😢

Toggling the Button Sets does not help, quitting Aperture does not help, rebooting also not ... 😀

But I noticed, that it will work when I switch between Aperture Libraries, with the button set in the keyword controls panel set to "Stock Categories", and this seems to be a variant of the "Wedding, Sports, Animals" problem that Kirby and me explored together. There we had exactly the problem that switching libraries while using a custom keyword set caused the buttons to vanish. Now the buttons seem to stay but do assign the wrong keywords.

Control Bar Button Sets Drop-down shows non-existing Sets "Wedding", "Sports", "Animals"

What I'll do is, I'll delete my custom sets in all libraries, then delete the preferences, and then rebuild the button sets.

Actually I'm a day late, but what the heck I like the image!

yes, a perfect design for an icon. But I'm starting to miss Gomez.

Not on a system with a library with non-stock keywords. When I switch over I'll see is I get the same error you're getting if you haven't got it by then. It's always something.

Yes, please. I'd like to see what happens with non-stock keywords.

I was hoping 3.2.3 would fix my import time zone issue but it still happens (to me at least).

With my Lumix images the time zone adjustment is still o.k. (but I imported from the card reader); I don't have access to the Canon today, but I can try tomorrow if I still see the bug.

Léonie

Kevin,

I wondered when you would drop in - nice to see you joining in on the fun 😉

So rebuilding the Library shouldn't be the fix.

😁 Actually, when Kirby and I investigated the "Wedding - Sports - Animals" nuisance, we found indiviual button sets stored in each individual library, not in the Presets. The Preference file points to the button set to use, when Aperture launches, and Aperture used to be confused, when the library didn't have a button set named like the default in the preferences.

Cheers

Léonie

Update:

I see exactly the same behaviour of Aperture 3.2.3 on my older MBP running Snow Leopard 10.6.8; The keyword controls, keyword menu, and keyword shortcuts are o.k. with the stock categories, but not with my custom button sets.

Work around:

• I deleted the custom button sets
• selected the stock categories in the keyword controls
• renamed one keyword to force a writing of the preferences
• quit Aperture and rebuild the library
• launched Aperture again and redefined my custom keyword sets.

Right now it seems to be working again with my main Aperture Library on the Lion MBP - keeping the fingers crossed 🙂

Léonie

Because Kirby and I browsed the Aperture Library Packages - if you select your Aperture Library in the Finder and Ctrl-click it, then select "Show Package Contents" you can inspect the folders inside; we found the button sets in

Database -> KeywordSets.plist

an individual set for each Library.

There is also a copy of the keywords list:

Database -> Keywords.plist

You can read and edit these files with Xcode, if you have it installed.

I was hoping 3.2.3 would fix my import time zone issue but it still happens (to me at least).

Frank,

If you are still interested - I didn't get my Canon EOS 5D out till today, but the time zone correction is still not working if I import directly from the camera.

BTW: I never noticed, but Aperture sets different times for the imported movies and the imported raw image - and both are wrong 😟

Regards

Léonie