Interactive debugger for Lightroom plugins

The Lua IDE "ZeroBrane" now supports interactive debugging of Lightroom plugins. This means you can set breakpoints, step through your code line by line, examine/watch your variables as you do so etc. It can be quite helpful when debugging a complex situation in a plugin, and I don't think it was previously available.
For more details see here,
http://notebook.kulchenko.com/zerobrane/debugging-lightroom-plugins-zerobrane-studio-ide
See the last screenshot for a view of the interactive debugger.
(Disclaimer: I am not affiliated with them but have worked a little with their software, and like it. Paul, the developer, is very responsive and helpful, in case you should still encounter the occasional quirk.)

I just tried it in Lightroom 5.6/Mac, and it worked well. (I don't have the latest version of ZBS installed, however.)
The only thing I see is that if you import it as local LrMobdebug, it should be "LrMobdebug.start()", not Lrmobdebug.start(), i .e. upper/lower case 'm'. (turns out this is wrong in the article too). However, LR should inform you of this when you start the plugin, with the error message "An internal error has occurred - attempt to index global Lrmobdebug (a nil value). So maybe you have caught this already.
The only real suggestion I have is to restart Lightroom, as that sometimes helps. Otherwise, I followed the steps in the article, i.e. script opened in ZBS, project directory set etc. I did not set a breakpoint as Lrmobdebug.start() already breaks itself.

Similar Messages

Looking for Lightroom Plugin Developer for a Project

We are looking for a developer who can help us create a Lightroom plugin that will allow Lightroom users to upload their photos for print to our web based print and production service. Minimal user interface required. In the first stage of the project, shopping cart including pricing and shipping information will be handled by the web system. Later stages may include advertising pricing information inside Lightroom.
For more information respond to this thread or send an email to [email protected]
Klaus Sonnenleiter
http://www.printedart.com

studiodh33,
Please see private message if you haven't already...
-Rob

Iweb 08 and SlideShow Pro 1.0.3 plugin for Lightroom 1.3.1

I have an iweb site I did last year using iweb 06 and slide show pro with the iphoto plugin and then used the slide show pro in Flash. www.mattmosher.com
That worked great just paste the html code into the exported iweb site and put the slide show folder and swf file in the folder and it worked great.
NOW
iweb 08 and slide show pro for lightroom gives you a realtime visuals of your slide show. Awesome plugin.
However when I paste the code into my html document the slide show does not show up. It also generates 2 swf files named loader and slideshow pro. Along with 2 xml files named param.xml, images.xml along with a js file swfobject.js
I really do not know how to fix the problem.
Does anyone have any knowledge on this topic???

I don't want to sound mean, but you should'nt have got any firmware updates from any other site other than Apple's or through iTunes, I'm afraid. I think that's where the problem has come from.

Downloading the LR-plugin "presets for lightroom", which I bought before.

Hi I bought the plugin "presets for lightroom", and I can't find a file or a folder in my "download-folder" for installing after with lightroom. How may I download the plugin?

Thank you. No I was expecting to have some kind of reply to my inquiry. Maybe its in the 8 - 10 day process, but I would think there would have been some kind of notification.
I'll give that I try though. Pretty frustrated experience, so I especially appreciate your help.
Joyce

Which are your favorite plugins for lightroom?

hi
just for curiosity
which are your favorite plugins for lightroom?
thanks

That's a very broad net you're casting.
I mean Flickr is flickr users favorite plugin, and those with Nik Collection may be fond of their Nik plugins...
Which plugin(s) you like / use really depends on the person and workflow.
I mean, I'm particularly fond of the plugins I've written, but that's because I understand how they work, they do what I want, and if ever I encounter a bug I fix it. But some people are not so fond of my plugins...
I have written over a 100 plugins, and use about 10% of them regularly, and about half of them not at all (the other 40% on an occasional basis).
In other words, plugins are a means to an end. If you have no desire for that end, you'll have no desire for the plugin that accomplishes it.
For example, TreeSyncPublisher is indispensible if you want to maintain an export tree external to Lightroom, but otherwise it may be useless. YMMV...
Perhaps a better question is:
"What are some good sources for plugins so I could peruse and find those that may help me get my job(s) done?"
Partial Answer:
* Rob Cole
* John Ellis
* Jeffrey Friedl
* John Beardsworth
(and be sure to visit the plugin exchange)
There are a lot of other great sources not mentioned here, and my apology in advance if I neglected you - nuthin' personal I assure you...
Sorry - I realize this wasn't exactly the answer you were looking for. I could give you a list of plugins I use most, but I fear it would not be of much value to you, since you probably would use a totally different cross section. Feel free to contact me outside the forum with questions about specific plugins.
Rob

Beta test: PLUS Plugin for Lightroom. Protect your images.

Many of you on this forum are PLUS members or have contributed to the development of the PLUS standards. We are inviting all forum members to particpate in a beta test of a new Lightroom plugin developed by Timothy Armes that will allow Lightroom users to inject PLUS license statements into images on export. Companies around the world are building PLUS into their DAM systems, allowing them to ingest your rights information upon receiving your files, and to use automation to better manage images and to avoid infringement.
For those unfamiliar with PLUS, the PLUS Coalition is an international collaboration between all industries involved in creating, distributing, using and preserving images. Spanning 30 countries, PLUS is the largest photography-related organization, representing the interests of both owners and users. The Coalition has developed the Picture Licensing Universal System, an integrated system of standards approved by all industries, to simplify and facilitate the communication and management of image rights.
To receive a free copy of the beta version of the plugin, please email info at usePLUS.org
We thank Adobe for continued generous support of the PLUS initiative from the beginning. Adobe is a Leadership Circle member of PLUS.
Jeff Sed!ik
PLUS
www.usePLUS.org

Sweet! - and thanks for informing us.
I keep edited photos auto-published for screen-saving.... but my screen saver doesn't have the nice options of LrDisplay.
Thanks again,
Rob

Question rgd Jeffrey's Export-to-Flickr Lightroom Plugin

Hi.
I stumbled across this plug-in in Scott Kelby's LR2 book, thought it was a cool feature, and was about to install it when I came across this:
"By authorizing this link, you'll allow Jeffrey's Export-to-Flickr Lightroom Plugin to:
Access your Flickr account (including private content)
Upload, Edit, and Replace photos and videos in your account
Interact with other members' photos and videos (comment, add notes, favorite)
Delete photos and videos from your account"
Is this really so? By adding this plugging I will give this Jeffrey access to delete my Flickr photos?
I'd really like to know before installing this thing.
Thanks in advance,
ole k

I guess I was a bit confused by reading: "By authorizing this link, you'll allow Jeffrey's Export-to-Flickr Lightroom Plugin to: . . . . .
Delete photos and videos from your account", as if the plug-in sort of would have a life on its own and start deleting my files. Which, I see now, was not the case. See also my other two replies to this thread.
As for Flickr to delete (among other things) my files, I'm really not that worried, as I am an amateur with little or nothing to lose. It was the idea of having this 3-part program interfering with my photos which scared me off a bit, along with the fact that I only yesterday encounterd another LR plugin - from Adobes/Scott Kelbys site, which included two trojans. But it all seems sorted out now.
Thanks,
ole k

GPU notes for Lightroom CC (2015)

Hi everyone,
I wanted to share some additional information regarding GPU support in Lr CC.
Lr can now use graphics processors (GPUs) to accelerate interactive image editing in Develop. A big reason that we started here is the recent development and increased availability of high-res displays, such as 4K and 5K monitors. To give you some numbers: a standard HD screen is 2 megapixels (MP), a MacBook Retina Pro 15" is 5 MP, a 4K display is 8 MP, and a 5K display is a whopping 15 MP. This means on a 4K display we need to render and display 4 times as many pixels as on a standard HD display. Using the GPU can provide a significant speedup (10x or more) on high-res displays. The bigger the screen, the bigger the win.
For example, on my test system with a 4K display, adjusting the White Balance and Exposure sliders in Lightroom 5.7 (without GPU support) is about 5 frames/second -- manageable, but choppy and hard to control. The same sliders in Lightroom 6.0 now run smoothly at 60 FPS.
So why doesn't everything feel faster?
Well, GPUs can be enormously helpful in speeding up many tasks. But they're complex and involve some tradeoffs, which I'd like to take a moment to explain.
First, rewriting software to take full advantage of GPUs is a lot of work and takes time. Especially for software like Lightroom, which offers a rich feature set developed over many years and release versions. So the first tradeoff is that, for this particular version of Lightroom, we weren't able to take advantage of the GPU to speed up everything. Given our limited time, we needed to pick and choose specific areas of Lightroom to optimize. The area that I started with was interactive image editing in Develop, and even then, I didn't manage to speed up everything yet (more on this later).
Second, GPUs are marvelous at high-speed computation, but there's some overhead. For example, it takes time to get data from the main processor (CPU) over to the GPU. In the case of high-res images and big screens, that can take a LOT of time. This means that some operations may actually take longer when using the GPU, such as the time to load the full-resolution image, and the time to switch from one image to another.
Third, GPUs aren't best for everything. For example, decompressing sequential bits of data from a file -- like most raw files, for instance -- sees little to no benefit from a GPU implementation.
Fourth, Lightroom has a sophisticated raw processing pipeline (such as tone mapping HDR images with Highlights and Shadows), and running this efficiently on a GPU requires a fairly powerful GPU. Cards that may work with in the Photoshop app itself may not necessarily work with Lightroom. While cards that are 4 to 5 years old may technically work, they may provide little to no benefit over the regular CPU when processing images in Lr, and in some cases may be slower. Higher-end GPUs from the last 2 to 3 years should work better.
So let's clear up what's currently GPU accelerated in Lr CC and what's not:
First of all, Develop is the only module that currently has GPU acceleration whatsoever. This means that other functions and modules, such as Library, Export, and Quick Develop, do not use the GPU (performance should be the same for those functions regardless of whether you have GPU enabled or disabled in the prefs).
Within Develop, most image editing controls have full GPU acceleration, including the basic and tone panel, panning and zooming, crop and straighten, lens corrections, gradients, and radial filter. Some controls, such as local brush adjustments and spot clone/heal, do not -- at least, not yet.
While the above description may be disappointing to some of you, let's be clear: This is the beginning of the GPU story for Lightroom, not the end. The vision here is to expand our use of the GPU and other technologies over time to improve performance. I know that many photographers have been asking us for improved performance for a long time, and we're trying to respond to that. Please understand this is a big step in that direction, but it's just the first step. The rest of it will take some time.
Summary:
1. GPU support is currently available in Develop only.
2. Most (but not all) Develop controls benefit from GPU acceleration.
3. Using the GPU involves some overhead (there's no free lunch). This may make some operations take longer, such as image-to-image switching or zooming to 1:1. Newer GPUs and computer systems minimize this overhead.
4. The GPU performance improvement in Develop is more noticeable on higher-resolution displays such as 4K. The bigger the display, the bigger the win.
5. Prefer newer GPUs (faster models within the last 3 years). Lightroom may technically work on older GPUs (4 to 5 years old) but likely will not benefit much. At least 1 GB of GPU memory. 2 GB is better.
6. We're currently investigating using GPUs and other technologies to improve performance in Develop and other areas of the app going forward.
The above notes also apply to Camera Raw 9.0 for Photoshop/Bridge CC.
Eric Chan
Camera Raw Engineer

I posted the following information on the Luminous Landscape forum (GPU used in Develop but not Library?) in response to comments you made there.
I am very puzzled by the extremely blurry image in the second screen capture when the GPU is enabled.
OS X (10.9.5)
Hardware configuration:
   MacPro (late 2013)
   AMD FirePro D300 2048 MB
   Apple Cinema Display 1920 x 1200
   16 GB RAM
   1 TB SSD
Test file: Nikon D800 NEF, 50 MB
(0) open the Develop module
(1) select a different NEF file and zoom to 1:1
(2) clear the ACR cache
(3) select the test file
(4) take 3 screenshots to illustrate the 3 display states (the first one is hard to capture)
(5) select another image
(6) same 3 states are present
(7) return to the test file and the same 3 display states are present
   Why isn’t the ACR cache coming into play in step 7?
If I repeat this process with the GPU disabled the image is displayed without the intermediate states.
I have attached the 3 screenshots mentioned in step (4).

Looking to purchase Nik software for Lightroom OR Photoshop. Is there a difference in the versions?

I currently use photoshop for all of my photo editing. I just purchased a copy of Lightroom though, which I plan on integrating into my workflow. I'm also looking to buy the complete collection of Nik software. If I want it to be compatible with photoshop, the complete collection is $200 more expensive. My question is are the versions of Nik software the exact same whether using it for Lightroom or Photoshop? What potential drawbacks are there for me not to be able to use Nik in photoshop, but only in lightroom?
Thanks!

The versions are similar but the photoshop version gives you the extra tools for, brushing, erase, fill and clear which to be honest i've never felt a great use for and if you duplicate the layer in photoshop before heading back to LR (to use NIK) you essentially get the same thing. Eg:
LR to photoshop as TIF or PSD
Duplicate layer
Save and back to Lightroom
Add NIK effect
Back to photoshop if you want to do any brushing or mask erasing of the nik plugin you applied in LR because you have the original layer underneith.
Even better if you think you can get away with all your editing in LR because you will always have the adjusted RAW alongside the TIF or PSD that Nik software will create anyway. I say save your money, a whole $250 now because the Lightroom version has been reduced again.
Ahh if only LR would give us layers........

Basic Questions On List View Plug-in For Lightroom

I need some basic information about the List View Plug-in for Lightroom:
HERE ARE MY QUESTIONS:
I have 40-60 photos per folder. Can List View list that many files on successive pages?
Most of the time I have 15-30 keywords or keyword phrases listed per picture. If I could widen the column I could see all of them. If the column does not widen, will the keywords not shown still be there to be exported to an Excel column, and then shown?
The thumbnail pictures on the end of all the summary lines are cool, but can I delete them before exporting to Excel?
Thank You Very Much for any information about this Plugin,
THANK YOU,
Sandy

Your questions seemed to be asked without actually tried the trial of the plug-in. I did, just now, and from what I can tell, with only have 20 images to test with since that is the trial limitation:
1)      The number of rows is fixed, and you can use the slider at the top-right to move from one page to the next.
2)      The columns do not change width in the plug-in though what you can’t see still gets exported to Excel although I’d expect all the keywords to be in one Excel column, not one column each.
3)      There are several sizes of thumbnails that can be selected from, including None—this is new compared to the one screen-capture on the plug-in website, so setting None as the thumbnail size is how you’d prevent thumbnails from going to Excel. I tried exporting thumbnails and they were all broken images, so maybe it doesn’t actually work, or maybe there is a limitation in the trial mode.

