Lua soap integration in lightroom

HI ,
I AM USING LUA SOAP AND LUA SOCKET TO CALL THE WEB SERVICE. IT IS WORKING FINE WHEN I TRIED TO CALL THE WEBSERVICE WITHOUT INTEGRATING WITH LIGHTROOM PLUGIN.
WHEN I TRIED TO INTEGRATE THE PLUGIN WITH THE LIGHTROOM IT SI UNABEL TO LOAD THE LUA SOCKET FILES.
PLEASE TELL HOW TO INTEGRATE THE SOAP FILES WITH LIGHT ROOM.
THE FOLLOWIN GERROR I AM GETTING WHILE INTEGRATING WITH LIGHTROOM.
An error occurred while attempting to run one of the plug-in‚Äôs scripts.
error loading module 'ssl.core' from file '/opt/local/lib/lua/5.1/ssl.so':
dynamic libraries not enabled; check your Lua installation
**** Error 2
Could not load the post-processing filter from this plug-in.
error loading module 'ssl.core' from file '/opt/local/lib/lua/5.1/ssl.so':
dynamic libraries not enabled; check your Lua installation
Please tell me the solution asap

Hi,
I'm pretty sure the functionality you are trying to access is disabled. The LR SDK limits the LUA standard capabilities available to the developer and I'd be extremely surprised if they allowed us to load object files. If it was an option I'm sure Jeffrey Friedl wouldn't have had to take such a torturous path to get SHA1 digests working.
So I think your best option is to ask for SOAP support to be integrated into Lightroom because that publicly available module will not work within the environment provided by the SDK.
Thanks,
Matt

Similar Messages

What good is video integration if Lightroom can't share with ANY other apps ???

Perhaps I am missing the VERY obvios, however it seems to me as if LR4's video integration is missing just about anything there is to miss.
Really crazy to think that those apps are coming from the same house ;-)
1) There is NO possibility to export to non-compressed media an include the Metadata CAREFULLY set in Lightroom. DPX does NOT get the LR4 Metadata written to them.
2) Exporting an H264 to H264 directly without intermediating will downgrade the quality so severly that one does NOT want to look at that video anymore.
3) Adobe has a wonderful way of sharing Metadata between its professional apps, so if one applies metadate inside of i..e Bride, Premiere Pro will be able to read them and vice versa.
ALL metadata applied inside of LR4 - STAY in lightroom 4. No other adobe app will be able to see those metadata. This is beyond crazy to me. And I have a HARD time understanding
why adobe implemented all those features of video if they are absoluty NO USE to anyone. Unless of course one would want to watch all his videos in Lightroom UNCUT.
But since the adobe lightroom crew has not yet figured out the obvious and included Lightroom in Apple's FronRow - I dont see that happen, at least for Mac users which are VERY acustomed
to a certain luxury that ANY OS should feature!
Perhaps adobe just wanted to pad them selves on the shoulders with Video capabilities which ARE GREAT when it comes to applying metadata, setting in and outpoints etc etc etc.
But if NO EXPORT (besides DPX which is NOT metadata capble) not severly degrading is possible why on earth did they implement it...
If this wasnt so darn tragic I would be laughing but I would LOVE to actually be able to use Lightroom to handle my rushes (footage) and be able to apply metadata in LR4 and then just import into Premiere.
Perhaps this just the first beta's shortcomings. I really hope so.
If I am missing the very obvious and doing something wrong, please enlighten my poor soul ;-)

So adobe sets up ONE forum to officially discuss LR4....
Then I enter the discussion and you tell me to put it up somewhere else...
Nice
Just as confusing as having to enter develop mode to access the white balance eye dropper....
This whole thing is getting too confusing for me...
NOevertheless I added my gripes over there.... And now I am only waiting to be told that I should post it somewhere else....
If adobes software wasn't the currently best, I sure would jump ship and that immediately !

Integration between Lightroom 4.2 and PS Elements 11.0

