Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Apple is right to let Aperture go

After at first being a little surprised at Aperture’s demise it occurred to me that Apple is right to do this. Continuing to develop an app with small market share on an operating system with small market share makes little sense. It is better for them to admit defeat and try something better then continuing to go down the wrong path.


The technology landscape has changed a lot since 2005 when Aperture 1.0 came out. There are different ways to access files such as sandboxing and iCloud drive. These technologies will become an important way to get photos between a Mac and an iOS device. Tagging files in Aperture was helpful but relying on the tagging system built into the OS would be a much better solution (someone else just mentioned this recently and I strongly agree.) If a new pro photo app made it’s tags available to the Finder and Spotlight those tags should show up along side similarly tagged files that were created in other programs.


Also Aperture’s competition from Adobe is fundamentally flawed. An all new pro app could address the problems that Adobe’s photography apps have. Anyone who has used Adobe’s solutions should be well aware of their shortcomings.


1. Photoshop, which came into being in the 1980s, was not built around technology like raw and therefore requires a rather clumsy workflow.


2. When a document gets exported to Photoshop the user is presented with a confusing array of choices as to how that photograph should be handled. Each option with it’s own series of advantages and drawbacks.


When a photo gets brought back into LR after being edited in PS it creates a new copy. If that photo then gets edit a second and third time it just keeps creating more copies of the image. The same problem can be said of adobe camera raw.


4. I always thought it was a little odd that you have to export an image from LR in order to use it in another app. App’s like LR, Aperture, and Photos are file navigation programs so why do I need to bring a photo from one navigation program (Lightroom) into another navigation program (the Finder) in order to work with it? Yes, I realize that at times you may need a smaller resolution file of an image like for a webpage but why can’t I just make a smaller version from within the photo navigation program and keep the images all in the same app? Doesn’t make sense to me.


It doesn’t have to be this way. Modern apps like Pixelmator are similar to PS except they can handle raw directly from within the app. It seems like it would be possible to team up with Pixelmator so that a raw photo could go between the two apps while keeping all their settings in tact and not requiring users to make unnecessary duplicates of exported files. For an example you could change the brightness in Apple’s Pro app and then it would still stay at the same setting in Pixelmator. And then if you changed the brightness again in Pixelmator the adjustment bar setting would be brought over to Apple’s Photos.


Since Pixelmator didn’t exist when Aperture 1.0 came out the two companies were not able to unify their two products. When you start over with a new product considerations like this can be taken into account. One of the things I hate about Adobe’s photo apps is the way that a lot of modern technology like raw feels very tacked on (because it is.)

Posted on Jun 30, 2014 11:31 PM

Reply
34 replies

Jul 11, 2014 1:30 PM in response to pik80

Since I think Mavericks tags were mentioned I wanted to resurrect that part of the thread.


Turns out that DevonThink can make use of a script DevonTechnologies makes to copy an image's keywords TO Mavericks tags. So if your photo has the IPTC keywords "Messi" and "Argentina" those will become the files Mavericks tags "Messi" and "Argentina." Photos can be referenced in DevonThink, so you don't have to dupe your photo files. But rendering the previews of image files is pretty slow. But it's a nice tool if you need for some reason to add the keywords to Mavericks tags (and while it can display the keywords I don't think there's a way to write them).

Jul 11, 2014 6:41 PM in response to pik80

I'm possibly a little confused by what your meaning by mavericks tags, and saying tags and keywords are the same thing.


If we mean the tags that display on the lefthand side of a finder window which start out as Red, Orange....Work Important and so on, then I DO NOT want that list linked to my Aperture keyword list of 1900+ words, how would they all fit. 😕 Now mavericks tags linked to Apertures metadata labels could be very useful.


It was suggested that every app uses the same Contrast tool, how does that encourage innovation and refinement by 3rd party apps. Your just saying to developers, don't bother, apple have it sorted.


One last point to Rob

"Perhaps the Mac OS will be more iOSified"

That you can bet your bottom dollar on. 😁

Jul 11, 2014 8:19 PM in response to Acetone.

What I mean is if I search for a tag in the Finder (or another general search app) I want to see every tag/keyword that is related to that tag. It doesn't matter if it's aperture pictures, bookmarks, email messages, pages documents. The way it is right now I have to open aperture search for that tag then open Firefox and search for the same tag then open Mail and search for the same tag. It shouldn't work that way. I should just do a search for a tag in Finder and see everything all at once, no opening multiple programs to run a single search.


