Will Aperture 3.6 work in Mac OS Sierra?

It worked for me.

No more Sierra for my MBP and me. 😉

Yesterday I used my Timemachine to get back to El Capitan. It was soon easy!

All is working fine now, - and Aperture is also working as it should! Nice!! 🙂

Thanks for all the help provided in here, - and good luck to you "stuck" on Sierra.

Here's a link to get back to El Capitan, using Timemachine:

http://osxdaily.com/2016/10/02/downgrade-macos-sierra/

Good luck 😉

As already reported, the Sierra update just moved a little bit the problem: Aperture won't crash any more upon pressing the "f" key, it will crash when exiting the full screen mode. It looks like the update changed the "sensitivity" of the OS to errors, rather than curing the problem.

I was eventually able to rebuild my Aperture library and make it work under Sierra !

For me the problem was that in some photos I made use of the custom fields (like "website reference").

After deleting the information inside "website reference" for all photos (one by one !) and then rebuilding.

oraziosimone

You mention 'Custom Field'

Try using a field name that does not contain a 'space' character

Hope this helps

Brian

Actually the offending field is "WebsiteReference" (no spaces) - I wrongly called it "custom" because I think it is not "exposed" in the IPCT views proposed by Aperture by default, but I did not "create" it as a new IPCT tag myself. By deleting information from this field (which was tedious since I did it one by one, no way to do it via "batch change") then I could successfully rebuild the library and it worked. I have other IPCT tags containing a space (like "Image City", or "Contact Email(s)") which are not causing any problem.

So maybe this is the message to anyone (like me) which was trying to rebuild the Aperture library and still was getting the same error after rebuilding. Hope this helps.

Simone

Here on 10.12.1 on a Late 2013 MBP. Still get the "crash" when I try to import. I deleted the prefs file and still have the problem. This was my first attempt to "fix" Aperture. Hadn't been using it much and put off dealing with the problem.

Did you try importing? I haven't read this entire thread, but Importing and Full Screen have been problems for many.

Yes, I did.

I wrote it.

import issue is much worse because it lacks the functionality, not work efficiency.

I have no option panel on Import scene, so I can't control what/how to import.

I saw the no functionality on import too, and I use that feature.

I tried importing my Library into a new Library and Aperture became non-responsive. Could have been busy, but Activity Monitor didn't think so.

Since I have my Aperture Libraries on a separate disk, I'm installing El Cap on that disk. Won't be fast but I know it's time to move on. Means rebooting to use Aperture which isn't wonderful.

Unfortunately I've lots of reorganizing to do. I'm going to look at Capture One.

Another alternative is to get one of the virtualization programs and have El Cap and Aperture installed there. But I've got an SSD and space is already an issue.

Haven't ruled out downgrading.

ogawa9 wrote:

Yes, I did.

I wrote it.

import issue is much worse because it lacks the functionality, not work efficiency.

I have no option panel on Import scene, so I can't control what/how to import.

Have you tried any trouble-shooting in Aperture? The Import panel never stopped working for me; It might be a problem with corrupted preferences files interfering in your case. If the Import panel does not work it used to help to remove the Aperture Preferences and the Aperture Presets.

I'd try to take a note of all preferences settings, quit Aperture and then remove these files from the user library:

• The preferences and Container: ~/Library/Containers/com.apple.Aperture/OldData/20130315T064748.72+0100/Library /Preferences/
• The Import Presets: ~/Library/Application Support/Aperture/Import Presets.plist

Then restart the Mac before trying again.

The procedure is described here: https://support.apple.com/en-us/HT201289

Look at the paragraphs:

• Steps to reset preference settings
• Move the user created presets, keyword lists, and so on...

Whilst trying to work with my AP-Library from El Capitan in macOS Sierra, I was running more or less into the same problems like described in the previous posts.

1. Full screen opened (hitting F), but crashed whilst hitting F again to close full screen
2. Batch editing (Command-Option-B) did not show the window
3. in the tab „Info“ the window for preferences (the gear wheel icon) didn’t open
4. etc.

