There are some interesting things being discussed here, and several of them apply to my situation. I apologize for hijacking the thread, but it looks to be dead anyway, and at least this will force it back to the top of the list.
So I had firsthand experience with the "photoshop prints nothing" problem last week while trying to print untagged and unmanaged RBG files for profiling. I read several of the work arounds for that problem, but just wasn't convinced that some type of CM wasn't being applied and therefore defeating the purpose of the targets. In the end, I was able to use someone's laptop with CS3 to print the targets, everything went well, profiles created, problem solved! Or so I thought... Now that I have the profiles created and am trying to print some 16-bit images, we have a big problem- they look terrible! The color is over-saturated, and the prints are way too dark. Take the exact same file(s), don't check the 16-bit box and they look great. I have made sure to enable 16-bit in the photoshop print module as well as the epson driver, I've also tried it enabled in one and not the other. It feels like I have tried every combination of available options, but I really hope I'm missing something... I'm on a MacPro running 10.5.7 and CS4, I've tried both ProPhoto images as well as Adobe1998. I have the Leopard print driver, and to the best of my knowledge everything else is up to date.
However, there is currently a glitch with the result that once you print the image from CS4, Leopard will convert the image data to Generic Gray or Generic RGB (if you're in Grayscale or RGB mode, respectively) before handing it off to the driver. This conversion messes things up because it happens __after__ the conversion using your B&W profile of choice (i.e., what you select from PS's Printer Profile popup menu in the Print box).
Ah, so that's what's happening...
Good to know.
Having the same issue (Dual G5, OSX 10.4.11, PSCS4, Epson R2880, latest driver for 10.4 downloaded from the site, printer is the default printer).
Saw that the print preview (when saved as pdf) was Generic RGB instead of AdobeRGB (which is embedded when printing from PSCS2). Suspected that somehow the data sent to the printer got converted (since the pdf wasn't garish in color like the PSCS2 output), but couldn't imagine why...
Any new info on whether this'll get resolved?
Back to using PSCS2 for printing I guess, or using this as a workaround.
Did a tests, and there appears to be a huge drawback to this workaround: It prevents you from printing anything that's outside GenericRGB gamut. (Even worse actually, since the "convert to profile > Assign GenericRGB" step oversaturates colors, so even more clipping occurs as in a straight "working space > GenericRGB" conversion)
Posted some examples on my blog here: http://www.getcolormanaged.com/color-management/part2/
I'd love to be wrong here, but I don't think I am...
So, back to PSCS2 for color managed printing. Bummer...
Yes, we're still working with Apple and the printer manufacturers to try and resolve the color workflow problems.
The printer driver returns information about what it can and can't do to the OS, then the OS feeds that information to the application, and the application has to disable functions that are not available for that driver. If the driver or OS get confused, the application has no idea and just has to do what the OS said was allowable.
Europe, Middle East and Africa