How would you refine a contrast?

Jul 12, 2014 1:36 AM in response to Yer_Man

Terence Devlin wrote:


One last point to Rob

"Perhaps the Mac OS will be more iOSified"

That you can bet your bottom dollar on.


Lets add that to "Apple are becoming MicroSoft", "Steve Must Be Turning In His Grave" and "You can't right-click on a Mac" as another of the prime indicators of the clueless.


iOSified can be thought of in different ways, Apple are making Yosemite and iOS work much closer together with all the Handoff, Mac answering your ringing phone and so on, all by the cloud and bluetooth i guess at the moments, and even though not a true pro app, the new iWork package was just a straight port of the iOS version, which they slowly added original features back.

To think Apple don't want more integration between the two OS is naive beyond belief.

pix80

I see were your coming from on the search front, and as Rob showed in post 3, it can be done in finder.

I tried it, and it sort of worked. It found keywords embedded in .jpg but not ones used in Aperture referenced raw files, something I guess would be easy for Apple to implement, the only issue I can think of is you could be inundated with results if your not careful. If the search covered every possible use of a word, without the targeting of just keywords or just text in written documents.

Jul 12, 2014 1:45 AM in response to Acetone.

and even though not a true pro app, the new iWork package was just a straight port of the iOS version, which they slowly added original features back.


And that is just not true. That's the same kind of logic that lead to the whole 'No Right-Click on a Mac' claptrap. Someone doesn't make the time to actually look at what is done and comes up with a catchphrase.


Yes the two Oses are going to work more closely together but that does not mean that the OS X version and the iOS version will have the same capabilities. They won't and they don't and they didn't. The new iWork package was not "a straight port of the iOS version". But don't take my word for it. Take this guy's word - and he knows as he wrote the book on it - you know actually looked closely at what is actually happening:


What Apple has done is to ensure document integrity when a Pages document travels from Mac to iOS and back. Providing that integrity is what made the iWork reboot necessary, and something like that is what is behind the transition from Aperture (and iPhoto) to Photos


and then:


Nor do the Mac and iOS apps provide identical capabilities: the Mac Pages app provides a lot more functionality than the iOS app. Take styles, for instance: you can apply paragraph, character, or list styles in either app, but you can create new styles only on the Mac. There are dozens of places in my Pages book where I point out that one feature or another is only available on the Mac.

So much for iOS-ification


Have a read of the whole thing. It doesn't dissolve into a handy catch phrase, but it's actually a good summary of what's going on.


http://tidbits.com/article/14783

Jul 12, 2014 6:10 AM in response to Acetone.

@Acetone

"I tried it, and it sort of worked."

Sort of working shouldn't be where we set the expectation bar at though. Rob's workflow was just too complicated. At one point he described doing a search where you had to type in "wedding" twice (as the keyword and as the tag) in order to find all instances of that topic.

"It found keywords embedded in .jpg but not ones used in Aperture referenced raw files"

It's got to work better then that.

"the only issue I can think of is you could be inundated with results if your not careful."

I don't see the problem. What is wrong with getting a complete listing of results rather then a partial listing? You can always keeping adding search criteria to get fewer, more refined results if you like.

Jul 12, 2014 10:26 AM in response to pik80

pik80, sorry for the confusion but I was just citing an example. It actually is far easier in practice.


Remember that although "tags" and "keywords" are words, they are more than that. Their context adds meaning. For example, the word "wedding" in the body of a Word document, in the caption field of IPTC data, in Mavericks tags, and in IPTC keywords means different things to a searcher. And of course you can go further by limiting the search to the place searched (the PIctures folder, say) or by adding other criteria. So if I just search for tags:wedding I get something different than if I search keywords:wedding. But there are other ways to do that, like just searching "wedding" AND kind:image, or searching "wedding" anywhere in my Pictures folder.


And Acetone, I agree having lots of Mavericks tags can be a pain. If you just use the Finder. It stinks for tags. There are applications out there that make tagging much useful, like Leap. Or Path Finder. Or, as pik80 noted, HoudahSpot. Which, as noted, can search for keywords and Mavericks tags easily. I'm sorta suprised there aren't more utilities for tagging (Tags and Punakea having expired), but I guess it isn't catching on that much.


