Sorry I haven't gotten back to you about some cross-posts - still owe someone a clear step by step on mutli-screen workaround w/ Aperture 3 and arraysync… been busy with 2 gigantic print installations, a new 9900, etc, etc.
In any case a few of my blog readers sent me an issue regarding color conversions that appear to be really messed up.
Here is the general issue…
1) Import any file format into (JPEG/TIFF not RAW) that has colors outside of sRGB gamut and has a wider gamut profile like Adobe1998 or ProPhoto.
2)Not only is the onscreen display of those colors WAY WAY different than ANY color space conversion scenario that you can concoct in PS but it is impossible to get back to the original colors (that are out of sRGB gamut) when exporting…
3)The results produced by Aperture do not seem to be reproducible in any open/convert/save workflow in PS including just assignment of profiles involved.
I have tried every possible permutation of original/convert to target/convert back to original profile using every method possible in PS and cannot even begin to simulate the behavior of Aperture when importing ProPhoto/Adobe 1998 files into Aperture and then exporting them with the same profile as they used to be…
I can post a file that one of my readers gave me that clearly illustrates the issue fi you would like… Essentially it is an image with a block of a single spot color that happens to be outside of sRGB…
Thanks Robert to continue to work over this problem. At this point I have not heard back from Apple support. This makes AP3 like the Apple TV in Steve’s words, “Still a Hobby.” I can only hope that enough people put in complaints to Aperture Feedback to get it fixed. Thank you
Here is a test file that was originally sent to me along with a possibly better explanation of the issue…
No problem - I have done further testing and cannot come up with any suitable explanation as to what is going on here.
Thanks Robert. DBmoore, you have talked with Apple a bit about this right? Didn’t they contact you for more info at some point? Or am I thinking of another issue…
If they did, then don’t expect to hear a resolution. That’s not the way it works; if they contact you for more info they’ll do what they can and hopefully roll a fix into a future release, but don’t expect to hear from them again unless they need more information.
As I’ve pointed out before, when it comes to color space stuff I’m a bit of a n00b so I can’t offer anything of value to this conversation. You guys are well more versed on this than I am.
— Have you signed up for the mailing list?
My main goal is for someone to either prove a small group of us right by confirming our findings or to prove us wrong (I seriously doubt this only because I am arrogant and tenacious and tried my best to prove DBmoore incorrect but could not).
If there are just a few other folks out there with PS and a basic knowledge of color space conversions that can either confirm this is a GIANT problem or explain what the conversion process actually is so that it can be worked with that would make me happy.
1)If there is some sort of consensus that my observations are correct then we all have a fairly giant issue that you, me, and anyone that remotely listens to us needs to be aware of.
2)There is a very very funky but explainable set of conversions going on that has to be considered in just about any serious photographer’s work-flow.
Grant Symon first told me about it. I think he got it off the Aperture forum site back in July of 2011!!!!!!!!!!!!. Im a professional and really like apertures’ workflow but this Color Management CM is Hobbyist! I want to be a FanBoy again, and hate being the squeaky wheel.
not hobbyist - just plain broken…
No I didn’t get it off the Aperture forum … it was me that posted it on there.
I actually came across this motherfucker of a bug (excuse my French) about a year ago now. I sat on it for a while, because I have some contacts with Apple and tried to get it dealt with that way. That went nowhere, so I then simply submitted it as a bug through the normal channels and then finally posted a report about it on the Aperture forum.
It seems to me that the engineers have not really understood what the problem is, because in the last 2 updates they have described ‘fixed’ issues, that they ‘fixed’ and those descriptions would fit this bug. However, the ‘fixes’ haven’t changed anything. This is very frustrating and is almost more of a concern than the bug itself.
nice to have you chasing this bug too. The more noise, the more chance they’ll hear something. :) :) :)
It’s about as worrisome as my ordeal with a to be nameless “color management” vendor that has gone NOWHERE in the course of a YEAR of me working on it with them - directly with their “engineers” that seem to want to blame the issue on the way OTHER stuff works that their company officially SUPPORTS. Fuck it - I decided to go XRITE about 3 mons ago but have not purchased yet due to the new product line-up/device just released. Soon though.
So since this topic came up today I sent another email to the person at Aperture feedback
firstname.lastname@example.org. He Surprised me with a reply! But atlas its typical of apple.
Thank you for checking in. Unfortunately, I do not have any new information regarding this issue at this point. If any information does become available, I will update you.
In the meantime, and as always, if you have any questions, please let me know.