It seems that trying to print a photo with Description and Labels being checked in the Output section will not happen.
Any thoughts on why this function will not work in my recent upgrade to CS5 (version 12.0 x64)?
Thanks
Am running OS X 10.5.8.
The printer is a HP LazerJet 9050 that the whole office uses.
I can get the image description to print on my other computers here in the office that are still running CS4 and CS3.... but it won't work with the new CS5.
Only when I go into the Print menu, and then to Print Settings and click "preview" is when I can get the labels and description to print with the image. And then it will cut off the caption, so I must reduce the print size for the whole caption to fit on the letter-sized paper. AND the font is horrible! It looks like a screen shot with super-low resolution.
Hmm. That's a PostScript printer, and I'm seeing labels and description working on those, too, but I only have 10.6 here to test from. It's possible there's a bug there. I'll see if I can get someone with a 10.5 machine to look at that.
When you click "Preview" it ends up going through the non-PostScript printing path, and the font gets rasterized to the same resolution as the image (the entire thing gets sent to the printer as a bitmap), so that's why the font doesn't look as good in that case.
We are having issues on numerous Macs running 10.6 with printing labels in PS CS5 also. They are not isolated to one type of printer. The errors are reproducible to different makes and models of printers. Some machines print the label as what looks like a bunch of dots,something like braille type. Other machines will print out only the color space, i.e. "RGB".
Having this problem on three different Macs, two at work, one at home, all running OS X 10.6.5, Photoshop CS5, and several different printers. The work computers are brand new 27-inch IMacs, and the home machine is a 24-inch IMac, about 4 years old. Very frustrating, as we have a need to do this every day and can't come up with a good workaround. Would appreciate any help!
Jim
We are having the exact same problem. We have multiple printers and all of them are having issues when labels are turned on in the Photoshop CS5 12.0.2 print dialog box on Mac OS 10.6.5 machines. One of our printers gives a Postscript error "Offending Command: limitcheck: yyyyyyyyyyyyyyyyyy" and stops the print. Another printer seems to ignore the Postscript error and print the image but with no labels. If we turn off the labels option, everything prints fine out of Photoshop CS5.
Interestingly, if in the Page Setup dialog box in the Print window of Photoshop CS5 I select to save as a PDF and open that PDF in Illustrator CS5, the labels shows up, but it doesn't seem to be text. It looks like an image.
Adobe Tech Support is being very unhelpful. After speaking to my 4th "Senior Level" tech they will not even test the problem on their end. Apparently no one at Adobe Tech Support has a Mac with Photoshop CS5 on it to try printing from.
Sorry, there's a bug in printing labels to PostScript printers.
If you print to PDF, that uses a different printing path, and avoids the bug. The labels are printed as images in that case.
The problem is with the width of the label, so if you shorten the name of your file to less than about a dozen characters, that will work, but that may not be practical.
Shutting off labels is the sure workaround.
Apparently a Mac os 10.6.5 printing issue with landscape mode and postscript printers...
There's a fix, but you have to be adventuresome and willing to make some system administrative changes to your mac via terminal.
Remember to always make a backup of your computer before changing anything!
hope this helps...
http://discussions.apple.com/thread.jspa?threadID=2644180&start=15&tst art=15
Seriously Adobe, can it be that hard to hire a programmer to fix this? This does have an impact on workflow in larger (and smaller) graphic design workflows. PLEASE, throw a couple dollars toward this problem. We spend hundreds of dollars towards your products and this type of problem shouldn't have gone on this long. Sorry for being so blunt.
I'm a Mac technician at a string of newspapers and we're converting our daily to CS 5.5. One of our photographers piped up with this issue on Friday when he was trying to print his proofs and get them to his editors.
I originally thought the problem was with the old HP LaserJet 5000 printer he was using. However, three test printers later — Ricoh Aficio AP610N, HP LaserJet 4240n, Konica Minolta Bizhub 222 — I go searching and find this post.
I have confirmed this issue in both OS X 10.5.8 and in OS X 10.6.8, booting in both 32-bit and 64-bit.
Our photographers will probably have to remain in CS4 until this is resolved.
Is there anything new on this issue? As the previous poster mentions — in May of this year — we paid serious cash for this product. An answer would be *greatly* appreciated.
For more of a complete answer, I believe it is some ridiculous number like 12 (TWELVE) characters MAX for the filename. I don't know many graphics deptartments that can really operate on such short filenaming conventions.
It has been over a year since this post was started and still no real response or fix from Adobe. Adobe has been really out of touch with it's customers the last few years. They remind me of how arrogant and aloof Quark was with it's customer in the 90's before Adobe started selling InDesign.
A year, come on guys, put a programmer on it for a week and have him fix it. It's items like this that bring things to a head and end in a Class Action Suit from all your previously loyal customer base. Adobe, what ever you do, don't post another indifferent response to this post. Not posting a response would be better than some "We'll get around to it" response, it's already been a year.
While this is good news it is not really a solution. We do not have CS6 beta and do not plan on getting it or updating to full CS6 when released (at least not very soon after release.) This is more of a "we'll make our customers throw money at the situation" kind of fix instead of addressing the issue in the current release version.
North America
Europe, Middle East and Africa
Asia Pacific