What icc profile are you using in Lightroom? If you are getting bad color, it usually means the color management chain is broken down somewhere. If you are using "managed by printer" and a complex printing chain with a generic postscript driver, this is not so strange. By default Lightroom sends prophotoRGB data to the driver if you select managed by printer. The fact that it works correct when you directly print indicates a color management chain problem in the other case. I have no experience with these but the symptoms sound like there is a color profile conversion somewhere in the postscript chain that should not happen.
Do you have good icc profiles for this machine? Can you force driver color management off in the print setup?
We are using the correct ICC profile in all scenarios, it is just that Lightroom seems to have hardcoded the cgpdftops filter when converting a file to PostScript. We have tried many variations of ICC profile combinations when creating output from Lightroom in our Mac environment using PS drivers, but the results are always "80's Color". We have also tried setting our RIP systems to input profile Pro Photo RGB w/o luck, but in theory LightRoom should be passing along the ICC Profile information in the PS file.
I highly doubt that Lightroom does anything to the file sent to your RIP
than give it a pdf. From my experience Lightroom absolutely puts the
correct color space info in the pdfs it sends to printer drivers. The
postscript driver is doing something weird to it. Could be some weird
communication mishap but hard to trouble shoot from here. What happens if
you set this up using a generic postscript printer driver and just select
the correct ppd for it?
On Fri, Aug 22, 2014 at 10:20 AM, Adam Orcutt <email@example.com>
I have already tried a PDF file, with the same color results Generic PS with the a multitude of PPD's don't seem to be the issue. Lightroom is doing something from within the application architecture, resulting in the the cgpdftops being applied while on Mac OS environment. I am reaching out directly to Adobe on this for their solution.