Jaymer wrote: ↑Mon Aug 02, 2021 8:57 pm
Is there any harm in running nconvert over and over on the same files? ... or any way to prevent this.
That depends on whether the files are in a lossless or lossy format: if they are JPEGs the quality would be expected to be progressively degraded, using the option to 'save at the estimated original quality (when possible)' could minimise that, but it would still be unlikely to meet your needs.
You could in principle convert the files to a lossless format the first time your script is run, but depending on the type of images, whether photographs or line drawings for example, that could have a significant impact on filesize.
if my images dir holds 1000 files, and 5 new ones come in today.
I only need to resize 5 - but no real way to identify just those 5. I may process these a few times per day.
So when my script starts, nconvert will process 1005 files, but only 5 will need to be resized to my spec.
All the others will be skipped i guess?
No, they will all be opened and then resaved...
Maybe I could set archive bit at the end of my process, and powershell could only run nconvert on the files with NO bit set when it next starts (which would only be the new files)?
Something like that, I don't have detailed knowledge of Powershell or that level of knowledge of CMD either.