PS Elements as the editor for Lightroom??

Is anyone using PSE 6.0 as the editor for Lightroom? I am considering it because it is much less expensive than a CS3 upgrade.
However, I am concerned about losing ProPhoto RGB as the color space between the two. Is this a legitimate concern?
Any other recommendations out there?
Thanks in advance for your help.

When you say upgrade... do you have some version of Photoshop? I'm still using CS2 and it works with LR.
If you've used Photoshop a lot, I would definitely try out Elements first. Personally, I didn't care for it. Yes, quick fixes are easier, but you can do that in LR. But if I had to pay many hundreds for Photoshop and I wasn't tied to certain features or plugins for PS, my attitude toward Elements would change real fast.

Adobe revel for lightroom 5, unsafe

I recently upgraded to lightroom 5, so..had to download & reinstall the Adobe Revel export plugin. After a frustrating time installing the thing..it worked for one day. Then...my Norton Security quarantined it, stating it was exhibiting unusual behaviour, and it was from an untrusted source ( cloudnet.net) so, am stuck because when i try to install the plugin from "cloudnet.net".. my Norton security quarantines it. I delved into the workings of "cloudnet.net", and found that it is associated with "Delta Search" another site noted for malware & spyware, and other malicious adware. Where can i get a safe Revel plugin for lightroom?...

