🚀 go-pugleaf

For what it's worth, I gave up hope that Adobe will ever fix this issue with ImageReady. It's absolutely pathetic that they have known about the problem over something like at least 4 or 5 major releases now (not to mention tons more minor patches) and still the problem exists -- but there you have it, a company that evidently doesn't care about certain products or aspects of them, doesn't read user posts on their own forums or at least selectively ignores some of them, fails to respond with even an acknowledgment that this is an ongoing bug and some sort of "we have no plans to fix it" statement (which would at least let us know where we stand on the issue), and provides a ridiculously obtuse reference to the issue and a non-solution to it in its support knowledgebase.

Way to go, Adobe.

I switched to a little free utility called Irfanview that does a pretty good job of batch processing this particular optimization that I was talking about. Of course, all of the OTHER various ImageReady batch-processing droplets I was planning to create are now just unfulfilled pipe dreams...but oh well.