Hey @BarlaeDC ,
Thanks for stepping in
I sure can:
- Documents : I believe only big documents are creating issues. I'm working on books and Inlays/ Book blocks are most of the time within 100-400 pages.
- Size : Varies quite a lot. with lots of images (always unbedded). The total Links folder goes within 1-7Gb, sometimes even more. Indd files are from 50Mb to 600Mb. Print PDFs can go as high as 2.5Gb.
- Platform : MacBook M3 Max - 64Mb Ram - Sequoia 15.4.1 - 12/4 Cores - 40 graphic cores
I'm using a big custom script for dealing with exports. See UI panel attached.
For the coding part, here's the part where I deal with the print PDF
// Access and modify the PDF export Print presets =================
var myJobOptionsPrint = gCol2e1.text;
if (inPrRarSp.value == true) {app.pdfExportPresets.item(myJobOptionsPrint).exportReaderSpreads = true}
else {app.pdfExportPresets.item(myJobOptionsPrint).exportReaderSpreads = false};
// Set PDF export preferences
app.pdfExportPreferences.properties = {
pageRange : inPrPaSele1.text, // ========================
effectivePDFDestinationProfile : gCol1e1.text,
viewPDF : true,
optimizePDF : false,
}
if (inExpPrefSync.value == true) {
// Export the document with asynchronous method =================
var exportPrintFile = setEditPrintPath.text + gFole1.text + "/" + gFe1.text + gExeInPr.text + ".pdf"; // Chemin de destination du fichier exporté
app.activeDocument.asynchronousExportFile(ExportFormat.PDF_TYPE, exportPrintFile, false, myJobOptionsPrint, "", false);
} else
{
…
I'm pretty happy with it and the script itself appears to work just fine. Never had any error/ bad argument or else. It's just that sometimes, with no special pattern, the export goes into the background tasks and either doesn't start (stays at 0%) or is stuck at 99%.
If it's an "normal" issue that goes with the use of the inner behavior of the function, it's ok I guess. But if there is somehow something we could do to help it, well, I'm eager to know.
I've read a while ago (can't remember where/ who wrote it) a post of one Adobe expert who were talking about some very technical stuff on how PDF exports were done, and why multi-cores processors couldn't help speeding up the process. As far as I understood correctly, exports can only be done on one core. Since we, users, don't have to handle the cores, I would assume that if bad luck happens, the conjunction of an export on one core which was already busy doing something else on the computer would create some kind of overload and make the export impossible. That would probably not happen if the export is not asynchronous, just because of the way cores are handled.
That was my understanding then, took it for granted, and explains why I didn't ask about it sooner.
Now, as Confucius said “He who asks a question is a fool for a minute; he who does not ask is a fool for life.”
Any feedback would be then well received
Thanks
9
Replies
AdChoices