But here's a reason why Mavericks tags can be useful to the photographer: RAWs. A search for say "wedding" in a folder of JPGs, RAWs, and XMPs will find both the keyword "wedding" in the JPGs and XMPs. But the RAWs won't show in the list of results. Lotsa times I just then select the name of the file minus the extension and search again and I find the RAW. Fine. But awkward and time consuming.


But if I were to add the Mavericks tag "wedding" to the RAWs themselves then I could find all the RAWs, XMPs and JPGs with one search in the photo folder with "wedding." Mavericks tags are added in extended file attributes, so they're not written to the RAW itself. It's been useful, but it's a big pain. I wish there were a way to link sidecars with their RAWs, but I haven't found anything. Or maybe an AppleScript to copy from an XMP to Mavericks tags.


If you use Aperture it's even worse because it doesn't write changes to metadata, even on jpgs (I think), unless you export.


The TidBits article was kinda interesting. Turns out the changes in the OS X version were because it was basically incompatible in part with their own iOS apps. No wonder they changed it. The author speculates that this is what's going on with Photos; the idea is that changes on one Apple platform are the same on another. Fine, sorta iWorks with images. I can see how this encourages use of iCloud and Apple hardware and maybe they'll finally get a worthwhile cloud thing going. Sorta also explains dumping Aperture. He seems to be saying the priority is cross-platform integration with iOS (that's why "iWork Had to Change"). Probably it will be a boon to Apple fans.


And are people really still fighting the PC vs Mac thing? How last century.

Jul 13, 2014 11:21 AM in response to Rob Gendreau

I bought aperture on the App Store. i am not really a pro, but i am definitely a camera enthusiast. I have a nice DSLR and i have done a couple of family member weddings. I am good at using the tools, I just don't earn a paycheck doing this. I like aperture, it was full featured enough. I could adjust things pretty easily, I could work with raw files. I just hope that Apple creates a good enough pro level tool with the new photos app. I just needs to be able to store my images on the hard drive. And I just need to be able to work with raw files and do everything that I could with aperture.


I am not interested in buying Adobe light room at all. It is too expensive as a standalone product. I am not going to be paying for a software as a service type of program to manage my photos. So I'll be waiting for the new photos app, and hopefully it will be good enough to replace aperture.

Jul 13, 2014 11:25 AM in response to pik80

One thing I hope Apple gets right is to make there be a single app for photos on iOS. Right now you have iPhoto and you have the photos app and it it's just weird to have to switch between the two of those to get things done they don't really work well together.


Also the iOS app for Photos could use to be much more powerful. They should be able to do raw files. I should be able to use my SLR camera and import photos and then edit them on an iPad. Upload them to iCloud. And then back them up on my computer's hard drive later on when I am home.


Maybe the next version of the iPhone will be able to take raw photos. And then you would be able to edit them in iOS or on the photos app on the computer. Come on Apple, be the first company to release a phone that takes raw photos.

Jul 13, 2014 4:37 PM in response to graigsmith

Well I'd be happy if after over half a year they just had desktop support for 2014 cameras.


And the iPhone does take RAW; every digital camera does. Apple's software does the RAW processing; the issue is whether they'd let an app or their own software directly access the RAW, save it, etc. You can do RAW with a Nokia Lumia, however. I believe the AV Foundation in iOS gives access to some of the data, but I'd think that if you could generate a RAW file like the ones we have in DSLRs it would have been done by now.

Jul 14, 2014 11:06 AM in response to Rob Gendreau

@Rob

There are tons of great tagging tools on the Mac. Recently I have been started using Pixa which is a fairly new app and one of my favorites. I don't think anyone has brought up Yojimbo yet which some people like (I haven't used it yet.) Did anyone bring up Tembo? If you spend time looking around MacUpdate there are a lot of apps.

Jul 14, 2014 11:19 AM in response to Rob Gendreau

I don't think iPhone does shoot raw and the same can be said of many other consumer cameras. As I understand it the pro cameras are able to capture a lot more information about a photo then consumer cameras like the iPhone. I am not sure what a raw shooting iPhone would accomplish as I don't believe it captures the data that a pro camera does.

Apple is right to let Aperture go

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.