You are here

87 posts / 0 new
Last post
Aperture in El Capitan #1
Alan Cairns's picture
by Alan Cairns
June 8, 2015 - 4:26pm

As far as I can tell on a quick test, Aperture appears to run normally on OS X 10.11 (El Capitan). The closing dialog box about “updating sharing information” appeared to be blank, but all else seemed normal. I’ll try it out over a longer period, and report back if any problems develop.

 

Alan

Rafael - MyDarkroom.ca's picture
by Rafael - MyDarkroom.ca
June 8, 2015 - 11:42pm

From the 10.11 beta 1 pre-release notes:

Aperture

    Known Issues

  • Importing RAW files may cause the app to quit unexpectedly.
  • The Aperture workspace may disappear occasionally. To bring back the workspace, click on the Aperture icon in the dock.
  • Some Sony RAW images may not appear correctly.
  • Dismissing certain dialogs may cause the workspace to become unresponsive and require a force quit and relaunch.
  • Aperture may quit unexpectedly when attempting to print photos. The Photos app can be used to print instead.

I am still debating if I am installing this…

LindsayAnnLaw's picture
by LindsayAnnLaw
December 8, 2015 - 4:59pm

I can’t get Raw photos to even show up… to try to import them.  

Rafael - MyDarkroom.ca's picture
by Rafael - MyDarkroom.ca
June 8, 2015 - 11:43pm

And the notes regarding Photos:

Photos

    Note

  • Photos libraries are not backwards compatible. Once a library has been opened in the OS X v10.11 Developer Beta, it will no longer be openable in OS X Yosemite or earlier.

 

    Known Issues

  • Photos must be launched once in OS X v10.11 Developer Beta 1 in order for services including iCloud Photo Library, iLife Media Browser to work correctly.
  • Photos may occasionally become unresponsive when attempting to quit if the library contains certain MPEG video files.
helalwi's picture
by helalwi
June 9, 2015 - 4:03am

Is this good new for Aperture users? I expected the program not to run any more. But it seems that this is wrong. Does this mean that Apple after all is still minding Aperture?

Best regards, Alex

Ingmar's picture
by Ingmar
June 17, 2015 - 12:35am

Anything new on this? Some other experiences?

Still using Aperture as I havent’ decided on a replacement yet. And if it’s working fine with El Capitan than I might stay a ‘little’ longer with my beloved DAM

Rick's picture
by Rick
June 24, 2015 - 10:20am

I would not hold out for any Aperture fixes for El Capitan. I think that Yosemite will be the last stop for Mac Users that will remain on Aperture. I am one of them. I have sent my displeasure and received a response from Apple Executive Relations that basically has ended any new hardware purchases once Yosemite is no longer support on new Apple hardware.

Best Regards,

Rick

Krakatoa Sundra's picture
by Krakatoa Sundra
June 24, 2015 - 12:45pm

Hi Alan,

Do you have one of the latest macs that will support Metal? Do you notice speed improvements? Apple says Core Graphics and Core Image will use Metal. And since Aperture uses these API, do you notice improved speed? Thanks!!!

 

Robert Ke
twitter: rke21

also at:
instagram: rke21
facebook: outdoorphotographynow

Alan Cairns's picture
by Alan Cairns
June 24, 2015 - 8:16pm

My most recent Mac is my MacBook Pro retina from 2012.

 

Alan

 

 

Krakatoa Sundra's picture
by Krakatoa Sundra
June 27, 2015 - 12:48pm

Apple hasn’t published an official list of which macs will have Metal support. Do you feel a speed increase when working with Aperture on El Capitan? Or does it feel about the same?

thanks!!

Robert Ke
twitter: rke21

also at:
instagram: rke21
facebook: outdoorphotographynow

Ray's picture
by Ray
June 24, 2015 - 6:58pm

Items in the published bug list are items that assets will be allocated to. Aperture and iPhoto are in the list. No guarantee they will eventually get them working. But I’d bet against the naysayers.

