Serious bug in Lightroom printing

I was wanting to spread a panorama print over two pages, and because the printer does a larger margin on the bottom of the page, I needed to flip the image to have its join (halfway) on the top of each printed page (bear with me!). So, to do this, I flipped the image along vertical and horizontal axis, and dragged it so that on one printed page it would print the left side of the image, and on the other printed page, it would print the right side of the image. The "left" side is the flipped image. I have the "zoom to fill" option selected (as I want it to fill the available vertical height), "rotate to fit" off, as I don't want it rotated or fitted.
So, in the Print view, I have a resulting display that is showing me a flipped version of my panorama, with just a half of it visible, and a non-flipped version (the original) with its half displaying in the area LR defines as the printable crop on each page. I've repositioned the photo so that I see which parts I need to print on each page.
When you go to print the flipped image, despite it showing correctly on the screen, it doesn't print what I see on the screen, but rather it prints the other end of the image that is cropped off the display'd print area!
I tried making a "real" (not virtual) copy, same problem.
I tried printing to a PDF and also having LR directly print to a JPEG, and had the same result.
I ended up having to take the image into photoshop and save a copy of the pano, crop it to the half of the image I wanted to print, and bring that back into LR and print it - I had still flipped it in LR to print it, but as I'm printing "the whole image" now, it printed fine.
So, there is something really broken in the LR printing, I don't know if it is the display crop of LR that is not being applied when you print in ANY situation, or if the display crop of the printed area is not being applied properly only when an image is flipped horizontally.
Thanks
William
ps: I can' provide screen shots if the description is too convoluted!

Because you appear to have an urgency with your problem the best course of action I can recommend is to file a TAR with support with your test case and ask for a fix to your problem.
Thanks -- Jeff

Similar Messages

Lightroom - Printing 13x19

I have a problem getting Lightroom to accept the 13x19 sheet size -- don't have this problem with smaller size sheets. When I hit ok the right margin resets to 4.57". Am I missing something or is this a bug? Here's the steps I take (in order):
Set 13x19 sheet size in: Page Setup & Print setup & Properties & Page Layout. (This is when the margin resets)
In Page Layout -- Check Reduce/enlarge document to 100% & set size as 13x19.
In Layout -- set the cell size to 13x19
In Impage Setting -- check zoom to fit
Thanks for the help.