It appears that the Delta Search software found its way to your computer independently of Revel or Lighrroom and may be interfering with your installation of hte plugin.
http://www.bitdefender.com/tech-assist/self-help/how-to-remove-delta-search.html
Bitdefender describes it like this and offers suggestions as to how to remove it:
Many users complain they have been tricked into installing third party toolbars that may overwrite default settings in their browsers such as the home page or the preferred search engine.
http://www.bitdefender.com/tech-assist/self-help/how-to-remove-delta-search.html
It should not be related to either Revel or Lightroom.

Lightroom Plugin Problem.

Hi guys,
I recently installed some new plugins for lightroom and added them using the lightroom Plugin manager and I have also activated them. Although, I have done all of this, they don't appear on my publishing services list or my Lightroom plugin manager when I save it and Exit. Please some guidance would be helpfull!

If you are using Jeffery Friedl's Smugmug publish plug-in you can do the following:
Create Normal Collection in LR i.e. "Sunsets"
In the Smugmug Publish Services create a new Smart gallery (call it Sunsets as well) (See instructions on Jeffery's site for specifics on doing this)
Once the empty Smart Gallery has been created then you can edit it in Lightroom to have the rule(s) like below:
Choose Source as Collection, Contains All, 'Sunsets' (as the text to match)
I could not test this out directly with Smugmug as I only have a Zenfolio account.
But the instructions on Jeffery's site look like this is applicable to either his Smugmug or Zenfolio plugin.
Now, if I add/delete a photo to the normal LR collection titled 'Sunsets' then the corresponding Smart collection in the Publish services shows the same.
You then have to click on the Publish button to get the actual website updated with the changes.
Hope this helps point you in the right direction for what you are trying to accomplish.
Bruce

Is it wise to keep the Nikon camera files "DSC's" after downloading them and converting to DNG files via Adobe converter for lightroom use. In other words do the DNG files have all the raw data I would ever need in processing or should I save the camera'

Is it wise to keep the Nikon camera files "DSC's" after downloading them and converting to DNG files via Adobe converter for lightroom use. In other words do the DNG files have all the raw data I would ever need in processing or should I save the camera's DSC files?

DNG files do not contain some metadata supplied by the camera, which can be used by the manufacturer's software. Thus, if you don't keep the original Raw photo, you will lose this information.
If your 1000% sure you're never going to use the manufacturer's software, then this isn't a problem. But who can be sure what software you will be using 10 years from now?

How to find serial Number for BCC Plugin?

Hi,
How to find serial number for Bcc plugin on FCP?
I need format my Mac so before that I to find the serial number?
Please anyone can help me....

The serial number has the format like E-111-aaa-222-bbb-333-ccc-444-ddd-5ee-ffff, it can be found on a piece of paper which has 3 stickers with it inside the box.

Interactive debugger for Lightroom plugins

Similar Messages

Maybe you are looking for