Rafael - MyDarkroom.ca's picture
by Rafael - MyDarkroom.ca
June 24, 2015 - 11:26pm

iWeb was discontinued in 2011 (OSX Lion). It still works under Yosemite (except the MobileMe part). So I am not panicking on Aperture stopping to work tomorrow. But just sad to see it stagnated and abandoned by Apple.

Rick's picture
by Rick
June 25, 2015 - 4:08am

What bug list and what confirmation is the from Apple that resources will be allocated? I sure would like to see that as everything else they said is one maintenance release for Yosemite and Aperture is done.

Best Regards,

Rick

Ray's picture
by Ray
June 25, 2015 - 9:31am

https://developer.apple.com/library/prerelease/mac/releasenotes/General/…

From a person who gets paid to fix these bugs. They don’t publish what they have no intention of fixing, it’s not a bug. No guarantee all the bugs on the list will get fixed.

Rick's picture
by Rick
June 25, 2015 - 10:48am

Sorry but known issues can simply remain known issues and having to use Photos to print is not a viable option.

Best Regards,

Rick

Ray's picture
by Ray
June 25, 2015 - 11:21am

“No guarantee all the bugs on the list will get fixed.”  Not sure what you’re sorry about.

Its a little late in the game to still be dependent on Aperture for key functionality.

freediverx's picture
by freediverx
July 23, 2015 - 9:02am

Unfortunately there are no suitable alternatives to Aperture at the moment, as your own comments have confirmed. You, an expert on the topic with an admittedly large amount of time on your hands, have come up with dead ends and are currently relying on an unsatisfactory mix of three different applications, which in tandem still fail to adequately replace Aperture.

Most comments on this topic point people to Lightroom. You seem to agree with my impression of Lightroom (and all other Adobe products) as buggy, poorly designed, unintuitive, and slow. You also seem to confirm that Lightroom, despite comments to the contrary, does not fully substitute Aperture’s functionality, even poorly.

I have no experience with the other products you mentioned, but it sounds like they are at best a band-aid approach requiring multiple applications that together yield a half-assed solution, and even then only after a considerable amount of effort. 

For me photography is a hobby and a passion - one that I’ve had since I was in high school. The moment that hobby turns into a grueling, non-paying job is the moment it ceases to be a hobby or even an interest for that matter.

I’m a big fan of Apple and generally support their business strategies and practices but what they’ve done to Aperture, and more importantly to Aperture users, is a travesty. People trusted Apple and invested significant amounts of time and effort to create image management/editing workflows revolving around the product. To abandon all these people while there are no suitable alternatives on the market is unforgivable.

This also speaks to the broader issue of Apple’s repeated failures to properly develop and manage cloud-based solutions. The discussion forums are replete with horror stories of data loss and corruption with both Apple’s cloud-based photos solution as well as their more recent cloud-based music solution. While Apple still makes beautiful hardware, the quality of their software has plummeted considerably. More importantly, they have yet to demonstrate any competency in cloud services, which paints a dire image considering they’re encouraging everyone to entrust their data to the cloud.

Part of me admires your stoic pragmatism in nonchalantly “moving on”. But another part of me resents your dismissive tone towards frustrated Aperture users who aren’t as glib about this transition.

Marco Roman's picture
by Marco Roman
September 17, 2015 - 2:29pm

Very good argument, I think and feel mostly in the same way.

Matt's picture
by Matt
October 1, 2015 - 6:02pm

My sentiments exactly.  Well written.  You have very well captured my thoughts.  If only Apple read such threads about how its decision to kill Aperture affects people so devoted to their products and willing to invest in the company to foster their personal passions, I can’t imagine they would have killed Aperture.  Instead, the ‘selfie’ community and a desire to (finally) try its best at cloud services seems to rule the day.  My trust in Apple has severely declined post Steve Jobs, even though many laud Tim Cook as a successful successor.  I don’t see that yet.

