robcole.com Forum
March 28, 2024, 07:00:06 pm
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to SMF For Free
 
   Home   Help Search Gallery Staff List Login Register  
Pages: 1 ... 3 4 [5] 6 7 ... 10
 41 
 on: September 10, 2014, 04:38:59 am 
Started by oajungen - Last post by oajungen
If I am correct you can download the file with the URL below.

https://www.dropbox.com/s/f0atxs66q1e1fn6/JPG.rar?dl=0

Please let me know if you have been able to do so. I will remove the file when done.

 42 
 on: September 10, 2014, 03:50:46 am 
Started by oajungen - Last post by areohbee
Probably too big for email attachment, so better to use a big file sending service, like copy.com or dropbox or yousendit - your choice..

 43 
 on: September 10, 2014, 02:54:48 am 
Started by oajungen - Last post by oajungen
Hmm - ExifMeta is not a smart plugin. What I mean, is *all* data is handled generically (it has no model-type smarts..).

So if you're getting funny metadata values, I'm guessing those funny metadata values are just what's in the file..

That said, in a fairly recent version I did add custom metadata decoding, and so that could be used for special model-specific handling, e.g. to support funny D810 values.

Either that or I'm wrong, and there's a bug in ExifMeta, but step 1 is to check what's really in the 810 file using exiftool, if you know how. If you don't know how then send me a sample file and I'll check it out.

Rob

Hi Rob,
Thank you for the prompt reply. I will sent you a file with some explanation about which changes made to the picture controles, so you can check it yourself. I hope it is a bug or something else you can change because at this moment I really can't make any clue about which values are changed. So looking into the dark unfortunately.

Do you have a preferred way of me sending you the file?

One other thing I just noticed is the auto update function with the 5.7 version is taking around 2% cpu time constantly and my laptop isn't going into sleep mode fully anymore. I noticed because my laptop was very warm this morning when I removed it from the charger, normally it is cold. When I disable the auto update function it is solved and cpu usage is back to zero. Not sure if the update caused the sleep mode issue, but it is constantly taking cpu time. Meaby you could look into this also?

Regards,
Olaf.

 44 
 on: September 09, 2014, 05:36:15 pm 
Started by oajungen - Last post by areohbee
Hmm - ExifMeta is not a smart plugin. What I mean, is *all* data is handled generically (it has no model-type smarts..).

So if you're getting funny metadata values, I'm guessing those funny metadata values are just what's in the file..

That said, in a fairly recent version I did add custom metadata decoding, and so that could be used for special model-specific handling, e.g. to support funny D810 values.

Either that or I'm wrong, and there's a bug in ExifMeta, but step 1 is to check what's really in the 810 file using exiftool, if you know how. If you don't know how then send me a sample file and I'll check it out.

Rob

 45 
 on: September 09, 2014, 01:01:41 pm 
Started by oajungen - Last post by oajungen
Hi,
I have replaced my Nikon D800 with a D810 a little while ago.
For the D800 I was using this tool together with metadata-presets-jfriedl.lrplugin to display several values like white balance and the picture control settings like picture controle name, sharpness, contrast, brightness, saturation and hue. With the D800 this was working perfect. I was able to read the (jpg) corrections I made in the camera with the picture control settings. Values I got looked like: normal, -1 or +1 depending on the correction I made. It was working perfectly!

With the D810 this isn't working anymore. I am getting really strange values like -124 for brightness and hue. Even more strange when I change sharpness on the camera the exif data of contrast is changed when I use this tool. The D810 is the first camera which uses picture control 2.0 (with addition of an extra slider for Clarity). Does it mean this tool isn't compliant with the D810 yet? Any idea how I can solve this issue or when this tool will be compliant with the D810 / picture control 2.0?

If I can help you with testing or something else to make this work, please let me know!

Kind regards,
Olaf.

 46 
 on: August 30, 2014, 03:26:08 am 
Started by John - Last post by areohbee
Thanks John!  Smiley

 47 
 on: August 30, 2014, 03:25:05 am 
Started by photof2as - Last post by areohbee
Consider using the new plugin by Chris Reimold for focus points, if your camera is supported (@now: Nikon & Canon):

http://www.lightroomfocuspointsplugin.com/


 48 
 on: August 30, 2014, 03:21:16 am 
Started by John - Last post by areohbee
Sorry all for being so late to the party - this should be fixed now in latest version (5.6.2) of ExifMeta.

 49 
 on: August 30, 2014, 03:17:21 am 
Started by John - Last post by areohbee
HI John,

Sorry for the delay - I can't seem to convince this forum to notify me of new posts (argh..).

The exiftool built-in with ExifMeta won't overwrite versions of exiftool that you've installed - it comes in the .lrplugin folder, like other plugin files..

PS - @v5.6.2, ExifMeta will auto-select the built-in version on Mac if path to executable in plugin manager is blank.

Rob


 50 
 on: March 15, 2014, 12:42:32 pm 
Started by John - Last post by kleinjn
Same Problem for me: ExifMeta.lrplugin is greyed out in the 'Choose' Box

Pages: 1 ... 3 4 [5] 6 7 ... 10
Bookmark this site! | Upgrade This Forum
SMF For Free - Create your own Forum

Powered by SMF | SMF © 2016, Simple Machines
Privacy Policy