-
All replies
-
Helpful answers
-
Sep 22, 2016 10:23 AM in response to Nikontravelerby léonie,I have plans to buy a Nikon DL24-500 camera when it comes out. It shoots Nikon .nef RAW. One of the other issues with continuing to use Aperture is that all Apple Raw updates will not work in Aperture as far as I know.
I purchased my current camera after Apple stopped the development for Aperture. But since the RAW support for new cameras is rnow eleased as updates to OS X and not to Aperture or iPhoto, Aperture can also use the RAW support.
I still can develop the RAW images in Aperture. It just requires to update to the most current macOS X.
-
Sep 22, 2016 10:27 AM in response to léonieby Nikontraveler,Thanks for the heads up
Good info. I am just so reluctant to upgrade either of my macs past Yosemite at this time. But that is good to know for future.
-
Sep 22, 2016 5:41 PM in response to Nikontravelerby dav,I have the suspicion that Apple has been moving from a content/media creation focus, to a content/media consumption focus. I believe I need to look elsewhere for a reliable future using pro tools.
-
Sep 22, 2016 8:04 PM in response to In_between_dreamsby MyndSurfers,I have the same error, which I have also reported on:
I am using 27 inch iMac 2010.
I have just installed Sierra Release version 10.12. With Aperture 3.6, I am receiving this notification repeatedly and consistently:
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 the Crash Reporter…..
The error is raised when I seek to IMPORT images. However, if I ‘CONTINUE’ the images import.
The error is raised if I try to alter an EXPORT preset. I am unable to adjust the export preset. Fortunately I have many presets setup.
This is the advice on the Apple Support site for addressing this kind of issue.
Get help with Aperture 3
https://support.apple.com/en-us/HT201289
As per above, I have now (a) Repaired, then (b) Rebuilt the database. Same fault results, as below. Aperture seems to possess most functionality, however, I remain ANXIOUS that my version of Aperture is on its last legs!
The Crash Report details are:
Exception Name: NSInvalidArgumentException
Description: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil
User Info: (null)0 CoreFoundation 0x00007fff8332f7bb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff97a9ca2a objc_exception_throw + 48
2 CoreFoundation 0x00007fff8324b6ad -[__NSArrayM insertObject:atIndex:] + 1389
3 RedRock 0x00000001036d339c +[RKPropertyMgr customInfoKeys] + 308
4 RedRock 0x00000001036d3741 -[RKPropertyMgr dependentKeyPathsForKey:] + 795
5 RedRock 0x00000001036d3948 -[RKPropertyMgr dependentKeyPathsForKeys:] + 201
6 Aperture 0x0000000102d14817 Aperture + 1640471
7 Aperture 0x0000000102d157bb Aperture + 1644475
8 Aperture 0x0000000102edf040 Aperture + 3518528
9 Foundation 0x00007fff84d2dc88 __NSFireDelayedPerform + 417
10 CoreFoundation 0x00007fff832aff44 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
11 CoreFoundation 0x00007fff832afbd3 __CFRunLoopDoTimer + 1075
12 CoreFoundation 0x00007fff832af72a __CFRunLoopDoTimers + 298
13 CoreFoundation 0x00007fff832a72f1 __CFRunLoopRun + 2081
14 CoreFoundation 0x00007fff832a6874 CFRunLoopRunSpecific + 420
15 HIToolbox 0x00007fff82846f6c RunCurrentEventLoopInMode + 240
16 HIToolbox 0x00007fff82846da1 ReceiveNextEventCommon + 432
17 HIToolbox 0x00007fff82846bd6 _BlockUntilNextEventMatchingListInModeWithFilter + 71
18 AppKit 0x00007fff80f3d5f5 _DPSNextEvent + 1093
19 AppKit 0x00007fff8164d8eb -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637
20 Aperture 0x0000000102ff0a81 Aperture + 4639361
21 AppKit 0x00007fff80f31fbd -[NSApplication run] + 926
22 ProKit 0x00000001043e339a NSProApplicationMain + 333
23 Aperture 0x0000000102b940b4 Aperture + 65716
24 Aperture 0x0000000102b93a44 Aperture + 64068 -
-
Sep 22, 2016 8:38 PM in response to MyndSurfersby jfaughnan,Anyone with an Apple ID can submit a bug report: https://bugreport.apple.com/problem/viewproblem
At least that's my understanding. You used to have have an associated dev account, but I think that may no longer be true.
No idea if Apple is interested in reports on Aperture, but if it impacts software other than Aperture they might be.
I'll be staying on El Capitan at least through July of 2017...
-
Sep 23, 2016 3:50 AM in response to Nikontravelerby Brian O'Reilly,Folks
As a long term Mac and Aperture user - I want to make Aperture 'last' as long as possible
Following on from comments in this thread - I have quickly tested some of the mentioned 'bugs'
I have tested Sierra/Aperture as follows...
On a Mac Pro 2010 (5,1) - 16 GB Ram - ATI Radeon HD 5770
Clean install of Sierra 10.12
- Thumbnail are upside-down in list view
- With a Curve adjustment and then a straighten adjustment - the exported image is OK
- Brush adjustments - seem OK - no offset
- Link to Plug-in menu is OK - I used BorderFX as a test
- Soft Proofing does not work
- Full Screen (f) is OK - does not freeze Aperture
I do not wish to disagree with any of the issues reported by fellow Aperture users - but I am very keen to make a definitive demonstrable list of bugs that we may be able to get fixed by a future MacOS update
Please - if you want to assist in making such a list - please add to the above - or agree/disagree
Best regards to all fellow Aperture users
Brian
-
Sep 23, 2016 8:23 AM in response to Brian O'Reillyby leicanerd,Hello Brian,
thank you for posting your Mac´s specs. This could be very helpful to track down bugs to some hardware related issues.
I agree with your bug list and found that soft proofing works in the print dialog only.
The first time I hit f for fullscreen mode took a while but did not result in a hang. From then on it worked fluently.
I tested with a Macbook Air 2011, Intel Dual-Core i7 1,8 Ghz, 4 GB RAM, Intel HD Graphics 3000 (had still not the courage to switch my working horse MacPro).
Beta release notes of Sierra stated that Apple´s Developers worked constantly on weeding out Aperture bugs. So there is still hope...
Best regards,
Eberhard
-
Sep 23, 2016 11:18 AM in response to Brian O'Reillyby agherrera,Agree but what happens to those who are clearly experiencing bugs you seem not to be able to replicate. "F" key crash issue has been quoted by many in the past 24 hours and is still an issue on my machine to the point of damaging the library every time. Should keep it on the list as it exists... I would be remarking on it if it didn't.
-
Sep 23, 2016 1:46 PM in response to agherreraby Brian O'Reilly,Fellow Aperture Users
I agree that we should not dismiss any issue that any User is having with Aperture
If some Users are having an issue and other are not - then first we need to determine why this is the case.
Can Users who are having an issue with the Full Screen problem please advise other users of what the Spec. of their Mac is?
I stated the basic Specifications of the Mac I tested on.
I have an array of Macs and am totally willing to test on them to see if I can reproduce the problem.
"Agherrera" - what Mac are you using?
Best regards
Brian
-
Sep 23, 2016 3:00 PM in response to Brian O'Reillyby Proggie,MacBook Pro (Retina, 15-inch, Late 2013)
2.3 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 750M 2048 MB
Intel Iris Pro 1536 MB
-
Sep 24, 2016 10:07 AM in response to léonieby jfaughnan,Léonie, Aperture supports reprocessing old RAW images:
"When you start using Aperture, all of your existing images continue to use the previous version’s image processing, in order to preserve their appearance. Any of these images can be individually reprocessed to use the Aperture 3 image processing. You can also use the Reprocess Masters command in the Photos menu to reprocess selected images, projects, books, slideshows, webpages and web journals, Light Table albums, albums, and Smart Albums.
Reprocessing a large number of images can be a time-consuming process. Therefore, you may find it easier to reprocess images on an as-needed basis. For example, if you have five-star selects, you may decide to initially reprocess only those images. Images are not affected by being reprocessed more than once; if an image already uses Aperture 3 image processing, reprocessing it again has no effect."
I wonder if reprocessing old RAW images would make a difference in how Sierra works with Aperture. Just a hunch ... I haven't tried it. Maybe image issues are in the processed output that Aperture uses for some rendering.
For my uses I suspect reprocessing would be ok.
-
-
Sep 25, 2016 6:01 PM in response to léonieby e2photo,I have spent the past year migrating my main aperture libraries (2001-2015, 350,000 plus pictures) per to Lightroom cc. Almost done, but glad that I did. All my 'negatives' are pointed to by Aperture and Lightroom cc. Once done I will never revisit Aperture unless there is a critical emergency
-
Sep 25, 2016 6:27 PM in response to jfaughnanby benji888,I tried the link, states I must be a registered developer to report bugs there. Only other way is if I become a beta tester.
However, I think there is a way to report bugs, I just don't know if/when apple actually reads them. (Select Bug Report in "Feedback Type", which also tells you to give them your hardware and software configuration.) https://www.apple.com/feedback/macosx.html
^this method is limited to text only with a character count limit. No way to add screenshots or send crash reports.
