Nikontraveler

Q: Will Aperture 3.6 work in Mac OS Sierra?

Will Aperture 3.6 work in Mac OS Sierra?

OS X Yosemite (10.10.5)

Posted on Sep 8, 2016 11:19 AM

Close

Q: Will Aperture 3.6 work in Mac OS Sierra?

  • All replies
  • Helpful answers

first Previous Page 7 of 11 last Next
  • by freediverx01,

    freediverx01 freediverx01 Oct 5, 2016 9:56 AM in response to SEB575
    Level 1 (90 points)
    Mac OS X
    Oct 5, 2016 9:56 AM in response to SEB575

    Official support for Aperture ended with El Capitan. Considering how many people Apple has ****** off with this move, though, I would hope they'd be making some effort to avoid and/or fix any Aperture issues within reason. This is why it's so important for everyone to file a bug report. If you can't be bothered to file a report, then you have no right to be upset when they don't fix the issue.

  • by Ron Taube1,

    Ron Taube1 Ron Taube1 Oct 5, 2016 4:48 PM in response to e2photo
    Level 1 (74 points)
    Oct 5, 2016 4:48 PM in response to e2photo

    HI Can I ask you a couple of Questions? I am about to do the same, namely import about a terabyte of photos from Aperture to Lightroom 5  Can you give me any tips on how to do it?  I've pretty much reconciled that I won't be able to preserve the non destructive ness of aperture so I would probably just import all edited photos that are say flagged or starred Any tips?

    Thanks for your time.

    Ron

  • by SEB575,

    SEB575 SEB575 Oct 5, 2016 7:08 PM in response to freediverx01
    Level 1 (12 points)
    Photography
    Oct 5, 2016 7:08 PM in response to freediverx01

    well geez freediverx01..lets be a bit less snarky...cuz 1. I was a BETA tester for El Capitan so that I could help identify glitches and 2. I have sent in about 3 million reports...lets not assume too much, ok?

  • by freediverx01,

    freediverx01 freediverx01 Oct 5, 2016 7:54 PM in response to SEB575
    Level 1 (90 points)
    Mac OS X
    Oct 5, 2016 7:54 PM in response to SEB575

    I wasn't suggesting you didn't file a bug report. But a lot of people can't be bothered so I was using the opportunity to remind everyone why it's important to do so.

  • by e2photo,

    e2photo e2photo Oct 6, 2016 5:47 AM in response to Ron Taube1
    Level 2 (170 points)
    Oct 6, 2016 5:47 AM in response to Ron Taube1

    The first thing is make sure you understand how LR works with the catalog (same as Aperture Library).  I spent about a month working on individual projects in Lightroom to learn basic Lightroom, but also to learn how it manages the image files.  I have written a very short blog on my experience: http://www.e2photo.net/blog/long-overdue-update.html.  But feel free to contact me because the blog does not include a lot of detail.

     

    1. Make sure Aperture is up to date.  I think it is 3.5.1

    2. Make sure all the image files are referenced rather than managed in a structure that you are comfortable with.

    3. Make sure there are no missing files

    4. Make sure the Aperture trash is empty

    5. Make sure to up date the previews to the largest size you want.  (Lightroom will gather those previews as 'finished JPEG images call Aperture Previews).  

    6. I repaired the databases (not sure how critical this was but it seemed like a good idea)

    7. I had multiple Aperture libraries (one for each year).  So I imported each Aperture Library into a Lightroom catalog using the plugin in Lightroom.  Once each year was imported, I then consolidated the individual Lightroom catalogue into one large catalog spanning multiple years.

    7a. On the initial dialogue, make sure you are pointing to the correct Aperture Library and make sure you designate the your preferred location for copied images/video.  This will mostly apply to Preview files, if you have made sure all of the images are referenced.

    7b. There are a couple of very critical checkboxes to pay attention to in the Aperture-LR import dialogue box.  First check the option button.  If you want your Aperture Previews, check 'For Images which have been adjusted in Aperture....' and also check 'Leave referenced files in your Aperture....'  The last check will allow both Aperture and Lightroom to point to the same original files, but more importantly will substantially minimize the size of the LR catalogue.

     

    Others have described what will and will not come over.  For myself, pictures fell into a few categories: junk, only Aperture edited, picture with complex editing (these were the ones I have slaved to get exactly as I wanted).  The complex edited picture were most important to me and they were in tiff or psd format.  These imported fine.  I lost all of the Aperture edits, but after working with Lightroom for a couple of months, I realized that LR actually produced a better final result than Aperture so I decided I would simply redo simple edits in LR, if there was a need for a particular picture (or I could go to the Aperture Preview image).

     

    My project had several purposes, but one of them was to pull together all of the personal/family work and separate out all the business related activity.  I was able to consolidate all of the family stuff onto 3 16TB drives and I am happy to say that all of the combined business/personal drives have now been moth-balled with both Aperture and Lightroom pointing to all of the image files.  So I really feel done.

  • by Brian O'Reilly,

    Brian O'Reilly Brian O'Reilly Oct 6, 2016 6:05 AM in response to Nikontraveler
    Level 2 (193 points)
    Photography
    Oct 6, 2016 6:05 AM in response to Nikontraveler

    Fellow Aperture Users

     

    Following on from my previous post - I have conducted a series of tests on various Macs

     

    Before I start, I must make it clear that I totally accept that many users are having problems with 10.12 Sierra

    Like most of you I really like my workflow in Aperture and would like to continue to use it

    As such, I am keen that we can report back toApple and hope they are in a position to fix Aperture issues but at an OS level

     

    Tests conducted:

     

    Thumbnails upside down in List view

    Curves Adjustment and Straighten - not visible in export

    Brush Adjustment - off by one pixel

    Link to Plug-In menu not working

    Keyboard shortcut ‘f’ (for fullscreen) causes crash

    Keyboard shortcut ‘w’ (Inspector - Next Tab) causes crash

     

    Test procedure

     

    External Drive - Firewire 800

    Clean install of MacOS 10.12 - customer release

    Clean install of Aperture 3.6

    Import of JPEG and Nikon Raw Images to a new Library - Images are Managed

     

    Test machines:

     

    The above Hard Disk was used a start-up drive on the following machines - with a Thunderbolt to Firewire adaptor as needed

     

    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

     

    My test results are as follows - and were identical in all of the above tests

     

    Thumbnails upside down in List view - Issue found

    Curves Adjustment and Straighten - not visible in export - Issue not found

    Brush Adjustment - off by one pixel - Issue not found

    Link to Plug-In menu not working - Issue not found

    Keyboard shortcut ‘f’ (for fullscreen) causes crash - Issue not found

    Keyboard shortcut ‘w’ (Inspector - Next Tab) causes crash - Issue not found

     

    Conclusion

     

    So - clearly, there is an issue here and I am happy to investigate further

    Either my test was incorrect - or there is another issue with users who are experiencing the problems

     

    Again - I must stress that I am aware that some Users are having issues that make Aperture unusable

    But my tests have not been able to reproduce them.

     

    Please let me have more detail of the exact actions in Aperture that cause the issue and I will retest

     

    Hope this helps

     

    Brian

  • by agoodmanwa,

    agoodmanwa agoodmanwa Oct 6, 2016 10:13 AM in response to Brian O'Reilly
    Level 1 (8 points)
    Oct 6, 2016 10:13 AM in response to Brian O'Reilly

    Thank you, very helpful and complete.

    I also get the "Internal Error" and must crash when I try to access "Info". Do you have the same experience?

  • by Proggie,

    Proggie Proggie Oct 6, 2016 10:19 AM in response to Brian O'Reilly
    Level 4 (1,308 points)
    Oct 6, 2016 10:19 AM in response to Brian O'Reilly

    Thanks for doing these tests. If I made available a minimal library that crashes Aperture for me, would you be willing to try your tests with it?

  • by Ron Taube1,

    Ron Taube1 Ron Taube1 Oct 6, 2016 10:38 AM in response to Nikontraveler
    Level 1 (74 points)
    Oct 6, 2016 10:38 AM in response to Nikontraveler

    Thanks Brian for your efforts. They are appreciated.  I realize that you might not know the answer to this question but I see that you say your edits did not transfer from Aperture to LR but I was wondering if I just exported all of my edited aperture files with the latest version to a separate folder then imported that folder into LR might that not work?  Unlike you I don't care to re edit all of my photos so I'm thinking that this might be  a way around the issue.  My plan that I've been thinking about for months is to just save my best stuff and delete the rest. I always do this at the end of the year anyway because I make  dvd for friends and family of my best photos of the year anyway and I would save all of those. I have a file of flagged photos that I draw from.  You are obviously more knowledgeable about this than I.  Please let me know what you think.  Plus I see from your posts that there are issues with sierra so I"m going to have to do something soon to end my relationship with Aperture. 

  • by West29,

    West29 West29 Oct 6, 2016 10:57 AM in response to e2photo
    Level 1 (23 points)
    Notebooks
    Oct 6, 2016 10:57 AM in response to e2photo

    Thank you for taking the time.  Sounds like its still awkward which is such a shame.

  • by Brian O'Reilly,

    Brian O'Reilly Brian O'Reilly Oct 6, 2016 1:38 PM in response to agoodmanwa
    Level 2 (193 points)
    Photography
    Oct 6, 2016 1:38 PM in response to agoodmanwa

    agoodmanwa

     

    I tested changing tabs with the 'w' shortcut and did not experience any issues

     

    Brian

  • by Brian O'Reilly,

    Brian O'Reilly Brian O'Reilly Oct 6, 2016 1:39 PM in response to Proggie
    Level 2 (193 points)
    Photography
    Oct 6, 2016 1:39 PM in response to Proggie

    Proggie

    If you upload a test library to say 'Dropbox' and give me access - I will test as you indicate

     

    Best regards

     

    Brian

  • by Brian O'Reilly,

    Brian O'Reilly Brian O'Reilly Oct 6, 2016 1:41 PM in response to Ron Taube1
    Level 2 (193 points)
    Photography
    Oct 6, 2016 1:41 PM in response to Ron Taube1

    Ron

     

    Perhaps you have misunderstood. I did not do any tests involving Lightroom - so regrettably, I cannot assist

     

    Brian

  • by xtravoice,

    xtravoice xtravoice Oct 6, 2016 1:49 PM in response to Nikontraveler
    Level 1 (8 points)
    Photography
    Oct 6, 2016 1:49 PM in response to Nikontraveler

    All of these responses are helpful, and it seems it really matters which Mac you are using for the varied successes and failures. I asked earlier, but have not seen if anyone has tested Sierra and Aperture on a

    - Macbook Pro 15" (Retina, Mid 2012)

    - Intel Core i7, Processor Speed: 2.6 GHz

    - Intel HD Graphics 4000; NVIDIA GeForce GT 650M

     

    [I'm not sure which of the above specs are most relevant and might identify a common issue among users)

  • by Italy74,

    Italy74 Italy74 Oct 7, 2016 1:36 AM in response to In_between_dreams
    Level 1 (8 points)
    Photography
    Oct 7, 2016 1:36 AM in response to In_between_dreams

    Mmm I'm waiting for next month if anyone has better news... I might even switch right now from El Capitan where I still work (for what I do) but if it doesn't work in 10.12 is a deal breaker for me - eventually if there's really no other solution, within Christmas I might move to Capture One, more in line with the idea I have of editing.

first Previous Page 7 of 11 last Next