P: Jpg exposes bugs in QImage and ZoomBrowser

Technic al BS aside I have windows 7 new adobe elements 10 and zoom browser 6.7 (newest).
Don't care about who or what causes this issue but now I have it and I can't use my zoom browser as I have in the past as it's too slow to load adobe edited images. As a simpleminded consumer I just want this fixed - don't care by whom - seems to me that the company that helps me 1st wins my dollars in the future. Who wants my money most?

See previous comments. Canon needs to debug their code, or contact Adobe and we can help them debug their code.

Hi, I've got an issue as above since changing from APE8 to 10

The problem occurs when opening a folder containing an edited image or images in Canon's Zoombrowser software which I use for collecting, collating and viewing images.

Problem is only when opening folders containing images (and the images themselves) which have been edited in APE10. Unedited folders and pictures or those edited with other software (including elements 😎 open immediately as usual.

However, if a folder contains an APE 10 edited image, or images, it takes about 30 seconds before the folder completely opens for each picture it contains that's been edited in APE 10. So for example, a folder with 1 APE 10 image takes about 30 seconds to open, while a folder containing 4 APE 10 images takes 2 minutes to open and a folder with 6 APE10 images takes about 3 minutes etc.. If I then want to view an APE 10 edited image, it then takes about another 30 seconds to open that particular image.

As stated, never had the problem viewing images edited with APE 8 or other editing software.

Picture sizes (all jpegs) are the same and if I edit in APE 8, all is still fine in opening and viewing through Zoombrowser, the problem only occurs with images that have been through APE10.

This was the response from Canon:

"This still reads as an Adobe issue due to the fact that you state APE 8 was compatible with Zoombrowser and the problems occur since upgrading to APE 10. The only suggestion I have is make sure you are using the latest version of Zoombrowser. As for the compatibility issue with APE 10, I am unable to offer support on third party software."

Any help would be much appreciated

Thank you

Talk to Canon about getting an updated version of Zoombrowser that fixes the bugs.

I have a problem with pse 10
When I have processed an image in pse 10 and store in as a jpg-file,the canon zoombrowser has big problems with showing it (it takes appr. 20sec). If I then open the same image in pse 8 an then save again in jpg the canon zoombrowser has no problems with showing it. Can anyone tell me what to do ?

You are belaboring it, and continuing your attempt to shift blame onto Photoshop for the bugs in your software (or just your misunderstanding of file format standards and how to parse file formats correctly).

I don't want to belabor this and I promise this will be my last post, but you really do need to get more familiar with the JPEG spec because the Qimage parsing issue is ancillary to the header corruption caused by the intermittent CS5 bug. The Qimage bug will never surface unless the file header is corrupted and this CS5 bug results in undeniable corruption of the header. A file corruption bug is worse than an "error handling" bug in my opinion.

And yes, those files *are* corrupted. You have a thumbnail embedded in the JPEG stream itself and as such, the spec calls for that embedded thumbnail to be free of JFIF segments. Simply put, embedding a profile in a thumbnail image IS NOT ALLOWED by the spec yet the CS5 bug is causing the APP2 JFIF segment to appear there: where it shouldn't. I suspect that might be why BreezeBrowser and other software are having issues with the files. Yes, with the right error handling, they can work around it, and maybe it can even be argued that they SHOULD work around it because embedded profiles in thumbnail images are not allowed. But they really shouldn't be there in the first place so I suspect it is possible that other software engineers have not accounted for that non-spec condition either.

Supposedly QImage has a new version out that fixes the bug.

You're contradicting yourself. The JPEG images parse correctly, and doesn't affect applications that read JPEG correctly. Only QImage has problems because it failed to parse JPEG images correctly.

Yes, we will work on the very minor Photoshop issue.
But the problem discussed here is a more major QImage issue of failing to read JPEG images correctly.

Well I ;have jsut fininshed working 20 files for a client and when sent to Qimage to print only 2 of them were messed up and had re-open them in raw as jpegs and re save as. this fixed the problem and they are now ready to print. Please stop being little kids and fix the problem. I have been printing and loving Qimage for many years and this problem has only been happening for a short time now. As mentioned but not noted by me with the latest release.