I am using Lightroom 4.2 and PS Elements 11.0. Clicking "Edit in" in LR when I have selected at least two photos, I get as bottom menu item "Open as layers in Photoshop...". When selecting this item PS Elem. nicely starts up but after waiting for a while no layers are created. Same applies to the HDR and Panorama options. The only LR menu item working is the one moving to the PS Elem editor sec. After carrying out editing of the file(s) in PS Elem and saving (as) there is only the option to include the edited file in the PS Elem catalog (while the version set option is "greyed out"). In the normal Photoshop (CS versions) the edited file is nicely included in the LR catalog. I now have to follow a cumbersome route by importing the file from within LR. Another issue is when 16 bit files are loaded into Elements; there is no warning that layers can only be generated/worked on in 8 bit mode.
Yet another, small LR issue, is that when in library mode moving from the center thumbnail grid/pane to the left Navigator, etc and right Histogram, etc. panes, the cursor changes into a double headed arrow passing the separation line and but does not turn back into the cursor (mode). Only moving fast through the separation line or "going over the top" passing along the top menu items helps
Obviously anyone with some suggestion as how to solve/circumvent the issues above?
Message was edited by: doctorspek

Photoshop Elements does not support layes with 16-bit files. Additionally, there is no HDR function in Photoshop Elements. You should be getting an error letting you know this is the case when you try from Lightroom.
These menu options are designed to be used with Photoshop, not Photoshop Elements and would normally be greyed out. Have you had a version of Photoshop install previously? When looking at the Edit In menu, what does it say at the top? Does it say "Open in Adobe Photoshop Elements..."?
Saving the file should automatically import it into Lightroom, even if you use the option to add it to the Elements Organizer as well.
As for the cursor not changing back to normal after crossing over the panel dividing line (which allows you to grow or shrink the panels) is rather curious.
All of these issues could be caused by corrupt settings files. Deleting these while the applications are closed will cause them to be recreated at next launch (with default settings). I would suggest doing this will all Adobe preferences (not just PSE and LR). Where they are stored depends on what OS you are working on.

Integration between Lightroom and Photoshop broken

It will almost inevitably turn out that I'm missing something glaringly obvious, but since upgrading to Lightroom 5.5 and Photoshop CC 2014, my photos are losing their LR adjustments when sent to PS. I'm no longer asked how I want the RAW files rendered, and resetting the warning dialogues in both applications has had no effect. I've been using PS and LR together for a couple of years now, and have never seen this problem.
Steve

Well, i have fixed it for now — just removed the 5.5 and reinstalled 5.4, which seems to be working fine with Photoshop CC 2014.
Waiting for a fix now is not so bad
Here's the mac 5.4 version at adobe storage http://download.adobe.com/pub/adobe/lightroom/mac/5.x/Lightroom_5_LS11_mac_5_4.dmg

SOAP integration with mySAP CRM system

Hi,
Currently I am using JCO to connecting to mySAP CRM system as per the following configuration:
<b>Version: ISA 3.0 SP13 </b>
Java Version: 1.3.1_07
Java VM Version: 1.3.1_07-b02
JCo Version: 2.0.5 (2002-09-03)
Servlet Engine: SAP J2EE Engine/6.20 PatchLevel 34165
Operating System: Windows 2000 / 5.0
Want to integrate SOAP with mySAP CRM system. Would any body suggest me what all the configuration setup & components I need?
Regards,
Vinayak