If I open a new library in AP in Sierra everything works fine. Oho!

If I try to merge an (El Capitan) AP-library into the new created library in Sierra all above mentioned problems were the same…

Creating a new AP-library in El Capitan and open this one in Sierra works fine! Oho again.

Therefore obviously something must be a wrong in the develop or metadata part of my main aperture library used in El Capitan…

Trying a test library with a few photos and different applied metadata or develop settings brought the solution - at least for me. The custom metadata fields are leading to the suspicious problems described above.

Not knowing if there exist different problems caused by hardware or macOS Sierra leading to the AP-problems for other users, but give the following tipp a try.

1. Create a new AP-library in Sierra
2. Import 3-5 photos (only importing, don’t add metadata, no develop settings, therefore check your import options)
3. try if your specific problems still occur (e.g. hitting F for fullscreen, Command-Option-B for batch editing)

If everything works fine now, do following

1. Open your main AP-library
2. Create a new project and name it whatever you like (e.g. Sierra Test)
3. Search for custom metadata fields using „Aperture Metadata“ and „is not empty“
4. Copy some of the photos found (at least one) into your new project (Sierra Test)
5. Export the project folder as a new AP-library (e.g. Sierra Test Library)
6. Open the new AP-library (Sierra Test Library)
7. Try if your specific problems still occur (e.g. hitting F for fullscreen, Command-Option-B for batch editing). I sure it will
8. Go to tab „Info“, hit the gear wheel icon, go to „manage custom fields“ (sorry but I only work with german version; therefore it may be named a little bit different in english version, but I’m sure you find it)
9. Delete all custom fields
10. Try if your specific problems still occur (once again e.g. hitting F for fullscreen, Command-Option-B for batch editing). I guess everything will work.

If everything works as it should, you have found your specific problem. Congratulations! Otherwise there must be other problems due to hardware or macOS Sierra which I am not able to detect (thanks god!).

Now open your main AP-library and !!! STOPP - DO NOT delete the custom metadata fields!!!. Please first think about if you need your custom metadata field data! If not delete them. If you need them, my suggestion is to copy them over to the keywords field. I will not describe this, as I assume you are a long time user and know how to do it. When you have finished, you should now delete your custom metadata fields. As soon as the last field is deleted, Aperture on macOS Sierra will work again as it should (and has yet running El Capitan).

There is one more thing ;-)

if you use smart albums AND have some custom metadata fields selected, please be sure to change your settings respectively to the „new home“ of your custom metadata field data…

GOOD LUCK

Thanks, this helped. I can now get the import dialog box. But if I try to use Metadata Presets and edit them, I get the weird Crash/Continue message. I deleted ~/Library/Application Support/Aperture/Metadata Presets.plist, but still get the Crash/Continue message. I was able to import.

I removed all the items at the top level of that folder (all a bunch of presets) and still can't use the Metadata Presets. I do use that one. I can live without it, but Batch Change still doesn't work—losing that is not acceptable.

Unless another fix shows up, I guess I'll be booting into El Cap which I installed on my Aperture Library drive since my SSD doesn't have room (or rolling back my MacBook Pro) for Aperture.

I had the problem with the Info panel crashing not being able to batch change only with the first beta version of Sierra. Once I had my system back on the official release the Info panel and batch changing are working, even the "Batch Change: Apply to original" and also batch changing of my custom fields.

Have you tested, if you can batch change in a new test library, now that you removed the presets? Sometimes a string with invisible characters in one of the IPTC tags is causing the problems with the Info panel, or illegal GPS tags from a GPS tracker, that adds out-of-rang values, if no signal can be received.

I forgot to mention that I worked from a clean install setup. Made a second partition on my internal hard drive and installed macOS Sierra and only Aperture just to check if it will still work. Further more updated meanwhile to 10.12.1. I did not test this on 10.12. (and now are not able to do it anymore). Don't know if this may be helpful.

But I agree totally with you. It is not acceptable working without Batch Changing. Maybe tipp of leonie will fix this (I have not tried).

sorry, I was to quick with my response