Aperture Users Beware

[simonsi]

Having migrated to Capture One for any photo processing, I have maintained iPhoto purely to enable me to order print products for delivery to family.

VERY concerned to find after installing 10.10.3 the tiny iPhoto library I had, had been migrated to Photos before opening the Photos app. As that is a oneway ticket I would have been hugely concerned if Aperture access was removed purely by installing 10.10.3.

This is concerning because although a unified library, my "Aperture" library was based on an iPhoto library and named as such (it had been successively updated via OS X updates) and although both iPhoto and Aperture could interact with the library it was listed as an iPhoto 9.6 library rather than an Aperture 3.6 library.

I strongly suspect had I not already converted to Capture One, I would by now have zero Aperture capability on my library without having to restore it to its unconverted state (all 600GB of it).

 

[Attonine]

No such problem. I don't have an iPhoto library, just Aperture. As had been pretty well documented before release, Photos duplicates your iPhoto or Aperture library, it does not touch your original library. I opened Photos just to have a look, and low and behold, it took about half hour to set itself up and create the duplicate library. No problems, no missing photos from Aperture.

 

[simonsi]

No such problem. I don't have an iPhoto library, just Aperture. As had been pretty well documented before release, Photos duplicates your iPhoto or Aperture library, it does not touch your original library. I opened Photos just to have a look, and low and behold, it took about half hour to set itself up and create the duplicate library. No problems, no missing photos from Aperture.

Did you not get the message that iPhoto updates are no longer reflected in the library? If so is Aperture locked out also?

Important to note, I had't run Photos, I had installed 10.10.3 and loaded iPhoto. At that point the library was already migrated and Photo's set to be the Photo manager, no discussion, permission or choice.

Anyhow, if it works for you great. Personally I won't trust my images to Apple's software ever again. For instance it would have been interesting how it would have duplicated a 600GB library on a 1TB drive.

 

[ChrisA]

VERY concerned to find after installing 10.10.3 the tiny iPhoto library I had, had been migrated to Photos...

So far you are the first and only onto have this problem. Are you SURE you did not click any "OK" button?

 

[simonsi]

So far you are the first and only onto have this problem. Are you SURE you did not click any "OK" button?

I installed 10.10.3 and then loaded iPhoto. Nothing as part of the update process that I am aware of and Photos wasn't started up to that point.

Interesting that Photos seems to be only 50MB in size, I've heard of code efficiencies but given both iPhoto and Aperture are over 1GB IIRC can that be right?

Most people load up Photos to see what it is like, as I am already converted to Capture One that doesn't interest me. So even if the conversion is part of the 10.10.3 install (say as part of the iCloud setup), most wouldn't notice or care.

 

[Attonine]

Did you not get the message that iPhoto updates are no longer reflected in the library? If so is Aperture locked out also?

Important to note, I had't run Photos, I had installed 10.10.3 and loaded iPhoto. At that point the library was already migrated and Photo's set to be the Photo manager, no discussion, permission or choice.

Anyhow, if it works for you great. Personally I won't trust my images to Apple's software ever again. For instance it would have been interesting how it would have duplicated a 600GB library on a 1TB drive.

Can't remember if I received any message, and Aperture is not locked out of anything.

You should have 2 libraries. One for iPhoto/Aperture and one for Photos. As is very well documented, Photos creates a duplicate library, it does not touch the original library.

I think I my know what you are referring to as my Aperture library was labelled as "migrated to Photos", and I had to redirect Aperture to this library when I opened it for the first time after update. As soon as Aperture was pointing in the right place, the label disappeared. I don't think this label is indicating any change, I think it's advisory, telling you that "this is the library that was used to create the duplicate for Photos"

 

[Bruno09]

For instance it would have been interesting how it would have duplicated a 600GB library on a 1TB drive.

Not a problem : a Library is based on hard links.

http://sixcolors.com/post/2015/02/the-hard-link-between-photos-and-iphoto/

https://forums.macrumors.com/threads/1853086/

 

[maflynn]

I have most of my Aperture libraries on a DAS, I'll have to double check the one that is my internal drive. I have my system backed up on TM, and I've been on LR since last year but for archival purposes I want to maintain my Aperture libraries.

Thanks for the heads up on this.

 

[Frosties]

So far you are the first and only onto have this problem. Are you SURE you did not click any "OK" button?

Had the same problem, did just as the poster, updated and opened iPhoto. Never touched photos. First prompt from iPhoto, my library was migrated. After opening Aperture I had to choose library as it was 2 to choose from. Apple's beta testers are useless, as always.

 

[simonsi]

So it seems the Photos migrates your iPhoto library as part of the 10.10.3 update application and not as part of firing up Photos for the first time. There are some implications here:

What will happen on future updates, was 10.10.3 unique in this regard (as it introduced Photos into the OS), or can subsequent OS updates be expected to reapply that logic where the user has elected not to use Photos?

My library was a legacy iPhoto library, even though it have been updated to a unified library. Does this update methodology apply to native Aperture libraries?

The combination of these two is incredibly arrogant of the developers, it effectively removes any opt-out by the user and shows that they have absolutely ignored many user-cases in their development.

 

[simonsi]

Photos creates a duplicate library, it does not touch the original library.

My point is Photos had not been run. The Photos library was created by the update process, not by my choosing to run the Photos app.

See above for another poster reporting the same.