Hi Ram,
I am not sure if this is still a valid question. But anyways, you can find the process here [http://help.sap.com/saphelp_crm50/helpdata/en/ac/0a346c104541af9d587666efc95da3/content.htm ].
1.     Maintain an RFC destination to the CTI system
                          Transaction sm59
                          Select http connections to external server and click on create
                          Enter all details.
                          Save
2.     SAP Menu
                           Interaction Center -> Interaction Center WebClient -> Administration -> Communication Management Software -> Interface Settings -> Maintain Communication Management Software Connections
                           Maintain the entry "BCM" and corresponding rfc connection entry
3.     SPRO -> CRM -> Interaction Center -> Basic Functions -> Communication Channels -> Define Communication Management Software Profiles ? Maintain a new entry for CTI system
4.     Maintain Business Role
                          SPRO - > Customer relationship management -> Business role -> define business role
                          Select IC agent and click on ?Assign function profiles?
                          For the function profile ID ?CONTACTCENTER? maintain the created CTI profile (you can use f4 help)
                          Save
5. Maintain system settings ( TA: CRMM_IC_MCM_CCADMX) and assign the profile that was created in IMG to the CMS system ID in the admin menu (TA: CRMM_IC_MCM_CCLNK).

Integration problem Lightroom 2.4 - Photoshop CS4

Hi,
I have a problem with editing in photoshop! Nothing seems to work as in the video's and documentation.
Problem description:
When I use the option to edit a selected photo in CS4 or edit as a smartobject in CS4 CS4 starts
up but the photo is not imported. Lightroom displays an error message " cannot start CS" (after some delay).
Is this a known problem?
Your help will be appreciated!

I wouldn't delete the prefs.
I have had this occur two or three times but not consistently - have reported a bug but cannot reproduce !! Random is hard to track and find.
However LR will open Ps and after the error message if you do the edit/open again all will be well.
If you want you can open PS first and the problem doesn't seem to occur.

Integrating Bridge & Lightroom?

Seems like a simple matter to me and very convenient. I'll be testing this over the weekend but am hoping to hear from others and have the benefit of their insight when I do, The plan is to copy files from an SD card to my HD, into my pre-existing photography folder, use Bridge to browse and choose the images I want to keep, then cut and past the images I want to keep into a Lightroom "watched folder" for "auto import" into my LR catalog. I;m still working through several resources, including Martin Evening's book, the online "help", and online tutorials to research my ideas about such a workflow.

I agree with John. What you describe probably works, but is not really optimal. Better IMHO to import all into Lightroom and use Lightroom to cull. It's simpler, and by reducing an extra stage of work removes a possible source of errors and mistakes, I find.
I find it easier to have everything in LR from the start. Even at the initial cull stage, it's handy to be able to go into Develop Module to see if an underexposed image can be brought up, for example, when deciding which to cull. I shot 1500 at a wedding last weekend, and found LR worked pretty well that way.
Actually, I don't cull much at the start; rather I star-rate in LR. I find with weddings I get requests like: "have you got a one like 432 but including Aunty May?" only to find there is one that's perhaps not well framed that I might have culled. Instead I cull only complete no-hopers, and keep the rest until after the final selection. Again, that's easier if everything's in LR.

Using the SOAP inbound channel of the Integration Engine

Hi,
I am following the blog of Stefan Grube.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
However I have difficulties.
Is this blog still relevant for SAP PI7.10?
I have set this up as a test for a scenario I have.
Current Scenario NOT using your Blog and working perfectly.
SandBox PI       Development PI
File > SOAP >   SOAP > ABAP Proxy
What I am attempting now is.
SandBox PI      Development PI
File > SOAP > Integration Engine > ABAP Proxy
I am using our SAP PI Sandbox to push a SOAP message using a Receiver SOAP adapter channel.
Transport Protocol: u201CHTTPu201D
Message Protocol: u201CSOAPu201D
Conversion Parameters:      u201CDo not Use SOAP Envelopeu201D
Target URL: u201Chttp://<Integratio Server Host Development PI>:<Port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=FigmentD&Interface=urn:figment-co-za:fleetcard:efuel_50ppm^oa_Msg50ppm&QualityOfService=ExactlyOnce&sap-user=<PIAPPLUSER>&sap-password=<PASSWORD>u201D
SOAP Action: u201Chttp://sap.com/xi/WebService/soap1.1u201D
I am however getting the following error on the SandBox Pi AE.
u201CSOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 MOVED TEMPORARILYu201D
Please can you assist in this matter.
Regards
Willie Hugo

Hi williem,
Stefans weblog works great. The error you are getting is some wrong data you are sending. Please verify the data you are sending is correct. Also check this threads for the same errror:
ADAPTER.HTTP_EXCEPTION / HTTP 302 Moved Temporarily
Re: SOAP client receives HTTP 302 Found
Re: Synchronous RFC-XI-Web Service with no request method
HTTP Error (302) Found when calling Web Service on XI
Regards,
---Satish

Lightroom features/bug fixes I would like to see in next version

I love the Adobe Lightroom Application. It is very intiutive and out of the different RAW processing programs I've tried, it is the only one that has most of the features I need and has the least amount of complications. However, I think there are still places to improve upon:
* Decouple raw processor from the monolithic software executable so that updates to the RAW camera component to add new cameras can be made without requiring huge downloads or reinstallation of a new software program but simply updating a few DLLs and files.
* Improve performance of the Develop panel. It is extremely slow on my laptop running 32bit Windows 7 and 3GB of RAM with dual core processor (pre-Core duo). 8 to 10 seconds for the "loading" message to disappear per image no matter how often I have loaded or edited the image. No caching is being done at all.
* On my higher powered Desktop (Quad Core2 processor/4GB RAM,Windows 7), Adobe Lightroom frequently will start behaving strangely after only a few hours of running. It seems like it is leaking resources or something because eventually functionality will start failing. Specifically, right clicking on images will no longer bring up menus for example. If i shutdown and restart the application, the problem goes away.
* Photoshop-like healing brush. Many times I want to "brush" over areas of image defects but the only choice in Lightroom is the healing tool which always creates a circle and does not allow "brushing". This only works if the defect is a spot and not an irregular area.
* Adjustment with Arbitrary Mask tool. Bibble 5 has this nice concept where you can mask out a section of an image and then apply adjustments to it without affecting the rest of the image. You simply draw a mask and then you can apply adjustments to it. The only option in Lightroom is to select the "Mask" option but that leaves the decision of where exactly you want to mask to Lightroom which only uses edge contrast to determine masking area.
* I'd like a way to tell Lightroom to update the metadata (write out) on all images that are out of sync. Right now the write metadata function will write out metadata to all files whether or not it is required. This means that it is inpractical to try to update your entire catalog as tens of thousands of files will be written to and not just those that are out of sync. This is very important as a way to preserve editing metadata in case of loss of the Lightroom catalog.
* Option to write import metadata to imported files. For example, I have an import metadata for copyright and keywords and I want the imported JPG or DNG files to permanently have this metadata so that even if individual files are copied my copyright and other metadata are preserved with it.
* Option to append text labels to automatically generated import destination folder names. So for example, I can still import into date based directories but append a description to help me remember what the folder contains when I'm later browsing it. Right now it is either/or. You can either choose the name of the import folder destination OR you can have the software generate one for you.
* A google-type search box at the top of the library panel so that ad-hoc searches can be done without having to fool around with the filters. Everybody is used to a single search box for simple textual searches.
* some way to filter images by whether they have been exported previously or not
* Please support lens and shooting information for Sony DSLRs in both JPG and RAW files. Also support 3rd party lenses on Sony DSLRs without assigning the wrong Minolta lenses to them. I want to be able to see both Lens name, max aperture, focusing distance (if available) etc...
* Some way to edit the Shooting lens information to support lenses which are not known to Lightroom, and if suggestion above won't be implemented, some way for the user to edit the lens id --> mapping table so that I can properly map my own 3rd party lenses.
* Facial recognition/tagging option. Some way to have Lightroom apply people tags after I have tagged representative images. Handle multiple people in a scene.
* Automatic (batch) export of images on schedule. I would like a way to configure Lightroom to automatically generate particular export configuration of all my images in a catalog (or some defined subset) such that new files or files that have been edited since last export are automatically exported on a schedule even if Lightroom is not running. Perhaps a Lightroom batch service. This is so that I can always have up to date processed versions of my images for use in my media center display. I would like to configure the Lightroom batch service to run weekly at say 2am every day, run a particular export function and export all new or modified images to a network share accessible by the media center. That way, I can always have access to cropped and edit images without manually doing exports all the time or having to remember which files I've edited and then export them. Also by doing this at off hours it would not slow down my computer while I'm using it.
* Better profiles for Sony DSLRs and support for their picture styles the same way that Canon and Nikon camera are supported.
* Teethering support for Sony DSLRs that have this feature
* Support for parametric plugins -- Plugins that do not require the image to be exported before running.
* Simple support for "picture frames" when exporting. Some way to apply a frame to an image as part of export with a dozen or so frames included and a way for 3rd parties to create more.
* A better way to safely share catalogs or pictures between multiple computers/users in a networked environment.

Did these come to you all at once, or have you been saving them up for a while?
Anyway, Adobe *should* be able to handle long lists of FR, but another option is to break them up and submit them for voting on the new FR/Idea site that will shortly replace this one: (It was really hot for a while, but has cooled down lately...)
http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om
HopeSpringsEternal2008 wrote:
I love the Adobe Lightroom Application...
Me too, and continue to push for improvements as well...
HopeSpringsEternal2008 wrote:
* Decouple raw processor from the monolithic software executable so that updates to the RAW camera component to add new cameras can be made without requiring huge downloads or reinstallation of a new software program but simply updating a few DLLs and files.
They are already decoupled - you can update ACR independently for new camera support, however it's released at about the same frequency as Lightroom itself, so that doesn't help much. Perhaps this should be reworded: "Provide more timely ACR updates..."
HopeSpringsEternal2008 wrote:
* Improve performance of the Develop panel. It is extremely slow on my laptop running 32bit Windows 7 and 3GB of RAM with dual core processor (pre-Core duo). 8 to 10 seconds for the "loading" message to disappear per image no matter how often I have loaded or edited the image. No caching is being done at all.
I've been complaining about this for a long time - ACR cache is worthless for me too - if dev image not in RAM cache, takes same amount of time to render whether in ACR disk cache or not. Some say ACR cache speeds things up for them - perhaps you need to *believe*...
PS - After new motherboard upgrade, this went from 15 seconds to 3 seconds average.
HopeSpringsEternal2008 wrote:
* On my higher powered Desktop (Quad Core2 processor/4GB RAM,Windows 7), Adobe Lightroom frequently will start behaving strangely after only a few hours of running. It seems like it is leaking resources or something because eventually functionality will start failing. Specifically, right clicking on images will no longer bring up menus for example. If i shutdown and restart the application, the problem goes away.
Yep - Lightroom still has some leaks - gotta restart it from time to time...
HopeSpringsEternal2008 wrote:
* Photoshop-like healing brush. Many times I want to "brush" over areas of image defects but the only choice in Lightroom is the healing tool which always creates a circle and does not allow "brushing". This only works if the defect is a spot and not an irregular area.
+1 vote - arguably the most desired addition to the dev tools. I bet Lr4 will have this (no inside info though).
HopeSpringsEternal2008 wrote:
* Adjustment with Arbitrary Mask tool. Bibble 5 has this nice concept where you can mask out a section of an image and then apply adjustments to it without affecting the rest of the image. You simply draw a mask and then you can apply adjustments to it. The only option in Lightroom is to select the "Mask" option but that leaves the decision of where exactly you want to mask to Lightroom which only uses edge contrast to determine masking area.
+1 vote - this is one of my highest hopes for Lr(4) too: sophisticated auto-masking + manual masking: to apply to all or at least most adjustments...
HopeSpringsEternal2008 wrote:
* I'd like a way to tell Lightroom to update the metadata (write out) on all images that are out of sync. Right now the write metadata function will write out metadata to all files whether or not it is required. This means that it is inpractical to try to update your entire catalog as tens of thousands of files will be written to and not just those that are out of sync. This is very important as a way to preserve editing metadata in case of loss of the Lightroom catalog.
Frequently requested - some use pre-startup database query + plugin to make collection in the mean time (I dont).
HopeSpringsEternal2008 wrote:
* Option to append text labels to automatically generated import destination folder names. So for example, I can still import into date based directories but append a description to help me remember what the folder contains when I'm later browsing it. Right now it is either/or. You can either choose the name of the import folder destination OR you can have the software generate one for you.
RC Importer supports this - its an import plugin that bypasses the import dialog box - not for everyone...
HopeSpringsEternal2008 wrote:
* A google-type search box at the top of the library panel so that ad-hoc searches can be done without having to fool around with the filters. Everybody is used to a single search box for simple textual searches.
Maybe the seeds of a good idea here, but may be worth some refinement/clarification - what would be searched? Would special syntax be supported? Personally, I mostly hate all 1-box search fields, because one never knows what's being searched and how, e.g. does it search the whole catalog?, is it case sensitive? On the other hand, I get the convenience factor... - I think if accompanied by help and/or the ability to pop up a dialog box for refinement or options, this might make a nice addition. Along these lines, I sometimes think a quick-smart-collection would be nice too - for when one wants to search 2 text fields, instead of just one. I keep a temporary smart collection just for this purpose, but still...
HopeSpringsEternal2008 wrote:
* some way to filter images by whether they have been exported previously or not
Change detecting export plugins have mostly solved this for me (and publishing for some folks), although adding export info (and metadata change info) to catalog for searching / sorting still sounds like a good idea to me...
HopeSpringsEternal2008 wrote:
* Automatic (batch) export of images on schedule. I would like a way to configure Lightroom to automatically generate particular export configuration of all my images in a catalog (or some defined subset) such that new files or files that have been edited since last export are automatically exported on a schedule even if Lightroom is not running. Perhaps a Lightroom batch service. This is so that I can always have up to date processed versions of my images for use in my media center display. I would like to configure the Lightroom batch service to run weekly at say 2am every day, run a particular export function and export all new or modified images to a network share accessible by the media center. That way, I can always have access to cropped and edit images without manually doing exports all the time or having to remember which files I've edited and then export them. Also by doing this at off hours it would not slow down my computer while I'm using it.
Yes, better export management would be welcome. Export Manager might help you (if you have multiple export destinations to update), but its not a panacea... Many of us ultimately "consume" our photos outside Lightroom, having the consumption copies kept up to date more fluidly would be good. Using change detecting export plugins (along with export-manager) and/or publishing helps..
HopeSpringsEternal2008 wrote:
* Support for parametric plugins -- Plugins that do not require the image to be exported before running.
Yep - much room for plugins to get better integrated with Lightroom proper, to participate in image enhancement, as well as other things...
HopeSpringsEternal2008 wrote:
* Simple support for "picture frames" when exporting. Some way to apply a frame to an image as part of export with a dozen or so frames included and a way for 3rd parties to create more.
That would be nice. Although support for 3rd parties to add frames *upon export* already exists (export filter plugin + export post-process actions), as well as adding text overlays and such. But since its not built into Lightroom, one has to find them and configure them... And there is no good way to preview them in Lightroom... I think this would go nicely with the previous request - ability to feed image data to plugins for preview in Lightroom. Even if these updates were not built-into the dev module - i.e. weren't kept updated automatically whilst editing - just being able to click a 'see final' button or have it rolled into the build-previews function, so one could have post-process imaging plugins (with preview before export) - might be a nice compromise until true imaging plugins (that fit into dev pipeline) are supported.
The end - for now...
-R

Using Adobe Lightroom with OSX Photos

I love the iCloud integration of the new Photos app, it's really great having all my photos available on my phone.
I also love the editing capabilities of Adobe Lightroom.
Has anyone figured out a way of using Photos for the iCloud integration and Lightroom for the editing and post processing?

Terence Devlin wrote:
See what I mean:
there is no way to sensibly use the two apps together,
Yes, from the Photos + Lightroom together perpsective.
But taking it back to the root, what is the best way to have the same benefits offered by photos (tight integration between iOS and LR)? If Adobe weren't so stingy with their cloud storage, it would be a lot simpler answer because you'd just stick the their storage and product suite.
How can someone who takes a fair # of photos on iOS get those seamlessly to LR and conversely have access to their photo catalogues on iOS when they want to show them? I think the answer may be CC Photography + Smugmug but there are pitfalls to the smugmug iOS client (does not background sync, nowhere near as good as Photos, does not integrate with other apps where you may want to use the photos collection).

Loading native code lua modules

I'm trying to load a C lua module into my Lightroom Plugin. Unfortunately I can't get it to work and keep getting the error:
An internal error occurred
Could not load toolkit script: PluginGUI-OSX
This is an Objective-C code lua library and the error occurs on the following line in my lua script:
require 'PluginGUI-OSX'
I've also tried preceding this with the following, but still I get no luck:
package.path = package.path..";./?/init.lua;./?.so"
Has anyone ever had luck trying this? Or does anyone on the Lightroom team know it to be impossible?
Thanks in advance
Rich

Hello,
I've got a similar problem. But I don't want to include native code. As in every example plugin I've found, I wanted to extract portions of my code to other scripts (just as FtpUploadTask.lua in FTP example)
But whenever I add the following line to my ExportServiceProvider I get an error:
require 'RhubarbHttpClient'
The error message looks as described in the post above:
Plug-in error log for plug-in at: /Users/krizleebear/Library/Application Support/Adobe/Lightroom/Modules/rhubarb-gallery.lrdevplugin
**** Error 1
An error occurred while attempting to run one of the plug-in‚Äôs scripts.
Could not load toolkit script: RhubarbHttpClient
**** Error 2
Could not load the post-processing filter from this plug-in.
Could not load toolkit script: RhubarbHttpClient
When I just put my code from RhubarbHttpClient.lua directly into my ExportServiceProvider, it's working.
The full code can be viewed on google-code:
http://code.google.com/p/rhubarb-gallery/source/browse/#svn/trunk/rhubarb_lightroom_plugin /rhubarb-gallery.lrdevplugin

Lightroom to Photoshop & Back :: Two Requests

b Two Related Requests:
1) Easier and more natural integration between Lightroom and Photoshop. Maybe a button at the bottom of the Develop Module. It could fit right next to Previous.
2) The option of saving an image as a PSD rather than have LR automatically save it as a copy. Everytime you start from a raw file and open in Photoshop it creates a new PSD saved to the hard drive, whether you want it or not. Then if you do it again it adds another file with the next number in the name. My preference is to simply have LR open the file in PS and then let the user decide what to do with it from there.
By the way, I do enjoy using Lightroom.
Thank you for your consideration on these requests.
Linda

