Jeffrey’s “System Info” Lightroom Plugin

This Lightroom plugin shows (in the Plugin Manager) some data about Lightroom and the machine it is installed on. An example display is shown below.

A plugin developer may ask a user to send a screenshot of the data as part of debugging an issue. It can also be used to check your system clock (by comparing it against the clock on my server), and to explore the various Lightroom preset folders.

This plugin works in Lightroom 6/CC (and older versions as far back as Lightroom 3, though some features depend on the version of Lightroom).

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

It's free.

Note: as of version 20141019.22, on Windows systems the plugin checks for the POODLE security vulnerability, and if found, offers to fix your system.

Here's an example of the information it shows:

Version History
( Update Log via RSS )

20150427.27 Update for LrCC/6
20150206.26

In the POODLE-vunerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.

20150131.25 Broke out the Lightroom cache into its constituent subfolders
20141220.24 The list of plugin paths could have repeats
20141120.23

Added the ability to calculate the size of your caches (standard previews, smart previews, Lightroom app cache, and system ACR cache). Also displays the size of the catalog.

20141019.22 Windows Systems: Detect whether Lightroom is vulnerable to the "POODLE" SSL 3 vulnerability, and offer to fix it if so.
20140902.21 New build system
20140814.20 Add a line for the Lightroom preferences file. List installed plugin IDs and paths.
20140731.19 Registration fix for Lr5.6
20140729.18 Previous updates broke support on Lightroom 2
20140720.17 More Creative-Cloud support.
20140715.16

Fixed an issue with Creative-Cloud revalidation.

20140708.15

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.14 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.13 Build-system update
20140625.12 Fix a silly bug introduced in the previous build.
20140624.10 Create a plugin log with much of the data shown
20140422.9 Fixed a bug in the serial-number display
20140417.8 Fixed a crash that happens on some European systems.
20140417.7 Added the count of catalog items. Better Creative-Cloud support. System numeric format. Various cleanup.
20140410.6 Now shows details of your local preset folders
20140410.5 Now displays your Lightroom serial number
20140204.4 Added info about the system's display sizes, and the application window size.
20130524.3 Apparently, a recent change broke things on Lr2, which some folks apparently still use.
20130425.2 Added support for some of my personal build-system stuff
20130416.1 initial release

All 5 comments so far, oldest first...

Hi Jeffrey. I’m hailing from Canada.

I’m interested in trying my hand at writing a Lightroom plugin and thought you might be able to help me get started, or potentially stop me from wasting a lot of time. The idea I have in mind includes capturing new keyboard shortcuts do performing actions based on them. For example, capturing ctrl-alt-e and adjusting exposure.

I know that it is possible to access many of the capabilities of Lightroom from Lua, but is it possible to capture keyboard presses and respond to them from a plugin?

Thanks.

The short answer is “no”. The long answer is “no, not possible”. I wish it were, because I’d love to remap some things beyond what OSX lets me. There might be ways with the OS to intercept input before it gets to Lightroom, but I’m not familiar with them. —Jeffrey

— comment by Gerald on December 31st, 2013 at 10:32am JST (3 years, 4 months ago) comment permalink

Jeffrey,

after installing the latest Version I receive a

Plug-in error log for plug-in at: C:\Users\kw513143\Documents\Adobe\Lightroom\Zusatzmodule\sysinfo-jfriedl.lrplugin

**** Error 1

Beim Ausführen eines Skripts des Zusatzmoduls ist ein Fehler aufgetreten.
AFTER_C:29: attempt to call a nil value

Sorry about that; I’ve just pushed a fix. —Jeffrey

— comment by Klaus on June 24th, 2014 at 3:29pm JST (2 years, 10 months ago) comment permalink

****My System Info plugin can show your serial number; shift-click on the “keep private” note to bring up a dialog where you can copy the serial number to your clipboard, which you can then paste into an email.***

Well, it seems you don’t really know your own Plugin? 😛 🙂 Because there is neither a part of “keep private” in your plugin, nor is there anywhere a part with the tag “keep private”. I checked System Information as well as your own plugin. In System Information it is not fully shown (last numbers are ****) and in your Plugin there is nothing except the Hash of the Serial. And no chance to copy it, as there is nothing to click on.

To be honest the most confusing manual I have seen. I guess nobody would find this “keep private” thing.

How Adobe stores the info has changed over time, and the serial number is simply not available to the plugin in many cases. If the plugin can’t figure it out, it of course won’t show it. —Jeffrey

— comment by Chris on July 15th, 2015 at 12:46am JST (1 year, 9 months ago) comment permalink

Dear Jeffrey, I’m writing from Germany.
This plugin reports at field “OS” a value of “Windows” or “OSX”. How does the plugin detect this value? Up to now I couldn’t find a suitable way to determine this string.

Lightroom’s plugin infrastructure makes this info available to plugins, both by the global WIN_ENV and MAC_ENV globals, and also via the LrSystemInfo namespace. —Jeffrey

— comment by Eckhard Henkel on February 17th, 2016 at 2:16am JST (1 year, 2 months ago) comment permalink

Jeffrey, thanks a lot!

E.g. “LrSystemInfo:osVersion()” has different outputs at Windows and at OSX. A sample return value at Windows is “Windows 10”, the same call at OSX returns “10.11.3” (without “OS X”).

Your hint to the both boolean globals is exactly, what I was looking for. With your help I could find them documented at LR SDK programmers guide. –Eckhard

— comment by Eckhard Henkel on February 18th, 2016 at 12:38am JST (1 year, 2 months ago) comment permalink
Leave a comment...


All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.


You can use basic HTML; be sure to close tags properly.

Subscribe without commenting