Official

Accepted

Unanswered

Advanced Filters

Search Results (193)

Relevance

Closed

Lightroom: make baseline sharpness and color noise reduction for raws be 0 (so all raw baselines are same as for rgb files) + bonus idea..

It's really great that raws and jpegs have the same baseline settings now (since PV2012), well, except for sharpness and color noise reduction. No more dealing with brightness baseline of 50, and contrast 25, and blacks 5.. - yippee! I propose that raw sharpness default value be zero, and color no

Ideas

 • Lightroom Classic

14

0

1

Closed

Lightroom SDK: Ability to apply snapshots programmatically.

methods to apply snapshots would be appreciated. as it stands, we can create them, but then there is no way for a plugin to do anything with them, The user can apply them to individual photos, one by one, but it would be great for a plugin to be able to apply them programmatically. For example, a

Ideas

 • Lightroom Classic

29

1

1

Closed

Lightroom SDK: photo:applyDevelopSnapshot only works in develop module

I realize this function has not been released yet for full support, but in the interest of possibly having it working upon initial release (presumably 5.1): photo:applyDevelopSnapshot() doesn't work when in library module. Unless there is a parameter needed (is there?). And since there is current

Problems

 • Lightroom Classic

12

2

Closed

Lightroom 5 SDK: catalog:getActiveSources() throws an error if called too soon during startup.

Work-around: dbgf( "getting active sources" ) local srcs for try = 1, 5 do local sts sts, srcs = LrTasks.pcall( catalog.getActiveSources, catalog ) -- assertion failed error when called upon Lr startup, hmm... dbgf( "returned from g

Problems

 • Lightroom Classic

7

2

Closed

Lightroom SDK: LrFileUtils.fileAttributes - include read-only.

Some plugins can benefit from having the status of the read-only attribute of a file - please add to LrFileUtils.fileAttributes - thanks.

Ideas

 • 

Not planned

 • Lightroom Classic

18

1

1

Closed

Lightroom SDK: plugin preferences are tied to name of plugin folder.

-previous content deleted- I figured out the cause of the problem: I've been passing _PLUGIN object to LrPrefs.prefsForPlugin instead of _PLUGIN.id (or nil). That ties the preferences to an amalgamation of the plugin object that includes the plugin path (instead of the id), so if the plugin folder

Problems

 • Lightroom Classic

32

0

Closed

Lightroom 5.2 SDK: selection change callback not called by change in most selected photo.

referring to LrDialogs.presentFloatingDialog Most plugins that care what's selected also care what's most selected. Not having a callback when most selected changes takes a lot of the fun out of it (you have to implement selection change detection by constant polling which makes the callback featur

Problems

 • Lightroom Classic

7

1

Closed

Lightroom SDK 5: Omission in documentation of LrDialogs.presentFloatingDialog

There is no mention of 'resizable' in documentation of args, yet floating dialogs can be made resizable, or not, depending on said arg.

Problems

 • Lightroom Classic

11

0

Closed

Lightroom SDK: Long delay required after adding a photo to catalog, before white balance can be changed to custom, reliably.

As it stands, if one adds a photo to the catalog in a with-do function, one must sleep for a good while before it's ok to change white-balance to custom in a subsequent with-do function. If wait is not long enough, the temperature and tint values will be wrong afterward (they will change to "unpredi

Problems

 • Lightroom Classic

11

0

Closed

Lightroom SDK: Support all data types in custom metadata

This is my #1 feature request for the Lightroom SDK Presently, custom metadata values do not have to be text, but they will be treated as text anyway in library filter & smart collections. There are four problems with this: 1. If plugin assigns a numeric value of 1.667 to some metadata field, as e

Ideas

 • Lightroom Classic

70

11

9

Closed

Lightroom SDK: complete keyword management functions

I've not thought about details in a long time, but from the top of my head, and in addition to allowing plugins to readily keep an updated table of keywords (keyword events would help in this regard, since polling the entire set for changes can be very time consuming for a plugin), functions to: -

Ideas

 • Lightroom Classic

27

3

5

Closed

Lightroom SDK: Plugin API to unlock database temporarily.

This is one of my highest hopes for the Lightroom SDK As much as I love having a nice API for reading the Lightroom catalog, sometimes a lightening-fast SQL query could return much more info much faster. My present workaround is to issue a command to kill Lightroom, then read the now unlocked Light

Ideas

 • Lightroom Classic

21

4

4

Closed

Lightroom SDK: programmatic control of dialog sections - expanded or collapsed.

Regarding plugin manager and export dialog boxes (including publish settings)... Problem: Some users are intimidated by things they don't understand, or simply have a hard time knowing which things are the most likely to need attention. I would love to have some sections open/closed upon first-run

Ideas

 • Lightroom Classic

15

0

2