--
M.A.Stough Photography

Lisa's picture
by Lisa
October 13, 2015 - 8:11am

Reply to freediverx: Yes, Yes, Yes. I HATE Lightroom. For every hour I spent working in Lightroom, I could get exponentially more work done in Aperture. Aperture was/is (now that I have disabled onscreen proofing) so simple and intuitive to use. Why did they have to kill it? 

This: “The moment that hobby turns into a grueling, non-paying job is the moment it ceases to be a hobby or even an interest for that matter.” Perfectly said.

Rick's picture
by Rick
June 25, 2015 - 11:30am

A little late? I have been using and invested in Aperture since version 1.0. I find it interesting that any one calling themselves a professional photographer would consider giving it up for something as bad as Photos. My investment is in the 10s of thousands of client photos. Since the announcement was made just last year I fail to see why I am late. Apperantly your position is Apple can do no wrong. I am that this is one loyal long time customer who sees it differently.

Best Regards,

Rick

Ray's picture
by Ray
June 25, 2015 - 3:26pm

Sorry, I’ve already moved on. Lightroom for DAM and some edits, C1 Sessions for XTrans edits. Apple is doing what they believe is the right execution of their business model. Time to move on.

freediverx's picture
by freediverx
July 23, 2015 - 9:18am

What are XTrans edits? A cursory search suggests it’s something proprietary to Fuji cameras. Is this correct?

Ray's picture
by Ray
September 30, 2015 - 5:09pm

Yes, Fuji X series.

mkg's picture
by mkg
June 26, 2015 - 11:18am

Quite frankly, I don’t understand why Aperture has not been given to OpenSource or spun off in some way.  There is sufficient user base to keep it alive and evolve. Given that Apple has no interest any further, why not?  It really doesn’t compete with Photo app - completely different focus.

I’d tried LR originally when deciding on Aperture and found it to be extremely cumbersome, and now considering move to C1.  If Aperture is open sourced or spun off, would muddle along until that new version comes out.

Realizing that I’m in the minority on this but I really don’t need to photo stream, and capture everything with my iPh; hence, Photo is going in the wrong direction for me…

Ray's picture
by Ray
June 26, 2015 - 2:09pm

I’ve wondered the same myself. It makes a lot of sense and with the filters built into the OS, would be fairly simple to improve the editing side. On the catalog side, they could strip out all the connectivity stuff and simplify support in an area that Apple changes constantly and was never particularly reliable, assuming limited Open Source resources. Then fix what is a somewhat flaky data base, at least with referenced which is what I used.

I’ve also thought perhaps they intend 3rd party developers to turn Photos into Aperture. But it seems with the developers have decided to introduce their own apps. Some interesting apps have recently been introduced, Emulsion, Mylio, Affinity. But they are lacking in many areas: keywording, local adjustments, dependent on xml files, etc.

Here’s my experience which might be of some use to those still using Aperture: I started looking for a replacement for Aperture about a year ago. Have been running Aperture, Lightroom and C1 in tandem now for a year. For me, the only choice was the wrong choice, Lightroom. I don’t like the interface. The code leaves a lot to be desired. But for anyone that depends heavily on DAM, it’s one of the very few choices in town.

I also spent some time with a database approach, Photo Supreme. OK app but unless a database is designed to work with a specific editor, there are shortcomings. I chose to use C1 Sessions with Photo Supreme. Good, not great, where it wasn’t great it was all a function of C1 not adhering to standard industry metadata practice and C1’s ongoing challenges with importing JPEG and tif files it can read and exporting tif files other apps can read. Not to mention no matter how pristine I got my Aperture library, it just was not going to import into C1 without a lot of missing images or images it could not read. Unfortunately, C1 provides no filtering tools, beyond a list of files that did not transfer (nothing on what it can’t read other than looking for an icon on the thumbnails) so sorting out the library was not in the cards. And no idea how many files it could not read as I wasn’t going to go through 30,000 thumbs and count icons.

Neither C1 nor Lightroom run near as fast as Aperture on the catalog side. The develop side varies. Overall, the Aperture GUI can’t be matched by either.

C1 has a really fine develop side. For both Nikon and Fuji I find the conversions excellent. Better than Apple or Adobe. Edit all you want, they are still better right at default. Nomenclature is similar to Mac so I found it a quick pickup. The catalog has improved from v7 but that’s not really saying much. It’s lacking in both features and performance. For those that are not catalog dependent, the Sessions mode is gorgeous. But that means Aperture users needs to consider abandoning a library/catalog.

Lightroom is Lightroom. Stable, does little wrong. For high production needs it’s great. For me, as an amateur with plenty of time on my hands, I don’t need its strongest point. I have also been through many of the complaints that dot the Adobe forums. It’s classic Adobe, every OSX update breaks something (my Dell monitor’s desktop layout now gets screwed up after my Mac wakes from sleep under 10.10.3, 10.10.2 is fine - expect it never to get addressed.)

I’m now on Lightroom and using C1 Sessions for my XTrans files. It’s a safe place to be. In the meantime I’m keeping an eye on some of the new apps and continue to ask myself if I really need a database approach beyond the Finder and an image browser.

mkg's picture
by mkg
June 26, 2015 - 4:11pm

Thanks for the insight.  Just haven’t made the commitment to goto C1

Shortly after Photo was released, I gave up and immediately signed up to CC photo subscription at $10/mo for LR and PS, thinking that its $120/yr and PS alone was worth it, since I needed to upgrade my old PS anyway (and not have to spend couple  hundred dollars upfront).  I really try to like LR - both 2014 and now 2015 versions but it really doesn’t do it for me.  Its too compartmentalized and is not at all fluid.  If I have to think that way, I’d rather use Bridge + PS, over LR since still need PS anyway for some things.

So have done nothing.  If C1 comes along with a good discount, I’ll probably give it a go sooner than later.

 

helalwi's picture
by helalwi
June 26, 2015 - 10:48pm

And what DAM would you apply then?

Yesterday I made the STEP and ordered CC. But unfortunately on my MAC I have seemingly some issues with my “Read/Write rights”. I am not able to install the ADOBE Installer program. They have an excellent support chat. But I have to do now tons of things that I am not sure if I am able to follow all the massive instructions that I got to fix my Mac. So I am at a point to give my subscription back. I am rather frustrated at the moment.

For me the DAM is important as in the past I used keywords, locations, faces etc. for each single photograph. I did this consequently over all the years and I fear to loose part of that work which I probably will. 

Best regards, Alex

Ray's picture
by Ray
June 27, 2015 - 5:46am

The good news is Lightroom sucked in all of my metadata and images just fine. The import plug-in worked like a champ.

The bad news is you might be better off just wiping your disk and doing a fresh install. I’ve on and off used Lightroom for 9 years. It can get picky and it can have issues when Apple releases updates. Currently I have 2 issues: the sleep issue I noted above and an inability to select some thumbs with the mouse. Need to use the arrow keys or restart Lightroom. Both issues are well documented in Adobe’s forums. I can live with them.

Would suggest doing a good amount of housekeeping in Aperture before you move and understand what Lightroom will do with adjusted Aperture images. With the latter, it creates jpegs and places them in a unique folder. Which means all of those images will not be where the masters reside. I took all of my 3 to 5 star rated Aperture raws and saved a tif version to the appropriate folders. A lot less work than putting the jpegs back into their appropriate folders.

After you’re done with the import, just let Lightroom run. It took me 2 days for it to build its 2880 previews on a 3.0 i7 rMBP. I only built previews for 2,100 images. Those were Fuji XTrans intensive which Adobe struggles with. Don’t expect a quick build like you get with Aperture. You’ll see this with your normal imports as well. Hope you like coffee breaks.

