-
All replies
-
Helpful answers
-
-
Sep 20, 2016 11:43 PM in response to Proggieby léonie,That crash does not look good.
Try, to find out, if this problem is system wide, or happens only for your current Aperture library. It may be a data error.
- Create a new Aperture library for testing with a few test images. Does Aperture work for this test library?
- If Aperture is not working on your test library, log into the another user account and test there. Perhaps you have corrupted preferences files: Isolating an issue by using another user account
-
Sep 21, 2016 12:08 AM in response to léonieby Proggie,Created an empty library and imported one of the photos. Problem doesn't exist in this new library. I did rebuild the original library but that didn't help. I also tried starting in safe mode, but that didn't help either
-
Sep 21, 2016 12:14 AM in response to Proggieby léonie,Than you have probably items in your aperture library that cannot be processed. It might be a problem of corrupted media files.
Do you also see the crash, if you hold down the shift key while launching Aperture to defer the generation of previews?
-
Sep 21, 2016 12:56 AM in response to léonieby Proggie,The weird thing is that I exported the project that I last imported as a new library, then deleted that project from the mail library. I then opened up the exported library and showing an image in fullscreen also crashes there. So I thought that there must have been something specific to that project, so I opened up the original library that no longer contained that project and it still crashes! So the original library crashes, and the exported one crashes, but a brand new library with only a couple of images doesn't crash. For the record the exported library is only 10 or so images.
There are no previews being generated in both cases. And it only crashes when I press F to show (any) image in full screen, otherwise things work fine.
-
Sep 21, 2016 1:16 AM in response to Nikontravelerby In_between_dreams,I've issues with Aperture with the newly released Mac OS Sierra.
The application crashes when switching to 'F' full screen. Also when using 'W' to switch between the tabs. I have forwarded a crash report, from the pop up dialogue window in Aperture.
"Internal Error"
An uncaught exception was raised. Choose 'Continue' to continue running in an inconsistent state. Choose 'Crash' to halt the application and file a bug with crash reporter. Choosing 'Crash' will result in the loss of all unsaved data."
I will try again later...
I was using a MacBook 11" 2014 (maxed). I won't be updating the OS on my MacPro until I find out what's happening with Aperture.
-
Sep 21, 2016 2:27 AM in response to In_between_dreamsby In_between_dreams,.... just to add
There is only a handful of images on my MacBook Air / Aperture (80 approx). I only use my MacBook Air to offload images from my cameras 'in the field' so that I may start culling & key wording before transferring the projects to the MacPro at base where the heavy lifting is done.
The Loupe appears to be a little 'sticky'.
I've tried going to 'Full screen' using the Menu & avoiding the 'F' key.... still an issue. The 'Internal Error' will appear. If you choose 'Continue' Aperture will behave as normal..... until you get the 'Internal Error' again when tabbing the windows. Aperture will eventually lock up, which then requires a 'Force Quit'.
Some images appear now with "Unsupported File Format', after closer inspection these are images which are being sync'd with SmugMug.
No doubt there are more issues with Aperture, I thought it best to get some feedback back to the Aperture community at this early stage.
-
Sep 21, 2016 7:55 AM in response to In_between_dreamsby Proggie,So looks like you have the exact same problem as me (see posts just above yours). At least I'm not the only one. Sigh...
-
Sep 21, 2016 9:57 AM in response to léonieby John Purlia,I've not yet completely convinced myself, but it looks like the previous problem with brushing when a Burn or Dodge adjustment is present on an image may, in fact, be gone. This would be remarkably good news, indicative of a problem within El Capitan and not Aperture! I'll have to notch out some time to do side-by-side tests with Aperture under Sierra and El Capitan to verify, but it would be a very welcome relief to no longer have to ping pong my process between two versions of the OS.
Are we building an extensive list anywhere of known differences between Yosemite, El Capitan, and Sierra?
-
Sep 21, 2016 10:11 AM in response to John Purliaby Marc P,There is (already !) a new Siera beta released today... Its probably sound to wait a few weeks before updating for us Aperture lovers...
-
Sep 21, 2016 10:35 AM in response to John Purliaby léonie,Are we building an extensive list anywhere of known differences between Yosemite, El Capitan, and Sierra?
You could start a discussion to collect the known problems
-
Sep 21, 2016 11:01 AM in response to Proggieby Proggie,Seems it's not about any specific photo going into full screen that causes the crash. I can just have a project view open and go into full screen and it will crash. It will also crash when trying to open Metadata presets, and the Inspector HUB. But again it only happens in my main library, and the one I created by exporting a small project. A brand new library with a couple of images does not have this issue.
-
Sep 21, 2016 11:44 AM in response to Proggieby léonie,Proggie wrote:
Seems it's not about any specific photo going into full screen that causes the crash. I can just have a project view open and go into full screen and it will crash. It will also crash when trying to open Metadata presets, and the Inspector HUB. But again it only happens in my main library, and the one I created by exporting a small project. A brand new library with a couple of images does not have this issue.
Then you may have corrupted media files in the library or the library needs fixing.
Corrupted media files can be prevented from being processed by launching aperture with Shift key held down during the launch. That will defer the generation of previews. Did this test have any results?
Did you try to repair or rebuild the library?
-
Sep 21, 2016 12:26 PM in response to léonieby Proggie,Holding shift on launch doesn't help (no previews to generate anyway). And I did repair permissions and rebuild a couple of times and didn't help either.
And another user above has exactly the same problem, so it seems it may have something to do with Sierra (and perhaps 2014 and older laptops) after all.
-
Sep 21, 2016 3:23 PM in response to Nikontravelerby agherrera,Just loaded Sierra and Aperture crashed right away. If you hit the full screen "F" key it seems to trigger the crash. Cannot get Aperture to turn on at all now, completely went to black screen and upon reboot "error in library" window shows up. Upon trying to rebuild permissions now on library, the progress bar hasn't even shown up. So total meltdown! BAD NEWS for Aperture!!! BOOO HISSS APPLE FOR DROPPING APERTURE!!!! PHOTOS IS A JOKE!
