Will Aperture 3.6 work in Mac OS Sierra?

This is interesting find. Now here is something you may try and report back. If one creates a new library in Sierra and then "Imports" an entire old library created in previous OSs, Do the crashes stop?

After following this thread for a while, I cloned my Late 2013 iMac drive to an external, and installed sierra on it.

I loaded up a small test library in Aperture on Sierra and when it loaded (the external is quite slow...), i pressed "F" and got the dreaded "Inconsistent State" message.

I also tried on my Mid 2012 MacBook Pro and my wife's 2015 MacBook Pro. All had the same result.

So I tried the suggestion to create a new library in Sierra, and then import the crashing library into the new library.

I'm delighted to say, it worked! No crashes when entering full screen mode at all.

I tried a second small library and it also worked without problems.

I tried the original, crashing library, and it still crashed. Then I tried to open the library with command & option pressed to bring up the "Photo Library First Aid" window. I first tried "Repair Permissions", that didn't help. Neither did "Repair Database". But when I tried "Rebuild Database", the library would load and enter full screen without a crash.

The ultimate test will be to try a backup of my main library... It's a 1TB monster, and I'll need to find some space to hold the 2nd copy, if I have to do the import into a new library trick. Maybe this weekend...

But I'm happy to say, at first glance it looks like Aperture & Sierra will be working for me, for a while longer at least.

I sympathize with those that it doesn't work... Maybe try the import into a new library method. Maybe it will work for you. I hope it does.

Thank you for testing on a Mid 2012 Macbook Pro. (is it a retina?) I've been waiting to hear about a test with such a machine. Do my specs match yours or do you see anything you think would be concerning (if you know)?

MacBook Pro (Retina, Mid 2012), 2.6 GHz Intel Core i7, Intel HD Graphics 4000 1536 MB

Alan,

Could you indicate which graphics card you're using? What I'm hearing from Topaz is that the Intel 4000 is playing well with Sierra. I have both the Intel 4000 and the NVIDIA GeForce GT650 and it's the GT 650 that's crashing the program. Since Aperture and the Topaz plug-ins are graphics intensive, my early 2013 MBPro Retina always uses the NVIDIA card since its the higher spec'd graphics card of the two.

I've contacted NVIDIA and their response was as follows:

"We don't support drivers for the GeForce 650M on Apple computers. Apple customizes these chipsets from NVIDIA. They customize the vBIOS and for support you'll have to contact Apple."

Today I received this from NVIDIA:

"Sorry for the late reply, Looking through the issue being reported here there isn't anything I can suggest to resolve this currently, I'll have to get a bug filed for the QA and Dev teams to investigate further.

If more information is needed by the teams i will be in touch."

xtravoice wrote:

Thank you for testing on a Mid 2012 Macbook Pro. (is it a retina?) I've been waiting to hear about a test with such a machine. Do my specs match yours or do you see anything you think would be concerning (if you know)?

MacBook Pro (Retina, Mid 2012), 2.6 GHz Intel Core i7, Intel HD Graphics 4000 1536 MB

My Macbook Pro is not retina. I did not try it again with Sierra after I got it working on my iMac.

I'll try to check it this weekend, if I have time.

leicaman94044 wrote:

Could you indicate which graphics card you're using? What I'm hearing from Topaz is that the Intel 4000 is playing well with Sierra. I have both the Intel 4000 and the NVIDIA GeForce GT650 and it's the GT 650 that's crashing the program. Since Aperture and the Topaz plug-ins are graphics intensive, my early 2013 MBPro Retina always uses the NVIDIA card since its the higher spec'd graphics card of the two.

My iMac, where it is working after importing to a new library or Rebuilding the database has an NVIDIA GeForce GTX 780M.

Any thought on this configuration?

MacBook Pro (15-inch, Early 2011)

2.2 GHz Intel Core i7

16 GB 1333 MHz DDR3

AMD Radeon HD 6750M 1024 MB

Intel HD Graphics 3000 512 MB

Hi,

