|
#11
|
||||
|
||||
|
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
__________________
i should say more clever stuff |
|
#12
|
||||
|
||||
|
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!
__________________
www.frozenlife.co.uk/blog/ |
|
#13
|
|||
|
|||
|
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... Last edited by luminist; 12-30-2005 at 02:26 PM. |
|
#14
|
||||
|
||||
|
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…)
__________________
Traducteur de Pixelpost en français. Si vous utilisez les templates par défaut, téléchargez leur version française dans l'espace templates. photofloue.net : un blog en français sur les photoblogs et la photo photoblog work in progress | portfolio |
|
#15
|
|||
|
|||
|
Quote:
so maybe you will find some help at their website? PP includes the routines but it is not Pixelpost |
|
#16
|
||||
|
||||
|
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.
__________________
Affordable Website Design in North Wales |
|
#17
|
||||
|
||||
|
Having the same issue as OP
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: Code:
case "927c": $tag = "MakerNote";break; //a bunch of data case "9286": $tag = "UserComment";break; //text string 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. |
| Post Reply |
| Thread Tools | |
|
|