No prob 

Thanks.

I'm not sure how it got into the whacky state - it seems like you attempted to do an update without these steps preceding:

* commit
* reload.

If you did those steps, then it's gotten into a funky way somehow. If you did not, then that's the problem.

Commit re-writes plugin files based on changed preferences, and those changed plugin files need to be reloaded - that's pretty-much how it works.

It shouldn't become disabled though, which is a concern to me. Anyway, if you do configure, commit, reload, and update, and still have a problem, one way to start over is to clear preferences and reload - to do so, enable advanced debugging (debug section) and reload - you'll see a button 'Clear Prefs' (preset manager section) - click it and choose to clear all prefs, then reload the plugin. At that point you can re-set-up armed with your new knowledge and hopefully have better luck.

PS - Regarding the disabling should it continue - the diagnostic info is not quite what I need to see (not your fault, it's a bit complicated..), save diagnostic info as before (if present when plugin disabled), then click the reload button again, and if still disabled and diagnostic info present, re-save with a different filename and send me both - sorry for the hassle..

Also, please enable verbose logging until this problem is resolved (top section of plugin manager), that way when you send it next time it'll have more useful info in it. But best not to update too many files before sending it, or else it will be huge! - thanks. Posting here or sending direct to me - either is fine.

Rob

If the plugin and auto-update are enabled, when you delete the 'ExifMeta Updated' time field, it should force an update, and the date should be repopulated with the current time.

There are two ways data may be updated:
1. Automatically (as referred to above).
2. Manually - using the update function of the file menu.

If data isn't being updated automatically, then you have to do it manually.

But if you only have headers and no field labels (with field values), then no fields are enabled/committed. It's sounding like when you commit there is a problem. I believe my previous post had trouble-shooting instructions - to reiterate: if plugin stays enabled, then send me the verbose log file after doing a commit, followed by an update (either automatic or manual); if plugin not staying enabled, then after being disabled I need to see the plugin author's diagnostic (saved in a file).

See sticky topic '01 Download ExifMeta' in this forum.

Well, a lot of things are as they should be, but the plugin should never become disabled (unless you disable it).

Put another way: Deselecting the auto-update (most-selected photo) will and should cause auto-updating to stop (I am aware it's slightly odd: think of enabling most-selected photo as "enabling auto-updating, period (and no point in having it enabled, if you aren't going to at least be updating a minimum number of photos - the most-selected photo is that minimum). - I will invent a clearer way to show it in the UI - thanks.

If fields in right panel aren't populated, then (presumably) it's because the metadata does not exist, or the photo has not been updated since those fields were enabled. Consider deleting the 'ExifMeta Updated' date, to see if it gets auto-updated (it should, if enabled), or run a manual update. If you do the update, and the metadata exists, and the fields are still not populated, then there is a bug.

PS - I assume by "rc Metadata" you mean the "RC Standard" metadata viewing preset.

But really, all bets are off if the plugin is not staying enabled. To trouble-shoot, when it "auto-disables itself" save the diagnostic info to a text file - plugin author section (NOT the plugin log file).

If you are able to keep it enabled, then it will be time to see if problem is due to operator misunderstanding or bug - to trouble-shoot: enable verbose logging (top section plugin manager), then run a manual update, then inspect and/or send me the verbose log file.

PS - ExifMeta does not use keyboard stuffing, so problem is probably not due to assistive device permissions etc.

Hi SCC,

Have you tried enabling ExifMeta (Status section of plugin manager).

The log file did not have much in it - were there diagnostics mentioned (in plugin author tools section).

I'm still working on the "assistive devices" stuff, but that stuff not required for ExifMeta functionality.

I don't think the problem is exiftool configuration, yet, or at least there was no indication that anything had yet been tried which uses exiftool.

I know some people are using ExifMeta in Mavericks, so there is hope..

Rob

Thanks BillaVista,

I wonder if Lincoln ever got has data..

PS - exiftool is included for Mac users too now  .

Rob

If I had all the data (which raw settings should display which user-friendly text strings..), I could put together a preset in short order, but I don't have a D810 to experiment with.

Bottom line: if you come up with the requisite info (by experimentation or from Nikon support..), I'll roll it into a preset for you, if that would be a sticking point..

Not sure what else to say..

~R.

You're welcome.

I certainly recommend shooting raw if that helps - Lightroom does a mighty fine job with D810 raws (now that the color/profile issues are resolved - knock on wood).

Anyway, I have no additional ideas, other than the one presented in previous post..

Good luck,
Rob

Got the files - thanks, but you're probably not going to like what I have to say next 

The values you're seeing (I'm seeing anyway) are just how they are in the file. ExifMeta does not decode metadata on a model-by-model basis, it just shows you the "internal" (raw format) values. If you want to come up with something more friendly, you have to do it yourself by editing the getNameAndValue function in advanced settings.

Let me know if you decide it's worth rolling up your sleeves and I'll try to help.

PS - Regarding cpu consumption - yes: auto-update will consume some cpu, more or less depending on ExifMeta general settings and whether photos need updating or are already updated. I up-throttled the rate in v5.7 so freshly imported photos would have exif-metadata at the ready more quickly, perhaps I should have made it configurable - under consideration..

Cheers (if possible),
Rob

Probably too big for email attachment, so better to use a big file sending service, like copy.com or dropbox or yousendit - your choice..

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

Thanks John! 

Consider using the new plugin by Chris Reimold for focus points, if your camera is supported (@now: Nikon & Canon):

http://www.lightroomfocuspointsplugin.com/

Sorry all for being so late to the party - this should be fixed now in latest version (5.6.2) of ExifMeta.