Plus they removed aperture off the app store, why? It's not like "photos" replaced all those editing features. Again... What the hell Apple?!
Any Mac app reconfigured to work with IOS is watered down in order to do so.
There are no projects and events in Photos. There are only albums that happen to have the same content as the projects and events that existed in the Aperture and iPhoto libraries. And at least in Aperture albums and projects were never sorted by date (either by kind, name or manually) except for completely linear list of projects with zero organisation. That completely linear list is replaced by the equally completely linear list of years, collections, and moments. The key difference is that Photos splits up photos based on capture date and location, not allowing a manual division and that the sort order is fixed with oldest on top (where Aperture allowed reverting that order and for manual sorting).I just don't understand why in the Photos app they removed the ability to merge or split albums. Also Aperture and iPhoto sorted Projects and Events by date with the most recent first. That made sense. Now Photos doesn't allow for that. If you want by date you need to scroll down to get to the most reason.
An interesting question why you had a folder structure for albums and not one for events? Albums were a secondary form or organisation, ie, each photo had to be in an event but an image did not have to be in an album.How well does it do with migrating the folder structure that albums are sorted into in iPhoto, if you have that sort of structure in your library?
For example, sync with IOS device in iTunes doesn't work for me (yes I am up t date) it shows a pane with a dropdown menu from which I can choose sync with iPhoto or sync with Photos. Libraries migrated but only sync with iPhoto works, Photos App shows 0 photos available.
Any thoughts? Thanks
i would not consider that to be an "idea" that they had for the new Photos app, but rather an oversight. Drag-and-drop between apps needs to be specifically supported. I was recently surprised I could not drag a photo from Photos into a chat app that I was using, and had to go through the Export-then-Upload procedure, which is totally not Mac-like.
I don't like it, Some deeply flawed ideas. One of the most useful features of iPhoto was dragging a picture out to a folder or to an application like photoshop. Dragging out a raw file creates a JPG and deposits it in the folder and you cannot drag into photoshop or send the raw to an external editor. Useless.
So you predict ('will') that this will happen as a normal course of action?Photos will migrate your events from iPhoto and store them in a folder for you in the 'Albums' view. Hours later half of these events will have randomly disappeared, without any user interaction what-so-ever.
They're unifying the photo experience between iOS and OS X. Eventually, there will be extensions/plugins that can be added to photos just like in iOS that will bring back all, if not, most of those editing features.
How do you add locations to photos?
Quote:
Originally Posted by coolfactor View Post
What are you doing differently?
Either give me more storage for free - my photo library is relatively small (people on here talk about collections with 40,000 photos in, I only have 7GB of photos)
I don't like it, Some deeply flawed ideas. One of the most useful features of iPhoto was dragging a picture out to a folder or to an application like photoshop. Dragging out a raw file creates a JPG and deposits it in the folder and you cannot drag into photoshop or send the raw to an external editor. Useless.
>360.000 and 2TB. Not going into cloud. iCloud photo library looks much better than what it replaces, but please Apple, give us better tools to handle what goes to the cloud and what stays on our local storage systems (I've three local copies). And make sure that Photos works with large libraries - number of photos is not going to shrink over years and it's not unheard of to have hundreds of thousands, over decade or two!
I'm calling BS on this. Even if true, we'd be talking months or years and Apple hasn't committed to any of this. Not even to add what should be the most basic functionality.
Short answer: you can't. Photos is a least-common-denominator approach; because Photos for iOS lacks a way to tag location to existing photos, Photos for OSX apparently can't have that functionality either. Similar to when Apple neutered the iWork for OSX suite to make it feature compatible with the iOS apps. Embarrassing, really, for a company of Apple's size.
Disagree. There is nothing normal with 360,000 photos in a library. Apple targets the mainstream here. If you need to manage such volums you are not a priority.
I think the mainstream (90%) of users will have less than 10,000 photos. I have 27 years of photos and 36,000 photos which I find to be a lot. 230GB which put me in the 500GB bracket. But I don´t consider myself mainstream.
>360.000 and 2TB. Not going into cloud. iCloud photo library looks much better than what it replaces, but please Apple, give us better tools to handle what goes to the cloud and what stays on our local storage systems (I've three local copies). And make sure that Photos works with large libraries - number of photos is not going to shrink over years and it's not unheard of to have hundreds of thousands, over decade or two!
...Photos is a least-common-denominator approach; because Photos for iOS lacks a way to tag location to existing photos, Photos for OS X apparently can't have that functionality either.