IPv6 is turned off - it does not work well in New Zealand, so I've turned it off completely and my computers only use IPv4.   ... View more

In short:  I experimented a bit and found that by adding the following entries to /etc/hosts I can block a few Adobe servers which then allows InDesign 2024 to launch normally and work properly. 127.0.0.1 p13n.adobe.io 127.0.0.1 crs.cr.adobe.com 127.0.0.1 lcs-cops.adobe.io With these entries in /etc/hosts, InDesign cannot reach these services and does not 'hang' on startup. ... View more

Hi Abhishek, sorry for the late reply. I added the issue with some more info to the Adobe InDesign Uservoice a few weeks ago: https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/49822995-adobe-indesign-2024-hangs-on-startup-blocking-a-f   ... View more

Hi Alberto, Sorry - I was replying to your previous response. Looks like it's working now - great!   ... View more

Hi Alberto, the latest version is 1.0.75; if you could try it out and let us know how that affects the behavior that would be very helpful for us! https://rorohiko.com/wordpress/2025/02/20/apid-toolassistant-updated-to-1-0-75/ ... View more

Hi Giulia! Sorry to hear you experienced crashes with Rorohiko plug-ins. Would you mind sending us some more info in this regard? If there are any issues, please reach out to support at rorohiko.com and send us crash reports, screenshots, any info you can spare: it's very hard for us to fix issues without any info. At least, let us know which plug-in is involved. Note that there is a version 1.0.75 of APID ToolAssistant available on our web site... ... View more

I ran a few quick tests - I used my CEPSparker 'starter' and generated a small CEP panel with some basic functionality in it. Built a ZXP on Mac, and built another ZXP on Windows, and tried to use it on InDesign 2025, and saw no issues.Mac-built ZXP works fine on Windows. Windows-built ZXP works fine on Mac.  These use a self-signed certificate (created on Mac), and I am installing with Anastasyi's Extension Manager. What I assume might be the most important tidbit in my tests is that my default CEP version is 6.1 - old, old, but works fine for basic extensions. The things that need to be verified are Try building for CEP 12, 11, 10,... and see if that makes the difference Try creating the certificate on Mac vs on Windows and see if that makes a difference Could it be a problem with thr Creative Cloud Deskop (rather than the ZXP or ZXP Installer)?  Creative Cloud app - ID, Illy,... .... My Wild Guess based on the very limited info we have would be that maybe somewhere in the process something is being line-ending irresponsible and changing line endings on what seem to be text files, and that might be enough to invalidate the signature. That would cause this 'symmetric' behavior, where Mac-created stuff is broken on Win and vice versa. Just a wild guess though -without being able to make the issue happen for me, I am guessing stuff from a position of ignorance. I currently don't have the time to put a lot of hours into this, so I am just adding my small data point to the pool... It looks like a hairy issue, and we probably need a systematic exploration of the problems space which is a fair bit of effort.  ... View more

Just on a whim, worth a try: start a Terminal window and have a look in the /Volumes directory. There is a long-standing bug in InDesign where stray, abandoned volume mounts cause all kinds of trouble. Clearing the stray entries from /Volumes would then fix the issue. ... View more

Also, you haven't answered Uwe's question: what is the URL you're trying to access by way of getURL? I suspect that might be where the issue lies. ... View more

Man, that code is _old_. I've since had at least two rewrites and other approaches which work better. Unless you really, really want to use that old code, make sure to check out JSXGetURL (https://coppieters.nz/?p=720) and ExtendExtendScript https://coppieters.nz/?p=220  If you have good reason to want to use this very old version, let me know, but if I could choose, I'd prefer to put the old GetURL.jsx out to pasture...   ... View more

For another speed comparison: I've set up UXPScriptSparker to make it easy to run side-by-side comparisons between UXPScript and ExtendScript speeds. One example: https://github.com/zwettemaan/UXPScriptSparker/wiki/InDesignBrot There are a few more sample scripts embedded into UXPScriptSparker ... View more

I just bumped into this today, and got around it by 'double-wrapping' the AppleScript, and execute the problematic code by way of a command line invokation. For what it is worth, here's a snippet of my code: var appleScript = "tell application \"Finder\" " + "to make alias file to POSIX file \"" + srcFilePath + "\" " + "at POSIX file \"" + dstFolderPath + "\""; var osaScriptCommand = "osascript -e \"" + backslashEscaped(appleScript) + "\""; if (srcFile.name != dstFile.name) { var intermediateFile = File(dstFolderPath + "/" + srcFile.name); var intermediateFilePath = intermediateFile.fsName; osaScriptCommand += "; mv \"" + backslashEscaped(intermediateFilePath) + "\" \"" + backslashEscaped(dstFilePath) + "\""; } var wrapperAppleScript = "do shell script \"" + backslashEscaped(osaScriptCommand) + "\""; try { app.doScript(wrapperAppleScript, ScriptLanguage.APPLESCRIPT_LANGUAGE); } catch (err) { }   ... View more

