PWP 6 64bit workflow mystery

[MikeG]

I've just been processing NYE's firework photos. I took the shots as jpegs so I could continuous shoot when appropriate.
After triaging, I processed my favourites in a workflow as follows:
Straighten (breakpoint), crop (breakpoint), sharpen, sharpen, save as jpeg.
To my surprise the new images were unreadable by all the software I tried EXCEPT PWP which could load them no problem.
As an experiment I made a one widget workflow - save. No problem with reading output from this.
Multitasking or not appears to make no difference.
Rebooting - no better.

And ideas?

Mike.
PS I'm running Windows 7 64bit Home Premium. Up to date.

[Charles2]

You might upload a file to http://minus.com/ and inform us of the link to it.

[MikeG]

Charles, thanks for introducing me to Minus!

I've uploaded the file. While doing so it became obvious that the file is really big, about 40MB. I checked and PWP 6 comes up with a similar number. The original file size is 7.23MB with a slightly higher pixel count than the edited file.
All jpg.

The uploaded file is here: http://minus.com/m2jp0WPtz#

Mike.

[gio]

Good Morning Mike,

obviously the file is a Tiff-File with a JPG-extension - i.e IrfanView says "Warning, the file xxx.JPG is a TIF file with incorrect extension ! Rename?"
Does renaming the extension to tif help?

Happy New Year
gio

[MikeG]

You're spot on. Renaming as a tif made it readable where it had not been previously.

So, perhaps there's a problem in the workflow.
Checking mine, in the Save Image widget I have selected (or left the default) of Unchanged for output file type.
The input file type is jpeg so unchanged means that the output file type should also be jpeg. Right?
Well we now know that it's a tiff file but with a jpeg extension.

Mike.

[gio]

Hello Mike,

I just tested again - you are right. If the output file type is left to "unchanged", the resulting file is written as tiff, but with the extension of the original file.
If the output file type is set to JPEG(or PNG) ... the file is really a JPEG (or an PNG) with the correct format and the right extension.

So this seems to be an error in the "Rename/File Save"-widget.

Edited: I just tested again: this occurs only, when there are breakpoints in the workflow. Without breakpoints the resulting JPEG-Image is "really" a Jpeg.

gio

[MikeG]

Gio,

Thanks very much for your help with this.
Perhaps the moral of the story in never to use 'unchanged' but always to select the output file type desired as 'standard practice'.

Mike.