-
All replies
-
Helpful answers
-
Oct 11, 2016 11:58 PM in response to freediverx01by léonie,For example, Apple's Sierra documentation states that "the UIAutomation framework is deprecated". I'm not sure what that framework was used for,
The UI Automation Framework is an interface for scripting an application by programmatically clicking elements in the graphical user interface. The main purpose of this framework has been testing the user Interface systematically. But it has been used for scripting applications as well, if the application did not offer any decent scripting interface.
This deprecation may effect plug-ins that rely on GUI scripting.
-
Oct 16, 2016 11:45 AM in response to léonieby leicaman94044,Léonie,
I'm dumping Sierra for Yosemite as I've had countless crashes when using a plug-in called Topaz Impression 2 in Sierra. The crash logs show that the NVIDIA GeForce 650M on my early 2013 MBPro Retina is the culprit. I've also noticed that Aperture often crashes in Sierra, probably due to the NVIDIA graphics card, when I move from the Adjustments to the Info Tab in Aperture.
I contacted NVIDIA regarding the issue and had a chat with a Supervisor. He claims that though NVIDIA makes the card, Apple customizes the vBIOS. Because of this NVIDIA doesn't support the card and Apple needs to provide the fix.
I don't see this happening as Apple is slowly abandoning Aperture... so I'm going to install Yosemite as I haven't heard of any issues in Yosemite.
Since a number of my Aperture files were processed in Aperture 3.6 while using the Sierra OS, is there a possibility that Aperture might not open in Yosemite since the files were processed while using Sierra, a newer OS?
I'm trying to resolve any possible snafus before going from Sierra to Yosemite.
I can't use Topaz Impression 2 at all in Sierra as it crashes due to the NVIDIA graphics and there is no fix for this.
-
Oct 18, 2016 4:56 AM in response to leicaman94044by Brian O'Reilly,Fellow Aperture Users
Those of you who have followed this thread will be aware that I have tested a new Aperture library on a variety of machines that can run Sierra.
In particularI looked for the:
Full Screen (f) crash
Change tabs (w) crash
On a new Library I could not make this happen
But - on my existing library I get the crash every time
Tried rebuilding Previews/Thumbnails/databases without success.
I also found another rather strange and obscure 'crash' situation - If you generate a new 'Custom Metadata' field that has a space in the description/name, then the crash occurs when you try to save the setting.
I will continue to test to see what is going on
However:
I am unsure as to whether Apple still monitors the input from users from the 'Provide Aperture Feedback' menu within Aperture - but I doubt it...
But - the feedback dialogues that occur when a crash happens seems to be more a feedback for Sierra - see below.
I strongly advise fellow Aperture Users to use these feedback dialogues to advise Apple of the issue
Maybe I am being optimistic that there might be a solution - but then I do believe in Fairies and Father Christmas :-)
Brian
-
Oct 18, 2016 7:33 AM in response to Brian O'Reillyby Nikontraveler,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? I would do this but I have not updated past 10.10.5 Yosemite.
-
Oct 18, 2016 8:02 AM in response to leicaman94044by léonie,Since a number of my Aperture files were processed in Aperture 3.6 while using the Sierra OS, is there a possibility that Aperture might not open in Yosemite since the files were processed while using Sierra, a newer OS?
it should only depend on the version of Aperture, not on the version of OS X. As long as you downgrade to a Yosemite version that can run Aperture 3.6, it should work.
when using a plug-in called Topaz Impression 2 in Sierra
I looked at the Topas webpage. The most recent update for Topaz Impression 2 I could find is for El Capitan. Perhaps a Sierra update of Topaz may fix ta part of the problem.
-
Oct 19, 2016 1:43 PM in response to Nikontravelerby Allan Hise,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.
-
Oct 19, 2016 2:33 PM in response to Allan Hiseby xtravoice,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
-
Oct 19, 2016 5:04 PM in response to Allan Hiseby leicaman94044,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."


