If your code stops processing when the 8191 limit is reached, that seems significant to me...RobertoG wrote:well, i think problem is not related to 8192 limit, because :
1. ALL files in command line (> 13300 chars) are processed by nconvert
2. 8192 is related to cmd.exe , not to internal CreateProcess function ,limited to 32k chars
https://blogs.msdn.microsoft.com/oldnew ... /?p=41553/
Processing the files by splitting the task into smaller conversions and then combining the outputs is certainly one possible workaround...i'm working on a workarond to manage it, a thing like:Code: Select all
nconvert -o temp1.pdf xx_p1.pdf xx_p2.pdf .... xx_p200.pdf nconvert -o temp2.pdf temp1.pdf xx_p0201.pdf xx_p202.pdf .... xx_p400.pdf etc...
Yes, but using a wildcard as in the following code:Only for information, have you tried to run in a .bat file a command like mine, related to your 1000_tif files, to check the error?
Or, do you want me to prepare the .bat and test?
Code: Select all
nconvert.exe -out pdf -multi -overwrite -c 1 -o 1000915388.pdf *.tif
Is there a reason why you can't simply use a wildcard as above, as it seems the easiest way and automatically accepts any number of input files?
I should also point out that the 1000 test TIFFs (which I originally created to test renumbering operations) all have very short file names, so the command line character limit is unlikely to be reached.