PS CS4 GPF when printing from an action
I have two printers, so when I'm batch printing I run an action which I recorded, one step of which does a Print Setup to select the correct (normally non-default) printer.
If I've done this manually once then all is well, but if I forget to do it then Photoshop will GPF when I run the action.
What gives?
Some interesting ideas, but I don't see how they actually apply in my case.
For example, print spooling doesn't come into play until I actually initiate the print - the GPF is occurring during print *setup*.
My basic beef, though, is that Photoshop GPFs and simply closes, potentially losing where I was in other images. An application should *never* GPF, no matter what happens in code which it calls, whether a printer driver, user-written script, plug-in, or whatever.
Similar Messages
-
CUPS Error message when printing from some applications
Hi. I've got an issue when printing from some apps, but not others. Up to a few months ago everything was fine, then it started when Word would not print direct to my printer (Epson Stylus Pro 3880), not a big deal as I don't use it a lot and could print it through Safari if needed. Then more worryingly as a designer I found that PDFs stopped printing direct too, again I can print through Safari and Preview. Last night I installed a firmware update and now InDesign (CS4) is refusing to print!! Not great as printing via Safari/Preview doesn't give me the same level of control over my prints. Just checked both Illustrator and Photoshop and they both print okay. I get the same error code each time "error: /usr/libexec/cups/filter/pstoraster failed" Does anyone know what could be causing this?
Thanks in anticipation. Dcytan,
As Matt pointed, an application printing to CUPS controls only the format of the input. It has no direct control over the chain of filters inside the printing pipeline. Acrobat isn't coded to use pstoraster, it is simpling submitting postscript to the print queue. In an un-molested Apple supplied CUPS setup, that works fine.
What is going on is that the CUPS system configuration got mangled by some third party bits. In the Unix tradition, the configuration is fairly transparent, in the form of plain text files. In particular, in /usr/share/cups/mime you will find out exactly how the filter pipeline is configured via a table of what filter to use to convert data between two mime types. So we can inspect how the filters are setup and how a broken pstoraster is getting into the chain.
I don't have a handy "before mangling" state, but I can clearly see the Apple specified filters to be invoked when the input data is application/postscript (in apple.convs). I can also see a conflicting filter definition referencing the broken pstopdf (in mime.convs) but with a higher precedence, overriding the apple specified filter. This is why, in reference to your points #1 and #2, simply removing pstoraster fails, because the filter configuration is what needs fixing.
On my system, I found the pstoraster filter to be a shell script referencing a MacPorts install of ghostscript. I've since removed MacPorts, but that evidentally left the CUPS configuration in this broken state. Without knowing exactly how the CUPS system was put into the broken state, fixing it can be a bit tricky. Another posting suggested replacing the broken pstoraster with the Apple supplied equivalent of pstocupsraster. That might work, but it would be better to simply remove the conflicting filter specification, which on my system is this bit in /usr/share/cups/mime/mime.convs:
# pstoraster is part of GPL Ghostscript...
application/vnd.cups-postscript application/vnd.cups-raster 100 pstoraster
Removing that will restore the Apple specified filter chain for postscript input. With the filter specification gone, you are free to remove the pstoraster filter itself.
On wating for Adobe to fix this...
Acrobat provides enough things to scream about without pinning non-Acrobat problems on it as well. Not only is this problem not the fault of Acrobat, but suggesting that Acrobat should reach into a CUPS system broken by some unknown third party and fix it is only going to complicate the situation by having two third party products trying to un-do each other's configuration of a system resource. Do you really trust Adobe to fiddle with system components it doesn't own? No, I didn't think so. Adobe installers and updaters have enough trouble with the stuff they do own.
So, why does this problem only seem to affect Acrobat (your point #3)? I suspect it is simply that Acrobat is in the minority of submitting Postscript to the print queue. Any print job produced via CoreGraphics APIs is going to enter the system via a different path (namely, PDF), but the Postscript method is completely legitimate and any application that submits Postscript will be affected in the same way as Acrobat.
I hope this sheds some useful light on what is really going on with this problem.
-john -
Banding occurs when printing from Illustratror/InDesign on HP Designjet Z5200 PostScript Printer
Recently we got the below printer for large-format prints such as posters, banners and the like.
http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/18972-18972-3328061-12600-3328080-4122732.ht ml
However so far when printing directly from InDesign and Illustrator there have been problems with "banding" (alternating stripes of darker and brighter colors on the paper when printing).
It seems that this could have something to do with either the type of paper and/or the OS (we use both XP and Win7) on which CS5 runs but I am still unsure if these are the real causes.
After having talked to a certified HP-technician (not only a support employee!) the technician pointed towards the CS5 package as the culprit.
At the very moment we are using a workaround that the before mentioned technician advised us to use which is basically the following.
Illustrator --> Saving the Ilustrator file, then opening it in Photoshop and saving as a tiff raster image in the relevant resolution, then importing the tiff raster image into HP's HP own "Instant Printing Pro" printing application.
InDesign --> Saving the InDesign file as a pdf, then opening the pdf in Photoshop and saving as a tiff raster image in the relevant resolution, then importing the tiff raster image into HP's HP own "Instant Printing Pro" printing application.
These two solutions both work without banding on the final print.
However, sometimes - as mentioned before - it seems that the paper might absorb the ink better if it's of a better/thicker quality when banding doesn't seem to occur (at the moment we mostly use plain paper settings in the local printer settings display when loading a roll of paper which also is a cheaper type of paper) and while banding seems to occur mostly when printing from XP machines it doesn't always seem to occur when doing so from Win7 machines.
What's the score on the above?
Any help and input is welcome and appreciated!Well, I have no official
connection to Adobe, but any manufacturer who sells a product targeted
at the graphic arts industry, and then says that the reason it doesn't
work is because there's a problem with the software produced by the
graphics industry leader needs a reality check. Printer manuafacturers
have had access to Adobe for years, so there's really no excuse for an
incompatibility problem.
Your company is a vendor? Get
escalated. HP should be all over getting this to work correctly,
including providing a RIP for you if that's what it's going to take to
implement proper printing. How do the expect you to demonstrate or
recommend this printer if it stripes the background?
Peter -->
You are right about basically anything that you said and I agree that this should be HP's headache. But it's not so simple at the moment.
First of all I'd hate to stand back like a dummy if it would turn out to be a minor driver setting issue or another insignificant problem that creates the banding. On the other hand it would of course also be the local HP-support failing since they didn't manage to tell us about it in the first place and that's really their job and responsibility but under any circumstance, I'd like to give the ideas and suggestions from the other participants further up this thread a chance and see if the pdf-printing or other ideas work. In other words..., if I'd complain to HP it had to be bulletproof.
Secondly we are supposed to sell these and similar products to our clients and if I should start a dicussion I'd have to argue not only with HP who would most likely claim that the workaround they told us works (in a way) and that this was a result - at least to them - as well. I might also have to start discussing with the CEO of our company, the purchasing department and the marketing director (the latter actually said some time ago when we had the first problems that if the printer didn't work according to the HP-consultant's promises they could have it back, so there is at least some hope there). At the moment I am too busy at work and too low paid to be getting into this. And I seriously doubt that HP would give us a RIP to be testing this off even though we'd argue that the clients won't be able to work this out if we don't do. They'd probably just say that it's mainly for plotting charts and architects or stuff or find a whole range of other excuses. It's not certain and there could be positive surprises but I'd say that that's not likely.
There is one other thing Peter that I am still wondering about...
If you take a look again at the fourth and last picture-link I posted you can see the exact same print as in link no. 3 but whereas the third link shows banding the last - the fourth image link - shows no banding at all. Now I am not a 100% sure anymore if these were both printed directly from Illustrator but to my best knowledge they were since I printed all of these banners the same day and I don't recall saving to tiff or using other programs. I might be wrong but if that's the case then the thick HP-paper doesn't band whereas the thin does. That's the reason why I stated previously that the banding might occur with thinner paper (or wrong paper load settings) and doesn't occur with thicker paper at all. As mentioned I don't recall this action a 100% but am pretty sure. Also therefore I would like to run another test when I get more time and won't be so busy at work as I am right now.
Do you think there could be a difference there...?
macinbytes wrote:
I'm guessing they have the same crappy Colorburst software that shipped with the HP we got and it's never going to get good with InDesign or Illustrator transparency. We have the thermal printer that is 6x more expensive and the software is still bad. At version 9.3 it still fails on InDesign transparency.
We just make tiffs or normalized PDFs for files containing InDesign transparency. Illustrator transparency generally works better than InDesign, but isn't infallible. Anything that uses the gradient feather tool in InDesign I don't even bother with a test print to see if it gets it because I know it will fail 100% of the time.
If they are a vendor they are in a Catch 22 if they do it right and go for a solution that normalizes the files properly before sending to the garbage software that ships with it. When you are talking about an entry level thermal inkjet the software package isn't going to be robust. Something like a GMG or other solution to handle all the show devices files works, but at best you are disingenuous about how files are being handled with your clients and face pushback when they can't run all the cool tricks to them when they get it out in the field.
Happens with Colorburst, happens with Colorgate, happens to a lesser degree even with the lower end Creo RIP. Fiery seems to get it good somehow, but doesn't power a ton of inkjets.
HP support is phonetag hell anyway for inkjets. They buy out tons of companies that produce anything printing like ColorSpan and provide bare minimum support on the products they slap an HP tag on. They want to sell inks and papers. They don't make the software and license it in bulk like the crap they load on their computers. They also usually ship with old software that needs at least a couple point releases before it is current, but even the current software on their thermal printers sucks at InDesign transparency. HP may need a reality check on their software, but I doubt they get it. They've got a sufficient stranglehold and supporting what is essentially a bottom of the barrel portion of their printing business is in the high maintenance low yield square for them.
macinbytes -->
Wow, now THAT is scary reading...!
If what you wrote is true then things really start looking bleak. But I can recognize some of the problems that you are mentioning although I am not into all of the details that you are writing about in your thread. But it sure looks like they just mass produce and try to keep support to a bare minimum whereas they are scoring big bucks on the media, inks and other accessories and then hope that complaints will die and people will just give up in the end.
It does make sense also seen in light of the fact that our local HP-consultant who "introduced" us to the printer praised it to the sky with a lot of "sales mambo jambo", trying it out in HP's own "E-share & Print" (which I was told by the HP-technician was the wrong HP-print program, instead he made me download and install the "Instant Printing Pro") whereas he NEVER even tried it off in any of the Adobe programs or asked some of our employees to do so.
If you are getting more info in regards to the development in these cases or solutions software-like speaking I'd love to hear from you.
Thanks for your time and for posting. -
Different Colors when printing from Photoshop and InDesign CS3
Different Colors when printing from Photoshop and InDesign CS3
I have the following problem:
When printing from Photoshop or InDesign to a PostScript printer, Adobe recommends to let Photoshop handle the colors (I use the German version, so I don't know the exact term used, it changes slightly in all CS3 apps anyway).
The manufacturer however told me to let the PostScript printer handle the colors.
When I chose this option in Ps's print dialog and then choose ISO Coated as the printer pfofile, the results are fine.
But when I place the exact same image in an InDesign file and print from InDesign or export to PDF and print via Acrobat, again using "Printer handles colors", the results are the exact same as if I had used Ps and chosen to let Ps handle the colors (way too saturated and a bit too red).
·Photoshop CS3
·InDesign CS3
·Test image is a TIFF in CMYK Fogra 27 Coated (which is also the working color space in Ps and ID.
·Printer: Xerox Docucolor 3535
·Printer profile: ISO Coated
How can I make sure the printer handles the colors in other CS3 apps than Ps? I tried it with ID's print dialog (translated from the German version: Color Management > Options > Color Handling: PostScript-printer decides colors).
Thanks a lot!RE: "You don't indicate what Xerox printers you have"
In my first post I named it, is that the information you need?
Docucolor 3535 using Splash 3535
That's interesting, so I have to find a way to turn off the printer's Color Management function? I mailed them, hope they can tell me how to do it easily. They usually just tell me to not use any profiles and so on, but that's the general rule in this area, I'm really tired of hearing it. Everybody seems to think profiles and LAB mode are nuclear science and I should stay away from it.
Anyway, the test image I'm using is a simple photograph (size A3, 300dpi), so no transparencies at all. I'm placing this image into an equally large ID file and print it from ID, then export it to PDF-X/3 and print it from Acrobat. Hope that helps. -
All of a sudden when printing from my desktop Mac in IPhoto the printout comes out black. My colors are fine on my HP color laser printer. I have printed many times and now all of a sudden it is not printing. A test copy from my printer comes out fine. I really think for some reason something has changed just in the last few days. Just communication with IPhoto and the computer.
As long as your cartriges are full, put a photo on you desktop, highlight it , click COMMAND P and the print preferences window should drop down, and select your printer and photo paper.
-
Colors not printing correctly - Only When Printing from Reader 9
I have recently been having problems printing color PDF's using Reader 9. Yellows are printing as blue, blues as pink, pink as grey, etc. I have no problems printing any other types of photos, documents, or powerpoint presentations so I am assuming it is some setting in Reader. My printer is an HP Color LaserJet CM1015. Any help diagnosing this problem would be greatly appreciated!
Thanks in advance,
DaveIt is using sRGB and that is the only color profile available.
In addition, when I try to print 4 slides per page and 1 slide per page, the colors are completely different than when I try to print 2 slides per page.
I have tried changing settings in print options and put them back to default and nothing I do changes the issue. Again, it only occurs when printing from Reader. Everything else prints colors perfectly fine. -
I want to remove the header and footer when printing from my mac, I can do this in the Page Setup on my PC but not on the Mac. I can do it each time I print but then it resets. How do I make a universal change?
== This happened ==
Every time Firefox openedGo to the "File" menu, then "Print." The window that appears will have three drop-down menus at the top.
The first is labeled "Printer",
The second is "Presets".
The third is unlabeled but has "Copies & Pages" selected by default.
Click on that third menu and select "Firefox" near the bottom of the list. -
HP Officejet 4630 Printer....how do change from the default setting when printing from the web?
HP Officejet 4630.....Windows 8, 64-bit
When printing from the web I am not able to change the print size.
1. Click File on Menu bar
2. Click Print open dialog box
3. Click Properties open printing shortcuts
Everything in Printing Shortcuts have a lock on it. Including Factory Default.
Any and all help with this problem will be appreciated.
Thank you in advanceI posted this to the wrong board. Can it be move to the right one?
thank you -
Printer doesnt appear in the print options window when printing from an application like word etc
Ok this topic is all over the help forums but I have a couple of different observations not previously covered and all remedies that have been posted and worked for most havent worked for me
First of all the Printer used to work with USB or NET connection and then suddenly unexpectedly stopped working. I cant say with 100% conviction whether this was when the upgrade to windows 7 occured or not
things I have tried:-
I have used the hp install wizard
I have a downloaded the windows 7 update.
I can ping the device
I can print a test page.
The icon appears in the device and printer window but with an exclamation mark.
I have tried NET STOP SPOOLER / NET START SPOOLER.
I can scan docuemnts OK
here is the part that I believe appears to be different from the other case on the forum.
If I open a word document and select print the printer preferences dialogue window opens but no printer is visible to select. When I select add printer it shows my network then double clicking this opens a window showing a printer icon but its a previous version?? so when I select it as a printer to add nothing happens and it still doesnt appear as a selectable printer in the printer preferences pop up window. So doesnt print any thing
Im lost for any other ideas to tryI had already tried this and it didnt work on your advice I repeated the process with same results it appears in devices list but with an exclamation mark but trouble shooter fails to find any problem
I refer you to the things tried and status in my first post i.e. I can ping the IP, I can scan. So my thoughts are now it must be something on my PC side that is the issue and not the printer or printer software.
Could it be a security level issue that's the reason why manual selection of add printer comes back access denied ??. Possibly I need admin login. However I am the admin and single user of my PC anyway so I should have access.
or some other PC setting why it doesnt see the printer in the printer settings when printing from an application ? -
HR_INFOTYPE_OPERATION not working when called from Dynamic action
Hi ,
Senario : I would like to execute a form from dynamic action which
creates a record in 0015 (Additional payment IT) .
I have writen the code as shown below am using FM HR_INFOTYPE_OPERATION
. When i execute the program from se38 it is creating a record, however it is
not created when it is called from dynamic action..when i debugged the code in
inside the FM HR_INFOTYPE_OPERATION there is a FM HR_MAINTAIN_MASTERDATA where
they are using call dialog (statement) and
sy-oncom = 'N' when called from Dynamic action and
sy-oncom = 'S' when called executed directly.
I tried to change the sy-oncom to S while run from Dynamic action it created
the record.
So Can anyone explain me abt sy-oncom and how can i resolve the issue..
code..
REPORT ZHRPYENH01 .
perFORM TERMIATION_9000.
INCLUDE DBPNPMAC.
FORM Termiation_9000 *
FORM TERMIATION_9000.
INFOTYPES : 0015.
*data : i .
*i ='c'.
*break-point.
*message i000(000) with i.
TABLES : PRELP.
DATA : P9000 TYPE PA9000." with header line.
DATA : P0000 TYPE STANDARD TABLE OF P0000 WITH HEADER LINE.
DATA : P0015 TYPE STANDARD TABLE OF P0015 WITH HEADER LINE.
DATA : HIRE_DATE LIKE SY-DATUM,
TERM_DATE LIKE SY-DATUM.
DATA : MOLGA LIKE T500L-MOLGA VALUE '25',
SEQNR LIKE PC261-SEQNR.
DATA : RGDIR TYPE STANDARD TABLE OF PC261 WITH HEADER LINE.
DATA : ACTUAL_PERIOD LIKE PA9000-RETENTION.
DATA : PNP-SW-FOUND TYPE SY-SUBRC ,
PNP-SY-TABIX TYPE SY-TABIX.
DATA : TER_PERNR LIKE PA0001-PERNR.
DATA : REF_PERNR LIKE PA0001-PERNR.
data : key type BAPIPAKEY.
data : payed_amount type p0015-BETRG.
data : future_payment_amount type p0015-BETRG.
data : p0002 like pa0002.
types : begin of t_deduction ,
deducation_date like p0015-begda,
future_payment_amount type p0015-BETRG.
types : end of t_deduction.
data : future_deduction type standard table of t_deduction with
*header line.
data : future_deduction type t_deduction .
data : RETURN type BAPIRETURN1.
*data : deduction_p0015 like standard table of p0015 with header line.
data : deduction_p0015 like p0015 .
xxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxx
****Prepare 0015 data for deduction
*deduction for payed amount
clear deduction_p0015.
*refresh deduction_p0015.
deduction_p0015-pernr = REF_PERNR.
*deduction_p0015-pernr = TER_PERNR.
deduction_p0015-lgart = 'M120'.
deduction_p0015-begda = sy-datum + 1 .
deduction_p0015-endda = sy-datum + 1 .
deduction_p0015-BETRG = payed_amount.
deduction_p0015-WAERS = 'SGD'.
deduction_p0015-ZUORD = TER_PERNR.
*append deduction_p0015.
**deduction for future payment amount
*loop at future_deduction.
*clear deduction_p0015.
*deduction_p0015-pernr = REF_PERNR.
**deduction_p0015-pernr = TER_PERNR.
*deduction_p0015-lgart = 'M120'.
*deduction_p0015-begda = FUTURE_DEDUCTION-DEDUCATION_DATE.
*deduction_p0015-endda = FUTURE_DEDUCTION-DEDUCATION_DATE.
*deduction_p0015-BETRG = future_deduction-future_payment_amount.
*deduction_p0015-WAERS = 'SGD'.
*deduction_p0015-ZUORD = TER_PERNR.
*append deduction_p0015.
*endloop.
Create a deduction wage type in 0015 for the employee
break-point.
CLEAR RETURN.
CALL FUNCTION 'BAPI_EMPLOYEET_ENQUEUE'
EXPORTING
NUMBER = REF_PERNR
VALIDITYBEGIN = '18000101'
IMPORTING
RETURN = return
if not return is initial.
message E000(000) with
'Referred Employee could not be locked for referal payment deducation,
please try after some time'.
endif.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '0015'
NUMBER = REF_PERNR
SUBTYPE = 'M120'
OBJECTID =
LOCKINDICATOR =
VALIDITYEND = SY-DATUM
VALIDITYBEGIN = SY-DATUM
RECORDNUMBER =
RECORD = deduction_p0015
OPERATION = 'COPY'
TCLAS = 'A'
DIALOG_MODE = '2'
NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
RETURN = return
KEY = key
break-point.
COMMIT WORK.
if not return is initial.
*return-TYPE
*ID
*NUMBER
*MESSAGE
message I000(000) with return-MESSAGE.
endif.
CALL FUNCTION 'BAPI_EMPLOYEET_DEQUEUE'
EXPORTING
NUMBER = REF_PERNR
VALIDITYBEGIN = '18000101'
IMPORTING
RETURN = return
xxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxx
Thanks and regards
-Senthil Bala
Message was edited by: senthil balaHi Senthil
Why at all U want a subroutine to create a record in IT0015 through Dynamic action.There are some standard codes available to update infotypes.
Let me give U an example
14 9CON BETRG 4 2 I INS,0015 This will create a record in IT0015 when IT0014 is updated with Wagetype 9CON
14 9CON BETRG 4 3 W P0015-LGART='5400' Set wagetype for IT0015(Here U can use a subroutine call to set the wagetype)
14 9CON BETRG 4 4 W P0015-BETRG=P0014-BETRG set amount for IT0015(Here U can use a subroutine call to get the amount)
14 9CON BETRG 4 5 W P0015-BEGDA=P0014-ENDDA set the dates(Here U can use a subroutine call to set the dates)
Hope this will help U.
Please award points if helpful -
When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly
When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly
Click on the print button
get the Print screen
Click Print then get the error
Am able to print fine from other applications
Have tried uninstalling and restalling Adobe 10.1.3, downgrading to v9. reinstalling the printer driver.
Process: AdobeReader [2372]
Path: /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
Identifier: com.adobe.Reader
Version: 9.4.0 (9.4.0)
Code Type: X86 (Native)
Parent Process: launchd [220]
Date/Time: 2012-07-22 18:19:40.579 +1000
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 9
Interval Since Last Report: 265926 sec
Crashes Since Last Report: 23
Per-App Interval Since Last Report: 30 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 6710821A-4F63-46E6-AD7A-75FB91C7B394
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000014
VM Regions Near 0x14:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
__TEXT 0000000000001000-0000000000003000 [ 8K] r-x/rwx SM=COW /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
Application Specific Information:
objc[2372]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 AdobeAGM 0x7e5f1824 PrintInstance::BuildEndPrintEvent() const + 84
1 AdobeAGM 0x7e5fa503 PrintInstance::NextPrintEvent() + 8157
2 AdobeAGM 0x7e5291f3 PrintSession::GetNextPrintEvent() + 151
3 AdobeAGM 0x7e529c60 _AGMPrintSessionGetNextPrintEventProc_GetNextPrintEvent(AGMPrintSession*) + 40
4 com.adobe.Acrobat.framework 0x8077def8 0x7fe0a000 + 9912056
5 com.adobe.Acrobat.framework 0x801d0749 AcroSecurityBailOutImpl + 2003525
6 com.adobe.Acrobat.framework 0x801d08eb AcroSecurityBailOutImpl + 2003943
7 com.adobe.Acrobat.framework 0x8004ffe0 AcroSecurityBailOutImpl + 428764
8 com.adobe.Acrobat.framework 0x800511fd AcroSecurityBailOutImpl + 433401
9 com.adobe.Acrobat.framework 0x7ffbaa3b CopiesPagesPDE_Prologue + 9523
10 com.adobe.Acrobat.framework 0x7ffbadce CopiesPagesPDE_Prologue + 10438
11 com.adobe.Acrobat.framework 0x7ffbb298 CopiesPagesPDE_Prologue + 11664
12 com.adobe.Acrobat.framework 0x7ffcc2ca CopiesPagesPDE_Open + 50672
13 com.adobe.Acrobat.framework 0x7ffcc495 CopiesPagesPDE_Open + 51131
14 com.adobe.Acrobat.framework 0x800066c5 AcroSecurityBailOutImpl + 127425
15 com.adobe.Acrobat.framework 0x80006852 AcroSecurityBailOutImpl + 127822
16 com.adobe.Acrobat.framework 0x80006a9b AcroSecurityBailOutImpl + 128407
17 com.adobe.Acrobat.framework 0x8018fe6e AcroSecurityBailOutImpl + 1739114
18 com.adobe.Acrobat.framework 0x801ffb92 AcroSecurityBailOutImpl + 2197134
19 com.adobe.Acrobat.framework 0x801ff925 AcroSecurityBailOutImpl + 2196513
20 com.adobe.Acrobat.framework 0x802e19ac AcroSecurityBailOutImpl + 3122344
21 com.adobe.Acrobat.framework 0x8001fa66 AcroSecurityBailOutImpl + 230754
22 com.adobe.Acrobat.framework 0x80020e3a AcroSecurityBailOutImpl + 235830
23 com.adobe.Acrobat.framework 0x80165925 AcroSecurityBailOutImpl + 1565729
24 com.adobe.Acrobat.framework 0x8016346a AcroSecurityBailOutImpl + 1556326
25 com.apple.AppKit 0x93d05fc5 -[NSWindow sendEvent:] + 7533
26 com.apple.AppKit 0x93c9f163 -[NSApplication sendEvent:] + 4788
27 com.apple.AppKit 0x93c30d11 -[NSApplication run] + 1007
28 com.adobe.Acrobat.framework 0x7fe0d28d RunAcrobat + 2557
29 com.adobe.Acrobat.framework 0x7fe0c9ce RunAcrobat + 318
30 com.adobe.Reader 0x00002e8b start + 2371
31 com.adobe.Reader 0x0000264a start + 258
32 com.adobe.Reader 0x00002571 start + 41
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9b0ac90a kevent + 10
1 libdispatch.dylib 0x98338e10 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x9833785f _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 3:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 4:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 5:: WebCore: LocalStorage
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.JavaScriptCore 0x9c9a7e81 WTF::ThreadCondition::timedWait(WTF::Mutex&, double) + 81
4 com.apple.WebCore 0x91b97501 WTF::MessageQueue<WebCore::LocalStorageTask>::waitForMessage() + 135
5 com.apple.WebCore 0x91b97454 WebCore::LocalStorageThread::threadEntryPoint() + 74
6 com.apple.WebCore 0x91b973b1 WebCore::LocalStorageThread::threadEntryPointCallback(void*) + 17
7 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
8 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 6:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9b0a9c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b0a91f6 mach_msg + 70
2 com.apple.CoreFoundation 0x95c619da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x95c6ab04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x95c6a1dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x95c6a088 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c5d80c4 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x9c5cbe25 -[NSThread main] + 45
8 com.apple.Foundation 0x9c5cbdd5 __NSThread__main__ + 1582
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x97b4c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9cd3de62 TSWaitOnCondition + 124
4 com.apple.CoreServices.CarbonCore 0x9ccaf37d TSWaitOnConditionTimedRelative + 136
5 com.apple.CoreServices.CarbonCore 0x9cd1167f MPWaitOnQueue + 200
6 AdobeACE 0x020310bd 0x2000000 + 200893
7 AdobeACE 0x02030ab5 0x2000000 + 199349
8 com.apple.CoreServices.CarbonCore 0x9cd125e0 PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
10 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97b4382a pthread_cond_wait + 48
3 AdobeAGM 0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
4 AdobeAGM 0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
5 AdobeAGM 0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
6 AdobeAGM 0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
7 AdobeAGM 0x7e4b09e1 thread_proxy + 45
8 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
9 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97b4382a pthread_cond_wait + 48
3 AdobeAGM 0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
4 AdobeAGM 0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
5 AdobeAGM 0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
6 AdobeAGM 0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
7 AdobeAGM 0x7e4b09e1 thread_proxy + 45
8 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
9 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9b0ab83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97b9be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97b4382a pthread_cond_wait + 48
3 AdobeAGM 0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
4 AdobeAGM 0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
5 AdobeAGM 0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
6 AdobeAGM 0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
7 AdobeAGM 0x7e4b09e1 thread_proxy + 45
8 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
9 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 18:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 19:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 20:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 21:
0 libsystem_kernel.dylib 0x9b0ac02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97b99ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x97b9b6fe start_wqthread + 30
Thread 22:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x9b0abbb2 __semwait_signal + 10
1 libsystem_c.dylib 0x97b4c7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x97b4c558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x93e79816 -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x9c5cbe25 -[NSThread main] + 45
5 com.apple.Foundation 0x9c5cbdd5 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
7 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9b0ac90a kevent + 10
1 com.adobe.Acrobat.framework 0x804ff1fe AcroSecurityBailOutImpl + 5340410
2 com.adobe.Acrobat.framework 0x8041adf7 AcroSecurityBailOutImpl + 4405491
3 libsystem_c.dylib 0x97b97ed9 _pthread_start + 335
4 libsystem_c.dylib 0x97b9b6de thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x7e5f17de ecx: 0x7e3f96ac edx: 0x00000001
edi: 0x7eac1420 esi: 0x01ab4228 ebp: 0xbfffdea8 esp: 0xbfffde60
ss: 0x00000023 efl: 0x00010286 eip: 0x7e5f1824 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x00000014
Logical CPU: 0
Binary Images:
0x1000 - 0x2fff +com.adobe.Reader (9.4.0 - 9.4.0) <8CEEE461-DF9E-46F5-816E-71DE8564A551> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
0x60000 - 0x61fff +com.adobe.eulaframework (??? - 1.0) <8AFCE794-4DCF-41B8-9D0F-30311D7BEB92> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/EULA.framework/Versions/A/EULA
0x2000000 - 0x210dfe7 +AdobeACE (??? - ???) /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACERight. After almost a day I finally sorted the problem.
Adobe Reader worked under the spare Admin account so I deleted that in case it was confusing the installer. I then rerpaired persmissions. I then re-installed Reader. Same problem "Internal Error"!!
So, I re-created another Admin account and opened Reader. No problem. After clicking accept licence it opened up with a question to make default or not. After this I hunted through every folder and found that Under 'User/Librarary/Application Support/Adobe' there was an Acrobat folder. When I checked the account I normally use there wasn't, and never was?? So I copied pasted a copy of the Acrobat folder into the same location on the non working account and all is fine.
Problem for me is, why did this happen? I wasted almost a day on this. Is it a problem with the installer, the Macbook or Permissions. I checked permissions and they are identical to those on the spare Admin account. So why did the installer not create the Acrobat folder on the main account from where it was installed? Reason it concerns me is with regard to updates. Will they also screw up?
I'll try to explore further as times goes on but for now I have to say I've had enough of Acrobat and Lion for one day. "It just works". Really??? -
Skin Tones Look Wrong When Printing From iPhoto
Hi
I'm having trouble getting the caucasian skin tones to look right on photos printed with my Epson Stylus C86 printer on Epson Premium Semigloss paper. They look too pinky/purple when compared with the screen of the Sony DSC camera I shot them with and also my iMac's monitor. They just look wrong as though the subjects have a combination of bad sunburn, high blood pressure and are blushing at the same time!
I've tried the following tips synthesised from other threads:
1. Downloaded the latest set of drivers from Epson's website.
2. Ensured that they are associated with the printer in ColorSync utility.
3. Selected the Use ColorSync option when printing from iPhoto's print dialogue box.
These made no difference to the default behaviour i.e. same color problems.
Could anyone guide me to a solution? I would rather not have to use another application to print them if possible. I'm not used to my Mac not "just working".
ThanksWhat color profile do the pics have? Is the printer set to the same profile?
Regards
TD -
[FIX] Darker prints and color shifts when printing from Lightroom 2
Hi,
The problem :
When printing RAW or TIFF files from LR2, you get a printer output that
is much darker than it should be and that presents various color shifts.
I'm using an Epson Stylus Pro 3800 with the latest Windows driver
(6.50 - which is rather old by the way). The workaround described below
works for me under Windows XP SP3. It should also probably work with
other systems/printers/drivers. Use at your own (minor) risk.
The "official" procedure for printing from LR is as follows:
1. Do not let the printer manage colors and select "Other..." from the
profile dropdown list and select the ICC/ICM paper/printer profile that
you want to use.
2. Click on Print... in LR which opens the Print Settings dialog.
3. Select the options you need and the paper you're using.
4. **Disable the color management from the driver's side** (in Epson's
drivers, "Mode | Custom | No Color Adjustments").
5. Print
Unfortunately, **this doesn't work** for many of us and this produces a
print that is dark and has color shifts as mentioned above. Note that
the same image prints correctly from QImage or Photoshop CS3 (that is,
the printer output corresponds to what you see on your calibrated
display).
Apparently, although color management has been (allegedly) disabled in
the driver, there's something wrong between LR and the driver which
makes that *both* LR and the driver are still trying to manage colors.
In other words, the "No Color Adjustements" option of the driver doesn't
seem to work with LR.
The workaround (found after hours of hair pulling and paper and
expensive ink wasting):
In step #4,
1. Instead of selecting "No Color Adjustments", set Mode to "Custom |
ICM
2. Click Advanced...
3. Check "Show all profiles".
4. Select Driver ICM (Advanced)"
5. Set **both** the "Input profile" and the "Printer profile" fields to
the very same profile that you specified in LR.
That is, if you specified Pro38 PGPP (Premium Glossy Photo Paper) in LR,
then also select Pro38 PGPP in both "Input Profile" and "Printer
Profile". This has actually the same effect has disabling color
management in the driver (what "No Color Adjustements" should normally
take care of).
That's it. When printing, you'll get exactly the same color results as
when printing from QImage or Photoshop. No more dark prints. No more
color shifts.
One might think that the bug is in the Epson driver but in that case,
QImage would have the very same problem. So I tend to think that the bug
is on the Lightroom side.
Note: Although Photoshop CS3 produces a correct printer output, it
demonstrates the same problem as LR when using the "Match Print Color"
option for soft proofing. But in that case, only the preview colors are
wrong. The printer output is ok. Which also tends to demonstrate that
Adobe has the problem, not Epson. Or maybe both... :-) .
Don't ask me why some users have the problem and other don't.
Hope this helps.
Patrick Philippot
MainSoft Consulting Services
www.mainsoft.frA sincere thank you for your reply, Michael. Sorry about the "it just doesn't make sense" shortcut. I have been trying to solve this issue since LR 1.1, spending dozens of hours on different trials and digesting everything written on this forum and the B9180 forum about color management and double profiling. My shortcut was a summation of my experience (and my frustration) but doesn't really advance the conversation. Here are some data that should be more useful in diagnosing the problem.
I am running Windows XP SP2. I calibrate my monitor monthly with the Spyder. The reason I suspect this may be an issue of double profiling is because the results (moderately strong magenta overlay plus an increase in contrast) match what more knowledgeable people than I on this forum describe when double profiling occurs. Perhaps I shouldn't presume it is double profiling, and follow Patrick Philippot's lead in naming the problem "color shifts." Patrick does refer in post #2 of this thread, however, to obvious double profiling.
I certainly do have a successful and consistent print method. With PS CS3, and either my Epson 1280 or my HP B9180, the output is almost always dead on. Here is how I do it. In PS from the print dialog box, under color handling I always choose "Photoshop manages colors." Then under printer profile I select the profile designated by the manufacturer for a particular paper/printer combination. Then in the printer driver I disable printer control of color. With the Epson I check the box "Off (No Color Adjustment)." With the B9180 I choose the option "Application Managed Colors." While I sometimes may tweak the final output, these procedures have served me well with PS for several years.
Contrasted with my positive PS experience, my experience with LR printing has been inconsistent. I regret having to be so imprecise but truly sometimes LR produces accurate results that match the calibrated monitor, but most of the time it does not. I use standard procedures with LR that parallel the PS ones described above. In LR's printing panel, under color management, I specify the correct profile, just as I did for PS. Then in the printer driver I use the same procedures I use with PS. Most of the time the prints have the magenta overlay and too much contrast.
BTW, the inconsistent LR printing only takes place with my HP B9180. I have never had any problem with off-color LR prints with my Epson 1280. Again, I emphasize that I have standard procedures that always work with PS (no matter which printer) and LR (but only with the Epson).
Unfortunately the LR printing problems are intermittent. Some of the time (perhaps 20%) LR produces fine prints in the B9180, indistinguishable from PS prints. When LR is printing well, it will continue to print fine until "something happens" and the output shows the color shift. This means I do not get a random sequence of good-bad-good-bad prints, but rather good-good-x factor-bad-bad-bad. Ths problem is that I do not know what this "x factor" is. Once, when LR was giving me accurate output, I simply changed the default printer (Control Panel-Printers and Faxes) from the B9180 to my Samsung 1430 laser; immediately afterwards the LR output colors shifted. Did LR react to this change in default printers? Another time I had good LR printing success with version 1.2 but ran into the problems described above when I upgraded to version 1.3.
Sorry for the long post. I am hoping that someone will see something that I am missing and provide a hint. I think, though, that Patrick is correct when he states, "I tend to think that the problem is with LR. After all, similar issues (obvious double profiling) are observed only in LR but with various printers." -
How to print within the margins of the page when printing from iPad to HP Envy D410a?
When I try to print something from the iPad, either the 1 or the 2, the result is that the image sent from the iPad is printed Borderless, which of course results in parts of the print being cutoff, is there someway to resize the print through the printer, since the iPads don't have drivers?
Also, I seem to have a similar problem when printing from my PC, only in it's case the resulting print is smaller, it seems to print into a margin size of 1" on all sides. The only app that I have found that lets me override this is Adobe Reader which has the page scaling options.
All suggestions will be appreciated. TIA.
Stephen.
This question was solved.
View Solution.You may download HP iPrint software to edit margins & borders:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01616126&lc=en&cc=au&dlc=en&product=4073738
Although I am working on behalf of HP, I am speaking for myself and not for HP.
Love Kudos! If you feel my post has helped you please click the White Kudos! Star just below my name : )
If you feel my answer has fixed your problem please click 'Mark As Solution' and make it easier for others to find help quickly : )
Happy Troubleshooting : ) -
When printing from an online PDF, the page prints in extra large scale. How do I fix this?
when printing from an online PDF, the page prints in extra large scale. How do I fix this?
This can happen when Firefox has misread the paper size from the information supplied by Windows. Clearing it can involve finding some obscure settings, but here goes:
(1) In a new tab, type or paste '''about:config''' in the address bar and press Enter. Click the button promising to be careful.
(2) In the search box above the list, type or paste '''print''' and pause while the list is filtered
(3) For each setting for the problem printer, right-click and Reset it. The fastest way is to right-click with the mouse and then press the r key on the keyboard with your other hand.
Note: In a couple other threads involving Brother printers, the preference '''printer_printer_name.print_paper_data''' was set to 256 and when the user edited it to 1 that fixed the paper size problem. If you see a 256 there, you can edit the value by doubling-clicking it or using right-click>Modify.
Maybe you are looking for
-
Is there a way to import SAP background jobs from one client to another? In SM37, there ia an option to export the job, but I don't see an option to import it. Thanks
-
Error while deploying application on weblogic server
Hi, I have created webservice and deployed on weblogic server. Earlier it was working fine. I added some logger and trying to redeploy it. But it gives following error. Weblogic Server Exception: java.lang.NoSuchMethodException: deploy(java.lang.Stri
-
Hi All, My requirement is to Display a Custom Report in Portal. This Report is developed in Abap. Since I am new to this portal thing I can think of only 1 idea to display these reports in Portal by creating transactional iViews . But In HTML transac
-
When i receive an invite from a different time zone, it adds it to the calendar with that time zone instead of mine and shows "floating" instead of the timezone... how do I solve this?
-
IPhone 4 won't turn on or show dead battery logo
So, one day I couldn't find my iphone. I look and look and then I finally find it just sitting on my bed (upper bed). I try to turn it on and it does something weird. If it's dead, it will show the dead battery and the connection sign, but it didn't