Claude,
A couple of points:
1. "Adobe" tends not to post to the forums about issues that may well be related to third party products. Instead, they leave it to users and forum hosts (i.e. it's User-to-User forum NOT an Adobe Support forum).
2. During the period that you guys established that a workaround was possible I was in the US on a photo shoot (Grand Teton and Yellowstone NP's). The other hosts may well have been looking into the forum, but they are not all Lightroom savvy, so probably did not realise the significance of your findings. In my case, access to the internet wasn't exactly easy and to be frank I had better things to do than to log on to the U-to-U forums. Likewise, on my return I had much more important matters to deal with than scan the hundreds of dated posts on this and 5 other Adobe forums.
However, I'm now home and have managed to clear most of the work that built up during my absence. So, having read your post and eventually tracked down what it was that you're writing about I have updated my Lightroom Printing tutorial and will post an FAQ linking to it sometime tomorrow. In the meantime, the tutorial can be found at http://www.computer-darkroom.com/lr_13_print/lightroom_print.htm#23%20February%202008

URGENT: Serious Bug in 2.0.2.9

We have uncovered a serious bug with the getElementsByTagName() method that could cause incorrect or inconsistent results.
Looking at the bytecode via a debugger, we traced it to the checkNamespace method of the XMLElement class. In this class, an explicit object comparison between two strings is performed (s == name). The correct code should be s.equals(name). While a common coding mistake, this creates randomly inconsistent results depending on how the compiler chooses to manage strings with identical values.
Any suggestions?
- Rick Bullotta
VP/CTO
Lighthammer Software Development
(www.lighthammer.com)
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by atorres ():
fjkf jkfl kj
It would be a solution IF the print method works... but it doesn't work 100% with DTDs. Take a look at my message posted at July 25, 2000 11:22 AM. Be carefull if you have standalone docs...
Good Luck for you (and for me too, I'm gonna need)<HR></BLOCKQUOTE>
null

Is there a serious flaw in LRs Print Module?

I have been having no end of difficulty getting a decent print from LR. The more I search for answers the more I find that others have the same issue. It seems to be related mostly to Canon and HP printers. Most Epson users indicate they are getting great prints.
Multiple combinations of settings have been suggested (all from very helpful folks, thks!) but all attempts have not produced anything remotely close to whats on the screen. PSE3 prints perfectly for me, and other comments indicate that CS2&3 and PSE4&5 also deliver superior results to LR.
It seems that there a serious problem with LRs Print Module whereby it cannot interpret and convert profiles properly? Has this been officially addressed by Adobe? If so, please direct to where I can find that information, please.
Dont misunderstand me, LR is a fantastic program and a very powerful RAW workflow tool. Even the Print Module has some really cool stuff, but not so cool when the colours dont come out close to the original.
Where does one go from here to find a solution to this problem?

Hi Dave
I posted this earlier in this thread about CS3 printing problems that Adobe has addressed and I just reviewed it again and noticed some common problems under the "Issues Fixed in this Release" as follows:
"Color matching is now correct on BPE printers (notably the Epson 3800) when Photoshop is set to handle color management."
"BPE Printers expect a Profile to be passed when Photoshop manages color. Photoshop now passes the Profile."
"Epson 2400 driver no longer does double color profiling when PS is handling the color management and we explicitly turn off Epson color management in the Print dialog."
"Color management will now produce identical results on Intel and PowerPC-based Macs."
"Correct Page Setup now comes up in the Print dialog when you change printers to print different documents."
"Page Setup would sometimes show the preferences for a previously selected printer."
"RGB to CMYK conversion with a specific ICC profile and Adobe(ACE) engine is fixed."
"Specific types of ICC profiles were being incorrectly converted. Converted images would appear close to black, if not entirely black."
These appear to be the same issues that are happening in LR that require a similar fix that CS3 required.
Here's the link again:
http://www.adobe.com/support/photoshop/ts/documents/kb402846/PhotoshopPrintingNotes.pdf

Hi, I developed a web application using HTML5-Offline Application Cache mechanism. Inspite of deleting the cache as mentioned in the above steps, Firefox still maintains a copy of the page in it's cache. Also, a serious bug is, even though we delete all

== Issue
==
I have a problem with my bookmarks, cookies, history or settings
== Description
==
Hi,
I developed a web application using HTML5-Offline Application Cache mechanism. Inspite of deleting the cache as mentioned in the above steps, Firefox still maintains a copy of the page in it's cache. Also, a serious bug is, even though we delete all temp files used by Firefox, and open the previously cached page, it displays it correctly, but upon refreshing/reloading it again shows the previous version of the page maintained in the cache.
== Troubleshooting information
==
HTML5: Application Caching
.style1 {
font-family: Consolas;
font-size: small;
text-align: left;
margin-left: 80px;
function onCacheChecking(e)
printOutput("CHECKINGContents of the manifest are being checked.", 0);
function onCacheCached(e) {
printOutput("CACHEDAll the resources mentioned in the manifest have been downloaded", 0);
function onCacheNoUpdate(e)
printOutput("NOUPDATEManifest file has not been changed. No updates took place.", 0);
function onCacheUpdateReady(e)
printOutput("UPDATEREADYChanges have been made to manifest file, and were downloaded.", 0);
function onCacheError(e) {
printOutput("ERRORAn error occured while trying to process manifest file.", 0);
function onCacheObselete(e)
printOutput("OBSOLETEEither the manifest file has been deleted or renamed at the source", 0);
function onCacheDownloading(e) {
printOutput("DOWNLOADINGDownloading resources into local cache.", 0);
function onCacheProgress(e) {
printOutput("PROGRESSDownload in process.", 0);
function printOutput(statusMessages, howToTell)
* Outputs information about an event with its description
* @param statusMessages The message string to be displayed that describes the event
* @param howToTell Specifies if the output is to be written onto document(0) or alert(1) or both(2)
try {
if (howToTell == 2) {
document.getElementById("stat").innerHTML += statusMessages;
window.alert(statusMessages);
else if (howToTell == 0) {
document.getElementById("stat").innerHTML += statusMessages;
else if (howToTell == 1) {
window.alert(statusMessages);
catch (IOExceptionOutput) {
window.alert(IOExceptionOutput);
function initiateCaching()
var ONLY_DOC = 0;
var ONLY_ALERT = 1;
var BOTH_DOC_ALERT = 2;
try
if (window.applicationCache)
var appcache = window.applicationCache;
printOutput("BROWSER COMPATIBILITYSUCCESS!! AppCache works on this browser.", 0);
appcache.addEventListener('checking', onCacheChecking, false);
appcache.addEventListener('cached', onCacheCached, false);
appcache.addEventListener('noupdate', onCacheNoUpdate, false);
appcache.addEventListener('downloading', onCacheDownloading, false);
appcache.addEventListener('progress', onCacheProgress, false);
appcache.addEventListener('updateready', onCacheUpdateReady, false);
appcache.addEventListener('error', onCacheError, false);
appcache.addEventListener('obsolete', onCacheObselete, false);
else
document.getElementById("stat").innerHTML = "Failure! I cant work.";
catch (UnknownError)
window.alert('Internet Explorer does not support Application Caching yet.\nPlease run me on Safari or Firefox browsers\n\n');
stat.innerHTML = "Failure! I cant work.";
== Firefox version
==
3.6.3
== Operating system
==
Windows XP
== User Agent
==
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729; .NET4.0E)
== Plugins installed
==
*-Shockwave Flash 10.0 r45
*Default Plug-in
*Adobe PDF Plug-In For Firefox and Netscape "9.3.2"
*NPRuntime Script Plug-in Library for Java(TM) Deploy
*The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
*Google Update
*4.0.50524.0
*Office Live Update v1.4
*NPWLPG
*Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
*Next Generation Java Plug-in 1.6.0_20 for Mozilla browsers
*Npdsplay dll
*DRM Store Netscape Plugin
*DRM Netscape Network Object
Thanks & Regards,
Kandarpa Chandrasekhar Omkar
Software Engineer
Wipro Technologies
Bangalore.
[email protected]
[email protected]

We have had this issue many, many times before including on the latest 3.6 rev. It appears that when the applicationCache has an update triggered by a new manifest file, the browser may still use only its local network cache to check for updates to the files in the manifest, instead of forcing an HTTP request and revalidating both the browser cache and the applicationCache versions of the cached file (seems there is more than one). I have to assume this is a browser bug, as one should not have to frig with server Cache-Control headers and such to get this to work as expected (and even then it still doesn't sometimes).
The only thing that seems to fix the problem is setting network.http.use-cache to false (default is true) in about:config . This helps my case because we only ever run offline (applicationCache driven) apps in the affected browser (our managed mobile apps platform), but it will otherwise slow down your browser experience considerably.

I just bought an Epson Stylus Pro 3880 and the printed images look yellow. I calibrate my MacBook Pro monitor with a ColorMunki Display. I want to make sure my Lightroom print settings are correct.

I just bought an Epson Stylus Pro 3880 and the printed images look yellow. I calibrate my MacBook Pro monitor with a ColorMunki Display. I want to make sure my Lightroom print settings are correct.

This what I have been trying...... Maybe my eyes are screwed up or don't understand the process....
What I have been trying to do is squint and make the apple disappear by moving the sliders around in each step. Is that correct?

WARNING: Serious bug in Netscape 6.01 browser

All--
I've just been bitten by a serious bug in the Netscape 6.01 browser, and
want to let you know about it before it bites you too. Full bug details can
be found at http://bugzilla.mozilla.org/show_bug.cgi?id=55055
A short summary is that the back & forward buttons incorrectly resubmit form
fields. For example, say I have this page flow:
Page A -> Page B - (submit form) -> Page A -> Page C
Use Back button to go from C back to A
On backing up from C to A, Netscape tells me that there are posted form
elements and asks if I want to resubmit them or cancel the back action.
Because I'm backing up to A, it tries to resubmit the form fields from page
B in order to show page A!
What does this mean? It means that the Web application gets another hit to
page B, as if the user had pushed a button on it again--even if this isn't
allowed by the application. In other words, the back button becomes a
serious threat to an application's consistency. Neither IE nor Opera do
this, nor did any other version of Netscape.
Please keep this behavior in mind if you are designing an application that
could be used with Netscape 6. For those transactions that you need to
ensure aren't executed more than once, you may want to set a hidden field on
the page (page B) or otherwise keep track of a value that indicates whether
the transaction has been executed or not. Another option might be to set an
HTTP header indicating that the problematic page (page A) can't be cached by
the browser (this differs from what one might do in the "normal" situation
of telling the browser not to cache page B, so that backing up from page A
to B wouldn't be possible).
Todd

Double tap with THREE fingers. Then go into Settings>General>Accessibility and turn zoom off.

Bug in Lightroom 3 - Folder Browsing Selecting Incorrect Text Case

I seem to have stumbled upon a bug in Lightroom 3. I was at first wondering why, when I had Auto Import enabled, no images were appearing in the Lightroom Catalog, even though they were being copied to the _Inbox folder which I created on my QNAP NAS to contain them. However, after the import had finished, I would Sync the folder and there they were.
This was very confusing until today, when I noticed a seemingly identical folder in the Folder dialog shown in the first image. This one *was* receiving the Auto-Imported files as well, except that this one was updating the Lightroom catalog correctly.
What is the difference between them? The second (working) Auto Import folder has the folder 'files' in lower case. This causes Lightroom to see them as different. Presumably this is for Unix support. This is logical. The QNAP NAS device is Linux based after all.
However, when I tried to correct the folder path entry in the auto-import dialog, it displays the 'files' folder in the wrong case (lower) even though both the QNAP folder browser and Windows Explorer display it with initcaps as 'Files'. See other images below demonstrating this.
So I'm stuck. As the Lightroom Auto-Import folder browser displays the folder in the wrong case, Lightroom will always see this folder as two different folders, even though they're the same. I can't rename the folder in lower case, or I risk losing all the Lightroom edits I've carried out against thousands of images in the folder named as 'Files'. Anyway, I *WANT* it named in upper case - this is an Adobe bug, not a QNAP or Windows bug.
See that Windows sees the folder name with initial capital:
See that the QNAP file browser sees the folder name with an initial capital:
See that the QNAP share manager sees the shared folder in upper case:
See that the Adobe Browser sees it in lower case for some inexplicable reason:

Thanks for your post and sorry you're also experience this two-folders-in-LR but only-one-at-the-Finder-level problem.
It looks like I've finally solved this problem, but I suspect I did so the hard way ... if I even understand where in the process things were fixed. As previously posted, when I tried to "move" one folder in LR into the other, LR got confused and deleted the entire contents of one of them! This was the existing one I had been using. Thousands of photos gone! I searched the hard drive and even used disk recovery software but, no, they had vanished. I luckily retrieved these photos from a backup drive, so that's good, but it makes one nervous to fiddle around with this particular problem.
Anyway, BEFORE I imported the new photos from the back-up drive, I first deleted LR prefs and in the process stumbled upon old LR prefs from LR2 and LR3 Beta. Cleaned them all out -- including LR prefs -- and wondered if that had anything to do with the problem. Then rather than Import>Copy the photos, I worked at the Finder level and copied them into position in the <2010> folder, retaining the month and date folder structure. This is at the Finder level. Then in LR, I used Import>Add and the photos properly were added to the existing <2010> folder (the newer of the two that was still there after the disaster ... the new one that LR is intent on importing into). It all works now.
Hope I've written that so you can follow along. Don't know if that will help you in your situation. If you have questions, please let me know.
Good luck, but don't work without a backup, OK?
Best,
Bradley

Serious bugs in the SR400 gated photon counter LabVIEW drivers

Hi
I am developing an application with SR400 and came
across what I think is a bug in the LabVIEW driver. Essentially, none
of the VI's allow you to set the preset counters. For instance, if you
call Read VI and choose mode A, B for preset T, there is no way to
specify preset T, which means that the count period defaults to some
factory default, not a situation you want. This might also explain some
of the timeouts some people are getting to SRQs that come later.
Further,
if you look at the block diagram of Read VI, the line selector string
is set to "CM 0" for two distinct choices of the count mode. This is a
serious bug. I do not know who wrote this driver, but it does seem, at
least to me, that they did a rather shoddy job of it. How this driver even got certification to be posted at IDN is something I cannot explain.
Comments welcome from those that use LabVIEW with SR400 and have used this driver.

Hi. Dwell time of 2ms is good for me. It would be great if you can send me this file to circumvent the 2000points/measurement. Also, If i understand it right, if I set the Gate to CW, then my gate should always be open for the count period, they why do I have to set the gate parameters at all. I want to change the integration time, but for some reason I am not able to change it in your setup 2.VI at all. I made some changes in setup 2.vi. I removed the setting for channel B as I am not going to use it and I integrated the readchannel.vi into this file. I am not sure if I made a mistake in doing this. Now, I am able to write some data to a file, but I not as I want. If it helps, I am uploading my modified VI file and an example data file (Gate A width is 0.992s, Gate A delay and delay step are 0, Gate A mode is CW, Dwell time is 0.002s).
Attachments:
SR400-V.vi.vi ‏125 KB

Rather significant BUG in Lightroom 3.0-3.2

Ok, I have found a really annoying bug in Lightroom. It was not there in 2.0, but is in 3.0 and 3.2. (I use the MAC version)
When in the library module, if you select a number of images and switch to the survey view. You cannot mark individual images as rejected. I have tried the following.
1. Highlight an image and hit X and ALL images are marked rejected.
2. Zoom in on an image and use arrow keys to switch between images and mark X, ALL images are rejected.
3. Actually click on an individual rejected flag under a single image, and again. All images in the survey view are marked as rejected.
Other instances of this bug:
-You can click on a rating on any individual image and it works fine, however if you hit the number of the rating, (4 for instance), then ALL images are ranked as four stars.
-If you either click on the color rating or hit 6-0, then ALL images are flagged with a color.
This bug effectively ruins survey mode. In previous versions survey mode was a great way to pull up images that are similar and to go through them, if you wanted to reject one, you would hit X and only that image was rejected... Now, there is no good way to rank and flag images in survey mode... The ONLY way it works is to click on an individual dot under an image to rate, but don't hit the number, or it will apply to all selected.
I can see it doing this if you are in the normal Grid or Loupe view, then it should apply to all selected, but survey mode should not behave this way. Please go back to the way it was in previous versions.
Thanks

In previous versions activating Auto Sync required the use of a modifier key and even then was only available in Develop module. However, following representations it was added to the Library module. A switch was added to the Synchronize button and an enabling command added to the Metadata menu. These so called improvements were intended to make the feature more discoverable and flexible. Unfortunately, they also make it more easier to screw up multiple images whilst leaving the wondering what they did wrong.

Fixed 11.0 BUG, but had another more serious BUG in 11.1

But no one found this BUG, \u200b\u200bI have a question, and also did not care for me, from time to time lay off 750 people this time, the 11.0 developer to cut, resulting in 11.1 H.264 encoding so bad. And 11.0 full immeasurably.
https://bugbase.adobe.com/index.cfm?event=bug&id=3005174 I guess because the fix this BUG, \u200b\u200bcaused. In fact, not good, if not repaired
https://bugbase.adobe.com/index.cfm?event=bug&id=3047043 11.1 New BUG, \u200b\u200bbut did not care for me, this is a very serious BUG, \u200b\u200bif not found, then it will put an end to 11 series, but 11.0 is excellent, and I hope can be restored to 11.0 in 11.2 look like.

But no one found this BUG, \u200b\u200bI have a question, and also did not care for me, from time to time lay off 750 people this time, the 11.0 developer to cut, resulting in 11.1 H.264 encoding so bad. And 11.0 full immeasurably.
https://bugbase.adobe.com/index.cfm?event=bug&id=3005174 I guess because the fix this BUG, \u200b\u200bcaused. In fact, not good, if not repaired
https://bugbase.adobe.com/index.cfm?event=bug&id=3047043 11.1 New BUG, \u200b\u200bbut did not care for me, this is a very serious BUG, \u200b\u200bif not found, then it will put an end to 11 series, but 11.0 is excellent, and I hope can be restored to 11.0 in 11.2 look like.

Serious Bug Powerbuilder 12.5.2 build 5609 with Inheritance

Hi ,
I'm using Powerbuilder 12.5.2. build 5609. I think it is the latest release. I have three windows in my app.
The Grandfather , the father and the child. Child window (w_child) is inherited from the father (w_father) which inherits from the grandfather (w_grandfather).
I have some events in my windows , clicked events with code etc.
I made a change in the grandfather , regenerated the father and the child and my code in the child window was messed up!. And when I say messed up I mean that the code in my clicked event was disappeared or moved in other cases to other events.
With Full build and incremental build didn't fix the bug.
Using export and import FIXED the issue.
BUT.....
Why is this happening ? Of course this is a Powerbuilder BUG but do I need to export and import my objects when I make a change to ancestors objects ?
FYI using the edit source option I can see the code that it's there.
Will this issue been fixed because this is a very serious BUG. Every time I want to make a change to ancestors should I need to export all objects and import them again ???
thank you
zkar

Hi Andreas ,
I don't know.
But I tried the below scenario and found a different bug.
Same hierarchy. Grandfather, Father and Child.
Steps to reproduce.
1. Go to Fathers screen and Add a button. Leave the name as it is. cb_1
2. Go to Grandfather and add a button(didn't have any buttons yet). The name will be cb_1.
If you try to open the Father's screen you will be prompted from Powebuilder with a messagebox which suggest to make the changes for you because there was a name conflict. OK fair enough.
But.
If you press OK and let powerbuilder handles this then this doesn't work.
Anyway. This is a completely different thing from the original post . But I have just founded out trying to reproduce it to a new application.
FYI. The application was at first in Powerbuilder 10 but we have Migrated succesfully to powerbuilder 12.5 and It was working fine until we ;ve changed the intermediate level of inheritance.
The solution to my problem is export and import the intermediate level so don't search anymore. You will loose time trying to reproduce it.
thank you

Serious bug for 8.1.7 solaris Sparc download file

I have downloaded the 8.1.7 solaris.cpio.gz file from the OTN page. I found a serious bug from the OUI program,that is when
I run the "runInstaller" command ,It apperrs that ./runInstaller : syntax error in line 1 unexpected "(".
Did anyone find this ? This is a seious problem for this install program , hope OTN to explain this situation. Thanks a lot!!

If you go to http://metalink.oracle.com, patches & updates is one of the options in the navigation bar.
Justin

Serious Bugs

Hi Tim/Klaus.
I'm posting this here in the hopes that it will get a bit more attention than is being paid in Metalink. I've run into several serious bugs that need addressing:
1) If there are xml-special characters in the data coming from the database (e.g. an '&') then, according to the people at Metalink, I'm supposed to escape them. That's an unacceptable answer. I expect the parser to do that for me. That's why I bought it.
2) When using CVS as an output type, if a null value comes back from the database nothing is emitted into the output stream. For example, if I have 3 columns A, B, and C, if column B is null the jar's emit:
A,C
instead of
A,,C
which means I have to wrap every column in nvl(...) calls.
3) In the documentation it specifically states that you can dynamically append a WHERE clause to a query using PL/SQL functions (BI Users Guide, Part# B40017-01, page 4-32). I cannot get it to work and so I submitted a report to Metalink. They're answer was "we don't think that this can be done". The WHY is it in the User Guide???
4) CSV output sends out files with an extension of .txt which means you have to take extra steps to get the data into Excel (ok, so that one isn't too serious :)
5) When I configure the SSO server to use WNA (which I have gotten to work) when I try to launch the Word plugin and login, the server throws a 500 misconfigured error. It works if I don't use the SSO server.
6) The $CURRENT_SERVER_URL problem
These are causing us real headaches. Can anyone answer some of these questions?
Dave

Dave please seperate your questions into different threads because they are unreleated issues. Also, be sure to search the forum for solutions vs posting. It will save everyone sometime.
Thanks,
Ike
1) Special characters should be removed, however, I don't know what your doing. By the way a parser doesn't remove anything, it parses.
3) Lexical paramters in where clauses in bi publisher enterprise 5.6.2 work like you would expect them to (like reports 6i), however bi publisher in the e-business suite they do not work as expected and lexicals are not treated by value. It's completly backwards since you would expect the functionality to work in 11i. With that being said, I don't know what your doing in your report. The functionality works.

Photoshop CS3 and Lightroom print discrepancies

Hello,
I am having an issue with printing from Lightroom. I have a profile for my printer/driver/inkset that I have used successfully with Photoshop. When I print an image in Lightroom with the "profile manages" using this profile with the same driver, the image is dark. the exact same image exported from Lightroom to Photoshop prints beautifully with the same driver/paper/inkset.
I have double and triple-checked my driver and lightroom print settings but cannot find anything that appears out of whack. I use a saved pre-set to ensure that my printer driver settings are identical each time.
Does anyone have any ideas?
thank you,
George Pappas

Thanks for the additional information, Andre. Your symptions seem to point to the same underlying cause of the problem that I have experienced even though your particulars are different.
I have been quiet on this issue becuase I have been involved in a "deep dive" through the problem with Adobe Technical support and by trying to make sense of the other causes/effects/workarounds found by members of the Lightroom and other forums. For now, I do not have a solution yet, but hope to have more tangible information and a solution to post within a couple of weeks.
I have been through four tech support interactions with Adobe and one from Canon. Unfortunately, these calls were less than satisfactory. While the people on the phone were nice, there very unhelpful and primarily engaged in "pass the buck" behavior by claiming the problem was somewhere else. The last support call with Adobe lasted 40 minutes with a very nice fellow who gave me USELESS feedback and directed me to a knowledgebase article that had nothing to do with my real problem.
Let me be clear, I am a 20+ year software industry veteran and understand the complexities of this stuff. It is obvious that Adobe and Canon cannot put fully qualifed (and expensive) people on the first point-of-contact for support issues. However, they should have a reasonable escalation procedure that routes a problem of appropriate complexity to a highly qualifed person after a reasonable number of support attempts are unsuccessful in solving the issue. So far, this has not happened and is very frustrating to me.
Here is what I know of the underlying cause of the issue thus far. It appears to be caused by the interaction between Lightroom, the operating system's color management, and the printer driver. In essence, each of us are getting prints that are "double" or "triple" color managed even though we are trying to select one color managment workflow for our output.
Photoshop/InDesign and other adobe applications use their own color management engine called ACE. Lightroom does things differently and uses the computer's operating system CM functions. I believe this why my prints continue to look good when printed out of Photoshop yet look lousy (too dark) when printed from Lightroom. Lightroom is making assumptions when it sends a print data stream to a printer driver that doesn't yield the same result becuase each operating system performs color management tasks somewhat differently and print drivers from Canon/Epson/HP also do not use the operating systems CM functions the same way. For Mac users, if you add the printing engine architecture change from of Mac O/S 10.4 to Mac O/S 10.5 you throw an additional level of change into the equation which is not helpful.
So, where does that leave all of us who have this problem? I believe that for a given print driver/profile/operating system, Adobe will need to provide us with a workaround that will result in quality prints. To do this means that someone in Adobe who has the knowledge has to put together a specific recipe of options that work for the major printer manufacturers/OS's/printers. The long run solution will, unfortunately, occur over time as Adobe modifies how Lightroom makes certain assumptions when it sends print data streams to printer drivers and printer manufacturers will update their printer drivers to be more bulletproof regarding operating system color managment differences.
Sorry for the long-winded message. Unfortunately, this is one of those seemingly simple problems that has a lot of underlying complexity and does not yield a "one size fits all" solution. I will keep this group updated on what I learn as I work with Adobe.
Best,
George

Serious bug in Lightroom printing

Similar Messages

Maybe you are looking for