Nik collection crashes Aperture

Question

peteb1975 Author

Level 1

8 points

Nik collection crashes Aperture

Despite previously working seamlessly, for some reason Aperture is now unable to launch Nik Collection plug-ins, causing Aperture to close every time. I am unaware of any changes to my system which would result in this (although I am by no means an expert in this regard)

If it helps, then I can provide the error report from Aperture, but its pretty big so I havent pasted it in here.

Thanks in advance to anyone who can get me up and running again.

Pete

Mac OS X (10.7.5)

Posted on Dec 3, 2013 4:44 PM

Reply

Answer 1

Dec 3, 2013 5:25 PM in response to peteb1975

Are you still on 10.7.5, or are you using newer version of OS X (and thus Aperture as well)?

There are some reports of people having issues with Nik with Aperture 3.5.1, though it's not crashing. Are you on the latest version of the Nik collection?

Reply

Answer 2

peteb1975 Author

Level 1

8 points

Dec 4, 2013 2:15 AM in response to William Lloyd

Thanks William

I am still on 10.7.5.

I have updated Aperture as far as is possible with OSX 10.7.5.

I am not sure how to update the Nik collection??

Pete

Reply

Answer 3

peteb1975 Author

Level 1

8 points

Dec 4, 2013 4:13 AM in response to peteb1975

Some additinoal information:

I am working on a Mac mini running OS X 10.7.5. I am using Aperture Version 3.4.4 (digital camera RAW 4.08 - Build 707.1).

I am unsure which version of Nik Collection is installed on my machine but I originally bought and installed the package in about May 2013 - I am not aware of it updating since then (unless it does so automatically with no warning).

Reply

Answer 4

Dec 4, 2013 9:29 AM in response to peteb1975

You can download a newer version on their web site:

http://www.google.com/nikcollection/

Reply

Answer 5

peteb1975 Author

Level 1

8 points

Dec 22, 2013 9:44 PM in response to peteb1975

So far no luck.....I was in daily contact with Nik help desk, which took an annoyingly long time to conclude that they did not know what was happening. This has been with the 'engineering team' for >10 days who are working on a fix.

It seems unilkley that it will be resolved this year.

Reply