Copy link to clipboard
Copied
When saving a FrameMaker 2019 book to PDF (Acrobat Pro DC installed), the Acrobat Distiller process takes anywhere from 8-12 seconds per page to process. For a 100 page book, that's over 16 minutes, which is several times slower than it used to be. What is causing this? I maintain my computer regularly and no other applications are behaving this way. Any suggestions?
Hi @en71557408:
Every application has a preferred way to create PDFs, and usually several other options. In FrameMaker 2019, the preferred technique is to use either use File > Save as PDF or use File > Publish and "generate" the PDF from the Publish pod. File > Save as PDF simply uses the last settings from the Publish pod, so if you need to edit or even just check the export settings, you have to open the Publish pod, and while you are there, you may as well just stay there to complete the p
...Copy link to clipboard
Copied
I've moved your post to the FrameMaker community. There is a better chance that somebody knows what's going on.
Copy link to clipboard
Copied
Thank you, Karl!
Copy link to clipboard
Copied
What point version of FM are you running? Are you all patched up? Check Help > Updates to check. Have you tried the other PDF methods? (Print Adobe PDF printer instance/Publish pod to PDF output)
Copy link to clipboard
Copied
Yes, I have the latest version: 15.0.7.973. This is a recent development, so perhaps there's something going on in that release.
I have tried four methods: Publish pod to PDF outputm, File > Save as PDF, Print Book to .ps, and Print Book to PDF. All are extremely slow.
Copy link to clipboard
Copied
On the path Print-to-.ps and separately Distill, which is the slow phase?
Are imported objects all local to the machine?
Copy link to clipboard
Copied
The distill phase was slow, but Barb found the problem for me--I had inadvertently selected the Use Distiller option in the Publish pod. This setting appears to be linked to the Print Book to PDF command in the File menu, because the fix worked when I used the command. I never use the Publish pod.
Copy link to clipboard
Copied
Why don't you use the direct PDF export from FrameMaker? That avoids the antique FrameMaker=>PostScript=>PDF shuffle via Distiller!
Copy link to clipboard
Copied
That sounds intriguing. I had not heard of "PDF export" before and spent some time trying to find out about it in various sources, including the online help. No results. Would you mind explaining how to do that or is the feature known by some other name?
Incidentally, the FM 2019 documentation recommends the File > Save as PDF method, which is what I've been using successfully up until a few weeks ago. Something has changed. My computer seems to be functioning normally other than being able to save FM books to PDF in a reasonable amount of time. Yesterday, one of the larger books I was working with took about two hours to convert to PDF. I tried everything I could think of, including rebooting Windows and checking for viruses, but nothing helped.
Copy link to clipboard
Copied
I think what Dov is talking about is the newer Publish feature - it uses a completely new engine to create PDFs.
Copy link to clipboard
Copied
If that's the case, I'm afraid I see no improvement. I'm averaging about 10 seconds per page, whereas a few weeks ago it was more like 1-2 pages per second, if not faster.
Copy link to clipboard
Copied
Hi @en71557408:
Every application has a preferred way to create PDFs, and usually several other options. In FrameMaker 2019, the preferred technique is to use either use File > Save as PDF or use File > Publish and "generate" the PDF from the Publish pod. File > Save as PDF simply uses the last settings from the Publish pod, so if you need to edit or even just check the export settings, you have to open the Publish pod, and while you are there, you may as well just stay there to complete the process. These use the new engine that Jeff referred to.
Neither of those options (again, they are really the same option) uses Distiller as a default. Distiller is still available for those who have determined that they need it, but it is no longer recommended. Is the Use Acrobat Distiller checkbox enabled in the PDF Settings dialog box? Does disabling it make a difference? (Click the Edit button in my screenshot, below.)
If that doesn't help, you might trying creating a new .sts file (maybe the old one is now corrupt?). Click the Change Settings button > New. FrameMaker stores the default.sts file in c:\Program Files\Adobe\Adobe FrameMaker 2019\fminit\Publisher. You can save the new one there with a different name (or really anywhere else where you can find it when you need to reference it).
Once you have created a new .sts file, click the Generate Selected Output button and let us know if the normal speed has returned.
If that still doesn't work, you might consider a uninstall/reinstall, or better yet, first, try resetting preferences. https://www.rockymountaintraining.com/adobe-framemaker-resetting-preferences/
~Barb
Copy link to clipboard
Copied
I'm still using Distiller because the font I use in my documentation will sometimes not convert correctly to PDF. It has all sorts of spacing issues. This is a bug that Adobe developers are working on solving, but for now, I have to deal with a slow process when I go to final.
Copy link to clipboard
Copied
That's good to know. Thank you!
Copy link to clipboard
Copied
Thank you, Barb! You're brilliant!
The problem was indeed that the "Use Acrobat Distiller..." option was selected in the Publish Settings. If that's not a default setting, I must have changed it at some point not realizing that it would affect the Save as PDF command in the File menu. I deselected the option and tried again. It didn't work at first, but after restarting FrameMaker, the change took effect and I'm back to a normal printing speed.
This eexperience is a good example of how the plethora of settings distributed across many dialogs in Frame, Acrobat, and Windows can be confusing to all but the most experienced users.
In any case, many thanks for helping me to fix this vexing problem.