safx / lightroomplugin-clarifaitagger Goto Github PK

View Code? Open in Web Editor NEW

42.0 6.0 15.0 1.75 MB

A Lightroom plugin suggests keywords of photo for you

License: MIT License

Lua 100.00%

clarifai lightroom-plugin

lightroomplugin-clarifaitagger's Introduction

LightroomPlugin-ClarifaiTagger

This Lightroom plugin helps you to add keywords to your photos, powered by the Clarifai, visual recognition service.

works with JPEG and Raw files
works on Windows and Mac OS X (not yet tested on Windows)

Create a Developer Account on Clarifai.com

To use ClarifaiTagger, you must first create a developer account on Clarifai and create an application.

Go to Clarifai and create a developer accout.
Click "Create an application" from Applications → Create a new Application.
Once you create your application, the Client ID and Client Secret are provided.

Installation & Setup

To install ClarifaiTagger, follow these steps:

Clone or download this project.
Open "Lightroom Plug-in Manager" from Lightroom menu → File → Plug-in Manager...
Click "Add" and select the ClarifaiTagger.lrdevplugin.

Or, simply put the ClarifaiTagger.lrdevplugin in its standard location as follows:
- Mac OS X (current user only): ~/Library/Application Support/Adobe/Lightroom/Modules
- Mac OS X (for all users): /Library/Application Support/Adobe/Lightroom/Modules
- Windows: C:\Users\username\AppData\Roaming\Adobe\Lightroom\Modules
Fill the Client ID and Client Secret fields with the values provided by clarifai.com for the application you've created.

How to use

Select the photos for which you want to add keywords. You may select up to 128 photos (the maximum supported by Clarifai).
Choose Request keyword suggestions from Clarifai from Lightroom’s Library → Plugin-Extras menu.
After a few seconds, the Clarifai Tagger window should pop up with the keywords suggested by Clarifai for each selected image.
Check keywords you want to add.
Click "Save" to apply changes, or "Cancel" otherwise.

Preferences

Tagging

Show Existing Keywords as Bold: uses bold face for keywords which are already in the catalog's keyword list
Automatically Select Existing Keywords: automatically selects the checkboxes for keywords which are already in the catalog's keyword list
Show Probability: Display each keyword's rated probability

Image Settings

Image Size: sets the size of thumbnail images sent to Clarifai
Keyword Language: determines the language of keywords received from Clarifai. By default, it's the language you configured as default for your application (on clarifai.com), however you can change this setting in the plugin preferences to receive keywords in some other language, if you desire.

lightroomplugin-clarifaitagger's People

Contributors

Stargazers

Watchers

Forkers

lowellmontgomery axelstahlhut moderatecontent planificats seidchr janroz digideskio aaverin circuit-killer takis2017 matthewmcd sanwal-clarifai brendt-napp sillyroot

lightroomplugin-clarifaitagger's Issues

Windows Version Error

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()

Tags are not marked to export

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

Improve functionality for hierarchical keyword sets

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.

Create new options for column/thumbnail (Tagger Dialog) and dialog window dimensions

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).

Error 85

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

Update documentation to cover new settings/fields

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).

API Keys have replaced Access Tokens/Client ID & Secret

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!

Select all button

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.

Plugiin not executable, what abiout Debug.lua

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

Error as follows: