-
All replies
-
Helpful answers
-
-
Oct 7, 2016 6:20 AM in response to Ron Taube1by e2photo,Ron, Yes you can export your files to jpeg or tiff to preserve the edits, but if you just redo your previews as unlimited high quality, those are in fact highly quality jpegs that retain your Aperture edits. These can be imported into LR and you can either pair(stack) or leave unpaired with the original file. They show up with part of their name Aperture_previews.
I rarely revisit a picture more than 6 months old. First, I shoot everything in RAW format. Typically, once I am done working(editing) on a particular set of pictures, I export the keepers as high resolution jpegs and upload those to an online site(zenfolio) for people to view. What I have experienced thus far is if for some reason I need to reedit one of those pictures, it is much easier to simply reedit in LR because the quality of LR edits is much better than Aperture.
Recently I have started a major project of creating print albums of pictures that span from 2001-16. Each album will be a major theme, like an important family vacation, or sequential pictures of each grand child and etc. As I was looking at the various collections of pictures, I discovered that my editing style had drifted considerably over the years and this variation did not look good in a printed collection of pictures. The only way I could address this issue was to reedit them to a most consistent style.
When I evaluated Capture One 9 pro, I discovered that it would not import tiff files. Since many of my critical edits were tiff, this issue was a fatal flaw to Capture One as a legacy retention application. This pushed me toward LR, but as I began to explore LR functionality during the free trial period, I really began to understand how much better it was than Aperture. I am very thankful that I started my transition in Sept of 2015 and just finished the final steps in the past week of having both LR and Aperture pointing to the same original files so when Aperture is completely dead, I will still be able to view and work on all of the pictures, if need be. BUT, over the past year any new pictures have never touched Aperture, thus forcing myself to learn a LR workflow.
-
Oct 7, 2016 6:33 AM in response to e2photoby Ron Taube1,Thanks very much. I didn't understand what you meant by redoing previews as unlimited high quality but I'm just glad that I can export my edited saved photos to LR. I have only used LR in a very minor fashion so it will be mostly new to me I have version five and am planning to get version 6 soon I'm guessing that as I get working with the importing of my aperture photos that what you are saying will be clearer to me. Thanks Again
Ron
-
Oct 7, 2016 9:04 AM in response to Brian O'Reillyby Proggie,Hi Brian,
Here's a library with one image that crashes for me going in/out of full-screen: 32.6MB zip file
https://dl.dropboxusercontent.com/u/98285/crashing.aplibrary.zip
-
Oct 7, 2016 9:27 AM in response to Proggieby jfaughnan,If it's a RAW image can you have Aperture update the master? (It's a menu option that has Aperture use newer image processing on older RAW images) Then retry ...
-
Oct 7, 2016 9:47 AM in response to Proggieby Brian O'Reilly,Proggie
Thanks for the test library
I have tested it on a machine with the following specs:
When the Library opened I got this dialogue box
I selected the following option - Rebuild Database:
This dialogue can also be 'forced' with 'Command-Option' as Aperture starts
When the Library opened it worked perfectly when I selected the shortcut "f" to go to full screen
Same when I used the normal Menu - View -> Full Screen
As some Users had mentioned problems with the "w" shortcut - I tried that as well - No Issues
Sorry I can't reproduce the fault - but perhaps it points to some other issue on the system which can be fixed
Let me know if I can run any further tests for you
Best regards
Brian
-
Oct 7, 2016 11:20 AM in response to Brian O'Reillyby Proggie,Hi Brian,
Thanks for trying. I've rebuilt many times (including right before uploading the library) and it didn't help
-
Oct 7, 2016 12:52 PM in response to Proggieby jfaughnan,try copying the library to a new location on your drive and running it from there (just make a copy). Could be a bad sector ...
-
Oct 7, 2016 1:21 PM in response to Nikontravelerby agoodmanwa,To All,
Here is some new information I just stumbled upon. The MacBook Pro (early 2011) I use for Aperture has two internal hard drives. The boot drive (SSD 500 gig) has Aperture and my main Aperture library on it and I am getting the "Internal Error" crash when toggling full screen (F) or trying to access the Info tab. All other functionality in Aperture seems to be OK. The second hard drive (750 gig platter) contains several other Aperture libraries I also use. When I switch to any of these other libraries, I can toggle full screen (F) and access info WITHOUT the "Internal Error" crash. I have not yet tried moving my entire main library to the 750 drive but maybe what I have found is significant to the main issue of Aperture in Sierra. Does anyone have any thoughts or comments on what I have found?
-
Oct 7, 2016 7:46 PM in response to Nikontravelerby Vincent Nall,I wish I had never upgraded from El Capitan to Sierra. After dropping Aperture, I feel that Sierra is another thumb in the eye from Apple since I can't use Aperture with Sierra. I have tried multiple work arounds and nothing seems to get me to where I can use Aperture with Sierra. I am looking to get rid of Sierra and get back to El Capitan. With about 250,000 photos in Aperture, it is far more valuable to me than anything Sierra can offer. Anyone have any suggestions on how to get back to El Capitan?
-
Oct 7, 2016 8:15 PM in response to jfaughnanby Proggie,Copying the library didn't help. But what DID help at least with the library I posted on dropbox is one or both of rebuilding the library and rebuilding the preview.
I will try this on my real library and see if I can make it work.
-
Oct 7, 2016 8:20 PM in response to Vincent Nallby Ron Taube1,HI Vincent. I'm sorry this is happening to you. I am in a similar situation with lots of photos in aperture. I havent upgraded to sierra yet and you are my best reason for not doing so. I wonder if Apple might help you with a clean install of El Capitan? Also I have read that some macs work better with aperture in sierra than others. How old is your Mac? i read some where that the newer macs work better. I might be wrong here but I thought I read that. Anyway please keep us informed of howyou solve this. I'm assuming you will. Ron
-
Oct 9, 2016 9:25 AM in response to Ron Taube1by Vincent Nall,This is the configuration that no longer works with Aperture after upgrading to Sierra.
I tried the iMac 27in we have in the office downstairs with El Capitan and Aperture works fine with El Capitan.
So I am moving this computer up to my office and spent another 1,600 at Apple yesterday on a fully loaded 21.5" to replace it downstairs.
Now, how to rearrange my office to add the add'l 27" so I can work on my photos with Aperture. I WILL NOT UPGRADE THIS 27" TO SIERRA.
-
Oct 10, 2016 1:52 AM in response to Vincent Nallby Siggi52,Hello,
first I have to say, I have also problems with importing picture and the full screen modus as most of you. I must say that I store only JPEG's, no RAW's. Here my configurations
Then I build a new library with only 60 pictures, all new JPEG and it works!
This morning I tried, with a test library, to recover the library from the back-up file and it works too. Now I exported a project from my real library as a new library and it did't work. Then I deleted this library and made a new one from the back up of this and it works
Could that be the solution?
Regards,
Siggi
-
Oct 10, 2016 2:02 AM in response to Proggieby Brian O'Reilly,Proggie
Glad you are making some progress - let me know if I can assist further.
As a general note to all fellow Aperture Users:
It seems there is a big difference between what some users are experiencing with Aperture 3.6 and MacOS 10.12
To recap - I have a clean install of Aperture 3.6 on MacOS 10.12 on the following machines
MacPro 2012 - 64 Gb RAM
MacPro 2012 - 48 Gb RAM
MacPro 2010 -20 Gb RAM
MacPro 2010 -16 Gb RAM
Mac Mini Server Mid 2011 - 8Gb RAM
Mac Mini Late 2014 - 8 Gb RAM
MacBook Pro 17” Early 2011 - 16 Gb RAM
MacBook Pro 15” Early 2011 - 8 Gb RAM
MacBook Air Mid 2013 - 4 Gb RAM
MacBook Pro 15” Late 2014 - 8 Gb RAM
None of the issues mentioned other than the 'upside-down' previews in list view are present
So - I have to draw the conclusion that the issue lies with the installed version of 10.12 people are using or an issue with the Aperture database
If I can assist with tests of small databases on the above machines - then I am happy to do so
Over to you
Brian






