Adobe Community: Using jpeg

Currently Being Moderated

1. Rob Cole,

Jun 13, 2012 2:03 PM in reply to jimkeir

Report

Consider looking at source code here, which does something similar:

http://www.robcole.com/Rob/ProductsAndServices/MiscLrPlugins/#ExportPe rcentResize

But, in a nutshell:

* Dump the export parameters using something like Debug.lognpp from John Ellis debug toolkit.

* Look for the option that enables the LR_jpeg_limitSize paramater to do it's deed.

Or,

* Save an export preset that has the limit size enabled.

* Save an export preset that has the limit size disabled.

Compare them

Rob

|

Mark as:

Currently Being Moderated

2. jimkeir,

Jun 14, 2012 1:05 AM in reply to Rob Cole

Report

Hi Rob,

Thanks - already done those though, unless I'm missing something obvious. The key difference appears to be the 'LR_jpeg_useLimitSize' value, a boolean. To be specific, I've tried:

- Passing through the existing table of parameters from the exportContext, but this doesn't work entirely correctly due to a bug in LR which someone reported in another thread, and Eric confirmed.

- Copying that table verbatim into a new, non-observable table and passing that in.

- Constructing an entirely new parameter table with LR_jpeg_limitSize and LR_jpeg_useLimitSize set appropriately

- Ditto, but with LR_jpeg_quality set to 1 as per the example in the SDK, in case it works as some kind of trigger

- Constructing a new parameter table with the only the values in a working saved preset (with LR_ prefix of course)

- Passing in both the original and copied property tables without the LR_jpeg_quality value set, again in case this acts as a trigger to disable the limitSize value

- Trying much lower size values, in case there's some kind of bug where the size is interpreted differently by the GUI and manual ExportSession creation

In other words, if I use a pre-created ExportSession, it is obeyed. If I take that set of parameters, copy them into a new parameter table and create a second ExportSession by hand, it is ignored.

Thanks for the reference to your existing code, but I'll not take a look since this is a bugfix for a commercial module and I try to avoid using sources that people have provided for free, out of respect for your time.

Cheers,

Jim

|

Mark as:

Currently Being Moderated

3. Rob Cole,

Jun 14, 2012 1:15 AM in reply to jimkeir

Report

I guess I don't know then.

I've never had a problem with:

local es = LrExportSession{ photosToExport=photos, exportSettings={

-- whatever I want, e.g. LR_this = that...

}}

es:doExportOn...

But maybe you've stumbled into a bug I'm not aware of.

Good luck,

Rob

|

Mark as:

Currently Being Moderated

4. Rob Cole,

Jun 14, 2012 1:22 AM in reply to jimkeir

Report

Dunno if export-percent-resize is the best example, now that I think about it: It doesn't create the export session in the above-mentioned manner (it's an export filter).

But you can look at the exportTif function in the NxToo.lua module of the NxToo plugin, which does something more like what you are trying to do I think:

http://www.robcole.com/Rob/ProductsAndServices/NxTooLrPlugin

|

Mark as:

Currently Being Moderated

5. jimkeir,

Jun 14, 2012 2:15 AM in reply to Rob Cole

Report

Hi,

OK, thanks, I'll take a quick look and see if anything looks different. Incidentally, setting the export width and height in a filter no longer works either. I know it used to. Now all images are scaled to the height that's set when the first call to waitForRendition() in the filter is called, that's what triggered this whole thing off. I need to scale differently per-image and the only usable workaround is to create one exporter per image.

Cheers,

Jim

|

Mark as:

Currently Being Moderated

6. Rob Cole,

Jun 14, 2012 2:21 AM in reply to jimkeir

Report

Post code snippet and perhaps somebody can see the problem?

R

|

Mark as:

Lightroom SDK

Using jpeg_limitSize

Jun 13, 2012 6:54 AM

More Like This

Bookmarked By (0)

Answers + Points = Status