Strange imageWrite() Behaviour on Specific JPG files

Hi BKBK,

I tried your example, and yes, it does indeed seem to work. This is very strange. I would argue that it's probably down to my coding ability, and that I may be doing something very wrong...on the other hand though, if this works for every other image not taken by this camera, then how can it? I'm at my wits end with this...I have tried every combination possible.

Hmm. Because my code is long and complex I wouldn't want to post it all here but I will copy and paste below the main part giving me grief. If you or anyone else can see problems with this it would be greatly appreciated.

As I said earlier, this code works, but not with these images. There's something else at play here.

Code
-----------------------------

<cfset myImage = ImageNew(variables.imagePath) />
<cfset imageSetAntialiasing(myImage,"on") />

<cfif val(arguments.imageWidth) and val(arguments.imageHeight) gt 0>
<cfset imageResize(myImage,val(arguments.imageWidth),val(arguments.imageHeight),"lanczos",1) />
<cfelseif val(arguments.imageWidth) gt 0 and val(arguments.imageHeight) lte 0>
<cfset imageResize(myImage,val(arguments.imageWidth),"","lanczos",1) />
<cfelseif val(arguments.imageWidth) lte 0 and val(arguments.imageHeight) gt 0>
<cfset imageResize(myImage,"",val(arguments.imageHeight),"lanczos",1) />
</cfif>

<!--- This is the line that errors, indeed any line that uses cfimage to write or imageWrite. I changed it to a tag recently to see if it made any difference --->
<cfimage action="write" destination="#variables.imagePath#" source="#myImage#" quality="#val(arguments.imageQuality)#" overwrite="true" />

<cfif val(arguments.imageBlur) neq 0>
<cfset imageBlur(myImage,val(arguments.imageBlur)) />
</cfif>

<cfset imageRotate(myImage,val(arguments.imageRotate)) />

<cfif arguments.imageGreyscale eq "yes">
<cfset imageGrayscale(myImage) />
</cfif>

<cfif trim(arguments.imageFormat) neq "">

<cfset variables.newFormat = uploadImage.serverDirectory & "\" & uploadImage.clientFileName & "." & arguments.imageFormat />

<cfimage action="write" source="#myImage#" destination="#variables.newFormat#" overwrite="yes" />
<cfimage action="read" source="#variables.newFormat#" name="getUploadedImage" />

<cfif fileExists(variables.imagePath) eq "yes">
<cffile action="delete" file="#variables.imagePath#" />
</cfif>

<cfelse>

<cfimage action="write" source="#myImage#" destination="#variables.imagePath#" overwrite="yes" />
<cfimage action="read" source="#variables.imagePath#" name="getUploadedImage" />

</cfif>


Mikey.

I wrote:
Looks like a case of vendor-locking. Do you happen to have an Olympus camera? And how did I know?

Download EditPad Lite. It is free. Use it to open both files, that is, to display the binary content as characters. Search for Olympus. You will find that there are numerous occurrences of the text 'Olympus Digital Camera' in the file that has been giving you problems. Is that a coincidence, I wonder.

But, then again, I thought it's very unlikely that a reputable vendor like Olympus would take the risk to frustrate users. So, let's start with the hypothesis that the error isn't caused by vendor-locking.

I ran the following code as a proof of concept:
<cfset kapitaine_friend = ImageNew(" http://www.unibands.co.uk/P6190172.jpg")>
<!--- <cfset kapitaine_friend = ImageNew(" http://www.unibands.co.uk/newP6190172.jpg")> --->
<!--- Convert image from JPG to PNG format. --->
<cfset ImageWrite(kapitaine_friend,"kapitaine_friend.png")>
<!--- Display PNG image. --->
<img src="kapitaine_friend.png">

There were no problems with P6190172.jpg or with newP6190172.jpg. It seems to rule out Coldfusion as culprit.

Take another look at the error-message, java.io.FileNotFoundException: C:\ColdFusion8\wwwroot\cms\skylitecms\cmsFiles\P61901721.JPG (The system cannot find the file specified). It could be a simple case of case-sensitivity. Have you tested it with lower-case extension, that is, P61901721.jpg?

Can you put a simple reproduceable case here (ie: some code). I can make
sure it gets in front of the appropriate people.

--
Adam

Looks like a case of vendor-locking. Do you happen to have an Olympus camera? And how did I know?

Download EditPad Lite. It is free. Use it to open both files, that is, to display the binary content as characters. Search for Olympus. You will find that there are numerous occurrences of the text 'Olympus Digital Camera' in the file that has been giving you problems. Is that a coincidence, I wonder.