Once you’re there is solid and a safe place to be. Library is referenced so easy to move again is the way I looked at it. I wasn’t willing to just wrap my Aperture library into a managed library and continue to rely on it. At some point, it’s not going to run.

freediverx's picture
by freediverx
July 23, 2015 - 9:35am

“[Lightroom] can get picky and it can have issues when Apple releases updates.”

A big part of this is Adobe’s one-size-fits-all software development strategy that eschews true native app development for OS X. Adobe couldn’t care less about a seamless user experience. All they care about is maintaining a software suite that is functional across a wide range of platforms at minimal cost and effort.

Their software as a service licensing just adds salt to the wound.

Ray's picture
by Ray
June 27, 2015 - 5:50am

The good news is Lightroom sucked in all of my metadata and images just fine. The import plug-in worked like a champ. The bad news is you might be better off just wiping your disk and doing a fresh install. I’ve on and off used Lightroom for 9 years. It can get picky and it can have issues when Apple releases updates. Currently I have 2 issues: the sleep issue I noted above and an inability to select some thumbs with the mouse. Need to use the arrow keys or restart Lightroom. Both issues are well documented in Adobe’s forums. I can live with them. Would suggest doing a good amount of housekeeping in Aperture before you move and understand what Lightroom will do with adjusted Aperture images. With the latter, it creates jpegs and places them in a unique folder. Which means all of those images will not be where the masters reside. I took all of my 3 to 5 star rated Aperture raws and saved a tif version to the appropriate folders. A lot less work than putting the jpegs back into their appropriate folders. After you’re done with the import, just let Lightroom run. It took me 2 days for it to build its 2880 previews on a 3.0 i7 rMBP. I only built previews for 2,100 images. Those were Fuji XTrans intensive which Adobe struggles with. Don’t expect a quick build like you get with Aperture. You’ll see this with your normal imports as well. Hope you like coffee breaks. Once you’re there is solid and a safe place to be. Library is referenced so easy to move again is the way I looked at it. I wasn’t willing to just wrap my Aperture library into a managed library and continue to rely on it. At some point, it’s not going to run.

freediverx's picture
by freediverx
July 23, 2015 - 9:37am

Did Lightroom preserve folder structure/hierarchy, keywords, location data, and face ID?

Ray's picture
by Ray
September 30, 2015 - 5:26pm

Sorry for the late reply. We’ve been on the road for 3+ months and a notification just got to me upon our return to the USA. I did a referenced Aperture library. The first time I did it I set all the options for the Aperture import plugin and ended up with all my edited Aperture images in one folder. Realizing I would then have to relocate them to the appropriate folder, I tossed the LR catalog, saved my high rated Aperture edits to tiffs in their appropriate folders and turned off the option to import Aperture previews. Worked like a champ, hierarchy was spot on and I go down quite a bit with nested folders. All keywording and ratings were spot on. I don’t use labels. I believe I unstacked all images prior to import. Don’t recall but LR did not have any stacked images after the import. I prefer the DAM in LR. The only area where Aperture is stronger is in the filter HUD. I prefer the editing module in Aperture. Part of the reason is my Fuji XTrans renders were superior and required a lot less work in Aperture. The tools I use, especially the brushes, are superior in Aperture. As are color adjustments. I don’t tend to use NR so, while LR gets a lot of favorable comments here, it means nothing to me. I have tried it. Quite heavy handed. While better than Aperture, C1 is better, as are a lot of NR specific apps.

freediverx's picture
by freediverx
September 30, 2015 - 5:51pm

“The first time I did it I set all the options for the Aperture import plugin and ended up with all my edited Aperture images in one folder. Realizing I would then have to relocate them to the appropriate folder, I tossed the LRcatalog, saved my high rated Aperture edits to tiffs in their appropriate folders and turned off the option to import Aperture previews.”

 

