Mike Chaney's Tech Corner

This appears while creating new images from a filter. This appeared on image number 3164 of 3300. Any ideas?

A little help, Anthony.
What appears when creating an image with a filter?

Fred

The error message shown in the topic's subject

....and what are you doing when this error pops up?
Are you creating a jpg? How..... ? The source image is a what created by what?
Fred

I'm taking a jpg file with a resolution of 2400 x 3600 (or vice versa) and reducing the resolution to 683 x 1024. This is during a batch edit, applying the filter to all images and creating new files.

Anthony,
Which reducing approach, please?
Email web copies?,  The convert image screen?    The Save AS screen?  Setting a new size in the Image editor screen?

The point is to replicate the error message. The more information the better.
How about the image?  Does it happen on the same image again, if you ran the routine again?
Does the size reduction stop at that point, or does it continue?
Fred

This is what I am doing:

1. Select a number of photos from the left hand qImage pane
2. Add them to the queue
3. Right click on the queue and choose Batch Edit
4. Adjust the resolution
5. Click Done
6. In the Enhancement/Filter Application pop-up, choose Apply to all images and Create new images
7. Set the jpeg quality to 100
8. Choose an Output folder
9. Click OK

The process does not restart when OK is click on the error. Because of the length of time involved in trying to reproduce the error in amongst 3300 photos, I think I will skip that bit unless a future run allows me to identify the exact image and test that. I only posted in case this was a recognized error that was likely to occur in a familiar circumstance, for example during a process consisting of a few thousand images.

Sounds like the sort of thing that a corrupted image header might cause.  Unless you can see the image number that is displayed on the status bar when the error happens or it fails to convert one of them, it'd take up to a dozen tries (cutting the list in half each time) to find the offending file.  Assuming there's only one.  Might not be worth it unless you are regularly converting those same files.

Regards,
Mike

Thanks Mike. I'll update this thread with better details if it happens again.

I had this same message last month with one image out of a batch that were sent to me from a cell phone camera. I opened the image on my phone, saved it, sent it back to myself and that solved the problem (wasn't a very good picture anyway).

About a month ago, I was converting a lot of large (camera size) images to 256x256 for use in a Mosaic program. I was doing this with batches of about 100 images, and probably did 20 batches. In at least half of them, I got this same error message. I was using the create web-sized images, and when it stopped with the error, the bad file was always one more than the one that Qimage said it was processing.(Since Qimage lies about which one it is processing-it's always processing the next one after the one it says. (Note to Mike-Just change "ing" to "ed", and Qimage will tell the truth about which file it is working on.)

Jeff Jessee

Hi - I'm having the same problem, I attach a picture that will give this error. It happens with ALL jpg's I create with Paintshop, Qimage will convert (option send E-mail) the offending picture and then it stops on the next image.

Thanks for the file: I can reproduce the message using that file.  It looks like some bad metadata in the file that is causing the problem but I'll have to try to pin it down.

And Jeff, no, it isn't lying.  :)  When it says "Processiong 1/2" it actually is in the process of working on file 1.  Where you are getting confused is that when it is done processing, it saves the image first and then copies the metadata (EXIF info) into the file.  So if file 1 actually has a problem at the metadata copying stage, you'll still get a JPEG for that conversion but no second file, making it look like the problem was in file 2 when in fact it had a problem in file 1.

Regards,
Mike

Update: fix will be out tomorrow, along with a couple little goodies.  :)

Mike

Now fixed in 2018.124.

Regards,
Mike

Thanks, works fine.