XnView Software

After experimenting with the IPTC features in 1.82 RC3 we have noticed the following: (The TIFF Doesn't work and the JPG's are corrupted. (see below)

1. Tiff IPTC data write does NOT work (at all). When editing editing IPTC data in 1.82RC3 Xnview appears to write the data to the TIFF file without errors. However, after refreshing XnView and opening up the 'previously written' IPTC data, the IPTC data does not appear (showing that the IPTC data was never written in the first place).
a. Also in the above situation, only the browser view context menu allows IPTC 'editing', NOT the preview view.

b. Also, in the above situation, ALL IPTC edit menu entries are greyed out and the short cut 'Cntrl - I' doesn't work.

2. JPEG IPTC data (NOT Jpeg 2000 format) entered in XnView 1.82RC3 WILL corrupt everytime the JPEG Data. We know this by Adobe Photoshop 7.01 giving an error upon opening any .jpg file that has been IPTC edited with Xnview. However, JPEG IPTC Data writing DOES work in 1.80Stable.

Guest wrote:After experimenting with the IPTC features in 1.82 RC3 we have noticed the following: (The TIFF Doesn't work and the JPG's are corrupted. (see below)

1. Tiff IPTC data write does NOT work (at all). When editing editing IPTC data in 1.82RC3 Xnview appears to write the data to the TIFF file without errors. However, after refreshing XnView and opening up the 'previously written' IPTC data, the IPTC data does not appear (showing that the IPTC data was never written in the first place).
a. Also in the above situation, only the browser view context menu allows IPTC 'editing', NOT the preview view.

b. Also, in the above situation, ALL IPTC edit menu entries are greyed out and the short cut 'Cntrl - I' doesn't work.

It's normal, IPTC editing work only on jpeg file.

2. JPEG IPTC data (NOT Jpeg 2000 format) entered in XnView 1.82RC3 WILL corrupt everytime the JPEG Data. We know this by Adobe Photoshop 7.01 giving an error upon opening any .jpg file that has been IPTC edited with Xnview. However, JPEG IPTC Data writing DOES work in 1.80Stable.

Really? You have not the problem with 1.80?

Strange i've checked IPTC writing with 1.82 final, and have no problem with PS7.

xnview wrote:

2. JPEG IPTC data (NOT Jpeg 2000 format) entered in XnView 1.82RC3 WILL corrupt everytime the JPEG Data. We know this by Adobe Photoshop 7.01 giving an error upon opening any .jpg file that has been IPTC edited with Xnview. However, JPEG IPTC Data writing DOES work in 1.80Stable.

Really? You have not the problem with 1.80?

We found the XnView problem in 1.82 (but NOT in 1.80.3)
It is when XnView "resaves" the Jpg when editing IPTC data from the Viewer mode! Resaving is Required when editing IPTC from the Viewer Mode. The XnView Resave Corrupts the file - and it will not open in PS7.

In Browser mode (and Menu option) XnView doesn't require "resave" when editing IPTC data, so the file then works perfectly in PS7.

Here's the XnView Resave Notice Warning after Editing IPTC data in Viewer mode:
Do you want to save changes to "(filename).jpg"?
Clicking Yes = Resaves and CORRUPTS the file
Clicking No = Doesn't resave - Doesn't write IPTC (EVEN though we chose IPTC "WRITE" in the Editing Dialog box)
Clicking Cancel = Cancels all = no corruption/no write of file

Of course once you choose Yes, you get the Save Picture Overwrite confirmation prompt.

Here is the PS7 error it generates:
"Could not open (file path).jpg because an unexpected end-of-file was encountered."


THE GOOD NEWS IS:
The above proceedure works perfectly in XnView 1.80.3. without corrupting the file when writing IPTC Data AND Saving the file.

****So... It is confirmed that:****
1.82 corrupts JPG files when resaving after IPTC Data write.
1.80.3 Works perfectly when resaving after IPTC Data write.

Question:
WHy can the Browser view write IPTC Data without resaving the file, and the viewer mode can't? (Viewer Mode require Full resave of entire Jpg file). It would sure be nice to have NO resave prompt after just editing IPTC data only. (Whole point of our using your great program instead of Photoshop for writing/editing IPTC data!!!!!)

(We just updated to 'member' so we can't edit last post)
SO... we're adding an Revised comment here:

The above was tested with Photoshop 7.0.
NOW we updated to Photoshop 7.01 with the IPTC patch.

Photoshop still complains of corrupted file
"This document may be damaged (the file may be truncated or incomplete). Continue?"

Pressing Yes in PS7.01 allows us to open the file.

Conclusion:
XnView 1.82rc3 might still be writing IPTC data (or resaving) incorrectly, whereas XnView 1.80.3 does fine.
OR...Photoshop 7.01 is still reading the XnView 1.82rc3 resaved file incorrectly.
(Note: Photophilia 1.9 is able to read the XnView 1.82 resaved files correctly).

Carl wrote:(We just updated to 'member' so we can't edit last post)
SO... we're adding an Revised comment here:

The above was tested with Photoshop 7.0.
NOW we updated to Photoshop 7.01 with the IPTC patch.

Photoshop still complains of corrupted file
"This document may be damaged (the file may be truncated or incomplete). Continue?"

Pressing Yes in PS7.01 allows us to open the file.

Conclusion:
XnView 1.82rc3 might still be writing IPTC data (or resaving) incorrectly, whereas XnView 1.80.3 does fine.
OR...Photoshop 7.01 is still reading the XnView 1.82rc3 resaved file incorrectly.
(Note: Photophilia 1.9 is able to read the XnView 1.82 resaved files correctly).

I can't rproduce it, could you send me a corrupted sample?

xnview wrote:

Carl wrote:(We just updated to 'member' so we can't edit last post)
SO... we're adding an Revised comment here:

The above was tested with Photoshop 7.0.
NOW we updated to Photoshop 7.01 with the IPTC patch.

Photoshop still complains of corrupted file
"This document may be damaged (the file may be truncated or incomplete). Continue?"

Pressing Yes in PS7.01 allows us to open the file.

Conclusion:
XnView 1.82rc3 might still be writing IPTC data (or resaving) incorrectly, whereas XnView 1.80.3 does fine.
OR...Photoshop 7.01 is still reading the XnView 1.82rc3 resaved file incorrectly.
(Note: Photophilia 1.9 is able to read the XnView 1.82 resaved files correctly).

I can't rproduce it, could you send me a corrupted sample?

I will email them to you.

Anonymous wrote:

xnview wrote:

Carl wrote:(We just updated to 'member' so we can't edit last post)
SO... we're adding an Revised comment here:

The above was tested with Photoshop 7.0.
NOW we updated to Photoshop 7.01 with the IPTC patch.

Photoshop still complains of corrupted file
"This document may be damaged (the file may be truncated or incomplete). Continue?"

Pressing Yes in PS7.01 allows us to open the file.

Conclusion:
XnView 1.82rc3 might still be writing IPTC data (or resaving) incorrectly, whereas XnView 1.80.3 does fine.
OR...Photoshop 7.01 is still reading the XnView 1.82rc3 resaved file incorrectly.
(Note: Photophilia 1.9 is able to read the XnView 1.82 resaved files correctly).

I can't rproduce it, could you send me a corrupted sample?

I will email them to you.

On xnview.com please...

Anonymous wrote:I will email them to you.

Do you have send me a sample?

http://img.photobucket.com/albums/v209/ ... DFORUM.jpg
http://img.photobucket.com/albums/v209/ ... DFORUM.jpg

Here are two corrupted files saved in XnView 1.82 RC3. Both were corrupted by editing IPTC data in Viewer mode and closing the viewer mode, which forced a resave and corrupted the file.

Photoshop 7.0 refused to open the files giving the error of and "unexpected end-of-file" (see above posts).

Photoshop 7.0.1 still gives an error, "document may be damaged (or the file may be truncated or incomplete)." But Photoshop 7.0.1 will still open the image. (see above posts)

Note: Filenames hold no relevance to this problem.

Have you tried using XnView 1.82.1?

ckit wrote:Have you tried using XnView 1.82.1?

I just tried it . . . and I still get the same error with 1.82.1.

I found a similar problem to this mentioned (top).

After upgrading to 1.82.1 it was not possible on my computer anymore editing IPTC information (on jpg), since the program terminated with an runtime error/ something like false adressing. After deinstalling and downgrading to 1.80.3 the problem was not found anymore, as before.
(Strangley I encountered similar problems with newest pixvue application.)

If the errorcode is needed I could install the newest version again and force IPTC editing to crash xnview (which always does on my computer with 1.82.1) to post the error here.

May it possible that there are some incompatibilities with other runtimes installed? Using MSWinXP.

Reg.

Guest wrote:I found a similar problem to this mentioned (top).

After upgrading to 1.82.1 it was not possible on my computer anymore editing IPTC information (on jpg), since the program terminated with an runtime error/ something like false adressing. After deinstalling and downgrading to 1.80.3 the problem was not found anymore, as before.
(Strangley I encountered similar problems with newest pixvue application.)

If the errorcode is needed I could install the newest version again and force IPTC editing to crash xnview (which always does on my computer with 1.82.1) to post the error here.

May it possible that there are some incompatibilities with other runtimes installed? Using MSWinXP.

Reg.

This has nothing to with our problem. Our XnView does _not_ crash. It just merely writes the file incorrectly when using the _viewer_ mode while editing IPTC (which then forces a "Re_Save") and corrupts the file saving it with _incomplete_ data.

The file opens in Photoshop (AFTER the warning that we have of file corruption of incomplete data) and will open everytime with the warning... unless RESAVED again in Photoshop.

No problem. I thought it could have something to do with it. Wrong handling? Maybe it is something different. Probably I should make up a new bug topic...

Reg.