-
1. Re: Third party plug-ins for develop module
hillrg Jan 30, 2009 8:53 AM (in response to SimonTindemans)I'll chime in here. I feel let down because part of the promise of Lr was a SDK. I sense that adobe is on board for workflow/DAM SDK but not anything that is part of the develop pipeline.
I have heard excuses that doing that would break the pipeline, but that just suggests poor design to me. Although not yet show time, bibble has made the promise to do this... -
2. Re: Third party plug-ins for develop module
SimonTindemans Jan 30, 2009 9:23 AM (in response to SimonTindemans)Well, I do believe that Adobe would like to offer a Develop SDK, but it'll probably have to compete for resources with other ideas/requests. Hence my bringing it up again.
>I have heard excuses that doing that would break the pipeline, but that just suggests poor design to me. Although not yet show time, bibble has made the promise to do this...
If not done correctly, it certainly has the potential to slow things down a lot. However, I don't believe the assertion of some on this forum that it's incredibly hard to implement. The biggest problem will likely be how to store the image-related settings for custom plug-ins. Do they get to go in the XMP data as well? How do you handle images with custom data when the plug-in is not present? Anyway, they'll figure it out, I think.
FYI, Bibble *already has* a raw pipeline SDK for quite some time in v4. Coming from RawShooter, I almost switched to Bibble for that reason alone (as a user and mini-developer), until I found out that it had some color issues with my camera... Luckily, Adobe has been on the ball color-wise, with the DNG profile editor. Now let's get this Develop SDK out there!
Simon -
3. Re: Third party plug-ins for develop module
Lee Jay-7OQGJF Jan 30, 2009 10:14 AM (in response to SimonTindemans)> I'll chime in here. I feel let down because part of the promise of Lr was a SDK. I sense that adobe is on board for workflow/DAM SDK but not anything that is part of the develop pipeline.
Rory, you are wrong about that.
http://blogs.adobe.com/lightroomjournal/2008/08/plugin_or_external_editor.html
"Take someone like Nik. They should be able to write a plugin that has the controls right in the adjustments in the delvelop module. It may not be true non-destructive editing, but lightroom could apply the settings from the nik plugin after all the other adjustments are made. just do this for the on screen preview and when the image is exported or edited in photoshop. This way you would get the things you want without having to go in and out of different programs which is Killing peoples workflow!
[I completely agree! Non-destructive imaging pipelines however are complex entities and opening them up to third parties requires a great deal of work in order to make the non-destructive workflow seamless. Frankly, we do have to prioritize our efforts and there were some fundamental image adjustments that had to come first. (See local brush and gradient tools.)]"
The comment in the brackets was from Tom Hogarty, LR/Camera Raw product manager. -
4. Re: Third party plug-ins for develop module
SimonTindemans Jan 30, 2009 10:33 AM (in response to SimonTindemans)Lee Jay, thanks for the link. Good to see that I seem to be saying the same thing as a Lightroom product manager - that means we may see this happen one day!
Simon -
5. Re: Third party plug-ins for develop module
hillrg Feb 2, 2009 9:57 PM (in response to SimonTindemans)> Rory, you are wrong about that.
Thanks Lee Jay. Tom's words are encouraging. -
6. Re: Third party plug-ins for develop module
Matt Dawson Apr 16, 2009 4:37 PM (in response to SimonTindemans)There have been numerous requests for third party plugin (or some way to extend the Develop module) over the years. I agree it is a critical item that needs to be addressed ASAP. Hopefully in LR3.
What I find most interesting about this particular request is that Simon has pointed out that Adobe already have the technology (Pixel Bender) and just need to apply it. Its already in Photoshop CS4 and Flash 10, and is used for non-destructive editing in those apps. So I'd be extremely disappointed if it doesn't make it into the next major release of their workflow/non-destructive editing tool. You'd have to be an optimist to expect it anytime before LR3.
The only real question remaining is will Pixel Bender, as it currently stands, meet the full needs of the LR plugin developer community? e.g. Could Noise Ninja or Nik plugins be ported to Pixel Bender? My guess is "not yet". Then Adobe need to figure out how much to change LR, how much to change Pixel Bender, and indeed how big a first step they take when adding Develop module extensibility to LR3. Lets hope it is enough for developers of the most popular plugins to invest the time and effort to develop LR specific versions of their products.
My 2c worth.
Matt