> My wish would be that LR opens in PS/ACR without saving a file in any
> format. That way, we could choose what to do and how to save in PS.
Me too, please!
For the moment, I take care to save metadata to XMP in LR, then open the raw file directly in photoshop (ACR4.1 develop the files as in LR), and finally save a jpg (or whatever) image that I import and stack with the raw file - there should be a way to automate this workflow, shouldn't be?
Btw, I use Photoshop besides LR for 3 main reasons :
1 masked adjusment layers,
2 merge to HDR, either with the built-in HDR, or simply by blending two exposures with masks,
3 photomerge to make panoramas.
I understand there is a market to share between CS3 and LR ;o) but I'd like to see these functionalities implemented non-destructively in LR!
1 shouldn't be very different from the PS way of doing it, and for 2 and 3 a comfortable way to do that could be to use some sort of "ueber-stack" : select all images to join in a (kind of) stack, and then have the result image at the top of that stack?
Of course, I speak in a user point of view, not a programmer's one ;o)! But I'd really like to make all my PP work in 1 soft only, and LR seems very promising to me.

Lightroom and Bridge

Ok, we all know there is great integration between Lightroom and Photoshop, as there should be. What about Bridge?
Or is Bridge being phased out even though it of course is integrated with almost all Adobe products?

Remember that Bridge is for folder browsing, like a glorified Finder or Explorer, and not for cataloguing. Lightroom is a catalogue and can record the location of pictures whether or not they are on drives connected to the computer. Bridge searches go through the file system, so chugging through all attached drives to find pictures, while LR searches its database. Those are big differences.
"Lightroom is better for images without a doubt. So in the eyes of someone who does graphic work, will Lightroom replace Bridge?"
No for graphic work, and that's Ian's point about the limited range of file types that LR handles. But in the eyes of someone who only does photographic work, Lightroom is likely to substantially replace Bridge, and in many cases totally. Quite often, continuing to use Bridge is because some people don't/can't get their head around working with a catalogue-based workflow, and/or they have a preference for working with folders. I might use Bridge to dig into metadata, but not for much else (I use iView/ExMedia catalogues for managing other file types).
John

Deleting Photo Files in Lightroom 4

I use Aperture 3 and am thinking of switching to Lightroom 4. I do not store my photos in the Aperture 3 library. Instead I store my photos in my own folder system on an external hard drive and I reference the files in Aperture. This works well for most functions, but when I delete a photo from Aperture, it simply removes the thumbnail and all versions from Aperture, but does not delete the actual photo file on my hard drive. If I want to delete the actual photo file I must click "show file in finder" and manually delete it from the finder window.
Is the process of organizing photos in your own folder system, and deleting unwanted photos, more seemlessly integrated in Lightroom 4?
Thanks!

Yes
When you start the delete, Lightroom will give the option to delete or simply remove the photo from the Lightroom catalog. Remove retains the file on disk whereas delete will delete the file.

Photomatix Pro HDR Plug-in Updated with additional Lightroom Functinality

04-Feb 2009
Update log
Updated in v3.1.3
- Tighter integration with Lightroom. HDR options are now set from the
Lightroom plug-in and the processed image can be automatically re-imported
into the Lightroom library.
- Bug fixed: Processing files in Canon sRaw format caused an exception.
- Bug fixed: Transfer of exif data was not always taking the information of
the normal exposure.
- Bug fixed: When tone mapping an HDR image file that was previously saved
as Radiance in Photomatix Pro, the color profile was not properly embedded.
- Bug fixed: When strip processing option had been enabled for HDR
generation in batch processing, checking the blending methods at the same
time made the batch return an error.
- Bug fixed: Processing source images in the BMP format returned an error.
Rikk

>DaveBurns:CR - Can you help me understand where? I'm looking at the Plug-in Manager now with the Photomatix
plug-in selected on the left. I don't see standard LR buttons to do those actions.
That's because you're looking at the Photomatrix plugin, not one of Jeffrey's plug-ins :)
I pointed to one of Jeffrey's plug-ins to show that one button updates can be performed for LR plug-ins. It is up to the author of the plug-in to include the update items that appear in the LR Plug-in manager and Photomatrix didn't provide that capability in their plug-in.

Lua soap integration in lightroom

Similar Messages

Maybe you are looking for