Skip to main content
T
Teddy_Boi_Toronto
Participant
June 1, 2010
Question

Problems making a PDF from Indesign CS5

  • June 1, 2010
  • 46 replies
  • 74913 views

Hi friends. I have recently switched to CS5 and I find that I usually need to close the program and then reopen it before I can make a PDF. It says it is working in the background but all it does is spin without creating the PDF. Anyone else having this problem? 

TED

    This topic has been closed for replies.

    46 replies

    B
    blisimo
    Participant
    June 6, 2012

    Hello guys,

    I was looking for answers concerning several problems arising wih my documents on Indesign CS5, so if it happen your indesign cannot generate PDF , do check for importing elements on your artwork whether you are working with EPS,becuse the main source come from here.

    Hope this will help you.

    P
    Panu_79
    Participant
    August 20, 2012

    Hi all

    I have spent couple of nights with this tedious problem. After hard research I solved it! I know this may be quite complex issue (in fact I am not sure about that anymore) and vary between different operating systems but I got it work. My set up is win 7 64bit and I am using Indesign 5.5.

    My problem was in sertain pages and as I removed these 3 pages exporting worked like charm. The problem wasn't so mysterious after all. Luckily my document is only 24 page so it wasn't so hard case to find these buggy pages. Page number 6, 13 and 14 was "infected" somehow.

    Hope this helps!

    Ps. using range in export settings help when you try to rake up the pages with issues.

    What's cousing the issues in thes pages is another guestion. Can't answer on that, yet!

    T
    TimeCruncher
    Participant
    August 20, 2012

    Thanks for your response. Actually I'm attaching a file that shows how I

    solved the problem, just in case this may come in handy for you. Your

    problem was not the same as mine. I used it and haven't had a problem since.

    P
    PagePenna
    Participant
    July 22, 2011

    I have also recently upgraded to CS5 and am having the identical issues with making a PDF, small or Print quality, from InDesign. Background tasking seems to take over and I cannot even quit the document to clear things out, so I have to force quit.  I have gone to Software update, but no updates are noted.  The weird thing is that I noticed your posting is a year ago and surely there would have been an update by now.  InDesign version is 7.0.0.355; Acrobat Pro is 9.4.5.  Any thoughts....anyone?

    claidheamdanns
    claidheamdanns
    Participating Frequently
    July 22, 2011

    We use a third-party plugin (part of a very expensive suite) that disables background PDFs, and haven't had a problem since. Adobe has not addressed this issue. Nor do they have any option for turning off background PDF in preferences. There are several non-Adobe options for doing this, though. Look on this forum; you will find some less expensive options to turn off background PDF, and I'm convinced that is the key to the whole thing.

    G
    GreyCatDot
    Inspiring
    August 25, 2011

    OK, I upgraded to CS5 in March and started having this and various other problems. I did also upgrade to SnowLeopard at the same time. Yeah, I know late adopter. Figured all problems would be fixed by then. No such luck.

    I am told by a mac tech friend that it doesnt happen to everyone but when it does, it is chronic. oy.

    I have tried everything you all have suggested including dumping prefs for Acrobat, ID and QuickLook and turning Spotlight off. (something to do with Spotlight because other non Adobe stuff was being affected too). I even tried dumping master page guides. That worked. For now. I won 5.5 at a local meetup so I am really hoping this got fixed. The question is, did it get fixed with either 5.5 or Lion?

    Thanks for your patience and help, yall.

    Dot

    M
    Adobe Employee
    MatthewLaun
    Adobe Employee
    March 23, 2011

    For those of you who are successfully able to export to PDF using the script or Booked document to prevent the background, threaded export, please consider this...

    After not being able to  reproduce a crash with some of the files I've been provided, I worked  with a customer to get a crash log from his background PDF export failure. The  crash log appeared to indicate an impact from the Extensis font  auto-activation plug-in. If you are using any of the Extensis tools in  conjunction with InDesign CS5, and are experience failures to export to  PDF in the background, please disable the Extensis toolset, restart  InDesign, then try to export again and see if the export is successfull.  Please report results here, including the exact Extensis product and  version.

    Sincerley,

    Matthew

    claidheamdanns
    claidheamdanns
    Participating Frequently
    April 5, 2011

    Matthew,

    I've tried updating Universal Type to it's latest version. I've also tried turning it all the way off, and InDesign is still crashing.

    But at least I am getting a real crash report now, and if you'd like another file to try out, I've got one here for you.

    Problem Details:

    Process:         Adobe InDesign CS5 [2692]

    Path:            /Applications/Adobe InDesign CS5/Adobe InDesign CS5.app/Contents/MacOS/Adobe InDesign CS5

    Identifier:      com.adobe.InDesign

    Version:         7.0.3.535 (7030)

    Code Type:       X86 (Native)

    Parent Process:  launchd [75]

    Interval Since Last Report:          685266 sec

    Crashes Since Last Report:           171

    Per-App Interval Since Last Report:  456761 sec

    Per-App Crashes Since Last Report:   17

    Date/Time:       2011-04-05 10:52:16.503 -0500

    OS Version:      Mac OS X 10.5.8 (9L31a)

    Report Version:  6

    Anonymous UUID:  CC909394-8DB6-49DB-BAD9-3ABDACAC03B1

    Exception Type:  EXC_BAD_ACCESS (SIGBUS)

    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

    Crashed Thread:  0

    Thread 0 Crashed:

    0   com.adobe.InDesign.Text       0x1df95fce GetPlugIn + 1096990

    1   PublicLib.dylib               0x016f3905 VOS_SavedData::Normalize() + 501

    2   com.adobe.InDesign.Text       0x1df9fe93 GetPlugIn + 1137635

    3   com.adobe.InDesign.Text       0x1e0b3469 GetPlugIn + 2265529

    4   com.adobe.InDesign.Text       0x1e0c8927 GetPlugIn + 2352759

    5   com.adobe.InDesign.Text       0x1e0c8f31 GetPlugIn + 2354305

    6   com.adobe.InDesign.Text       0x1df7e161 GetPlugIn + 999089

    7   com.adobe.InDesign.Text       0x1df7eabf GetPlugIn + 1001487

    8   PublicLib.dylib               0x014d9482 Command::DoImmediate(short) + 34

    9   com.adobe.InDesign.Utilities  0x1a818aa3 0x1a817000 + 6819

    10  com.adobe.InDesign.Utilities  0x1a818ccc 0x1a817000 + 7372

    11  ...adobe.InDesign.AppFramework 0x19482788 0x19468000 + 108424

    12  PublicLib.dylib               0x014da5db CmdUtils::ProcessCommand(ICommand*) + 59

    13  com.adobe.InDesign.SlugCubed  0x23cf81fd TTTextUtils::CopyStoryRange(ITextModel*, RangeData const&, ITextModel*, RangeData const&) + 637

    14  com.adobe.InDesign.SlugCubed  0x23d1461a SlugMechMetaDataClientNotify::InitializeSlugTextFromStyleLayout(UIDList const&, UIDList const&, PMReal const&) + 394

    15  com.adobe.InDesign.SlugCubed  0x23d1512b SlugMechMetaDataClientNotify::DoUpdateSlugText(ISlugDocDataMgr*, UIDRef const&, IDAAttributeGroup*, SlugInstance&, IMechMetaDataMap*, IMechMetaDataMap*) + 2731

    16  com.adobe.InDesign.SlugCubed  0x23d15877 SlugMechMetaDataClientNotify::UpdateSlugText(ISlugDocDataMgr*, UIDRef const&, IDAAttributeGroup*, SlugInstance&, IMechMetaDataMap*, IMechMetaDataMap*) + 215

    17  com.adobe.InDesign.SlugCubed  0x23d15a27 SlugMechMetaDataClientNotify::HandleSlugContentUpdate(UIDRef const&, IDAAttributeGroup*, IMechMetaDataMap*, IMechMetaDataMap*, IMechMetaDataMap*) + 391

    18  com.adobe.InDesign.SlugCubed  0x23d15df0 SlugMechMetaDataClientNotify::OnMetaDataUpdate(IDAAttributeGroup*, IMechMetaDataMap*, IMechMetaDataMap*, IMechMetaDataMap*) + 512

    19  com.adobe.InDesign.MechCubed  0x23b8fbf4 MechMetaDataServiceUtils::MetaDataContentChangeNotify(IDAAttributeGroup*, IMechMetaDataMap*, IMechMetaDataMap*, IMechMetaDataMap*, IDType<ClassID_tag> const&) + 436

    20  com.adobe.InDesign.MechCubed  0x23b3ef2d MechUtils::DoMetaDataNotify(IDAAttributeGroup*, short, IMechMetaDataMap*, IMechMetaDataMap*) + 157

    21  com.adobe.InDesign.MechCubed  0x23b47cd3 MechUtils::DoPromptAndAnalysis(PromptAnalysisParams const&) + 723

    22  com.adobe.InDesign.MechCubed  0x23b2da27 MechDocMetaDataMgr::DoPromptAndAnalysis(long, IDAAttributeGroup*, short) + 103

    23  com.adobe.InDesign.MechCubed  0x23b3ee36 MechUtils::DoPromptUpdate(UIDRef const&, long, short, IPMUnknown*, IDType<PMIID_tag> const&, long) + 214

    24  com.adobe.InDesign.MechCubed  0x23b12238 MechDocFileHandler::OnSave(UIDRef const&, long, K2::UIFlags, long) + 200

    25  com.adobe.InDesign.MechCubed  0x23b128d9 MechDocFileHandler::Save(UIDRef const&, K2::UIFlags) + 185

    26  com.adobe.InDesign.MechCubed  0x23b12c9c MechDocFileHandler::Close(UIDRef const&, K2::UIFlags, unsigned char, IDocFileHandler::CloseCmdMode) + 684

    27  WidgetBinLib.dylib            0x02b33049 DocumentPresentation::ClosePresentation(IDocumentPresentation::SchedulingBehavior, short) + 569

    28  ...obe.InDesign.Application UI 0x1b2f8099 GetPlugIn + 691433

    29  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    30  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    31  com.apple.HIToolbox           0x94c4a3e0 SendEventToEventTargetWithOptions + 58

    32  com.adobe.owl                 0x02c91966 OWLThemeAddBrush + 7174

    33  com.adobe.owl                 0x02d5ae71 OWLDocumentCreateNonComposite + 3627

    34  com.adobe.owl                 0x02cac140 OWLPaletteCreateNonComposite + 22850

    35  com.adobe.owl                 0x02cf495b OWLDockGetAnchor + 20221

    36  com.adobe.owl                 0x02cfbed9 OWLDockGetAnchor + 50299

    37  com.adobe.owl                 0x02c902f4 OWLThemeAddBrush + 1428

    38  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    39  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    40  com.apple.HIToolbox           0x94c4a3e0 SendEventToEventTargetWithOptions + 58

    41  com.adobe.owl                 0x02c91966 OWLThemeAddBrush + 7174

    42  com.adobe.owl                 0x02cc89d7 OWLPaletteCreateNonComposite + 139737

    43  com.adobe.owl                 0x02cfd08f OWLDockGetAnchor + 54833

    44  com.adobe.owl                 0x02c902f4 OWLThemeAddBrush + 1428

    45  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    46  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    47  com.apple.HIToolbox           0x94c66ecc SendEventToEventTarget + 52

    48  com.apple.HIToolbox           0x94d55de0 HIWindowButtonView::SendWindowEvent(unsigned long, unsigned long) + 208

    49  com.apple.HIToolbox           0x94d55d06 HIWindowButtonView::ControlHitSelf(OpaqueControlRef*, short, unsigned long) + 156

    50  com.apple.HIToolbox           0x94c5b357 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 9533

    51  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    52  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    53  com.apple.HIToolbox           0x94c66ecc SendEventToEventTarget + 52

    54  com.apple.HIToolbox           0x94cc0a45 SendControlHit(HIView*, OpaqueEventRef*, short, unsigned long) + 297

    55  com.apple.HIToolbox           0x94cc08c5 HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 45

    56  com.apple.HIToolbox           0x94d2a7d8 HIView::ClickInternal(CGPoint const&, unsigned long, void (*)(OpaqueControlRef*, short), OpaqueEventRef*, bool) + 254

    57  com.apple.HIToolbox           0x94d16fb6 HIView::ClickSelf(OpaqueEventRef*) + 370

    58  com.apple.HIToolbox           0x94c59771 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2391

    59  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    60  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    61  com.apple.HIToolbox           0x94c66ecc SendEventToEventTarget + 52

    62  com.apple.HIToolbox           0x94d145f7 HIView::Click(OpaqueEventRef*) + 329

    63  com.apple.HIToolbox           0x94d14459 HandleClickAsHIView(OpaqueWindowPtr*, OpaqueEventRef*) + 151

    64  com.apple.HIToolbox           0x94d13de9 HandleWindowClick(OpaqueWindowPtr*, Point, short, unsigned long, OpaqueEventRef*) + 505

    65  com.apple.HIToolbox           0x94d13bdb HandleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 791

    66  com.apple.HIToolbox           0x94ccf602 StandardWindowEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 96

    67  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    68  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    69  com.apple.HIToolbox           0x94cbc3d7 CallNextEventHandler + 95

    70  com.adobe.owl                 0x02cfcc8b OWLDockGetAnchor + 53805

    71  com.adobe.owl                 0x02c902f4 OWLThemeAddBrush + 1428

    72  com.apple.HIToolbox           0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181

    73  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    74  com.apple.HIToolbox           0x94c66ecc SendEventToEventTarget + 52

    75  com.apple.HIToolbox           0x94c79603 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2579

    76  com.apple.HIToolbox           0x94c4b4f6 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2134

    77  com.apple.HIToolbox           0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405

    78  com.apple.HIToolbox           0x94c66ecc SendEventToEventTarget + 52

    79  ...adobe.InDesign.AppFramework 0x1946b13f 0x19468000 + 12607

    80  ...adobe.InDesign.AppFramework 0x194905fa GetPlugIn + 14282

    81  com.adobe.InDesign            0x000028ab main + 187

    82  com.adobe.InDesign            0x000027c6 start + 54

    BobLevine
    Community Expert
    BobLevineCommunity Expert
    Community Expert
    April 5, 2011

    I'm using Universal Type Server, which is the Industry Class Workgroup version of little brother Suitcase, and I don't see any option for Managing Plug-Ins. Anyone else with UTS know where this Manage Plug-Ins option might be in UTS?

    As I mentioned, though, I also tried completely removing the plug-in and still got the crash.


    With Suitcase Fusion it's under the Type menu.

    Bob

    M
    Adobe Employee
    MatthewLaun
    Adobe Employee
    March 16, 2011

    All,

    For failures that only occur when exporting with the default Print PDF path, the recommendation is that you submit your document to me to enable us to reproduce the issue and find the root cause and solve it. Until all root causes are resolved, use the solutions documented in the following KB doc, or utilize the forementioned script to force PDF export into the foreground:

    http://go.adobe.com/kb/ts_cpsid_87876_en-us

    Sincerely,

    Matthew

    J
    jdnorman
    Participating Frequently
    March 17, 2011

    Hi Matthew -

    Could you let me know what e-mail address or private method I can use to send you a link to download a document that is giving me consistent trouble? It is a somewhat proprietary document for a client and I'd rather not post the link in this forum.

    I've tried disabling preflight, and also did this, which was recommended to me previous by Adobe support, to no avail:

    1. Delete the "Datastore" folder located here:

    2. HD / Library / Application Support/ Adobe / SING / Mark II / Datastore

    3. Relaunch InDesign and test.

    I have an open case number for this issue with Adobe support - it's 181910243. Using the script for exporting a pdf in the foreground is the only method that works for me. Attempting to export an idml of the same document also crashes InDesign, though a homemade Applescript which forces the export in the foreground works:

    set this_file to choose file

    tell application "Finder" to set file_name to (name of this_file)

    set posix_this_file to POSIX path of this_file

    set file_name to ReplaceText(file_name, ".indd", ".idml") of me

    -- display dialog file_name

    tell application "Adobe InDesign CS5"

    open this_file

    tell active document

    export format InDesign markup to choose file name with prompt "Save IDML Where?" default name file_name default location posix_this_file

    end tell

    end tell

    on ReplaceText(theString, fString, rString)

    set current_Delimiters to text item delimiters of AppleScript

    set AppleScript's text item delimiters to fString

    set sList to every text item of theString

    set AppleScript's text item delimiters to rString

    set newString to sList as string

    set AppleScript's text item delimiters to current_Delimiters

    return newString

    end ReplaceText

    thank you -

    Josh

    M
    Adobe Employee
    MatthewLaun
    Adobe Employee
    March 17, 2011

    @Josh,

    To send me private information, click on my name under my avatar, then on the right side of the page you'll see a link that says "Send Private Message".

    Cheers!

    Matthew

    T
    Teddy_Boi_TorontoAuthor
    Participant
    March 6, 2011

    Hi Everyone

    Well, as annoying as this pdf problem is, the solution is as annoying. Yes there is a solution, the only trouble is, I have no idea what it is. All I know is after one of the updates (a few months back) the problem simply went away. Now I have no problems making PDF in CS5 in the background. It doesn't freeze. Thanks for fixing it, whatever it did) but obviously there are still a lot of people suffering with the same problem.  I wish I could share my secret with everyone who tried to help, but the truth is, I have no clue. I am happy, that it is fixed.

    TED

    J
    jdnorman
    Participating Frequently
    March 6, 2011

    To my knowledge, there has been no update or further information since a forum user supplied a problematic file earlier in this thread?

    Peter Spier
    Community Expert
    Peter SpierCommunity Expert
    Community Expert
    March 6, 2011

    The 7.0.3 update addresses what Matthew was able to identify as a primary/common cause of trouble. Obviously there are still some other issues, but anyone who has NOT installed 7.0.3 should do so.

    S
    suzyq011
    Participant
    March 6, 2011

       I've had ALL of the problems listed in this thread! And I've tried all of the tricks! Recently I took a CS5 created file and tried making the infamous PDF. I tried CS5, CS4 & CS3 and the program was literally shut-down each time. Finally in desperation, I thought to try the "old-fashion" fix that we used to do. Print the file to a PS file. Then use distiller to make the PDF file. Guess what - CS5 has no option to print to file! Well that was frustrating! Then I looked at my list of printers and interestingly I had a print driver for ADOBE PDF. I printed to that and low-and-behold it created a PDF for me! It didn't give me any options for the PDF, but I can go into the PDF properties and pretty much fix anything I need to do!    Hope this helps others. I don't look at this as a fix for the CS5 software. It needs to be figured out, but I'll use this in the mean time. I will also be looking around for other software that can do the book typesetting for me without all of these issues - one that truly handles files that have hundreds of pages, makes creating a  TOC a breeze and actually does an accurate and complete Index. Does anyone have any recommendations?  - Sue

    C
    camiczoernie
    Participant
    February 15, 2011

    I began experiencing the same type of hangup everyone else seems to have when I installed CS5. I finally took the advice of an earlier poster and installed a scripting solution written by Uwe Laubender for exporting PDFs in "foreground" that seems to have solved the problem. My only gripe now is with Adobe for ignoring the issue.

    M
    Adobe Employee
    MatthewLaun
    Adobe Employee
    February 15, 2011

    @camiczoernie,

    We here at Adobe are definitely not ignoring these kinds of issues. Our InDesign 7.0.3 release contained a fix for one cause of hanging PDF export background tasks, there could be others. I would welcome any files and information that can reliably reproduce a crash or other failure in PDF export. Please feel free to send me a direct message and we can work off list to understand the failure and get it reproducible in house for our engineering teams to look into.

    Sincerely,

    Matthew

    claidheamdanns
    claidheamdanns
    Participating Frequently
    February 15, 2011

    Matthew,

    I am glad to see that someone there is paying attention. A lot of times it doesn't seem this way.

    I do know that this problem is pretty wide-spread. I am hearing it from every sector. I heard our prepress manager roundly cursing out InDesign CS5, and calling it nothing more than a public beta this morning.

    I'd be happy to send you some files. However, I don't think it is file specific. For me, for instance, yesterday, every second file would hang. And it didn't seem to matter at all which file it was. All day the first file upon opening CS5 would work fine, and then the second one would hang, and I would have to force quit the app on the second export. When InDesign would boot up again, it was the same thing again. The file that had previously crashed would make its PDF in a matter of seconds and then the next file opened would hang, and the program would have to be force quit.

    Today, things have been running pretty smoothly. I've only had to force quit twice today, I think.

    Gavin

    A
    Anonymous
    December 22, 2010

    Hi,


    I've to make pubblic amend because as the newbiest noob i didn't looked for the most logical solution before posting here. I'm so used to investigate bugfixes on forums that I didn't check if there was an update available and..there was actually. Updating to 7.0.3 solved the pdf export issue.

    Thanks Matthew for your concern!

    Cheers

    Massimiliano

    M
    Adobe Employee
    MatthewLaun
    Adobe Employee
    December 22, 2010

    @Massimiliano,

    I'm so glad to hear it. Happy holidays!

    Matthew

    claidheamdanns
    claidheamdanns
    Participating Frequently
    February 11, 2011

    I am experiencing the same issue. All day long, it will export one PDF fine, then the next document I open, it doesn't matter what, it will hang on the export ... after several minutes, I have to crash out of the program and restart. It will then PDF the same document that was hanging, in a matter of seconds. And then it hangs on the next document.

    Some days are worse than others. Some days it will go for quite a number of PDFs without hanging.

    I am running Leopard. CS5, with everything consistently updated to the latest version.

    I had thought perhaps it was a memory issue, but I have a 2x3 GHs Dual-Core Intel Xeon, with 10GB 667 MHz DDR2 FB-DIMM Ram, so this shouldn't be a problem.

    Extremely frustrating. I can open up the same docs in CS4 and PDF all day long, faster. Even the docs that do PDF out of CS5 seem to take twice as long.

    H
    Hamb1e
    Participant
    December 22, 2010

    You know, I used to always defend Adobe when people said they were frustrated by them, but its getting harder and harder. Last week I had a fully functioning CS3 + Acrobat 9 system, which I foolishly upgraded to CS5, thinking that months after it's release all issues would have been resolved by now and it would be better and faster and all the things one would expect from an upgrade. But have they? Nope.

    Quite aside from the ridiculous lag that InDesign now exhibits in everyday use, on a 2x3Ghz, 8GB Quad-Core Intel machine, there's a slew of stupid new features that can't be turned off. Background pdf creation? That stupid rounded corners yellow box? Automatic guides popping up all over the place? If you're going to add these 'amazing' new features Adobe, at least give us the option to turn them OFF and get back to just working sensibly.

    But the biggest issue is making PDFs from InDesign. Somehow Adobe have taken something that worked flawlessly and simply in CS3 and made it into a goddam mess. Fonts disappearing or jumping... graphic elements disappearing. Ok – known issue perhaps, I'll run an update. 'Adobe Acrobat update failed'. Okay, I'll waste time uninstalling, reinstalling and trying again from scratch... 'Adobe Acrobat upgrade failed'...

    What the hell are you people *doing* over there? How can you screw up things that were *working* fine? You're supposed to be fixing things that *didn't* work, not tampering with things that *did*. Can you please take a leaf out of Apple's book a'la Snow Leopard and get back to bloody basics – I don't care how long it takes you, get CS6 right for gods sake. I like your software – I want to use it, but you're now putting barriers up that make me hate it as much as I hate MS Powerpoint. And now I'm faced with having to weight up the choice of simply downgrading eight machines to CS3 again and getting a refund for this useless piece of CS5 junk, or bearing with it and wasting hours and hours getting it all working properly, if it ever will.

    I'd like to assume that CS6 will either be either free or a $29 upgrade to CS5 users as an apology for this debacle, but I guess that's hoping a bit much. At this rate Microsoft might as well buy Adobe, and then Apple can get on with developing their own design suite that 'just works'.

    One more time – I used to like you Adobe, but you are seriously trying my and many other users patience. Can you please wake up and smell the takeover before it's too late.

    A
    Anonymous
    December 21, 2010

    I Everyone,

    i bumbed in this thread as many, looking for a solution to this endless background export to pdf. We're also experiencing it and hope will be fixed soon ['cause its cool to have background tasks :)], but in the meantime here's what we have tryed and what worked so far:

    - on a small document, converting all the text to curves, did work [1 page document]

    - turning off preflight -> close and reopen the document -> export with presets and/or new profiles-> worked just once but its worth a try

    - import the document into a book then export the book as PDF (in foreground) always works like a charm

    - using this script http://indesignsecrets.com/forum/general-indesign-topics/pdf-export-problems-with-cs5 works as the above

    - saving a postscript file and then distill it, works as usual

    so there are many workarounds, we're happy to continue working almost as usual, anyway we hope to hear good news soon !

    Cheers

    Visualtricks

    M
    Adobe Employee
    MatthewLaun
    Adobe Employee
    December 21, 2010

    @Visualtricks,

    If you have a doc that will hang in background mode in CS5 7.0.3, but exports successfully in foreground mode, I'd very much like to get a copy so that I can get our developers to investigate and see if we have another cause of stranded threads. Contact me directly, or post it to sendnow.acrobat.com and share it with me that way, or FTP, etc.

    Sincerely,

    Matthew

    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices