Luminous Landscape Forum
Raw & Post Processing, Printing => Colour Management => Topic started by: Simon J.A. Simpson on February 27, 2010, 01:14:53 pm
-
MacFixit has posted an article about the beta release of Snow Leopard 10.6.3.
http://reviews.cnet.com/8301-13727_7-10456...tag=mostDis;dis (http://reviews.cnet.com/8301-13727_7-10456820-263.html?tag=mostDis;dis)
Intriguingly, the article lists one "focus areas from this build" as:
• Improves printing reliability and compatibility with 3rd party printers
Could this be the fix for printing non-colour managed files we are all hoping for ?
-
MacFixit has posted an article about the beta release of Snow Leopard 10.6.3.
http://reviews.cnet.com/8301-13727_7-10456...tag=mostDis;dis (http://reviews.cnet.com/8301-13727_7-10456820-263.html?tag=mostDis;dis)
Intriguingly, the article lists one "focus areas from this build" as:
• Improves printing reliability and compatibility with 3rd party printers
Could this be the fix for printing non-colour managed files we are all hoping for ?
I wouldn't bet anything on that, unfortunately.
-
I wouldn't bet anything on that, unfortunately.
Me either. But it's always good to have hope !
-
MacFixit has posted an article about the beta release of Snow Leopard 10.6.3.
http://reviews.cnet.com/8301-13727_7-10456...tag=mostDis;dis (http://reviews.cnet.com/8301-13727_7-10456820-263.html?tag=mostDis;dis)
Intriguingly, the article lists one "focus areas from this build" as:
• Improves printing reliability and compatibility with 3rd party printers
Could this be the fix for printing non-colour managed files we are all hoping for ?
This is not broken in 10.6 only in some Epson drivers.
Doyle
-
This is not broken in 10.6 only in some Epson drivers.
Doyle
Exactly. It keeps being reported as an issue with the OS, but my understanding is that it is just a matter of driver noncompliance.
Keep checking at the Epson site for patches.
-
Exactly. It keeps being reported as an issue with the OS, but my understanding is that it is just a matter of driver noncompliance.
Depends on who you listen to Marco. Apple engineers have publicly admitted there are "issues" which correlate exactly with what has been disclosed by industry experts working for Adobe. Furthermore other large companies who are outright industry leaders in the Colour Management field have also declared there are issues in 10.6 colour management. We may never fully know the exact cause, and in all likelihood it may be a little bit of everything, OS, software and drivers together.
Some however would have you believe that everything including global warming is Epson's fault, and insist they know the vendor's software better than the vendors themselves, and somehow are right whilst all those experts with actual credentials are wrong.
Anything you read on an internet forum should be taken with a pinch of salt. The mantra of "Do Your Own Research" applies.
-
Depends on who you listen to Marco. Apple engineers have publicly admitted there are "issues" which correlate exactly with what has been disclosed by industry experts working for Adobe. Furthermore other large companies who are outright industry leaders in the Colour Management field have also declared there are issues in 10.6 colour management. We may never fully know the exact cause, and in all likelihood it may be a little bit of everything, OS, software and drivers together.
Some however would have you believe that everything including global warming is Epson's fault, and insist they know the vendor's software better than the vendors themselves, and somehow are right whilst all those experts with actual credentials are wrong.
Anything you read on an internet forum should be taken with a pinch of salt. The mantra of "Do Your Own Research" applies.
Well, I can only say that, so far, I have not had problems profiling printing devices (inkjet and laser) using Snow Leopard. If the problem does indeed exist, I have yet to encounter it.
-
Well, I can only say that, so far, I have not had problems profiling printing devices (inkjet and laser) using Snow Leopard. If the problem does indeed exist, I have yet to encounter it.
Snow Leopard is only one part of the equation that is problematic, and in fact this began with Leopard, not Snow leopard. If indeed you are not having problems then either you are printing your targets from an older version of Photoshop, or if using CS4 you aren't profiling an Epson printer.
-
Snow Leopard is only one part of the equation that is problematic, and in fact this began with Leopard, not Snow leopard. If indeed you are not having problems then either you are printing your targets from an older version of Photoshop, or if using CS4 you aren't profiling an Epson printer.
It would seem that there have been various Apple colorsync difficulties even "pre-Tiger" let alone Leopard or Snow Leopard:
http://luminous-landscape.com/forum/index....st&p=321964 (http://luminous-landscape.com/forum/index.php?showtopic=38944&view=findpost&p=321964)
http://luminous-landscape.com/forum/index....st&p=240030 (http://luminous-landscape.com/forum/index.php?showtopic=29496&view=findpost&p=240030)
http://luminous-landscape.com/forum/index....st&p=117551 (http://luminous-landscape.com/forum/index.php?showtopic=16826&view=findpost&p=117551)
-
Expecting that 10.6 dot anything will fix all the recent, let alone legacy issues is folly. Doesn’t matter who blames who, the facts are, depending on the OS, driver and app, everything can work fine or not. For example, those with issues printing untagged documents in SN in Photoshop and certain Epson drivers could print them fine in Preview. You’d think that points a finger at Adobe but no, other combo’s can work or fail. I suspect there is a number of issues, bug fixes upon bug fixes from one company hoping to help another that have compounded this issue over the years. FWIW, Printer Manages Color falls into this camp of, it might work, it might not work, YMMV.
-
It would seem that there have been various Apple colorsync difficulties even "pre-Tiger" let alone Leopard or Snow Leopard:
http://luminous-landscape.com/forum/index....st&p=321964 (http://luminous-landscape.com/forum/index.php?showtopic=38944&view=findpost&p=321964)
http://luminous-landscape.com/forum/index....st&p=240030 (http://luminous-landscape.com/forum/index.php?showtopic=29496&view=findpost&p=240030)
http://luminous-landscape.com/forum/index....st&p=117551 (http://luminous-landscape.com/forum/index.php?showtopic=16826&view=findpost&p=117551)
I see it as a fact of "digital" life that things will not be perfect, and growing pains will be recurrent. And as a sign of a certain maturity to accept that, to some degree.
The question to me is not: "How bad is [Apple, Adobe, etc.]?" but instead "Now that [Apple, Adobe, etc.] knows of the problems, is it moving to address and fix them?".
Also, and possibly as relevant, instead of sitting on my hands steaming over the problems while waiting for a solution to be handed over to me, what can I do to obviate or circumvent them until an OS fix is provided?
My 2 cents.
-
I suspect there is a number of issues, bug fixes upon bug fixes from one company hoping to help another that have compounded this issue over the years.
Andrew- Entirely possible, but somewhere around 10.6, wouldn't you "assume" that Apple would have created stable, clean code for printing, new APIs or not. If they haven't, then they are the most culpable of the three parties. If they have produced clean code with 10.6 (and 10.6.3 won't contain a "cure") then the next most culpable party is Epson. Really, how hard is it to rewrite the drivers for the Pro printers and maybe the 3800 and 2880, six months after the 10.6 appeared. Lastly, I think Adobe deserves the least amount of blame in this three ring circus. Until Apple and Epson get their sheet together, Adobe (with CR4 and Lightroom) is just patching their bugs. I just wish the "retired" guy with the big stones and the Harley would offer some not so subtle "opinions" on the current state of this issue.
-
I just wish the "retired" guy with the big stones and the Harley would offer some not so subtle "opinions" on the current state of this issue.
I presume you are talking about me? I don't ride a Harley...I ride a BMW R1200 Adventure (which is a completely different sort of motorcycling experience). I suppose my appearance might induce you to assume I'm a HOG owner...
I know what's going on...I'm not entirely at liberty to say though. The ultimate fault is the Apple with their new API's that prelude the the use of older API's in Photoshop CS4 and now DEMAND that there is no such thing as an "intentionally untagged file". But the short term problem is the fault of the way the driver is reporting to ColorSync...Apple could fix it, Epson could fix it or Adobe could fix it...Adobe is less inclined to do platform specific fixes anymore and Photoshop and the same Epson driver on Windows is fine.
So, will 10.6.3 fix the No Color Management problem with certain Epson driver? I have no idea...you think Apple would pre-disclose anything to anybody? all I can say is we'll see...
-
I presume you are talking about me? I don't ride a Harley.....Apple could fix it, Epson could fix it or Adobe could fix it...Adobe is less inclined to do platform specific fixes anymore and Photoshop and the same Epson driver on Windows is fine.
So, will 10.6.3 fix the No Color Management problem with certain Epson driver? I have no idea...you think Apple would pre-disclose anything to anybody? all I can say is we'll see...
Thanks Jeff. Sorry I got the bike thing wrong. At least there is a recognition of "it" being a fixable issue ("The ultimate fault is the Apple") that someone could "rectify". Here's what I take from the situation. Apple has ONE operating system that they could fix. Epson has a THOUSAND +/- drivers that they could rewrite. Adobe has Photoshop and Lightroom. The first two can play Dumb and Dumber, but I hope Adobe will relent if the other two won't.
-
Thanks also, Jeff.
My understanding also (restrictions on disclosure also apply to me but I am sure you know a lot more that I !).
Thanks for a blast of common sense and some rational thinking.
-
Now, Jeff DID own a Harley at one time.
Wisely, he sold it....
-
Here in the UK at the moment the "Focus on Imaging" annual photgraphic show is on, think of it as a smaller PMA. I went yesterday and tried to find out anything I could about this issue.
I spoke to an Epson tech guy on their stand, I've spoken to him before and he's a nice guy, he is personally familiar with this issue and told me it is causing him grief as well as it's stopping him profiling papers easily on his own systems etc. He also said, all conspiracy theories aside, Epson really isn't the kind of company who would ignore something like this. He told me drivers have been recompiled for Snow Leopard and submitted to Apple and been approved, and those are what we're using right now, v6 or something. He said those drivers have two modes, colour management on and colour management off and that both those modes are working, so the error of double profiling is not being introduced during their part of the process, the data arriving at the driver has already been managed by colorsync. This we kinda know already. What is clear is that Epson are not going to build in a workaround directly into their drivers for one version of one piece of software, it just wouldn't be a clever thing to do.
I also spoke to two people on the Adobe stand. The first guy I spoke to was very familiar with the problem and it turned out he doesn't actually work for Adobe but was a freelance colour-management consultant brought in for the show. He was just as frustrated as the rest of us, maybe more so, and admitted he uses CS3 to print out the targets. He couldn't tell me anything about whether/when it will be fixed, but he did say he knew that engineers had been told to set aside one day a week to work on "JFI" issues, that is Just Fix It. He also alluded to the fact that CS5 would be coming out this year...
The second guy on the Adobe stand I spoke to wasn't overly familiar with the problem, but he did work for Adobe. He told me that all work on CS4 has been stopped and everyone is working on CS5 and that the problem won't be addressed in CS4.
This is not good news, and I have to admit I'm personally pretty annoyed about it, I don't consider this to be a bug, but a major flaw. If people are having to resort to installing the previous release of the software just to perform a task they should expect to easily perform, that is not a minor bug, no matter who the fault lies with.
Apple were not present at the show.
-
He was just as frustrated as the rest of us, maybe more so, and admitted he uses CS3 to print out the targets.
[...]
The second guy on the Adobe stand I spoke to wasn't overly familiar with the problem, but he did work for Adobe. He told me that all work on CS4 has been stopped and everyone is working on CS5 and that the problem won't be addressed in CS4.
Hold it...how is this a Mac OS problem if it doesn't manifest itself when using CS3?
Instead, following simple logic, wouldn't that point to problems with how Adobe implemented the print functions in CS4 rather than to problems at the OS or Epson driver levels?
-
Hold it...how is this a Mac OS problem if it doesn't manifest itself when using CS3?
Instead, following simple logic, wouldn't that point to problems with how Adobe implemented the print functions in CS4 rather than to problems at the OS or Epson driver levels?
Marco
Of all people I would have surely thought that you would know that PSCS4 uses Apple's new printing path while CS3 uses the old path.
The new printing path is where the problem is when printer drivers or applications (witness LR3 beta) are not written correctly which manifests itself with double profiling. So is Epson totally to blame for this, I doubt it.
As in my statement about LR3 beta where with Canon drivers that work correctly with LR2 and PSCS4 they do not work correctly with the LR3 Beta. Now whose fault is that? And this brings up an even bigger can of worms because apparently some Epson drivers work correctly with LR3 beta and do not double profile.
As for Apple, why do they insist with the new printing path that when application manages color is chosen the drivers (are supposed to) default to no colormangement, instead of the way the old printing path worked and let the user (or forces the user to) make these choices. Now whose fault is that?
So I am thinking this is a matter of trying to idiot proof color managed printing, and everybody seems to be chasing a moving target. Fix one problem for one vendor and screwup one for another.
Apple just give us all the choices back in the printer drivers like the old path was. THAT WORKED FINE!
Doyle
-
Marco
Of all people I would have surely thought that you would know that PSCS4 uses Apple's new printing path while CS3 uses the old path.
Mmmm..."of all people"? You know me that well?
No, I do not keep up with all the latest gossip. I'm lucky to have you to straighten me out... :-)
The new printing path is where the problem is when printer drivers or applications (witness LR3 beta) are not written correctly which manifests itself with double profiling. So is Epson totally to blame for this, I doubt it.
Help me here: the application or driver are not written correctly for the OS's new printing path, but that is Apple's fault?
So I am thinking this is a matter of trying to idiot proof color managed printing, and everybody seems to be chasing a moving target. Fix one problem for one vendor and screwup one for another.
Right. There is nothing wrong in trying to make the procedure less complex, as long as it doesn't create additional problems in place of the ones that it allegedly solves.
Let's not be too harsh and accusatory, though: as long as an effective, relatively simple workaround is still possible, the finger-pointing should only go so far, after which it turns sour and unproductive.
-
Help me here: the application or driver are not written correctly for the OS's new printing path, but that is Apple's fault?
Fault? No...
Responsibility? Yes...
Adobe "used" to hack around bugs and issues in the older print path but following Apple instructions to NOT hack around the new print path (called Tioga I believe), Photoshop CS4 is restricted to doing what Apple told Adobe to do for printing in CS4.
Epson, while producing new Leopard (and Snow Leopard) print drivers were also trying to follow Apple's APIs regarding ColorSync compatibility...seems they didn't quite get it right...but there were no hacks around the issues in CS4 so, as a direct result, you can't reliably output color management targets to certain Epson printers from Photoshop CS4...the work around is to intentionally tag the file with a profile so that Photoshop CS4 can work around the impossibility of sending an untagged file though the Apple print and ColorSync pipeline...
So, Apple's fault? Apple was the one forcing a change in the APIs and forcing new applications and drivers to follow those APIs. So, if you want to know who was responsible, I would point to Apple. Wouldn't you?
-
So what should a simple user like me do? I have an iMac running Leopard 10.5.8. I have LR2 and Beta 3 installed (but have not tried it for printing). I haves CS4. I have printed happily using LR2 and CS4. So far I have NOT installed Snow Leopard because I keep reading about all these problems.
Am I best sticking with what I've got and waiting for this problem to be solved? Am I worrying about nothing?
Peter
-
So what should a simple user like me do? I have an iMac running Leopard 10.5.8. I have LR2 and Beta 3 installed (but have not tried it for printing). I haves CS4. I have printed happily using LR2 and CS4. So far I have NOT installed Snow Leopard because I keep reading about all these problems.
The problems primarily being discussed here concern those printing targets for building ICC profiles. Do you have that need? If not, move on and upgrade if you wish. And even if you do need to print such targets, there are workarounds. IOW, while it would be nice if this all got worked out, its not a really big deal.
-
So what should a simple user like me do? I have an iMac running Leopard 10.5.8. I have LR2 and Beta 3 installed (but have not tried it for printing). I haves CS4. I have printed happily using LR2 and CS4. So far I have NOT installed Snow Leopard because I keep reading about all these problems.
Am I best sticking with what I've got and waiting for this problem to be solved? Am I worrying about nothing?
Peter
I am sure if you tell us what printer you are using there would be someone here that could tell you whether you can print in SL without double profiling or what workaround can be used if needed.
While printed unmanaged targets seems to be the only issue with newer Epson drivers, older printer are not really supported at all in SL and will give double profiling when printing using Apple's new printing path. However for application that use the old printing path none of these problems exist with a driver written for Leopard in Snow Leopard.
Doyle
-
Here in the UK at the moment the "Focus on Imaging" annual photgraphic show is on, think of it as a smaller PMA.
Well, maybe not smaller. PMA is shrinking ... Canon wasn't even there this year. They opted for CES and WPPI instead.
-
I am sure if you tell us what printer you are using there would be someone here that could tell you whether you can print in SL without double profiling or what workaround can be used if needed.
Doyle
I am using an Epson 3800 and haver a ColorMunki which I use mainly for screen calibration. I have only used the colormunki (with some expert help) to produce profiles for a couple of papers and otherwise use the Epson profiles which seem to work well.
Peter
-
I am using an Epson 3800 and haver a ColorMunki which I use mainly for screen calibration. I have only used the colormunki (with some expert help) to produce profiles for a couple of papers and otherwise use the Epson profiles which seem to work well.
Peter
The ColorMunki can have issues with leopard as well as Snow Leopard if making paper profiles but a simple work around seems to solve this (although I can't scientifically prove it does since I have no clue what the targets are supposed to look like ... I just know the profile seems quite normal and produces good results.), For calibrating your display it works fine.
As far as printing, other than the problem of printing targets mentioned by Andrew, the most common issue seems to be installing the driver and setting up the printer, both are pretty easy fixes if you run into them. First you have to have Rosetta installed on your Mac to run the Epson installer, not a big deal. Second when setting up the printer in the Print and Fax panel, it may or may not work with Bonjour, so you may need to use Epson IP instead. According to Epson site this is the opposite (the IP driver is problematic). I have been running a 7900 with Bonjour for a long time, then suddenly after I had to resinstall some things and reset my printing system, when resinstalling the 7900 I couldn't print. A call to Epson and the tech tells me to use Epson IP instead, "Bonjour doesn't work and never has". while this statement is absolutely false (the iMac sitting next to me was printing from Bonjour just fine while I was trying to get my laptop set up again), using IP solved my problems, both with the 7900 as well as Epsons workforce 610 consumer all in one printer.
To use Epson IP, when setting up the printer in the Print and Fax pane, you just have to wait for about 30 seconds for it to show up. The Bonjour choice shows up right away, the IP one takes a little while. Choose it and everything should work.
Edit: corrected wording as pointed out by Jeff in following post.
-
First you have to have Rosetta installed on your Mac to run the Epson driver, not a big deal.
Actually, you don't need Rosetta for the driver...you need it to run the installer. Epson needs to update their installer software. The driver itself is (or would be) happy without Rosetta.
-
Actually, you don't need Rosetta for the driver...you need it to run the installer. Epson needs to update their installer software. The driver itself is (or would be) happy without Rosetta.
Right. I said it correctly in the first part of my post describing the problems, but then didn't word in correctly when actually talking about how to resolve the problems. Thanks for pointing that out.
-
Right. I said it correctly in the first part of my post describing the problems, but then didn't word in correctly when actually talking about how to resolve the problems. Thanks for pointing that out.
Sorry bud...didn't bother to keep track of the whole darn thread :~(
I just get kinda tired by the back and forth...so when I see something I tend to pounce instead of reread the whole thread to see what might have been posted. Kinda hard to keep track sometimes...(and sometimes I'm purely SHOCKED, SHOCKED I tell ya) by some of the posts I actually make...
Has something to do with a really high late nite intolerance to, well, "not getting something just right"...
:~)
-
Thanks for your help guys. I guess I've always been reluctant to change things that seem to work OK unless there is some real benefit and I can't see much benefit in changing to Snow Leopard (at present) and giving myself some potential problems with printing using the 3800 or profiling with the ColorMunki. But ... I suppose I will have to take the plunge sometime.
Peter
-
Thanks for your help guys. I guess I've always been reluctant to change things that seem to work OK unless there is some real benefit and I can't see much benefit in changing to Snow Leopard (at present) and giving myself some potential problems with printing using the 3800 or profiling with the ColorMunki. But ... I suppose I will have to take the plunge sometime.
Peter
Since Apple (or whoever, whatever) screwed up monitor hardware calibration 10.5.6, I've reverted to 10.5.5. I now therefore have a G5 running 10.5.5, printing to an Epson 3800 from PSCS3, fed by Aperture 2. This works fine, beautifully in fact. Net result:
- i 'm not going to buy a Mac Pro (Apple loses revenue)
- i'm not going to buy Aperture 3, since it needs Intel (Apple loses revenue)
- i'm not going to upgrade from PSCS3 (and until now I always upgraded, since 2.0) (Adobe loses revenue)
- no incentive to upgrade my printer (Epson loses revenue)
All 3 can let me know when they've sorted it out. Until then ... whatEVER.
(Actually, unless Apple readjusts focus a bit away from consumer gadgetry, I can even envisage moving to Windows, where, remarkably, there's less of this nonsense these days)
-
Hi
I downloaded 10.6.3 today, have just profiled some paper, done a print and.... it works perfectly!
(iMac, Colormunki, CS4 and epson 3880)
I am looking forward to hearing about everyone else.
William
-
Hi
I downloaded 10.6.3 today, have just profiled some paper, done a print and.... it works perfectly!
(iMac, Colormunki, CS4 and epson 3880)
I am looking forward to hearing about everyone else.
William
By jove, I think he could be right!
More info to follow...
-
Doesn't specifically address the color profiling issue in the overview, reading the full specs now at http://support.apple.com/kb/HT4014 (http://support.apple.com/kb/HT4014) and remain hopefully optimistic: Second bullet point is this,
General operating system fixes and improvements provided for:
printing reliability.
-
Well, I can only say that, so far, I have not had problems profiling printing devices (inkjet and laser) using Snow Leopard. If the problem does indeed exist, I have yet to encounter it.
Me either which makes it impossible for me to test if the new build works or not. On the Epson printers I have, they behave as expected. Be great if someone that has a driver that didn’t work could comment about what the upgrade did or didn’t do.
-
My particular combination of MacOSX 10.6.3, Photoshop CS4 and an Epson 7900 is now producing untagged profiling charts correctly for the first time without the need to resort to a workaround. I have just updated the thread that I started back in January last year when I first encountered this particular problem.
http://luminous-landscape.com/forum/index....t=0#entry253945 (http://luminous-landscape.com/forum/index.php?showtopic=31410&st=0#entry253945)
Perhaps Wayne and a few others could test the same combination?
-
My particular combination of MacOSX 10.6.3, Photoshop CS4 and an Epson 7900 is now producing untagged profiling charts correctly for the first time without the need to resort to a workaround. I have just updated the thread that I started back in January last year when I first encountered this particular problem.
http://luminous-landscape.com/forum/index....t=0#entry253945 (http://luminous-landscape.com/forum/index.php?showtopic=31410&st=0#entry253945)
Perhaps Mac OS 10.6.3 has provided a fix on whatever was wrong in earlier versions?
I'm asking because I hopped straight from 10.5.8 to 10.6.3, and have had no experience of intermediate versions. (Whenever feasible, I try not to be an "early adopter").
-
Perhaps Mac OS 10.6.3 has provided a fix on whatever was wrong in earlier versions?
I'm asking because I hopped straight from 10.5.8 to 10.6.3, and have had no experience of intermediate versions. (Whenever feasible, I try not to be an "early adopter").
I first encountered problems with MacOSX 10.5.6
-
My particular combination of MacOSX 10.6.3, Photoshop CS4 and an Epson 7900 is now producing untagged profiling charts correctly for the first time without the need to resort to a workaround. I have just updated the thread that I started back in January last year when I first encountered this particular problem.
http://luminous-landscape.com/forum/index....t=0#entry253945 (http://luminous-landscape.com/forum/index.php?showtopic=31410&st=0#entry253945)
Perhaps Wayne and a few others could test the same combination?
That's good news. Unfortunately I won't be around any of my printers for a few days, but as soon as I am I will test this as well.
-
Hi
I downloaded 10.6.3 today, have just profiled some paper, done a print and.... it works perfectly!
(iMac, Colormunki, CS4 and epson 3880)
I am looking forward to hearing about everyone else.
William
Quick question, was the munki set to make a version 4 profile (default) or did you have the preferences set to make a version 2 profile.
Just curious if 10.6.3 resolves the problem with v 4 profiles as well.
-
I'm wondering the same thing about V4 Profiles. Now that a few people have given it a go and I just finished a job I think I'll do the download and hopefully I'll be pleasantly surprised and everything will work just fine. Thanks for reporting your results.
-
Hi Wayne
Good question!
I am at work now but will check when I get home, I've got a sneaking suspicion that I set it to Version 2 some time ago (unless it defaulted back to Version 4)
I will let you know in about eight hours.
Cheers
William
-
I down loaded 10.6.3 and running my first test print from my Epson 9600 and it's looking good so far - fingers crossed.
-
Quick question, was the munki set to make a version 4 profile (default) or did you have the preferences set to make a version 2 profile.
Just curious if 10.6.3 resolves the problem with v 4 profiles as well.
Wayne, it is set to Version 2!
Will I need to make new profiles in Version 4 or can I simply change it to Version 4 a print with current profiles? Or should I let sleeping dogs lie?
-
I down loaded 10.6.3 and running my first test print from my Epson 9600 and it's looking good so far - fingers crossed.
What settings are you using?
I have just tried a few tests with my trusty Epson 9600 and nothing works consistently with MacOSX 10.6.3 as follows:
1. Untagged profiling chart
CS2 and CS4 identical and correct when printed from Windows XP.
CS1 and CS4 on MacOSX 10.6.3 both incorrect and different from each other.
2. Test print tagged with ProPhotoRGB
CS2 and CS4 identical and correct when printed from Windows XP.
CS1 and CS4 on MacOSX 10.6.3 both incorrect and different from each other.
I used standard workflow to produce the untagged prints i.e. colour management turned off in both Photoshop and the printer driver.
I used standard workflow to produce the tagged prints i.e. colour managed by Photoshop and turned off in the printer driver.
The only anomaly is that in order to print from CS1 under MacOSX 10.6.3, I had to first set up a soft proof file in CS4 and then use this in CS1.
Profiles are not directly accessible from CS1 on my installation of MacOSX 10.6.3.
Edit1:
I have now run a more comprehensive series of tests on my Epson 9600 and the results can be seen here:
http://luminous-landscape.com/forum/index....showtopic=42745 (http://luminous-landscape.com/forum/index.php?showtopic=42745)
-
CS2 custom icc profile with print colour management off - image used for the test was a target print from colourmanagement.net this matches my print using the same setting printing under Tiger OS. I tried another paper with a canned profile and very acceptable results, tomorrow I'll print the target again on 10.6.3 using the ColorBurst rip to check the accuracy of the actual print. Then some known prints from my own files that should give me the confidence I need if it throws something odd I'll report it here.
-
What settings are you using?
I have just tried a few tests with my trusty Epson 9600 and nothing works consistently with MacOSX 10.6.3 as follows:
So your earlier post indicates things are working, are you now saying things are apparently working correctly except with Epson's older printers? Or are you suspecting perhaps things are not fixed?
I just tested some 7900 targets and untagged targets appear identical to those using Eric's workaround.
-
Wayne, it is set to Version 2!
Will I need to make new profiles in Version 4 or can I simply change it to Version 4 a print with current profiles? Or should I let sleeping dogs lie?
i would just continue to use it. You would need to make a new v4 profile to test it, but no reason unless you are curious ... no affect on image quality.
I may test this here at the shop tomorrow.
-
So your earlier post indicates things are working, are you now saying things are apparently working correctly except with Epson's older printers? Or are you suspecting perhaps things are not fixed?
My 7900 does seem to be producing my profiling test chart correctly now.
However, I haven't used or tested my 9600 since acquiring my 7900 in November 2008.
As a few people have been recently posting about 9600 problems I decided to run a few of my own tests out of curiosity and because I want to sell it.
I suspect the problem with the 9600 is that the print driver needs to be updated to work correctly with Snow Leopard. Unfortunately I doubt Epson will ever update this driver.
I just tested some 7900 targets and untagged targets appear identical to those using Eric's workaround.
Is matte paper looking ok?
-
I decided to do some detailed measurements for a baseline, going back to 10.5, before loading 10.6.3. I will then do a test for any changes afterwards.
First, The secret seems to be, as Jeff Schewe and others inferred earlier, to have the printer driver loaded so that its used instead of Apples drivers. In my case, its an Eps 4880, so when you click options for the printer, it should show driver ver. 6.12, which is the latest driver for 10.6 from eps.
Test profile- My own before snow leopard for Ilford Gold Fiber Silk from I1 TC 9.18 test charts, I1 Match 3.6.3, I1 Pro, rev. D. It has a few lumps but gives reasonable prints.
Test print- Eye ones lab_test_image.tif, which has the standard test chart imbedded.
From PS CS4, PS col. Mgt, rel. colormetric; Pr. col. Mgt. off. In case the post doesn't format correctly, I will try to correct it ( you may have to count the entries). In any case the important numbers are the dE's and the absolute comparison with the testchart orig. nos. Measured w/i1 share.
Patch no. Before SL (L*,a*,b*) After SL dE
1 38.2, 15.2, 17.7 38.2,14.8,16.2 dE1.5
2 66.9, 16.1, 18.5 66.2, 15.8, 17.0 dE1.7
13(blue) 29.4, 17.5, -53.4 29.7, 16.8, -52.8 dE1.0
14(gr) 56.0, -39.7, 36 55.0, -39.8, 34.4 dE1.9
15(red) 42.3, 56.6, 27.8 42.0, 55.7, 26.9 dE1.3
So- two possible conclusions- Getting the printer driver loaded correctly gets you past the snow Lep. problem, or------
Its uses the Apple driver no matter what it says its doing(which I don't believe to be the case).
As an aside, the dE between CS4 and LR2 prints goes up to between 4 and 7.
Scott McRae
-
Is matte paper looking ok?
Yes, I specifically tested using matt paper because I remember it seems to be the most problematic.
-
I decided to do some detailed measurements for a baseline, going back to 10.5, before loading 10.6.3.
I didn't read the rest of your post in detail(will later), but just a thought ... 10.5 is where this problem began and we began having to work around the problem. So not sure going back to 10.5 to achieve a "baseline" will work.
From all the testing I have done and seen Ryan do, the best work around was printing from CS2 on 10.4. Other combinations worked, (I think CS3 worked OK on 10.5) but Ryan seemed to have the most success getting his baselines printing from a Windows system.
I didn't measure my targets, I would assume some variance. However, problematic targets were easily differentiated visually when compared ... it was quite obvious is some color patches.
I hope to test this a little more thoroughly with my 11880 over the weekend, but it does appear that using 10.6.3, CS4, and the most recent epson drivers has resolved the problem in printing unmanaged targets on my 7900.
-
I'm still wondering if anyone has printed with a v4 profile with success. I mean no gray borders on the print.
-
i would just continue to use it. You would need to make a new v4 profile to test it, but no reason unless you are curious ... no affect on image quality.
I may test this here at the shop tomorrow.
I am curious - will check it out tomorrow and see what happens.
Thanks
-
Hi,
I guess that the latest software sets default to V2. I had V4 on my Color Munki but it's now set to V2 without my doing. My old profiles seem to have gray borders while new ones seem to work. Unfortunately I'm not experienced enough to observe subtle issues.
I essentially moved from Leopard to Snow Leopard when switching computers, so I have been trough a transition with a few issues.
I'm a bit confused that Apple is messing up color management, it was my belief that CM was one of the strong selling points of Mac OS/X.
Best regards
Erik
Wayne, it is set to Version 2!
Will I need to make new profiles in Version 4 or can I simply change it to Version 4 a print with current profiles? Or should I let sleeping dogs lie?
-
I'm a bit confused that Apple is messing up color management, it was my belief that CM was one of the strong selling points of Mac OS/X.
Not sure Apple is "messing it up", but they have tried to improve the printing pipeline as well as the functionality of ColorSync within the OS. Some of the changes are actually good ... you can actually apply a profile to about any document from any application ... for example you can print from iPhoto and actually apply color management.
No doubt there's been some glitches as they've moved to the new pipeline requiring applications and printer drivers to be updated.
-
I'm still wondering if anyone has printed with a v4 profile with success. I mean no gray borders on the print.
I can't speak directly to printing v4 targets, because I've held off on updating to 10.6 for the system I use to print until the dust settles. However, I'm on 10.6.3 on my laptop, and according to the test images on http://www.color.org/version4html.xalter (http://www.color.org/version4html.xalter), it still doesn't support v4 profiles. Maybe it does for printing but not for display, but that would surprise me.
-
I can't speak directly to printing v4 targets, because I've held off on updating to 10.6 for the system I use to print until the dust settles. However, I'm on 10.6.3 on my laptop, and according to the test images on http://www.color.org/version4html.xalter (http://www.color.org/version4html.xalter), it still doesn't support v4 profiles. Maybe it does for printing but not for display, but that would surprise me.
Downloaded and opened in Adobe Acrobat Pro, the test PDF file from the linked website does indicate (on my system) that both versions 2 and 4 icc profiles are supported by OSX 10.6.3.
The html file displayed on the website viewed in Safari does not seem to support version 4.
-
The html file displayed on the website viewed in Safari does not seem to support version 4.
So the html file doesn't support v4 or Safari?
-
Hi,
My "Safari" does show all colors correctly on the http://www.color.org/version4html.xalter (http://www.color.org/version4html.xalter) test.
I'm on 10.6.3, upgraded 2 days ago.
I believe that my display profile is V2 not V4.
I feel that color management is a complex issue, involving OS, software and printer drivers. It seems that version 2 work consistently so I use it for now, until some real expert tells me it's time to switch.
Best regards
Erik
Downloaded and opened in Adobe Acrobat Pro, the test PDF file from the linked website does indicate (on my system) that both versions 2 and 4 icc profiles are supported by OSX 10.6.3.
The html file displayed on the website viewed in Safari does not seem to support version 4.
-
I feel that color management is a complex issue, involving OS, software and printer drivers. It seems that version 2 work consistently so I use it for now, until some real expert tells me it's time to switch.
Its a good idea to stick with V2 profiles for awhile, keeping in mind there are differences between the use and capabilities of V4 display and output profiles (someone mentioned a V4 target, not sure what that is about). Some app’s have had difficulties with V4 display profiles. Some RIPs can’t deal with V4 output profiles. While Safari might be perfectly happy with V4 display profiles, other app’s may cause issues (LR was one such app).
-
Today I ran a more comprehensive series of tests on my Epson 9600 in order to establish which MacOSX versions work correctly with this printer.
The results can be seen here:
http://luminous-landscape.com/forum/index....showtopic=42745 (http://luminous-landscape.com/forum/index.php?showtopic=42745)
-
I didn't read the rest of your post in detail(will later), but just a thought ... 10.5 is where this problem began and we began having to work around the problem. So not sure going back to 10.5 to achieve a "baseline" will work.
From all the testing I have done and seen Ryan do, the best work around was printing from CS2 on 10.4. Other combinations worked, (I think CS3 worked OK on 10.5) but Ryan seemed to have the most success getting his baselines printing from a Windows system.
I didn't measure my targets, I would assume some variance. However, problematic targets were easily differentiated visually when compared ... it was quite obvious is some color patches.
My prints from CS4 to a 4880 and to a 2880 were fine under 10.5, so for me its an excellent baseline. The problems started when I loaded 10.6 and the printer drivers no longer worked. The point of my post was to show that for the 4880, if you have the latest Epson driver loaded correctly, you are back to the pre 10.6 conditions and to set up a test baseline for 10.6.3 after I loaded it.
http://luminous-landscape.com/forum/index....st&p=357306 (http://luminous-landscape.com/forum/index.php?s=&showtopic=41940&view=findpost&p=357306)
The results are good. A print, after loading 10.6.3, compared to the measurements in the above post for the 10.5 print (printed 5/23/09):
Patch ; L*,a*,b*- dE
1) 2.3
2) 1.0
13) 0.9
14) 2.8
15) 0.8
To describe these numbers in visual terms, none of these patch measurements were detectably different side by side in i1 Share, calibrated Sony Artisan.
Also, this repeatability over 11 months, different ink load and printer driver, damaging operating system changes, etc. is pretty amazing. There was no "work around" of any type in these prints or in the driver install.
Scott McRae
-
preliminary results on the 11880 are a mixed bag.
i1 match Target printed using 10.6.3/CS4 and Eric Chan work around match targets printed from 10.4.11/CS1.
Target printed directly from i1 match also were visually identical to both of those (good news, this was problematic in 10.6.2)
However, I cannot print any document with CS4 set to no color management ... either tagged or untagged. The computer sends the data to the printer, but nothing prints, paper moves through as though I printed an empty document or a document of 100% white.
The latest 11880 driver predates 10.5 so I'm not sure whether this is a problem related to my install or if it's a problem with the driver. I'll try this on the 11880 at the store tomorrow. Will be testing a 3800 this weekend.
-
However, I cannot print any document with CS4 set to no color management ... either tagged or untagged. The computer sends the data to the printer, but nothing prints, paper moves through as though I printed an empty document or a document of 100% white.
This morning I realised that I had neglected to investigate whether setting the 9600 to the default printer under System Settings/Print & Fax makes any difference to the print tests.
I will update my 9600 thread with my results shortly:
( http://luminous-landscape.com/forum/index....showtopic=42745 (http://luminous-landscape.com/forum/index.php?showtopic=42745) )
I have a few more tests to do but there is one thing in particular that you may like to know about.
If my 9600 is set as the default printer under MacOSX 10.6.3, then nothing happens whatsoever when I try to print an untagged test strip from CS4 with CM disabled in Photoshop and the print driver.
If I re-run this test after setting some other printer as the default then the 9600 will print the test strip but it is very slightly incorrect to my eye. I guess this would need to be measured in order to establish the delta difference from my benchmark test strips. Here are some other results for comparison:
Using MacOSX 10.5.8 and CS4, my 9600 produces an untagged test strip correctly *but only* if it is set as the default printer.
Using MacOSX 10.5.8 and CS1, my 9600 produces an untagged test strip correctly whether or not it is set as the default printer.
Using MacOSX 10.6.3 and CS4, my 7900 produces an untagged test strip correctly whether or not it is set as the default printer.
What happens if you print an untagged test chart on your 11880 with some other printer set as default?
In fixing Colour Management for the 7900/9900 maybe Apple have screwed up everything else?
Perhaps Epson need to update all of their Pro print drivers to work correctly with MacOSX 10.6.3?
As usual, it seems that the customer community is left to beta test MacOSX/print drivers and sort out the mess.
Perhaps Apple and Epson should set up QA departments?
-
Perhaps Epson need to update all of their Pro print drivers to work correctly with MacOSX 10.6.3?
It seems the US version of the 11880 driver may have some issues , and in fact may not be the correct driver. At my store today, I went to install the 11880 driver on my Mac, and got the notorious "A file named Preferences has the same name as a folder that needs to be installed error." In checking it seems this error should only be occuring if you install an older driver after you have installed one of the newer drivers ... for example the 9600 driver after installing the 7900 driver. But the 11880 driver shouldn't be causing this. This is info from the UK site (here if you are interested http://tinyurl.com/yb89twd (http://tinyurl.com/yb89twd) )
The US site driver version is 6.15 which caused this problem. The UK version is 6.55 .. I have no clue how the numbers are supposed to match up or even if they do, but I decided to install 6.55 on a different mac that was printing to the 11880, and did not get this error.
At that point I printed two targets (an i1 match target), 10.6.3 and CS4, one using Eric's work around and one using no color management with no problems. Visually identical. I also printed the same target from i1 match, and it was visually identical.
It appears the current 11880 driver on the USA site may be problematic. The preferences error should not be ocurring when installing the 11880 driver, since this error won't occur when installing a newer driver after installing an older one (such as the 9600). The fact the error occurred indicates the driver may not be current.
The 11880 seems to be fine printing targets as long as I have installed driver version 6.55 from the UK site. I'll confirm this on the 11880 at home over the weekend, but we now have both the 7900 and 11880 here at the store printing untagged and non color managed documents correctly.
I'm curious about your default printer thing, so I may try that on the 11880 at home before I delete the driver and install the UK version.
-
It seems the US version of the 11880 driver may have some issues , and in fact may not be the correct driver. At my store today, I went to install the 11880 driver on my Mac, and got the notorious "A file named Preferences has the same name as a folder that needs to be installed error." In checking it seems this error should only be occuring if you install an older driver after you have installed one of the newer drivers ... for example the 9600 driver after installing the 7900 driver. But the 11880 driver shouldn't be causing this. This is info from the UK site (here if you are interested http://tinyurl.com/yb89twd (http://tinyurl.com/yb89twd) )
That is an article I hadn't seen before so thanks for pointing it out.
I installed my Epson 9600 v3.09 driver after the Epson 7900 driver and yes I got the error.
I elected to overwrite the file.
At this point I ran my MacOSX 10.6.3 tests from my Intel Mac.
I now need to trash the whole of the Epson folder etc and reinstall the drivers from scratch starting with the Epson 9600.
Then I need to retest the 9600 from MacOSX 10.6.3.
Not sure if I will have time to do this for a few days bit I will pick up as soon as I can.
(BTW, it is nice to see Epson UK doing something useful for a change.)
-
6.55 should be the latest full release driver for the 11880, then there is a "common updater" to bring it up to Snow Leopard spec. This can be downloaded from:
http://tech.epson.com.au/downloads/Redirec...DownloadID=6324 (http://tech.epson.com.au/downloads/RedirectLink.asp?ProductID=styluspro11880&Email=&DownloadID=6324)
Which is via the Epson Australia website.
The common updater is also applicable to the 7900/9900. The 9600 doesn't have an update at the moment.
-
6.55 should be the latest full release driver for the 11880, then there is a "common updater" to bring it up to Snow Leopard spec. This can be downloaded from:
http://tech.epson.com.au/downloads/Redirec...DownloadID=6324 (http://tech.epson.com.au/downloads/RedirectLink.asp?ProductID=styluspro11880&Email=&DownloadID=6324)
Which is via the Epson Australia website.
The common updater is also applicable to the 7900/9900. The 9600 doesn't have an update at the moment.
Interesting. The info on Australia's site doesn't really jive with the US site.
On Epson USA's downloads the main installer is listed as 6.15 and is listed as compatible with Tiger, Leopard and Snow leopard. The common updater says it is for Leopard and "This updater corrects possible issues with image cut-offs and margin shift when printing landscape or borderless images."
Of course, wouldn't be the first time that things were clear, so I'll give it a shot tonight for fun. It seems the UK driver is the simplest fix.
-
Using OSX 10.6.3, CS4 and the latest UK driver for the Epson 3800. Printing targets and profile creation with the Eye One Pro seems to be working fine now.
-
When using the UK driver do you get any differences in the paper sizes? I see the 3800 US driver is different than the UK driver just mentioned in the last post. I'm hoping to install the Mac OS update later today and will print targets and see how it goes. It seems people are being able to do so without problems.
-
Finally I do not need a work around or to print from CS3 to print my targets. I am using a MacPro and MacBook Pro, 10.6.3 and CS4. I'm happy.
-
And now to test Snow Leopard 10.6.3v1.1 and PhotoShop CS5?
And every forthcoming release?
:-(
-
Has anyone beta tested CS5 with SL 10.6.3. If they have, please let us know the results. I'm only hoping all printing paths will remain the same.
-
And now to test Snow Leopard 10.6.3v1.1 and PhotoShop CS5?
And every forthcoming release?
Yes, specially if you are an early adopter.
Like it or not, that's the way it is.
-
Just adding to the data here...
OS X 10.6.3
Photoshop CS4
Canon IPF8300 Photoshop driver
Built a profile using Profile Maker Measure to scan and Eye One Match to generate the profile. Profile looks fine.
Same config but profiling an Epson 2200... that was a total disaster. The profile looks like some kind of Origami in ColorThink and the Granger Chart might actually pass as modern art.
Cheers, Joe
-
Same config but profiling an Epson 2200... that was a total disaster. The profile looks like some kind of Origami in ColorThink and the Granger Chart might actually pass as modern art.
Cheers, Joe
You will need to figure out what profile the driver is converting to when using Apple's new printing path and then assign that profile to anything going through going that driver. Do you print profile conversion first and then assign the profile that the driver is using.
Doyle
-
Wayne, your experience matches mine. I don't have an 11880 here, but I've worked with a few other photographers who've been troubleshooting printing targets to their 11880 with the USA version of the driver. They also ended up getting the driver from the Epson UK site and that worked for them.
-
Photoshop CS5 - 16 bit print output selected
Snow Leopard 10.6.3
Canon iPF5100
Canon Premium Bright Photo Satin Paper (260 GSM)
Canon Profile - Premium Bright Photo Satin (5100_PBPS260_S5_D50)
Converted to the printer profile and printed through Photoshop CS5's print dialog with 16bit output (Mac only), the print is identical in color and detail to the same image printed through Photoshop CS4 and Canon's 16 bit Photoshop Plug-in.
-
Photoshop CS5 - 16 bit print output selected
Snow Leopard 10.6.3
Canon iPF5100
Canon Premium Bright Photo Satin Paper (260 GSM)
Canon Profile - Premium Bright Photo Satin (5100_PBPS260_S5_D50)
Converted to the printer profile and printed through Photoshop CS5's print dialog with 16bit output (Mac only), the print is identical in color and detail to the same image printed through Photoshop CS4 and Canon's 16 bit Photoshop Plug-in.
Did you add Photoshop 12 or what ever the internal name is to the AppColorMatchingInfo.xml file. If not I have a hard time believing that you are getting "No color correction" in the driver. Tell me, is it defaulting to ColorSync in Color Matching?
Or are you letting the driver manage color?
Doyle
-
Did you add Photoshop 12 or what ever the internal name is to the AppColorMatchingInfo.xml file. If not I have a hard time believing that you are getting "No color correction" in the driver. Tell me, is it defaulting to ColorSync in Color Matching?
Or are you letting the driver manage color?
Doyle
It is defaulting to ColorSync and I set dialog to let Photoshop manage color as I converted the image to the paper profile. The Canon media setting was set in the Photoshop CS5 dialog. Color management is actually grayed out in the Canon printer interface.
-
It is defaulting to ColorSync and I set dialog to let Photoshop manage color as I converted the image to the paper profile. The Canon media setting was set in the Photoshop CS5 dialog. Color management is actually grayed out in the Canon printer interface.
Let me ask to a specific workflow.
If you choose PSCS5 manages color in the print dialog and choose the printer/paper profile, under Color Matching in the driver ColorSync is grayed our but selected as default? Now under Main/Color Mode: is No Color Correction selected and grayed out?
Doyle
-
Let me ask to a specific workflow.
If you choose PSCS5 manages color in the print dialog and choose the printer/paper profile, under Color Matching in the driver ColorSync is grayed our but selected as default? Now under Main/Color Mode: is No Color Correction selected and grayed out?
Doyle
See the uploaded images. Additionally if I click on the "set" button in the Main window under color management I get another screen that does indicate ColorSync under matching.
-
Do you print profile conversion first and then assign the profile that the driver is using.
Profile conversion? It's a target, there is no tagged color space or profile conversion. Driver is set to "none" for a profile. Are you talking about the work around? I'm aware of the work around but can't really be bothered by it. I have a Windows box I can use which works beautifully. I also have a Mac Pro still running 10.5.8 with Photoshop CS3 (and CS4) that works just fine as well, this was mostly an exercise in curiosity to see what would happen with an ANCIENT driver. I've been debating whether or not to upgrade the Mac Pro to Snow Leopard as I've been holding back due to the color management issues. Not really concerned about the Epson 2200 though. I don't really use it anymore, just wanted to give it a try to test the theory that the drivers are playing an integral part in whether or not you can print an untagged profile. I still have to give a test run on Snow Leopard with the IPF6100.
Cheers, Joe
-
See the uploaded images. Additionally if I click on the "set" button in the Main window under color management I get another screen that does indicate ColorSync under matching.
Because Canon drivers are special casing all application that print using Apple new printing path that is what I thought would happen. This manifests itself when application manages color is selected.
Until Photoshop 12 is listed in the AppColorMatchingInfo.xml file color management can not be turned off in the driver. Yes if your sending Canon's default profile that matches the media setting defaulted to that profile in the ColorSync Utility it will work because your double profiling with the same profile, but it will not work if are using custom profiles. This is the very same thing that happens with the LR3 Betas.
This is what will need to be added to the AppColorMatchingInfo.xml for PSCS5 to print correctly with custom profiles.
This is what is set for CS4 to print correctly.
<dict>
<key>CFBundleExecutable</key>
<string>Adobe Photoshop CS4</string>
<key>CFBundleVersion</key>
<string>11.0</string>
CS5 will need to be added into the AppColorMatchingInfo.xml file.
Doyle
-
You can set Photoshop CS5's print dialog box to printer manages color. Then you are able to select vendor matching and no color adjustment in the printer's dialog box.
I have not tried to print using this setting.
-
You can set Photoshop CS5's print dialog box to printer manages color. Then you are able to select vendor matching and no color adjustment in the printer's dialog box.
I have not tried to print using this setting.
Yes of course that is what you will get with printer manages color, but not CS5 managing color. CS5 needs to be listed (special cased) for it print correctly using custom profiles.
Check your PM.
Doyle
-
Until Photoshop 12 is listed in the AppColorMatchingInfo.xml file color management can not be turned off in the driver. Yes if your sending Canon's default profile that matches the media setting defaulted to that profile in the ColorSync Utility it will work because your double profiling with the same profile, but it will not work if are using custom profiles. This is the very same thing that happens with the LR3 Betas.
This is what will need to be added to the AppColorMatchingInfo.xml for PSCS5 to print correctly with custom profiles.
This is what is set for CS4 to print correctly.
<dict>
<key>CFBundleExecutable</key>
<string>Adobe Photoshop CS4</string>
<key>CFBundleVersion</key>
<string>11.0</string>
CS5 will need to be added into the AppColorMatchingInfo.xml file.
Doyle
Color me curious ... so where is this file? I can't find it on my system. Is it installed by canon driver software only?
-
Something interesting will be happening regarding printing targets with the launch of CS5. I've just confirmed that we're allowed to talk about it but I have to stress that there is no firm ETA.
CS5 removes the No Color Management option for printing. To cater for target printing, Adobe will release (via Adobe Labs) a free utility specifically for printing targets. The idea is to avoid the various issues we've all discussed here and just provide a solid tool for targets that does a proper NCM. There are no more details available at this stage.
-
Color me curious ... so where is this file? I can't find it on my system. Is it installed by canon driver software only?
Here is the path /Library/Printers/Canon/GARO/Frameworks/GARO_CUPS.framework/Versions/A/Resources/AppColorMatchingInfo.xml
Installed by Canon driver software but it can be edited to include new software. I have adding Lightroom 3 Beta 2 and it now prints correctly without double profiling. Photoshop CS5 should be easy to add by looking up the internal executable file name and version number.
Doyle
-
Something interesting will be happening regarding printing targets with the launch of CS5. I've just confirmed that we're allowed to talk about it but I have to stress that there is no firm ETA.
CS5 removes the No Color Management option for printing. To cater for target printing, Adobe will release (via Adobe Labs) a free utility specifically for printing targets. The idea is to avoid the various issues we've all discussed here and just provide a solid tool for targets that does a proper NCM. There are no more details available at this stage.
Is this a late April's Fool joke?
-
Is this a late April's Fool joke?
Nope...CS5 does NOT have a No Color Management option in the drop down menu...it was always a hack and with the most recent Mac print pipeline, essentially undoable.
So you can either do the Eric Chan work around (assign a profile then print to the driver with no color management) or use another app to print targets...hence the intention of doing a Labs.Adobe.Com free cross platform app for printing targets...
-
...hence the intention of doing a Labs.Adobe.Com free cross platform app for printing targets...
Can anyone advise a time-frame for the availability of this Adobe Labs print target app?
-
Can anyone advise a time-frame for the availability of this Adobe Labs print target app?
No, sorry. As I said, we've been advised that there is no ETA at this point which means no speculation. If that situation changes, I'll happily comment but my guess would be that Adobe will announce it anyway.
-
Correct, I posted a similar note to the ColorSync list moments ago. One of the advantages of putting it into a separate dedicated (much smaller) app is the ability to rev it as needed to deal with potential OS changes. Much less overhead than trying to do a full PS update.
-
Correct, I posted a similar note to the ColorSync list moments ago. One of the advantages of putting it into a separate dedicated (much smaller) app is the ability to rev it as needed to deal with potential OS changes. Much less overhead than trying to do a full PS update.
Eric-what do you mean by the Colorsync list......?
-
Eric-what do you mean by the Colorsync list......?
http://lists.apple.com/mailman/listinfo/colorsync-users (http://lists.apple.com/mailman/listinfo/colorsync-users)
-
v4 Profiles still have the gray bars on 10.6.3.
-
As I suspected PSCS5 will not print correctly without adding it to the special cases file. It needs to added so that "No color correction" is the default when choosing Photoshop Manages Color.
Here is the Fix for PSCS5.
http://www.dypinc.com/Canon/AppColorMatchingInfo.xml (http://www.dypinc.com/Canon/AppColorMatchingInfo.xml)
The file goes here.
/Library/Printers/Canon/GARO/Frameworks/GARO_CUPS.framework/Versions/Current/Resources/AppColorMatchingInfo.xml
Make sure you save the original in case you want to go back to it.
And printing gray in the none printing page area is still an issue, I suppose with Ver 4 profiles. Will test version 2 profiles next.
Doyle
-
Ok, so anyone know how I'd add Aperture to the AppColorMatchingInfo.xml file?
-
Ok, so anyone know how I'd add Aperture to the AppColorMatchingInfo.xml file?
Aperture is already in the AppColorMatchingInfo.xml. Version 2 & 3 of Aperture when choosing Aperture manages have the correct No color correction in the driver.
I do not print from Aperture, so what is not working correctly for you?
Doyle
-
Aperture is already in the AppColorMatchingInfo.xml. Version 2 & 3 of Aperture when choosing Aperture manages have the correct No color correction in the driver.
I do not print from Aperture, so what is not working correctly for you?
Doyle
Thanks, I was not sure about that as it is not directly listed as it use to be in Photoshop.
So I would have it under the Aperture Printing Dialogue Box the following. Rendering: Color Profile: Printer Managed.
Then hit print and then in the Printers dialogue box in the Main tab have Color Mode to No Color Correction.
I'm not sure if I was still running it through a profile this way though. I would have thought I could turn it off in Apertures print dialogue box instead of clicking Printer Managed.
-
As I suspected PSCS5 will not print correctly without adding it to the special cases file. It needs to added so that "No color correction" is the default when choosing Photoshop Manages Color.
Here is the Fix for PSCS5.
http://www.dypinc.com/Canon/AppColorMatchingInfo.xml (http://www.dypinc.com/Canon/AppColorMatchingInfo.xml)
The file goes here.
/Library/Printers/Canon/GARO/Frameworks/GARO_CUPS.framework/Versions/Current/Resources/AppColorMatchingInfo.xml
Make sure you save the original in case you want to go back to it.
And printing gray in the none printing page area is still an issue, I suppose with Ver 4 profiles. Will test version 2 profiles next.
Doyle
I have updated the AppColorMatchingInfo.xml file to include LR3.
Doyle