Incorrect flash info

[Coops]

If you look through the entries on my site (www.d70s.co.uk/blog), many of the entries state that the flash was fired when in fact in most instances it was not!! Any ideas what may cause this? Could it be anything to do with the way i save things in photoshop affecting the exif data or is it a pp issue?

Host Information
PHP-version 4.3.10 (Pixelpost's min requirement: PHP version 4.3.0)
MySQL version 3.23.54 (Pixelpost's min requirement: MySQL 3.23.58)

GD-lib bundled (2.0.28 compatible) with JPEG support

Server software Apache/1.3.27 (Unix) PHP/4.3.10 mod_perl/1.26 FrontPage/5.0.2.2510

EXIF Pixelpost is using exifer v1.5 for EXIF information.

Many thanks!

[blinking8s]

what kind of camera do you have? the biggest pain in the ass is that all the different camera companies like to write this data their own way, and often change it between models too...it's so hard to get down perfect.

[Joe[y]]

what kind of camera do you have?


pretty clear it's a D70s by the domain name! :p hehe



have a look here: http://forum.pixelpost.org/showthread.php?t=2279

nikon ain't all that great when it comes to exif!

[blinking8s]

haha...yeah, now more getting on the forum after my morning classes!

[raminia]

again a Nikon issue!

[Coops]

Cheers guys! It is indeed a D70s, looks like it's a Nikon thing! Everything else seems to be ok, just the flash from time to time! Oh well, not the end of the world!

[raminia]

PP uses Exifer for exif info, email writer of Exifer script. visit their site maybe there is a newer version of EXIFER available.
http://www.jakeo.com/software/exif/index.php

[Joe[y]]

PP uses Exifer for exif info, email writer of Exifer script. visit their site maybe there is a newer version of EXIFER available.
http://www.jakeo.com/software/exif/index.php

there is not.

but i don't think it can keep up with nikon.

[blinking8s]

i havent looked at exifers code in forever, but i swear there was a 1 and 0 setting for the flash ebing fired in something we used to use, if that was just swapped around then it would read correctly. or something...err...im going to class now

[Joe[y]]

i havent looked at exifers code in forever, but i swear there was a 1 and 0 setting for the flash ebing fired in something we used to use, if that was just swapped around then it would read correctly. or something...err...im going to class now

perhaps - but i don't think this is the case for EVERY photo and if it is then it is only for the nikon

[blinking8s]

yeah, but if they only shoot with a nikon d70, then there might be a way to hack it to work with JUST it...

i havent had a chance to look at the exifer code in a long time, so i am not sure

[Coops]

Thanks for the chat guys. As Joe[y] noted, it is not the case for every photo, just the majority of them! For the time being i've just removed the flash info, less confusion that way!

[luminist]

This problem isn't specific to Nikon; it's happened with my Canon 20D.

I'll test this more, but so far the only two RAW files it's happened with are the two that I've processed with C1 Pro (I normally use CS), although Exifer 2.1.5 for Windows reads the flash data in the resulting JPG correctly.

It seems strange that the standalone version of Exifer would give a different result than Pixelpost, but given the difference in processing tools I'm suspicious...

[phild]

This thread is still open for an answer ! Same problem with Nikon D200. If anyone has found a solution since the last post, I'd be happy to know it…
(apart from deleting the <EXIF_FLASH> line in the template…)

[Connie]

It seems strange that the standalone version of Exifer would give a different result than Pixelpost, but given the difference in processing tools I'm suspicious...

it is not Pixelpost, it is EXIFER 1.5
so maybe you will find some help at their website?
PP includes the routines but it is not Pixelpost

[Joe[y]]

unfortunately exifer is currently out of development which is probably the main reason right now. i'm looking into solutions - although, this may mean a new script.

[dhdesign]

I'm having the same issue as the original poster, but probably for a different reason.

I have images taken with 2 different cameras (HP 315 and Finepix S5000). Images from both show the proper flash state (fired or not fired) with the original exif data intact when uploaded to PP.

However, when I edit the properties on the image to add in the author and some comments regarding copyright information (right-click--Properties--edit fields--click Apply, then OK) and then upload them, all of the images show the flash state as "fired", whether it really was or not.

In looking at exif.php, there are 2 cases in the code, onefor MakerNote (I presume author) and one for UserComments. The code is as follows:

case "927c": $tag = "MakerNote";break; //a bunch of data
case "9286": $tag = "UserComment";break; //text string

There is nothing in the rest of the exif.php code to process that information, as I cannot find any lines with those tags in them. I'm not a programmer, and have no clue how to go through exif.php to fix this.

I know that this is not a Pixelpost program issue, as exifer 1.5 is an external process include within PP, so I am not expecting any of the devs to address this issue.

I did, however, want to bring it to everyone's attention as a possible cause for this problem, in case anyone else was having it and wondering why.