Is this on an M1 Mac or a regular Intel Mac? Please provide ample details (e.g. exact version of Mac OS X, exact version of InDesign, M1 or Intel Mac,...).    What URL are you accessing in the sample.jsx script? Have you verified that URL is accessible from your location?  For the sake of argument, the sample.jsx refers to https://www.rorohiko.com but if that URL is not accessible from your computer (e.g. because of firewalls), you'd get 'undefined' in the variable s. The sample.jsx is very rudimentary and has no error checking whatsoever. ... View more

Another thought: make sure to NOT separate sample.jsx from the JSXGetURL folder. They need to stay together. Merely dragging sample.jsx into your scripts folder will not work - it needs the JSXGetURL folder in the same spot.  ... View more

Hi,   Kris here. I just tried it out on an M1 Mac with Big Sur and it seems to work fine. However, do note that it won't work unless you run InDesign in Rosetta. I'd need to make a new version that also supports M1. It is on the back burner until I get through my to-do-list for paying customers, which means it might be a long time before I get to it. So, for now, if you're on an M1 Mac, you need to run it with Rosetta. ... View more

I might be wrong, just a guess, but could it be Apple's security sandboxes? Make sure the System Preferences are set up to allow the AppleScript to control Illustrator etc... - I've not studied this in detail, but more recent versions of Mac OS X are very picky in what they allow. I'd have a look in 'System Preferences - Security' and make sure allowance is made for the script to control Illustrator. I think it might be under 'Automation'. ... View more

I think you need to make some very rough back-of-the-envelope calculations. Below some rough ideas. Take them with a grain of salt and work it out for yourself. I've not carefully verified my calculations, so I might be far off base here or there. Also, I am ignoring things like occasional crashes, restarts... which can cause things to go slower than expected.   First of all, I'd be thinking of InDesign Server, rather than InDesign. InDesign is not meant for these kinds of tasks. InDesign Server gives you better performance than InDesign can.  Depending on document complexity, size, script optimization, clock speed, fonts used... you can expect rendering times, say, between 0.1s and 10s per document rendered (just a range of order of magnitude based on my real-life experiences with InDesign Server).   If you need to go faster than can be wrung out via script optimization and optimizing tweaks like using bits of C++ code, you need more instances of InDesign Server working concurrently.    If you need to process 1,000,000 documents in one single batch, you can expect a single InDesign server instance to take somewhere between 28 hours (a little over a full day), and 2800 hours - 116 days (more days than there are in the month).  If you need to process 1,000,000 documents, but it can be spread out over the course of a month (e.g. you could process 33,000 documents per day, every day) a single InDesign Server instance could handle simple documents in the most optimistic case (0.1s to process a document).   In the most pessimistic case (10s to process a document), you need 92 hours of rendering time, which means you need at least 4 InDesign Server instances processing concurrently to 'fit' that in 24 hours. At 10s rendering time per document, a single instance can handle 24*3600/10 = 8640 document renders per 24 hours, so 4 instances handle 34000 documents per 24 hours. If you need to process 1,000,000 documents in about a single day (e.g. end-of-month), the picture changes. In the most optimistic case a single instance could handle 24*3600/0.1 = 864,000 documents in 24 hours, so you'd need 2 instances working concurrently to manage 1,000,0000 docs.   In the most pessimistic case you need 200 instances working concurrently. That'll be expensive, I'd say. A lot depends on what your expected usage pattern over time is. Also a lot depends on how much can be pre-processed, pre-templated and how complex the documents are. The more variability they have, the more processing it will take.  All depends. It might be feasible, it might not. Optimizing the process up-front could make or break the feasability. I would also look into other solutions - e.g. the ones mentioned before, or things like Apache FOP, or custom-made things around iText or PDFBox or other alternatives.  A lot depends on how high you value good typography as provided by InDesign Server.  ... View more

I think the reason is that the second URL needs authentication.  Much depends on what kind of authentication method is used. ... View more

Hi all,   I now have a much better solution, which is an ExtendScript enhancement. Very easy to use (simply #include a jsx file which automatically selects and loads a binary DLL or dylib). It works with all applications that have ExtendScript (so it also works with Illustrator, InDesign Server, ESTK, Bridge...). It's based on libcurl. More info here: https://coppieters.nz/?p=375 My previous 'GetURL' was using node.js/CEP which is not supported with InDesign Server. This new approach does not rely on CEP, so it works with InDesign Server. Example: #include "JSXGetURL/JSXGetURLLoader.jsx" var getURL = JSXGetURL(); var s = getURL.get("https://www.rorohiko.com"); alert(s.substr(0,1000));   ... View more

Note that ActionRecorder is very old. It was using the old CSXS technology (Air/Flash based) which is not supported any more, and the signing certificates on it have long gone stale.  At the time we were very hopeful and sank a lot of time, effort and resources into ActionRecorder, but we never found any takers, and when the move to CEP was made, we could not afford rebuilding it from scratch, so we had to abandon the project... ... View more

P.S. As a little taster - here's the Github repo with the sample scripts I discuss in my session on speeding up ExtendScript. Register and watch my session to learn more and make your scripts faster. The session is aimed at InDesign Server, but many of the tricks apply to any ExtendScript. https://github.com/zwettemaan/ESBoost ... View more