Image Processor bug

J
Posted By
jfriend00
Oct 13, 2005
Views
228
Replies
2
Status
Closed
I tried to report this bug in the bug report form, but the CGIs appear to be down and it won’t take any bug reports now. So, I’m reporting it here.

Concise problem statement:

When I select a bunch of images in Bridge and run the image processor to convert them to JPEG, I sometimes get an error in the Image Processor and it stops processing files.

Bug Description:

The problem only occurs if you have the:

[X] Convert to sRGB

option on in the Image Processor. The problem only occurs with some JPEG files as the source files. But, once I see it occur on a particular JPEG file, it always occurs on that JPEG file. Other JPEG files work fine. I don’t know what is different about one JPEG file versus another, but I do know that I can reproduce the problem with the following sequence:

Alt-PrtSc to capture a screen shot
In CS2, File/New, accept the clipboard defaults.
Edit/Paste to paste the screen shot on the clipboard into the file. Flatten
File/Save and pick JPEG as the file type.
Run Image Processor.
Select to run it on open files.
Check the [X] Convert to sRGB
Pick a destination directory that different than where the JPEG is located. Pick options to create only JPEG, level 10, no change in image size. Hit Run.
You get an immediate error.
It asks you if you want to see more info. If you say yet, it says "User Cancel" or something like that.

When I step into the Image Processor in the ESTK, I find that the User Cancel exception comes from the ExecuteAction line in the ConvertTosRGBProfile function in the Image Processor.

The image processor will work on this file is you turn the [X] Convert to sRGB checkbox off.

How to Master Sharpening in Photoshop

Give your photos a professional finish with sharpening in Photoshop. Learn to enhance details, create contrast, and prepare your images for print, web, and social media.

C
chrisjbirchall
Oct 13, 2005
Okay Friend. Just tried it here with the same results (so you’re not going mad!)

Interestingly it doesn’t have to be a screen grab. Just going FILE>NEW and creating a (say) 6×4, adding some text and flattening, gives the same result. Even if you save it as a PSD and reopen it the same thing happens. Yet another, existing, file in the same directory runs through the Image Processor just fine.

If you convert the profile of your new file to (say) Adobe RGB it will then work okay. Even if you then convert it back to sRGB it will still work fine.

So it seems to have something to do with the profile not being read properly by Image Processor on a newly created document.

Over to you Chris Cox and Co.!

Chris.
J
jfriend00
Oct 13, 2005
Here’s an update. The bug system finally came back up so I did file the bug.

There’s also a separate discussion with a coded solution to this problem in this thread: <http://www.adobeforums.com/cgi-bin/webx?128@@.3bbb4d70>. You can patch your own Image Processor script to make it work.

–John

MacBook Pro 16” Mockups 🔥

– in 4 materials (clay versions included)

– 12 scenes

– 48 MacBook Pro 16″ mockups

– 6000 x 4500 px

Related Discussion Topics

Nice and short text about related topics in discussion sections