Image Processor Pro broken in CC2018 and Adobe's "support"

Cocktail Time

New member
Messages
3
Reaction score
3
TL/DR: Do NOT upgrade to 2018 if you rely on Image Processor Pro.

Image Processor Pro has been an integral part of my workflow for years. Originally offered as a third-party plugin by Russell Brown, it's been baked-in to Bridge/Photoshop for a while now.

My clients require delivery of five different files for every image I produce for them:

1 Tif file, full size, saved in Adobe 1998 color space for use in print

1 Jpg file, full size, 300ppi, saved in srgb for web and desktop use, labeled as "300"ppi

1 Jpg file reduced to 72ppi fsaved in srgb for web and desktop use, labeled as "72"ppi

1 PNG (to preserve transparencey) at 300ppi, srgb, labeled as 300ppi

1 PNG at 72ppi, srgb, labeled as 72ppi

As you might imagine, performing these transmutations manually for a dozen images at a time will break your brain. At one time I'd created a series of batch processes as droplets, (which broke my brain) and simplified the operation somewhat, but I had to run the images through the droplets in order to get them correctly arranged and labeled.

Image Processor Pro vastly simplified this operation, putting it all in one window and accomplishing all of the above including the correct renaming of the jpgs and pngs.

Adobe's broken Image Processor Pro as of CC2018, and unfortunately, rolling back to 2017... It's still broken.

Do NOT upgrade to 2018 if you need Image Processor Pro.

Adobe has been no help with this. The support wizard on their website dumps you into the community forum... no help... and provides no clue how to contact them by phone, chat or email. I got them on the phone by executing a google search, NOT through their support page, and was told that Adobe knows it's broken and their developers are working on it.
 
TL/DR: Do NOT upgrade to 2018 if you rely on Image Processor Pro.

Image Processor Pro has been an integral part of my workflow for years. Originally offered as a third-party plugin by Russell Brown, it's been baked-in to Bridge/Photoshop for a while now.
Russell actually had help in all this and it's not going to be updated.
My clients require delivery of five different files for every image I produce for them:

1 Tif file, full size, saved in Adobe 1998 color space for use in print

1 Jpg file, full size, 300ppi, saved in srgb for web and desktop use, labeled as "300"ppi

1 Jpg file reduced to 72ppi fsaved in srgb for web and desktop use, labeled as "72"ppi

1 PNG (to preserve transparencey) at 300ppi, srgb, labeled as 300ppi

1 PNG at 72ppi, srgb, labeled as 72ppi

As you might imagine, performing these transmutations manually for a dozen images at a time will break your brain.
Yes! Photoshop has been a 'one image at a time' affair from day one and while Russell's work helped, it's still not in PS's DNA.

We have Lightroom for that; built for this kind of work, processing multiple images.
At one time I'd created a series of batch processes as droplets, (which broke my brain) and simplified the operation somewhat, but I had to run the images through the droplets in order to get them correctly arranged and labeled.

Image Processor Pro vastly simplified this operation, putting it all in one window and accomplishing all of the above including the correct renaming of the jpgs and pngs.

Adobe's broken Image Processor Pro as of CC2018, and unfortunately, rolling back to 2017... It's still broken.
Adobe has broken all kinds of 3rd party products (I know, I'm a plug-in developer too). They don't do it out of spite, but it happens.
Do NOT upgrade to 2018 if you need Image Processor Pro.
Good point, if you rely on that tool and nothing in the NEW version is in greater need to you.
Adobe has been no help with this. The support wizard on their website dumps you into the community forum... no help... and provides no clue how to contact them by phone, chat or email. I got them on the phone by executing a google search, NOT through their support page, and was told that Adobe knows it's broken and their developers are working on it.
Again, it really isn't the Adobe PS team that let you down here; Russell just isn't going to do more work on that product. When something breaks your product, and again, I have a more than a decade of experience seeing this happen with our products, you have to fix them yourself. Unless you can prove the problem is a bug they introduced; that did happen for us once, PS broke our plug-in due to a bug we were able to show them. They fixed that bug, our product worked again.
 
ALSO:

FYI

I don't claim to be an engineer or to understand why, but I got IPP Pro working after installing manually in PS CC2018. Just 5 minutes ago.

I am using version 2015 3.2b5. I installed manually (following PDF instructions) on Windows 10 x64 on my new Core i9 PC. I have not checked it on Mac.

NOTE: The PDF calls out a manual file copy of "ImageProcessorPro.xml". The actual file (since the scripts have been updated) is called "ImageProcessorPro.mxi". If I copy that file, the script appears to work fine.

All I use IPP Pro for in saving out files in 5 different formats and sizes with custom names (used along with an Action). There may very well be other applications of the script that may not work properly and that I may not be aware of.

Good luck!

-----------------S
 

Keyboard shortcuts

Back
Top