This statement alone guarantees I will never let Lightroom anywhere near my Aperture library. Sounds like you’ve got things under control, but I sense that we appreciate different aspects of Aperture’s capabilities, and those I value most are the ones most lacking  in Lightroom.

Hugenoot's picture
by Hugenoot
June 29, 2015 - 5:06am

I did a update 10.10.4 to 10.11 and with RAW files from a canon 1Dx Aperture showed all images with a pink color cast. Only with fast preview the pictures had no pink color cast. All other things worked well…

Henrik Lorenzen's picture
by Henrik Lorenzen
July 8, 2015 - 1:58pm

i had the same issue with my Nikon D3 but after updating to beta 3 all is back to normal:)

and i would even say the speed has increased

 

 

Hugenoot's picture
by Hugenoot
July 10, 2015 - 3:14am

Hello Henrik,

thanks for your update, indeed Aperture runs fine on beta 3.

A great relief because none of the other programs like lightroom and capture has the options I like on aperture. File locking, version names, direct photo editing and apple script… 

Aperture user's picture
by Aperture user
July 16, 2015 - 8:54am

Edit: I read more of the comments and find you’ve answered my question.

Did you try importing RAW images? Importing RAW images caused a crash on public beta as of today. 

Thanks. 

PS. I had no trouble printing from Early 2009 iMac. As a side note, El Capitan seems to run fine on that old machine. Not my primary machine now.

gfsymon's picture
by gfsymon
July 10, 2015 - 2:16am

Apple have evolved into a complex money making machine.  However, they have solid enough strategies in place concerning their work ethic and how they move forward.

When Apple say; ‘Aperture is over, there will be no further development’ (or some such) this phrase is a typical PR phrase, in that, you have to understand what they are saying and why they are saying it.  In this case, it removes any kind of potential litigation threat, because it is clear that they are no longer ‘supporting’ Aperture.

Does this mean that Aperture will stop working at the next OS upgrade?  No.

I’m on the OS beta program and I can tell you that Aperture was in no way running normally on the first beta of El-Capitan.  Lots of issues.  I can also tell you that Aperture was cited as having issues in the release notes.

This seems a little contradictory doesn’t it?  They’re no longer supporting Aperture and yet they’re specifically mentioning it in bug fixing notes? No it’s not contradictory.

There are 2 ways, to maintain new OS compatibility for an application:

1/ you update the application to be compatible with the new OS software.

2/ you ensure that the new OS software doesn’t ‘break’ the application.

It is the latter of these two that Apple is doing and I can tell you that they continue to do this for some pretty old and otherwise defunct software.

So I expect Aperture to work pretty well in El-Capitan and hopefully in other future OS. It may have some glitches, most likely cosmetic, but it will probably work for quite a while to come.

As you might imagine, Apple could never ever say what I just said and in fact, I probably shouldn’t have said it either, because in two months or two years time, someone will probably reply to this thread, telling me that as a result of my comment, they spent half a million dollars on an image management installation and now it’s broken and they’re suing me.

What is certain, is that there will be no more updates to Aperture (although, I guess they could slip in one last sneaky one before the end of Yosemite, if it easier to fix bugs that way, rather than in the new OS).

One other thing that is important to understand.  Aperture, like all apps, ‘plugs in’ to the OS’s Core technologies.  These can evolve without necessarily breaking Aperture.  So Aperture can in some ways, continue to evolve and be ‘updated’.  A good example of this happened just today, when an update to Digital Camera Raw ‘updated’ Aperture’s ability to process raw files for 10 new cameras.

 

Ingmar's picture
by Ingmar
July 13, 2015 - 2:55am

Sounds encouraging enough to me. I’ll keep my hopes. ;) Of course I have to switch sometime in the long run, but I couldn’t decide yet. And I want so see more of Photos and it’s (hopefully) evolving DAM features.

Hugenoot's picture
by Hugenoot
July 13, 2015 - 7:00am

