Pixelpost

Authentic Photoblog Flavour


Go Back   Pixelpost Forum > MISCELLANEOUS > Archives > Bug Report 1.4.x

Post Reply
 
Thread Tools
  #11  
Old 10-06-2005, 05:35 AM
blinking8s's Avatar
blinking8s+ Offline
über loafer
 
Join Date: Oct 2004
Location: Bowling Green, Ky
Posts: 3,428
Send a message via ICQ to blinking8s Send a message via AIM to blinking8s Send a message via MSN to blinking8s Send a message via Skype™ to 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
__________________
i should say more clever stuff
Reply With Quote
  #12  
Old 10-06-2005, 10:12 AM
Coops's Avatar
Coops Offline
forum loafer
 
Join Date: Sep 2005
Location: London
Posts: 11
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/
Reply With Quote
  #13  
Old 12-29-2005, 09:51 PM
luminist Offline
forum loafer
 
Join Date: Jun 2005
Posts: 3
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.
Reply With Quote
  #14  
Old 05-12-2006, 09:47 AM
phild's Avatar
phild Offline
pp veteran
 
Join Date: Oct 2005
Location: from paris with love
Posts: 85
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
Reply With Quote
  #15  
Old 05-12-2006, 10:29 AM
Connie
Guest
 
Posts: n/a
Talking

Quote:
Originally Posted by luminist
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
Reply With Quote
  #16  
Old 05-12-2006, 04:02 PM
Joe[y]'s Avatar
Joe[y]+ Offline
Team Pixelpost
 
Join Date: Mar 2005
Location: UK
Posts: 3,101
Send a message via MSN to 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.
Reply With Quote
  #17  
Old 03-25-2007, 02:21 AM
dhdesign's Avatar
dhdesign Offline
pixelpost guru
 
Join Date: Mar 2007
Location: Ohio
Posts: 431
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
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.
Reply With Quote
Post Reply


Thread Tools




All times are GMT. The time now is 06:12 AM.

Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd. | Style Design: d3 designs