Export to PDF causes blacks to go grey.

Hello,
I have been dealing with an issue involving the way InDesign exports to PDF.  In images and boxes drawn in InDesign the black value is being reduced to 95% while the text remains full black.  I thought it was a printer issue but I looked more carefully at the PDF and sure enough it's in the image I outputted to PDF format.  How would it be possible that the blacks in images and drawn boxes could loose the 100% black but not the text?  Do I have a bad install or just a setting misplaced?
I am running CS5.5 with all the latest updates on a brand new Mac Book Pro.
Thanks,
Brett

It's too bad this is such a convoluted process.
I don't see any problem with 1-bit black or text black with a CMYK Transparency Blend Space, either in InDesign's Separation Preview or in Acrobat's Output Preview after exporting via the PDF/X-4 preset. In all cases output reads as 0|0|0|100 CMYK, which is what you would want and expect going to  press
A placed all black 1-bit psd in ID
Exported to PDF/X-4
Are you outputting separations or to a composite printer? If composite  is your Print>Output>Color, Composite Gray or Composite CMYK?

Similar Messages

  • When I export to PDF, the black text is printing in full color instead of just black

    I have Pages 09 (version 4.0.5). I am exporting a document to PDF and emailing it to a copy shop for printing. The document has a color cover, and 36 pages of black text inside. The copy shop is telling me that the pages with black text are printing as color pages instead of black and white pages. I need to figure out how to get them to print black to keep costs down. Is this a problem with my file, with the PDF export, or with their print settings?
    Things I've tried...
    1. Using the color palette, I have switched to the color sliders mode and changed all the text to CMYK with 100% black and 0% everything else. I have also tried changing it to grayscale with 0% brightness. Neither of these seemed to have an effect.
    2. I downloaded the trial version of Adobe Acrobat Pro and converted the PDF to grayscale. This worked, but it's only a temporary solution.
    Any other ideas?

    Peter,
    It's a pretty safe assumption that your average Joe isn't using text styles, but in this case you're talking to a guy who has worked as both a prepress technician and a graphic designer in a former life. I just don't have all the software of the trade at this point in my life. If I did, I sure wouldn't be messing with Pages and Preview. Although overall I'm pretty impressed with them, considering what they are.
    Anyway, I am using text styles and I made sure to update them all. The PDF still came out with the rich black color. I have a feeling Pages' PDF exporter automatically converts all black to that four-color rich black on the assumption that you'll want it. I wouldn't care, especially since I'm just printing at a copy shop with no special quality requirements, except that we're printing hundreds of these things every week, and the full color prints more than double the cost.
    Thanks for the help, guys! It looks like filtering the PDF through Preview will do the trick. If anybody can confirm a way to do this directly in Pages, I would appreciate not having to go through the extra steps.
    Ben

  • Export to PDF causes fringing around transparent PNGs only in Acrobat

    If I export to PDF from Keynote '09 using the "Best" setting, I'm getting black fringing around solid elements in a transparent PNG that was placed in the original keynote doc. This fringing does not occur when the PDF is viewed in Preview. Any suggestions on how to remove the fringing?
    Example is here: http://i.imgur.com/3QXGf.jpg
    Thanks in advance for the help.

    Perhaps my explanation of why this is a problem wasn't clear. The type of PDF links that Pages creates are, quite reasonably, set to highlight when clicked (there are a variety of options in PDF for the visual action of a clicked link; highlight is best for user feedback. In an ideal world, when the user clicks a link in a PDF, you want the a highlight box to appear over the text of the link - exactly over it, not too large, not too small.
    Because Pages creates two links for each internal hyperlink, but the user will click only one of them in the PDF (whether in Preview or Acrobat), the highlight is almost guaranteed to be wrong for every click. If the user clicks the top link, only the top two-thirds of the text will highlight, and if the user clicks the bottom link, there will be a weird highlight either on the bottom third of the text or underneath it. It's inconsistent, but in most cases, it's wrong.
    Obviously, this is only cosmetic, but it's the kind of mistake that hurts usability and detracts from the user experience, and as far as I can tell, there's absolutely no reason for it, making it a bug.
    cheers... -Adam

  • Export to PDF causes hyperlink failore

    the following issue happens only in Keynote!
    in Pages everything works perfect!
    If I'm linking files on my server with filenames like "abc def" (with a space inbetween),
    after exporting to PDF: the link is converted WRONG!
    in part of showing: 20% for the space, it shows 2520%
    with the result . . . . the file is not founded when Safari, or any other internet explorer opens.
    And this happens only in Keynote!
    The same procedure in Pages works perfect.
    Any ideas?
    muchas gracias
    Rony B.

    I take little encouragement on how to use Apple discussions from someone who has made 3 posts, one of which is extremely difficult to understand the other places blames on the responder for not reading it correctly and the bad software.
    I have twenty years of experience in posting in technical forums, have the third highest rating in this forum for being able to help users solve their  issues, I use  Keynote and Adobe Acrobat Professional on a daily basis to author  interactive technical manuals.
    I am bemused by your use of the  word unprofessional, this is a user to user open forum, I am not paid to make posts in this forum, you could easily get a solution to your issue from a university lecturer or an 11 year old school student. If you are really interested in assistance in the future, help those to help you.
    "A bad worker is ready to blame  their tools,   workmates and customers for their failings.
    A good worker asks many questions and listens and learns from the answers."
    the apprentices motto

  • Crystal Report export to PDF cause high Heap usage ?

    Hi all,
    As part of our reporting integrated with our JSF/JSP application, Crystal report is converted to PDF then sent to browser for user to display. mean while during peak load our Heap usage could reach 3.5GB - 4GB. So I am suspecting the unclosed byteArrayInputStream is the cause.
    (This is a production application so I am collecting information before change the code)
    Is the unclosed() byteArrayInputStream  really cause the problem ?  (the codes is below)
    Thank you,
    Krist
    ByteArrayInputStream byteArrayInputStream = (ByteArrayInputStream)
                                     reportClientDoc.getPrintOutputController().export(exportOptions);       
    reportClientDoc.close();
    writeToBrowser(byteArrayInputStream, response, "application/csv", EXPORT_FILE);
    private void writeToBrowser(ByteArrayInputStream byteArrayInputStream, HttpServletResponse
    response, String mimetype, String exportFile)
       throws Exception {
          byte[] buffer = new byte[byteArrayInputStream.available()];
          int bytesRead = 0;
          response.reset();
          response.setHeader("Content-disposition", "inline;filename=" + exportFile);
          response.setContentType(mimetype);
          //Stream the byte array to the client.
          while((bytesRead = byteArrayInputStream.read(buffer)) != -1)
                { response.getOutputStream().write(buffer , 0, bytesRead);}
          //Flush and close the output stream.
          response.getOutputStream().flush();
          response.getOutputStream().close();

    I do not know if my solution to my Heap problem will help any of you but I thought I would just post it here
    just incase yourselves or others come looking for possible solutions.
    I created a very simlpe report with 2 groups and not much in the way of complex functions. Whilst reporting against about
    100 pages of output everything worked fine, but as soon as we pushed the report up to 500+ pages we got all sorts
    of issues.
    java.lang.OutOfMemoryError: Java heap space
    After much hair pulling and trial and error I discovered that the issue came about where I did not declare formula variables as local. I was concatinating various street address details for of the envelope windows.
    Stringvar Address;      //    I was using this declaration
    Global Stringvar Address;    // Specific Global declaration
    Local Stringvar Address;    // Changed to this declaration
    After changing to Local, my report now runs with no hassels. And the memory usage whilst exporting the report has gone from maxing out at over 1GB to almost nothing (dont even get it registering)
    Am sure someone can come up with a better explanation for this and give reasons but just thougth I would share.
    Cheers
    Darren

  • Background Colour Incorrect when exporting to PDF from Crystal Reports 2008

    Hello All
    When exporting to PDF from CR2008 the background colour of the crosstab is incorrectly displayed. The problem is as follows to create a crosstab with a grey header row and column details in white we have used the following trick.
    Format Cross Tab Border Background is set to Silver.
    Crosstab Expert Grand Total Background colour is set to white.
    The result is a crosstab with header in grey and details in white.
    This report displays correctly in CR2008, and exports as seen on screen to everything but PDF. When exporting to PDF the Crosstab is completely grey taking on only the Background colour of silver, and ignoring the Grand Total Background colour being set to white.
    What is strange that when I print to PDF the format is also displayed exactly as required,
    Any help on this matter would be greatly appreciated.
    Some additional details.
    CR2008 version 12.3.1.683
    Adobe Reader version 9.3.3
    Windows XP Professional
    Thanks
    Phillip
    Edited by: Phillip L on Nov 23, 2010 1:51 PM

    If this is a big issue for you then please purchase a case and a Rep can duplicate and escalate to R&D.
    As a work around export to Editable RTF and in Word 2007 you can get a PDF export plug-in and then export to PDF.
    Thank you
    Don

  • White text appears black/grey after export to PDF - but only on a PC!

    I use Pages to make flyers in A4-format. But 8 out of 10 times I make one, convert it to PDF and send it to my boss via Mail, I get a reply where he says that everything looks good but the text.
    I have a colored background or image with white text on top in its own layer.
    This problem has been tauting me for several weeks now, and I thought I had the soloution recently when I started to make sure that the text layer where brought to the front (top layer). But still i get the message back that the text is either black or dark grey and can´t be read on his PC. It looks fine on my Mac, but not on his XP/Vista computer.
    - I usually convert using the "Better" compression mode.
    - I tried to convert it using Print - Print to PDF but the problem persists.
    - I have deleted the plist-file as well. Same problem.
    But since this doesnt happen with all my flyers, I am beginning to think that there is something I am doing "wrong" while making the flyer or that there is some kind of "rule" that I dont know about. Or is it an unstable PDF-export algorithm?
    Can anybody help me please?
    Message was edited by: Rayden78

    I use Pages to make flyers in A4-format. But 8 out of 10 times I make one, convert it to PDF and send it to my boss via Mail, I get a reply where he says that everything looks good but the text.
    I have a colored background or image with white text on top in its own layer.
    This problem has been tauting me for several weeks now, and I thought I had the soloution recently when I started to make sure that the text layer where brought to the front (top layer). But still i get the message back that the text is either black or dark grey and can´t be read on his PC. It looks fine on my Mac, but not on his XP/Vista computer.
    - I usually convert using the "Better" compression mode.
    - I tried to convert it using Print - Print to PDF but the problem persists.
    - I have deleted the plist-file as well. Same problem.
    But since this doesnt happen with all my flyers, I am beginning to think that there is something I am doing "wrong" while making the flyer or that there is some kind of "rule" that I dont know about. Or is it an unstable PDF-export algorithm?
    Can anybody help me please?
    Message was edited by: Rayden78

  • How do I export a PDF in 100% black

    I am currently trying to send an ad to a local newspaper, and apparently when I export my document it's not 100% black, instead it has mixed CMYK values. How can I export a PDF in InDesign so it preserves 100% black for the printers? All of the black text in my document has the color Black which is equal to C:0 M:0 Y:0 K:100 , what is the issue? Do I need to have specific export settings for a PDF?

    Use the default PDF/X-1a preset.

  • 100k black exporting to PDF as rich black

    Hey guys,
    I've rattled my brain for long enough over this issue, it's time to ask the wider community.
    When I export a pdf with any of my export profiles, all overprint 100k (black swatch) blacks are exported as CMYK. It doesn't matter if it's text or a graphic, the whole document is CMYK.
    My export profiles have been bulletproof for the past 2 years, I use numerous printers so I always export using a very generic profile. Within the last two days, something has happened with my settings and eveything I export has this issue. I've poured over my settings and none of it has led me to an answer.
    My only solution is converting to my generic profile with numbers preserved.
    This makes the problem go away but it doesn't answer the question of why it has changed after all this time.
    Help.
    Screenshot of doc open in InDesign with text selected with black swatch selected:
    Screenshot of doc in Acrobat pro seps with black unchecked:

    Actually, a better question might be how you avoided the rich black using what you believe are the exact same settings over the past two years!!
    Simply stated, if you do a PDF export and the CMYK content in your document is in a different CMYK color space than that specified for your output and your export setting call for converting colors to the output color space without the preserve CMYK values specified, there will definitely be a CMYK to C'M'Y'K' conversion occurring. This has been true since at least the first CS version of InDesign (InDesign 3).
    The problem with CMYK to C'M'Y'K conversions is that they are a 4-3-4 conversion. The CMYK values are not directly converted to C'M'Y'K' but rather, converted first to the color management connection color space by use of the input profile and then from that color space back to the CMYK color space specified in your export settings. Such 4-3-4 conversions do not preserve pure colorant values. Thus you have the possibility of ending up with rich black if your content's color space and the output color space differ. The preserve numbers option was put in to effectively ignore CMYK to C'M'Y'K' conversion entirely and only deal with the conversion of RGB color spaces to the output color space. (Another technology, known a “device link profiles” can be used for CMYK to C'M'Y'K color conversions, preserving pure colorants, especially black. Unfortunately, InDesign doesn't support device link technologies!)
    Then we must come back to why things supposed worked the last two years without specifying the “preserve values” option?!?!? One possibility is that previously your default CMYK color space exactly matched the output color space, thus bypassing any color conversion at all!
              - Dov

  • Exporting PDF's in InDesign cs5 (grey rectangles very small file)

    Hello there,
    I am having an issue where I export a PDF and it comes out with all my pannels on each page as a grey rectangle with diagonal lines. Also the file is only about 57KB when it should around 4MB for what I'm trying to do.
    This is what I'm doing and my settings:
    Fire>Export...
    Save
    Then my settings are
    [High Quality Print]
    I tried changing the optional settings within that as well, but it doesn't seem to be fixing the problem.
    Any idea's? I would appreciote it a lot.

    Please repost in the InDesign forum.

  • Blacks are becoming rich blacks when exporting to PDF in CS2

    Im having a funny problem I have never noticed before where when I export to PDF from InDesign CS2 all blacks turn to rich blacks. I am verifying this by opening it up in Acrobat and viewing the separations.
    I have narrowed it down to a single setting. I can replicate it by selecting the "High Quality Print" preset and then in the Profile Inclusion Policy selecting "Include All Profiles" then exporting.
    This shouldn't be... Colour conversion is turned off so the PDF compiler should not be modifying the colour... just sending a tag along with it.

    I understand the processes of colour management and in no way am I trying to turn it off. Can somebody please try it out and see if my original problem is happening to them. I'm only asking about one variable... The Profile Inclusion Policy.
    I understand "No colour conversion" option does not mean turning off colour management... Its keeps all source files in their original colour space. I know this stuff.
    I also know there is not a lot of different between the hight quality print preset and the press quality other than the press preset has the Convert to Destination option set for colour conversion which forces objects colour to that of the destination profile. However this is not important... And please dont argue about this point because I'm only looking for a solution to one problem and I'm not a novice.
    I want to know why when I select include all profiles the black is converted to a rich black?

  • Exporting CS5 file to PDF causes the document size to enlarge on PDF!

    I need help... FAST! I have a 14-page 4CP calendar that bleeds on three sides. The bleed size is 3/16", per the printer's requirements. When I export the file from InDesign to PDF, the overall page size is increased by exactly 3/16"! I nearly missed this and approved the job for printing. Luckily, I turned on the rulers in the PDF file to double-check all the page elements were properly placed and wouldn't fall on the fold. That's when I discovered that objects that I had placed on a page were extending into the fold and onto the next page. I went back to my InDesign file and found that those elements were properly placed and did not extend into the fold as they were doing in the PDF file. I tried different PPDs, exporting the file with and without printer's marks... all to no avail. I finally printed the file to a Postscript (PS) file and then exported that file to PDF and got it to work. However, I would prefer to avoid that extra step. What is going on? Why is the file enlarging (coincidentally the EXACT same amount that the bleed was set for) and/or what am I doing wrong? Any help would be GREATLY appreciated!

    Are you familiar with bleeds etc?  i.e. have you used them before?  It sounds to me as if you're doing everything mostly right but not realising that Acrobat and Reader (please don't mention Mac Preview) show the size including the bleeds when you choose those options upon export from Indesign.
    Go back and check your document setup.  Page size should be excatly just that, finished page size.  Bleed settings (you might have to tick more options to see them) should be also just that.  Export the PDF, go to 'Marks and bleeds' tick 'Use Document bleed settings' and you're done.  The document will appear bigger.
    oh and use the camera button for screenshots.
    You can see the actual size of the doc by going Advanced > Print Production > Crop Pages and toggling between TrimBox (the size the page will get trimmed to) and CropBox (which includes the bleeds and is what displays).

  • Can I ask InDesign to resample as it exports to PDF?

    When I export an InDesign CS document to PDF I'd like to know what InDesign does to the images that it exports. InDesign Help, in this case, was no help.
    I'll give a preamble so you know what I'm on about. Originally when I first started this project 2 years ago, I thought I would layout the images within InDesign, and just before printing I would go through every one of the 800 or so images in the book (it's a big book), and crop and resample them to 300 dpi at exactly the final printed size. Big job.
    After a few months of using InDesign I thought: no, I won't do that. When I export to PDF I'll assume InDesign will give me options to 'crop to frame size' and set the ppi to 300 dpi as well as converting images to grayscale if I so choose. It'll be automatic.
    I'll make it clear with an example. Let's assume an original image was scanned to give an image that is 4000 pixels wide and 2000 high, and that the final image is 20" x 10". It is to be printed on a Xerox iGen which requires 300 dpi for no loss of quality. So how does InDesign get that particular image into the PDF?
    Q1: Does it resample and export at 300 dpi? i.e. in the example above, will it export an image of 6000 x 3000 pixels to the PDF?
    Q2. Or does it export the original image and does nothing to the image except cropping if I ask it to? If it needs resampling that will be done at print stage by the iGen.
    Q3: I didn't see any options for converting to grayscale. Can you export a PDF as grayscale?
    Why I am concerned about this is because if the original image is exported, that may cause me file-size problems. I scanned most of my images at 20MB-60MB, yet a lot of them when printed will be of the order of 20 square inches and only require about 6 MB for adequate printing. I may end up with a PDF file that is 5 to 10 times larger than necessary.
    The real problem I have is: I trust PS and InDesign to resample my images, but I don't have that kind of faith in the iGen. If I can't ask InDesign to resample images when it exports, I may have a problem.
    When I did my original series of test prints in July 2006 on the iGen, I cropped and resampled the images ready for printing before I imported them into InDesign. So I haven't tested the iGen's resampling capabilities. I be blunt I don't trust it. The iGen ( a machine costing in the millions) failed a simple test of converting colour documents to grayscale. Here are my notes written at the time:
    b Converting to Grayscale using the iGen
    Do not use the iGen RIP to convert colour images to grayscale because it converts all gray densities above 90% to 100%. ie dark shadows end up as 100% solid black shadows with the accompanying sheen. I measured this figure from the K-only gradient at the bottom of the page. It appeared solid black for the first 9mm of a 96 mm black-to-white gradient. All densities between 100% and 91% ended up as 100%. The effect is very obvious in Mums hair which became a solid mass.
    My full notes on the iGen are here: http://jucreek.googlepages.com/temporary if anyone wants to have a look.
    Anyway, that's why I have concerns about images. Maybe I should just knuckle down for a week and go through 800 images, cropping and resampling every one in Photoshop. Talk me out of it, please.
    And that brings me to my final question:
    Q4: Can I ask InDesign to do that job for me: to crop, to resample at a certain dpi, and to overwrite the original image so that it all matches up?

    Guy,
    Let me try to recap all your statments with my comments:
    > Let's assume an original image was scanned to give an image that is 4000 pixels wide and 2000 high, and that the final image is 20" x 10". It is to be printed on a Xerox iGen which requires 300 dpi for no loss of quality.
    From the very start you're in trouble.
    The image size you describe, set at 300 dpi, will only be 13 1/3" by 6 2/3". If the image is scaled up to be 20" by 10", it will only be 200
    >dpi.
    So, we're starting with insufficient data according to your requirements.
    Nothing that InDesign or Acrobat does can make that image the correct resolution.
    > Q1: Does it resample and export at 300 dpi? i.e. in the example above, will it export an image of 6000 x 3000 pixels to the PDF?
    No, InDesign and Acrobat's print device will only resample
    b down.
    Neither will resample up.
    > Q2. Or does it export the original image and does nothing to the image except cropping if I ask it to?
    The image created in the PDF will be cropped. It doesn't touch the original file.
    > If it needs resampling that will be done at print stage by the iGen.
    I believe the iGen will only resample
    b down
    the same as InDesign and Acrobat's creation of the PDF.
    > Q3: I didn't see any options for converting to grayscale. Can you export a PDF as grayscale?
    As mentioned, that won't happen in the PDF Export but will happen with the PDF Print driver. However, that will also convert colors in the ID file, not just images, to grayscale.
    > Why I am concerned about this is because if the original image is exported, that may cause me file-size problems. I scanned most of my images at 20MB-60MB, yet a lot of them when printed will be of the order of 20 square inches and only require about 6 MB for adequate printing. I may end up with a PDF file that is 5 to 10 times larger than necessary.
    Perhaps I did my math incorrectly, but in your original example, 4000 x 2000 pixels cannot be set at 20 inches by 10 inches at 300 dpi.
    It requires 6000 by 3000 inches to be 300 dpi at 20 inches by 10 inches.
    > The real problem I have is: I trust PS and InDesign to resample my images, but I don't have that kind of faith in the iGen.
    I don't think you need to worry about the iGen if you set your images correctly. But as I said above, you haven't sampled them enough. So the iGen isn't going to do anything.
    > If I can't ask InDesign to resample images when it exports, I may have a problem.
    You set ID and Acrobat to
    b downsample
    not
    b upsample.
    > When I did my original series of test prints in July 2006 on the iGen, I cropped and resampled the images ready for printing before I imported them into InDesign.
    Cropping and resampling in Photoshop is always preferred as you have the options for how the resampling occurs that neither ID nor Acrobat have.
    > So I haven't tested the iGen's resampling capabilities. I be blunt I don't trust it. The iGen ( a machine costing in the millions) failed a simple test of converting colour documents to grayscale.
    No, I wouldn't have expected the iGen to convert to grayscale at all! Converting to grayscale can be done in the Acrobat print driver, but I would prefer to do it in Photoshop if I demanded very refined conversions.
    > My full notes on the iGen are here: http://jucreek.googlepages.com/temporary if anyone wants to have a look.
    See my comments above.
    > Anyway, that's why I have concerns about images. Maybe I should just knuckle down for a week and go through 800 images, cropping and resampling every one in Photoshop. Talk me out of it, please.
    You can resample using Photoshop's batch processing, but depending on the type of cropping that might need to be done manually in Photoshop. But if the cropping is always of a certain size and position that could be done in batch processing.
    > Q4: Can I ask InDesign to do that job for me: to crop, to resample at a certain dpi, and to overwrite the original image so that it all matches up?
    No, InDesign doesn't overwrite your original image, but it will change the image in the final PDF.

  • Slideshow exported to pdf: jagged lines

    Although this issue has been brought up before in this forum, it has never been properly answered or resolved. Therefore, I will be pretty precise about the procedure in the hope that knowledgeable people will take a closer look at the issue.
    For test purposes on this forum, I make a "slideshow" in LR 2.1 MacBook Pro using one single 10Mpx RAW image that has been pre-rendered 1:1 in Library. For this demonstration, the slideshow has no borders, no text, and 0 pixel margins in layout.
    First, I play the slideshow i LR 2.1 so it shows full screen on my 1920x1200 SpectraView monitor, then, to make you see the result, I do a screen shot and then crop the relevant detail from the image, then 'Save for web' jpg to make it web friendly so you can easily see it.
    The following image is the relevant detail of the full-screen LR image, namely a car (a very nice beautiful good-looking car, since it happens to be MY car:-)
    (http://tmp.bragit.com/slideLR.jpg)
    Then, in LR 2.1, I export to pdf, choosing Screen as resolution, which in my case is 1920x1200, at 100% quality, 'automatically show full screen'. Then I open the pdf in Acrobat 8.1.2, which shows it in full screen on my 1920x1200 monitor. Since the monitor matches the chosen resolution, the result SHOULD be at least as good as the way LR "plays" the slideshow, but preferably with some suitable amount of output sharpening.
    However, the car in the image now has very ugly jagged lines. To make you see the result, I do again a screen shot and then crop the relevant detail from the image, then 'Save for web' jpg to make it web friendly so you can easily see it. (This jpg sRGB procedure has not affected the visual result of the artifacts in any relevant way.)
    The following image is the relevant detail of the pdf-exported full-screen image, namely the car:
    (http://tmp.bragit.com/slidePDF.jpg)
    It should be pretty obvious that the result is unacceptable. It is not primarily sharpening that causes the jagged behavior, it looks more like a very bad resampling. Many people seem to have reported the same thing, so I wonder how come this hasn't been addressed at all in the last few versions of LR? Or do you really have a workaround?
    PS: increasing resolution further (to for instance 3000x2000 pixels) on export does NOT solve the problem; it only makes the artifact somewhat smaller.

    As to why I export pdf slideshows: there are three reasons and usages for this:
    1. Making relatively small (eg. 900x1440) slideshows to be sent over email to people. For about a year I have noticed the quality is lousy, but I first thought it was because LR did a much too strong sharpening on export, but much later I came to realize that the problem has a much more severe origin. I took for granted that Adobe was trying to do something about it, but obviously not.
    2. I can merge several pdf slideshows into one slideshow, so that I can have an Intro Screen at the start of each new "event", where each "event" may be only a few slides.
    3. The native quality of slideshows as shown by LightRoom is lousy in deep shadows, just as bad as in the Library module, despite it has been rendered 1:1. It is ONLY in the Develop module that shadows are rendered decently, or on export to jpg, or export to a pdf slideshow (but the latter has other problems as I have shown above). So, to make the shadows better, and to avoid various problems with the Slideshow module (such as starting or stopping on the wrong image), I often export to pdf. In addition, color management can behave differently when displaying the show on a separate monitor or projector, where LR and Acrobat sometimes differ, especially on Plasma screens.
    I have discussed the issue of bad shadow rendering before in this forum (long ago), and Jao thought it was due to a corrupt monitor profile, or at least an improper rendering intent, but I don't think so, and I showed screen shots so that everyone could see the effect. Some people only saw an almost black image, but that is because their monitor is bad. I have a very good monitor (SpectraView) that shows almost the entire Adobe RGB, and the profiling makes me able to see colors all the way down into the deepest shadows. Whenever color management is not working as it should, I see that immediately. It is in those shadows that the Library and Slideshow modules do a very bad job. Maybe the reason is that the previews are based on jpg, and jpg itself is extremely bad in shadows, usually causing severe posterizations.

  • Objects missing when exporting to PDF, but show up when printing to PDF

    Hi - I'm working with someone, both of us in InDesign CS4, and she has some documents that cause a few random objects to just go missing when exported to PDF (same on my computer). But when printing to PDF, they show up fine. They also show up fine if we recreate each individual object, but that can end up being a lot of work. She prefers to export to PDF because of quality. I'm drawing a blank on this one!
    The attached file shows the issue. The green blocks just don't want to show up when exporting.

    Peter -
    The links are just the PDFs of the black and white portions and don't really matter too much since they show up fine when exporting or printing to PDF. Our main concern is the green blocks, which are indeed the green areas of the plan you pointed out. They are actually separate objects created directly within InDesign that can be moved and adjusted.
    I just updated to 6.0.4 and that didn't help. I wonder if this may be a variant of the bugs I was reading about with master pages and certain things not showing up when creating PDFs or printing (even though none of these things are on the master page)?
    Thanks

Maybe you are looking for