Today I tested Aperture on 10.11 beta 3, imported 250 Canon 1Dx raw files. Made a selection, did the cropping, corrections and META-data then run a apple script to batch process the images to two folders. The script also combines the META-data in a different order (in the caption it puts the info from the headline, IPTC scene etc.) before Aperture export the image. Each folder has his own export setting, and everything works fine. A repeated this workaround a few times and no crashing of Aperture. Next test will be on the field during a soccer match…

 

freediverx's picture
by freediverx
July 23, 2015 - 9:47am

When Photos was first announced I had hopes that it could grow into an Aperture replacement through continued enhancements combined with third party extensions. However, everything I’ve seen suggests a fundamentally different image management foundation that is hostile to users who want to preserve the project/folder/album hierarchy they’ve built in Aperture.

I love the concept of having my images backed up in the cloud and accessible from every device. I also like the option of viewing images organized and grouped algorithmically by location and date. However, I am not about to abandon years of meticulous library organization to this dumbed down approach.

Photos’ failure to import my Aperture library with its organization intact was an immediate showstopper for me.

DANimage's picture
by DANimage
July 13, 2015 - 3:11pm

Aperture seems to be working fine except the picture displayed from the thumbnail picture is faded. Exporting the picture to a folder is working fine, the colours is there.

Frans….

 

Frans Lichtenberg

gfsymon's picture
by gfsymon
July 23, 2015 - 11:16am

Have you tried printing?  Big problems here.

Lisa's picture
by Lisa
October 13, 2015 - 8:17am

Reply to Frans: Disable onscreen proofing (from the View dropdown menu). This fixed the problem for me. 

Henrik Lorenzen's picture
by Henrik Lorenzen
July 16, 2015 - 9:35am

Yes i did and no issuse what so ever

i even tried to import old folders a round 20000 with no issuse 

Ken Sky's picture
by Ken Sky
July 23, 2015 - 12:53pm

So my dilemma is this: I never cared about Aperture as a DAM (It’s best feature). I love it a an editor and printer driver (It just fits my sensibilities) The higher dynamic range of the newer sensors makes its weak noise reduction immaterial. Can I still import, edit and print with Aperture on El Capitan ? If so, I’ll be happy. PS, I’ve tried C1 & LR but can’t stand the GUI’s.

Ken Sky

freediverx's picture
by freediverx
July 23, 2015 - 1:00pm

PS, I’ve tried C1 & LR but can’t stand the GUI’s.”

This can’t be overstated. I hate using Adobe software so much that switching over from Aperture would feel like switching from OS X to Windows 8.

gfsymon's picture
by gfsymon
July 23, 2015 - 2:17pm

I cannot print *correctly* in Yosemite or El Capitan.  There is a colorsync/profile problem where colours are being incorrectly printed.  It results in under-saturated files with banding in smooth gradients.

I haven’t printed for many months, but have needed to recently which is when I discovered the problems.  The good news, is that Pages can now print as well as Aperture used to (although you can’t choose intent) and it’s the simplest page layout app there is.  I’m printing to a z3100 on 24” roll and I can even centre the images with little effort!

Ken Sky's picture
by Ken Sky
July 23, 2015 - 2:54pm

That’s funny because I print to an HP B9180 on 13x19 Ilford Gold with no problems using Yosemite. That’s why I’m dreading upgrading to El Capitan. I’m just going to sit still and let others be the beta testers.

Ken Sky

gfsymon's picture
by gfsymon
July 24, 2015 - 12:22am

Depending on the type of image and the colour space you use, you may not notice the problem.  You don’t actually have to print to see the issue.

I’d be curious to know if you can see it and what version of Yosemite you’re running.  Download this file (a grad made in PS) and see if you see any banding when previewing.  If you use ‘Open in PDF’ you will get an accurate enough view.

It’s possible that I have a problem with my installation of Aperture, but unlikely and I have no problems printing from other apps.

Pages

You may login with either your assigned username or your e-mail address.
Passwords are case-sensitive - Forgot your password?