Will Aperture 3.6 work in Mac OS Sierra?

Tests were on 2 books within the same Aperture library on the two different Macs. I had now loaded in my main library (I do the books in my main library and export the book as a library for better control), and tested the PDF print (menu and button) and I get the same result. Tested three different books. This on my MBP. Main Library to big for MBAir without an external). Oh, I will attach a pic of the requestor I get after selecting SAVE AS PDF in the print requestor. After clicking OK, the requestor goes away leaving you where you were in Aperture (in the book screen). I followed the directions in the requestor (paper handling, etc.) each time, but the process always ends with the same requestor.

One problem that I do have and I don't think it has anything to do with Sierra because I had this before Sierra is that when I try to post to Facebook I get error messages and it asks for my name and password and when i enter it it still doesn't work.

There seems to be a general problem with Aperture and Facebook recently:

Re: Aperture and Facebook problems

The Final Cut issue is explained here: https://support.apple.com/en-us/HT203405

Look at the crash log. If it contain these lines, you are a victim of the Final Cut bug:

“Dyld Error Message:

Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager

Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture

Reason: image not found”

If not, you may want to start a new discussion with more details what you did before Aperture stopped working.

Apertur Evas on Sierra the same glitches as on El Capitan.

For Aperture you will gain nothing by upgrading, and I can use it as I could on El Capitan.

If you want the new features of Sierra, upgrade, but keep a full backup of your system, so you can revert to the previous system, if you should encounter unexpected problems, like incompatible device drivers for scanners or printers, older apps, that are no longer compatible.

See: https://support.apple.com/kb/PH25593?viewlocale=en_US&locale=en_US

You can click the "Report" button in the panel to see the report.

But also try to narrow down the problem, by checking if your library or or photos in the library are causing the crashes.

• To check for corrupted photos launch Aperture while holding down the Shift key. This will defer the creation of Previews. If Aperture can launch this way, you may have imported image files or videos that cannot be processed.
• To check for a library corruption, hold down the options key while launching Aperture and select to create a new library for testing. Does Aperture launch on a new library?

Edit with External Photo Editor not working. I've had Aperture running on Sierra for a while, but don't think used this feature. Does anyone else have this problem or is it working for them. Maybe I'm doing something wrong.

My external editor is Photoshop Elements 13. (I don't use an external editor much and lately have been upgrading Elements every two or three years. V. 13 is less than two years old. I'm thinking about some of the other photo editors, but as I don't use them much, I'm just sticking with something I know a little about.)

Hi There

Just did a check on 10.12.2 - all seems fine with my installation. Editing with 'External Editor' seems to work as it should

Is PhotoShop Elements actually showing in the Photos/Edit with menu item?

Perhaps re-link to PhotoShop Elements via the 'Preferences/Export/External Photo Editor menu...

Hope this helps, but please do report back with your findings

Brian

Thanks for responding.

"Is PhotoShop Elements actually showing in the Photos/Edit with menu item?"

Yes

I had reset in Preferences.

I have since noticed that it is creating a .tif file which shows up in Aperture viewer as another version, but Elements doesn't launch. Even if I launch Elements before, the photo doesn't load in Elements.

Since I know it works for some, it suggests something unique that I need to look at in my set up.

It might be the filename extension. My TIFFs are having a filename extension ".tiff", and are passed to PSE as ".tiff", but PSE is saving the edited version as a new file with the extension".tif" and Aperture does not recognize it. The PSE edited file is just wasting space in the library. PSE needs to replace the file that has been passed to it, with exactly the same filename extension. When I change the filename extension manually to ".tiff", Aperture can find it.

@léonie That's happening for me too. I don't remember having this problem with PSE before.

And if I ask it to save over (replace) the original .tiff, it doesn't. The changes are in the .tif. And the original .tiff is there unchanged.

And it's not trivial to find that .tiff, Aperture has created for PSE to work with. Search in System Files and then figure out which version is the one needed.

But PSE is not launching when the edit in External Editor is activated.

So there are two problems now—PSE not launching and PSE not saving correctly.

I need to try this with another External Editor.

External Editor works fine with Preview: TL;DR; I set the External Editor to Preview, selected Edit with External Editor, the file opened in Preview, I made changes, saved, went back to Aperture and the changes were there.

So PSE and Aperture aren't working well together. Not surprised since Adobe marches to its own drummer.

Unless I am missing something, to use PSE it is mostly manual except for Aperture creating a copy to work with.

One more push to move on, but I'll resist for a while since I don't use the External Editor that open.

One more push to move on, but I'll resist for a while since I don't use the External Editor that open.

I've moved on to Capture One Pro 10. It'll cost you about $300, but I'm loving the program. It doesn't have quite the polish of an Apple interface, but featurewise, it's Aperture taken to the next level. It's good enough for image management and it accelerates my processing speed while improving image quality.

The latest version 10.0.1 did a near flawless import of my largest Aperture library. I had some issues with the one done under 10.0.0, but I just did it again yesterday and it captured everything I expected it to capture from my old libraries.

Capture One Pro is on the top of my list, if I changed now it would be Capture One Pro. But I'm still waiting to see if Photos will do it for me. My needs aren't great, but one of the reasons I'm using Aperture is that when Aperture came out iPhotos wasn't quite enough. I'm just avoiding the pain of changing over. The problem with Sierra got me to get my Aperture libraries cleaned up in readiness for changing over. I can't imagine going through another macOS change but we'll see.

Thank you e2photo for your reply. I will keep all that you said in mind. I have just finally updated to Sierra and right now and have no problems editing in Aperture. I think it's because i have a new late 2015 27" iMac. One problem that I do have and I don't think it has anything to do with Sierra because I had this before Sierra is that when I try to post to Facebook I get error messages and it asks for my name and password and when i enter it it still doesn't work. I suppose I should start a new topic on this. I have dabbled in lightroom 5 and am still not comfortable with it. I am using Affinity 1.5 right now as an external editor for aperture and there extensions also work in photos but I rarely use that app. Affinity is a great app but does nothing for storage issues. I know eventually Aperture will not work for me and i'll have to move on to something else but i'm hoping that some new app will pop up that replaces all of the features of Aperture. Thanks again.

Ron

As of this post, I have finally upgrade to Sierra by way of upgrading from a mid-2012 MBP to a 2016 15" Touchbar MBP with the 4GB Radeon 460 card. I also switched from Capture One Pro from Aperture in advance to prepare myself for the possibility that I'd need to make a clean break.

I'm happy to report that Aperture seems to run quite nicely on Sierra on my new MBP. It's actually seems to be faster than Capture One Pro, though I haven't really tried to push Aperture beyond some basic browsing. I have the LG 5K Ultrafine external display and when I'm working on photos, I use that as the main viewer and my MBP as the catalog browser.

In this configuration, or just external display alone, Capture One Pro seems to have a tough time driving all those extra pixels on the high resolution screen. Aperture handles the extra load better. I expect that Capture One Pro will improve in performance with upcoming revisions, but for now Aperture continues to show how much potential Apple left on the table.