So has anyone tried this?
Weird, for some reason I don’t see the content of this post, just a blank field.
Sorry yes it workes like a dream
Can others who have moved to Sierra comment on how aperture is functioning?
I am not so lucky…
I upgraded yesterday to 10.12 and started using Aperture today. I am getting an error message when I click on the Info tab in the inspector panel (docked) and at other various times. The error states that something bad happened and giving me the option to crash or continue working in the app. It also states that if I continue, that it may not be stable. If I click continue, Aperture appears to work okay, but this is not a good start.
I have repaired my library a few times and it seems to have no effect. The Info tab error is consistent.
nMacPro, 16GB RAM, Library is about 90,000 images referenced and located on an external RAID 5 via TB2.
Sierra causes Aperture to crash badly when going to full screen mode. Hitting the “F” key or choosing full screen will cause the program to crash to a full black screen. Then you will have to force quit. Upon restarting you will get an error message and have to rebuild your library. So do yourself a favour and don’t hit the “F” key or go to full screen
Well, I guess this is The End for Aperture (it was great as long as it lasted). I also get a “Internat Error” clicking on the Info tab - and also when trying to make an import from a card.
To bad - you have been a great friend :(
I’ve been running Aperture all through the public beta testing and updated to the final official release available to all. It continues to work as well as it did before this release. I have seen that error/unstable state message too but not just in Aperture. Believe it is a wider OS bug. My tabbed inspector button is fine. I have encountered the black screen during full screen but came across that intermittently pre 10.12 so do not thing it is a new issue. I think it started to appear with 10.11 and is related to the re-configured spaces implementation. With quitting I was able to resolve it but I think I also worked out another way - it might be something to do with going to Apertures normal desktop space (I work with multiple desktops) and a stray full screen toolbar window or something being there.
Not the end just yet… but would suggest a fresh re-install for those with consistent crashing.
Still there is hope!
I tried Aperture on my MBP (also Sierra) and have no issues with the info tab or importing :) Will do further testing with my iMac tomorrow (holding my thumbs!)
I removed two plugins: Catapult and Perfect Mask, which seems to have solved the problem with “Internal error” when clicking on the Info tab.
My guess is that it’s the Catapult that is the bad guy - I don’t use these plugins anyway. Now I’m a happy Aperture user again :=)
Internat error is back (grrr..). Have removed all plugins but it does not help this time.
Maybe time for a fresh re-install. I remember being able to export keyword list but not sure about export preferences and other settings you might want to keep without re-doing. Sure a little search would tell you which files to keep so re-install is hassle free.
I have been doing some testing and still cannot get it to work.
I re-installed the app, removed the preferences, App Support (User), and App Support (System) and nothing has worked. I also did a full database Rebuild (with a clean app and preferences), which did not help.
If anyone has any troubleshooting suggestions that I have not mentioned, let me know. I really want to get this working again. I will start looking at other options, but will wait until after the first OS update to see if it is an OS bug.
Who says you have to update your OS every year? Just creates a mess with application and plug in software and is really only to sell iPhones. I’m not going beyond Yosemite. You can’t even create RAIDs with El Capitan because they basically dumbed down Disk Utility to the point of uselessness. The iPhone and iOS is leading OS X now “Mac OS” and the Macintosh around by the nose. Have two nMP 2013’s that are running Yosemite and 3.6. One is dual boot 10.9.5 and with Aperture 3.4.5 as well . Other downgraded from El Capitan which I left on a 100 GB partition. Just bought it before Sierra, which I will never run. 1 TB SSDs on both. Also Macbook Pro Retina 2015 Yosemite and Aperture 3.6. Aperture will be my go to for quite a while. Have no real use for Photos. Does not meet my needs. Snapshot shoe box. Have new Capture One, great RAW processing, but nothing has it all together with a DAM and publishing like Aperture but I see it as the future. Apple has created a situation where I probably won’t buy a new Mac until I have a new workflow, and I haven’t found it fully yet. These will last at least 5 years if necessary with current software. Nice going Apple. Used to buy new Macs often. Sold 150 as and Apple Video and photo VAR. Now in preservation mode. Do like my iPhone 6S 128 and my wife likes hers. So we’re fixed for Apple for quite a while. How about a self driving car for the management to drive away in? Watch out for left turning vehicles.
May be giving you a call re consulting, Joseph as to a way forward long term. Manage several clients as well. Some I have advised to stay on 10.6.8 until their computers die. Most stable system Apple ever developed. Before everything had to be Cloud based. They are heavily dependent on the old version of Pages which was screwed up for iPhone compatibility. Page layout a mess on the new versions.
I created a new library and imported 3000 images. This seems (holding my breath) to work. Something must have been broken, and neither of the Library repair tools worked.
I lost all edits but keywords and star ratings are still present. But, this can be a “good” thing - now I can rethink my library structure.
Glad you have it working again but shame about the edits. If you still have a backup of your previous library you could try selecting all the images and then exporting as a new library and then opening that version and see how it behaves. Maybe worth a shot if it saves you redoing those edits.
I just exported a few projects from my main library into a new Library, and the problem still exists. I then created a new library from scratch and imported a library of edited images (exported from the main library) and it still crashes.
The only way I could get it to work is to create a new library and import RAW images. In that new library, I have made some edits as I would normally do and it still fine.
Looks like you’ve given it your best shot. Hope the stability continues.
One observation, when working with the new library, the progress dialog (when quitting) in no longer blank ;). And Aperture feels a lot snappier then before.
Very jealous. Mine remains blank when in non-full screen mode but does work properly when quitting from full screen mode (was it always so?)
I noticed that as well. Everything happens at the speed of light.
I wonder if that is a result of 90,000 images, or if there is a problem in the database.
…a problem with my database.
I had all of the errors others were reporting. Used App Cleaner to delete everything associated with Aperture and then reinstalled the app. Haven’t had problems yet but I haven’t been using it much for the last week.
Digital Media Specialist
College of Education
University of Illinois
Champaign, Illinois 61820
Have tried using Aperture more since I reported my solution. Well it was not a solution after all. Still having the errors and crashing problems. Guess Aperture is dead as of 10.12.
Hi Bobmax 48
when you upgrade to to 10.12 did you do a clean install or an update of exiting Os
I used the a usb clan install and all is working fine
maybe you have some old plugins causing you problems
for usb install look at http://diskmakerx.com
Yes I did a clean install.
I’m not at my regular computer at the moment. But do a search on Apple Discussion groups at apple.com. Several people have succeeded in getting rid of the Continue/Crash dialog, and the Batch Change and Import problems. I’m still in the process of importing a large 900GB library. Smaller libraries are working, but until I get the large one imported and use Aperture I won’t know for sure.
From memory, the main problem seem to be with Custom Metadata. Make a copy of your El Cap library and in El Cap Aperture remove Custom Metadata fields (I think you see them in the Info sidebar and you get to them with a gear widget. You will lose that information.). That library can probably be opened in Sierra without problems.
You may need to delete ~/Library/Application Support/Aperture/Metadata Presets.plist (or better move file to temporary place while Aperture is not open, then relaunch. If need be you can move the temporary file back). I didn’t see any effect from doing this. I did this early and it solved some problems, but not all.
Some people have created a new library in Sierra and imported their original El Cap library into the new library.
I hope to come back and clarify when I get back to my main computer.
I never used the Custom Metadata fields. But I will try to create a new library and see if I can import the older Aperture library. I am not ready to use Lightroom. Instead I might use Keyflow Pro since I do lots of video also.
Some, I hope, relevant observations regarding Aperture, Sierra and Joseph´s recommendation to stay with Aperture for now. That is: do not migrate your library to Lightroom.
I have been running Aperture under Sierra since it´s introduction on an iMac Late 2013 and a MacPro Early 2008 without any more problems than I had under OS 10.10
and OS 10.11. Of course is this only valid with my workflow which only includes maybe 80% of Apertures functions. But on the other hand ….I do use plug-ins from
Noiseless CK, Intensify CK, Snapheal CK, DxO ViewPoint 3, Aurora 2017 and, of late, Luminar without additional problems.
This adds functions to Aperture making it a relevant tool for raw photo editing, and it´s still the best image cataloguing database available. (Yes I have Lightroom 6 on my computers too
and with the same plug-ins.)
I did a fresh install which had a few issues, first no full screen without crashes, and my presets wouldn’t persist past a quit of aperture.
I found the issue though… the prefs file had the wrong permissions… may be a more general bug in 10.12, gave the user account access and works fine…
life is never simple
I’ve been looking around trying to solve another problem and remembered reading somewhere that 10.12.2 fixed the full screen problem
Anyone else having trouble with their Facebook account and Aperture? I get an unknown error try again later message in the account settings in Preferences and when I try to upload to FB the login dialogue pops up with a similar message. Flickr account continues to work.