safx / lightroomplugin-clarifaitagger Goto Github PK

The documentation has had some edits to improve the English and readability. This can be further improved on to also provide:

• updated screenshots of the settings (Lightroom's Plugin Manager panel),
• discussion of the new options provided there
• updated screenshots of the tagging dialog
• discussion of how the new features affect what you see there (e.g. ancestor paths tooltips seen when hovering over a keyword that already exists in the Lr Catalog).

Works on Mac without problem.
On Windows I get an error message:
An internal error has occurred: [string "JSON.lua"]:383: nil passed to JSON:decode()

I never can dexecute plugin. Thre is the file Debug.lua missing.

Error as follows:

Hello LowellMontgomery,

I was happy to found your Plugin, but unfortunately due to the new API Key methode I am not able to get it started. It would be very nice if you could update your plugin for this new methode!

Thank you very much!

Right now, this plugin only really works for a flat-level set of keywords. It would be great if we could find—and allow to select, instead—any term that matches from within the hierarchy, maybe even with synonym matching.

The downside to this idea is that it (obviously) would take a lot more processing, so that would mean more time before the selection dialog would show up, but this could save a lot of tedious keyword-merging work for people who have a long list with hierarchy.

Anyway, I'm creating this "issue" because I'd like to see if I can improve this behavior and/or collaborate on what UI changes this might imply. I'll be experimenting on a new branch in my fork of this cool project.

When I export tags added by this plugin, they don't show up in the available "include on export" list.

Since yesterday I get the error 85 what does that mean and how can I fix it.

Sometimes you want to be aggressive with your tagging strategy. This would be a nice option to enable if you are interested in starting with everything clicked and want to take the irrelevant tags away.

Currently, we have a hard-coded size for the thumbnails shown above columns (and the column widths), as well as for the size of the tagging window, which is fairly small.

We can set defaults to be the same as the current hard-coded settings, and extend the preference panel to allow the dimensions to be set to a nice range of values.

In the feature branch I create for this issue, I will also extend the range of the images sent to Clarifai, since larger images generally provide better detail and result in better tagging results. The images will now be 400 – 2000px in size (vs formerly 224 – 1024). This should be a more reasonable range and 600px is probably a more logical default than the 400px (former default, which was quite small and resulted in many more tagging errors).