I have the "Internal Error" crash problem too. I tried to export singular projects one by one as separate libraries. Then rebuild each single library. Most of them will work after rebuilding. A few persist in giving the crash error. This happens either by pressing the "f" full screen mode and/or by asking for the "batch change" (Command+shift+B). While I can live without full screen, to me it's a must the "batch change". This happens both on a 11" MacBook Air (late 2014) and on a 20" iMac (2012).

I am going to make a new library for the new stuff (it seems to work), and will look at the old library for the old stuff, without going full screen.

There is another application having the "internal error" crash. I use Evernote with the Presentation Mode (a subscription feature) and within Presentation Mode I could right-click and ask a PDF copy of the presentation. This is now crashing with "internal error" while saving the PDF (although the "details" of the error are different w.r.t. the Aperture internal error).

Re: Sierra, I have tried a number of different ways to get it to work with Aperture without crashing and without unacceptable buggy responses.

The only method that works for me is to: export a gallery's Version photos (not as a gallery) and then import the version photos into a new Aperture file.

I have tried this with three galleries (1 at a time) and have not see any crashes or problems.

I am no longer using Faces or Locations, and limiting use of Keywords in case they are part of the problems I have had in using Aperture with Sierra.

So now to move only the files I need because I have over 200,000 photos in Aperture.

Don't do it, or if you did it- go back to a time machine back up with El Capitan. I've been using Aperture since it came out in 2005, and I cannot imaging my career as a professional wedding and headshot photographer without it. I'll try LR over the winter because I have no choice. But the Sierra is slowing down Aperture and you cannot batch rename.

THANKS for all the testing in here. I'm really happy to have found this tread!

It seems we are a lot in the same "aperture boat" here. 🙂

I have tryed to make a new library and import some pictures into it. And as you write, Allan, - now Aperture seems to work like in the good old days. 😀 GREAT!!

I have not (yet) tryed to import my "old" complete library into a new library, so I don't know if it will work?

I simply don't know how to import all my pictures (my old library) into a new library, so that everything looks the same, and all projects, albums and so on, is in the same order. Could someone please help me here ...?

(Today I ordered a new 3TB external hard drive, so I'm ready 😉)

My setup looks like this:

Macbook Pro 17" late 2011

2.4GHz intel core i7

16GB 1333 Mhz DDR3

Intel HD Graphics 3000 512 MB

I have 2 hard drives in. One 1TB SSD hard drive that holds all programs including Aperture, and one "normal" 1TB hard drive that is just for Aperture library.

Thanks 🙂

Steffen / Denmark

Just to add one piece of information. After rebuilding the Aperture library all references to referenced files were lost. Precisely the Volume information got lost. I had to reconnect files accordingly.

Has anyone tried today's Sierra update?

Sort of- but don't do it. I did on my Macbook Pro (my main workhorse for weddings) and it's a 2015 fully loaded. Once I did the update I noticed files from my D5 were processing a little slower, but when I went to batch rename a window showed up that I've never seen before which made you either crash or continue. Either way, I could not batch rename and that's a big a part of my workflow. However, on my Mac Pro at my studio (and older version 2008 tower) it's perfectly fine. But that computer is not compatible with a lot of the new Mac features, yet will run Sierra. If a lot of us complain to Apple, they MAY just bring back Aperture. Let's only hope, I hate LR....

on a late 2014iMac (4ghz i7) the update seems to have solved the "f" key full screen crash problem. Tested and so far so good so crossing fingers it holds up.

Doesn't fix it the full-screen crash for my Late 2013 rMBP. It does behave differently. Before it would crash going IN to full-screen. Now it crashes coming OUT of full-screen.

May I suggest going back to a time machine back up from El Capitan. DO NOT listen to Apple when they say that won't bring the computer back to the operating system- it will. I spent 5 hours the other day deleting my hard drive, reinstalling a previous OS only to find out that when I did a back up to reinstall, it also did Sierra. I said F this, and I went back to a back up from a few weeks ago, and boom! Back to El Capitan no problem.