Floating point overflow reported with CR2 files. JPG and DNG ok.

[MOL]

There were occasional reports in the past:

http://tech.dir.groups.yahoo.com/group/CanonSDK/message/1677


Uwe

[Phil Harvey]

Thanks  Uwe.  This indicates the problem could be the Canon DLL, not ExifTool, which makes more sense.  Can you un-install the Canon DLL?  Other people have had different problems with this DLL.

- Phil

[MOL]

The DPPDLL.dll is responsible for remotely controlling your camera, AFAIK. If you don't need that, you can safely stop the running service (or maybe remove the file alltogether). As the library is part of the Canon Digital Photo Professional application, I would rather suggest to simply uninstall the program and reinstall the latest version. That should fix the problem.

Uwe

[l_d_allan]

I do use EOS Utility for remote control (tethering), so I'm reluctant to remove dppdll.dll

I did look at file time-stamps for existing dppdll.dll files on my desktop and laptop. And ... there was a variety.

I updated to the latest DppProfessional 3.11.26 (2012-4-17) and RAWCodec 1.90 (2011-4-15) on both the desktop and laptop. But ... that didn't make any difference. The desktop still has the same "floating point overflow" problem with .cr2 files, while the laptop remains ok with .cr2 files.

Bummer ... anything else I can try?

But also I want to thank both developers (ExifTool and Gui) for making the utilities available and maintaining them.

[Phil Harvey]

Could you try removing the DLL to verify that this is the source of the problem?

- Phil

[BogdanH]

Hi,
I can't imagine DPPDLL.dll file causes that. I mean, this file is used only as long particular Canon software (i.e. Canon DPP) is running -otherwise, this file simply "doesn't exist".
On the other hand... I don't use Canon raw codec, but I think Canon raw codec could use this dll too. Is there a way to "disable" Canon raw codec (without uninstalling it)?
I have another idea... try to rename extension of "problematic" CR2 file; for example, change it from CR2 to CRx. And then run ExifToolGUI and try to modify metadata inside that CRx file.

Bogdan

[Phil Harvey]

Good idea!  (renaming to CRx)

[l_d_allan]

I was able to rename from .cr2 --> .crx and ExifToolGui worked fine.

I'm unclear what that means ... more or less likely that dppdll.dll is the problem?

BTW, I then renamed from .crx back to .cr2, and ExifToolGui could open it ok.

Also, the RAWCodec from Canon did indicate it was for Win-7-32, and was silent about Win-7-64.

HTH ...

[BogdanH]

Hi,
I totaly forgot the fact, that Canon raw codec exist for 32bit Windows only! For normal applications, this doesn't make much difference, but codec is so called "system" app (similar to driver). My advice is, uninstall it and get either:
MS raw codec - http://www.microsoft.com/en-us/download/details.aspx?id=26829 (free), or
FastPictureViewer CodecPack - http://www.fastpictureviewer.com/codecs/ ($15).

I'm confident, that this will solve your problem.

Bogdan

[l_d_allan]

I un-installed the 1.9.x CodecRaw from Canon (32-bit) and installed the CodecPack from Microsoft that you helpfully provided a link to. Rebooted.

Problem with "floating point overflow" still exists on the desktop. Drat.

(Note: this problem is of somewhat academic interest to me, since I immediatly convert the .cr2 files to .dng's and proceed with .dng's. It only became visible because I wanted to "tell" the .cr2's from the manual Samyang about the f-stop "earlier" in the tool chain.)

[BogdanH]

The idea to change extension from CR2 to CRx confirms, that there must be some app on your PC which "monitors" CR2 files. I thought this might be Canon raw codec, but obviously some other app does that. Because I don't use the same apps (and settings) as you do, I can hardly guess the solution. There are tools which can tell what app "owns" particular files, but as you said:
I understand that in your case the problem is "academic", but if that would happen here, I wouldn't sleep until resolved  .

Bogdan

[l_d_allan]

Is this the kind of thing that SysProc from SysInternals can report? I'm aware of that tool, but haven't used if for 5 to 10+ years, and never really was that aware of what it was doing.

Again, my interest is "academic" since .cr2's are involved rather than .dng's, but I am curious, and would like to be a "good citizen" as an expression of appreciation for the time and effort you have put into ExifToolGUI (and also the developer of ExifTool itself).

[BogdanH]

Hi allan,

It's been a while since I needed/used such tool, so I can't recall the app's name right now. I think, you can find such app by entering "who is the owner of the file" or "file unlock" (or similar) in Google. Just for info: in my case, it were avi-video files I had trouble with -in some cases, I couldn't rename or delete them.
Anyway, all this can be tricky and time consuming.

Bogdan