rshammaa

Q: How are Aperture and Yosemite getting along so far?

How are Aperture and Yosemite getting along so far?

 

Hi guys,

Is it OK for Aperture users to take the plunge and update to Yosemite, or is it wiser to wait for kinks to be worked out first? I didn't find any reference to this matter so far on this forum or on the web. I may have mort worded it correctly.

 

Thanks for responding,

 

Raphael

 

Also,

Why do I constantly run into the statement: "You are not allowed to create or update this content" when I click on "Post"? So annoying ....

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 20, 2014 1:50 PM

Close

Q: How are Aperture and Yosemite getting along so far?

  • All replies
  • Helpful answers

first Previous Page 3 of 4 last Next
  • by rshammaa,

    rshammaa rshammaa Oct 22, 2014 1:25 PM in response to JohnZonie
    Level 1 (4 points)
    Mac OS X
    Oct 22, 2014 1:25 PM in response to JohnZonie

    That's great John; when did you update to Yosemite?

  • by JohnZonie,

    JohnZonie JohnZonie Oct 22, 2014 1:29 PM in response to rshammaa
    Level 1 (36 points)
    Mac OS X
    Oct 22, 2014 1:29 PM in response to rshammaa

    The day it came out! (I'm like that ) It has been the smoothest update in my experience and I started with Tiger.

  • by Howker,

    Howker Howker Oct 22, 2014 2:00 PM in response to JohnZonie
    Level 1 (15 points)
    Mac OS X
    Oct 22, 2014 2:00 PM in response to JohnZonie

    I ran Cocktail to rebuild everything & clear all caches then CleanMyMac. Now it works better & the versions are there. Yes Leonie I had made sure my Prefs were right.

    Not for this forum but strangely when Cocktail ran the only cache it couldn't clean was the DNS one. Anyway AP3 at least workable again.

  • by ncmacguy,

    ncmacguy ncmacguy Oct 22, 2014 2:10 PM in response to ncmacguy
    Level 1 (5 points)
    Oct 22, 2014 2:10 PM in response to ncmacguy

    I replaced the "Vault" backup file that was apparently causing all the error messages from a backup. That has apparently resolved my problems with Aperture 3.6 and Yosemite.

     

    Aperture 3.6 and Yosemite now seem to be working well with each other, though I haven't spent a lot of time working with them yet. I'm very happy I had a couple good backup files available to fall back to.

     

    I haven't had any crashing problems on my mid-2011 iMac with Aperture or any other app with Yosemite.

     

    Before upgrading be sure you have a good backup to use in case of problems! (As everybody knows.)

  • by sotamphoto,

    sotamphoto sotamphoto Oct 24, 2014 3:53 AM in response to rshammaa
    Level 1 (0 points)
    Oct 24, 2014 3:53 AM in response to rshammaa

    I have what looks to be Aperture issues but I wonder if it is Yosemite.  As same with previous post I too experience issues with Aperture freezing and quitting expectantly, especially within full screen mode.  But here is an issue I can replicate without issue cause it is part of my photo editing workflow:  While in Aperture, launch a photo into full screen, then option-click and launch Photoshop CS6 (it does not matter if you make photo edits or not), save and close Photoshop, Aperture does not always load back to the main screen as the App in use, sometimes it is there, sometimes I have to click on the launcher icon to get it back, happens more so with Photoshop and less with direct access plugins like OnOne.  But even worse is If you now leave the photo full-screen view, and minimize Aperture or just move it to the side to get to the desktop, the desktop is inaccessible... it looks as if Aperture did not release to the finder.  Clicking the desktop or any desktop items does not give you access, if you CMD-Tab to see the Open Apps and choose Finder, it does not release to the Finder, it puts you back into Aperture, but looking at your desktop. You can however switch to another view and the desktop is accessible, but that view you are in is locked in Aperture.  If you quit and reload all works normal again, until you edit with Photoshop or plugins from a full-screen Aperture view. I even rebuilt my laptop from scratch and loaded only 1 photo into Aperture and I can recreate this issue.  Has anyone else come across this?

  • by Brighton-UK,

    Brighton-UK Brighton-UK Oct 24, 2014 4:51 AM in response to rshammaa
    Level 1 (0 points)
    Oct 24, 2014 4:51 AM in response to rshammaa

    Aperture 3.6 and Yosemite have been a nightmare for me too.

    On my mac (aperture) Im unable to see Camera roll images (from iPad)

    I understand that My PhotoStream and camera roll will be combined in to recent photos ( but in my case, images from camera roll have not been combined)

    So edits made on iPad are not available on mac


    Any suggestions to correct?


  • by léonie,

    léonie léonie Oct 24, 2014 5:21 AM in response to Brighton-UK
    Level 10 (107,215 points)
    iCloud
    Oct 24, 2014 5:21 AM in response to Brighton-UK

    On my mac (aperture) Im unable to see Camera roll images (from iPad)

    I understand that My PhotoStream and camera roll will be combined in to recent photos ( but in my case, images from camera roll have not been combined)

    So edits made on iPad are not available on mac

    That is not a problem of Aperture 3.6 and Yosemite, it is a bug by design in iOS 8, see this support document:

    iPhoto and Aperture don't have edits to photos you import from iOS 8 devices

     

    You cannot save edited photos to the camera roll like before. That is why transfer by USB does not transfer the edits, since the camera Roll only will hold your originals.

    With iOS 8 there are only two ways to transfer edits done on the iPad to your Mac right now -  share  the edited photo by mail or Shared Photo Stream.

    Or enable the iCloud Photo Library Beta  on your iPad. Then you can download your iPad photos from the iCloud webpage in the Photos.app. None of this is lossless. You can only download the rendered JPEG, and the edits will be burned in and cannot be reverted to original like before, when we saved a photo with filters applied to the Camera Roll. Also, when you mail a photo or download it from https://www.icloud.com/, the GPS will be missing.

  • by John Purlia,

    John Purlia John Purlia Oct 24, 2014 11:09 AM in response to rshammaa
    Level 1 (98 points)
    Mac OS X
    Oct 24, 2014 11:09 AM in response to rshammaa

    Overall, Aperture 3.6 under Yosemite has been well behaved, though not without certain problems that were not present under Mavericks. I've found things to me markedly more sluggish once a fair number of adjustments have been applied to a photo, especially while brushing. This is on a 27: iMac with a 3.4 GHz i7 processor, 24 GB RAM, and the higher end NVIDIA graphics processor. I most notice the slowness when brushing in adjustments and zoomed to 200%.

     

    There also is an annoying problem of the brushing cursor changing into an arrow whenever a notification pops onto the screen (typically, when an email is received or iTunes changes tracks).

  • by torreypines,

    torreypines torreypines Oct 24, 2014 1:31 PM in response to Kirby Krieger
    Level 1 (74 points)
    Oct 24, 2014 1:31 PM in response to Kirby Krieger

    Greetings Kirby - I would suggest that everyone who uses iOS 8.1 devices for image capture follow your suggested direct import workflow route into Aperture 3.6 - It is easy to turn off your iOS 8.1 device cloud upload settings. And why would one want to use the primitive iOS 8.1 photo editing to begin with?? There is a big difference between the Nikon NEF files I import into Aperture 3.6 and the iOS device images that I also can directly import into Aperture 3.6 - but at least I can use the Aperture 3.6 image processing to make edits on the iOS8.1 image files - and I can save those edit changes into my Aperture library.

  • by jpac,

    jpac jpac Oct 25, 2014 12:09 AM in response to torreypines
    Level 1 (8 points)
    Oct 25, 2014 12:09 AM in response to torreypines

    I would say the only difference between the Nikon NEF (et al) and the "primitive iOS8" edits is who uses what and how. Either for my daily selfies and family album items or your award winning digital pieces there is a gap in the workflow making it impossible for users to keep their original work available back in the iOS8 device. Nothing to blame Aperture since it looks more like an iOS "feature" but the Photo app powers have been promoted in such espectacular way that one may expect at least some basic edits to be accepted by a Pro app. And missing that,  there should be at least one WARNING message informing iOS8 users "all edits will be gone if you dare to import and sync".

     

    I still hope the Photos app for mac will support some of these "primitive" edits.

     

    Anyway, the console in my macbook pro is showing hundreds of messages like these:

     

    • 25.10.14 08:54:23,850 Aperture[2953]: ProThemeStore: No theme registered with id=1764
    • 25.10.14 08:54:24,135 Aperture[2953]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
    • 25.10.14 08:54:27,473 Aperture[2953]: The function ‘CGContextClear’ is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance
    • 25.10.14 08:54:30,000 kernel[0]: Sandbox: mdworker(1795) deny mach-lookup com.apple.audio.audiohald

     

    but being honest I can’t remember if these were already showing up while in Mavericks.

  • by léonie,

    léonie léonie Oct 25, 2014 12:58 AM in response to léonie
    Level 10 (107,215 points)
    iCloud
    Oct 25, 2014 12:58 AM in response to léonie

    added:

     

    Image Capture actually does transfer all iOS 8 edits from the iPhone to the Mac, only no app on the Mac can read them.  The edits are stored in the .AAE sidecar files, that Image Capture downloads, and we need to find an application for Yosemite, that can read .AAE format.

     

    See my post here:  in response to léonie

     

    I sincerely hope, that Aperture and iPhoto will be updated to be able to read the new lossless representation format for iOS 8 edits. It seems to be the new basis for app extensions and plug-ins.  Apple using new AAE sidecar format for iOS 8 photos? | iLounge News

  • by moebelli,

    moebelli moebelli Oct 25, 2014 12:29 PM in response to léonie
    Level 1 (1 points)
    Oct 25, 2014 12:29 PM in response to léonie

    Updated to Yosemite on my iMac and MacBook Air, running Aperture 3.6 on both.

     

    So far noticed:

     

    - extremely slow load times when launching a library, if you happen to use lots of libraries and switch back and forth between them (like me), this is a big problem

     

    - some adjustments made on an image do not show up when I go out to Mac Mail. I might rotate and adjust exposure, but when I share to Mac Mail, I only see the original photo with no changes at all

     

    All else seems to work fine.

  • by léonie,

    léonie léonie Oct 25, 2014 1:36 PM in response to moebelli
    Level 10 (107,215 points)
    iCloud
    Oct 25, 2014 1:36 PM in response to moebelli

    - some adjustments made on an image do not show up when I go out to Mac Mail. I might rotate and adjust exposure, but when I share to Mac Mail, I only see the original photo with no changes at all

    I have not noticed this. When I rotate or adjust the exposure, I see the edits in the Mail. I tested with JPEGs and Canon EOS 5D Mark II RAW files.

  • by rshammaa,

    rshammaa rshammaa Nov 4, 2014 10:15 AM in response to léonie
    Level 1 (4 points)
    Mac OS X
    Nov 4, 2014 10:15 AM in response to léonie

    Hi Léonie,

    So in 40 words or less Where are we with all this. Is it advisable to update to Yosemite yet?

     

    Thanks!

     

    Raphael

  • by Frank Caggiano,Helpful

    Frank Caggiano Frank Caggiano Nov 4, 2014 10:26 AM in response to rshammaa
    Level 7 (25,796 points)
    Nov 4, 2014 10:26 AM in response to rshammaa

    Yes, no, maybe. It really depends on each individuals setup and expectations.

     

    I've been fine, even on an old MBP with only 4gb of memory. I did a complete wipeout and clean install on that one.

     

    I'd suggest you make a clone of your current root drive, then install Yosemite and use if for a few days. If you decide it is not working for you juts clone  back and return to what you are running now. Running it  is really the only way to know if ti is going to work for you.

first Previous Page 3 of 4 last Next