Lightroom Classic 9.0: SDK ignores values set in updateExportSettings function (Timelapse plugin)

  • 7
  • Problem
  • Updated 4 weeks ago
  • Solved
  • (Edited)
A bug seems to be introduced with version 9.0 of Lightroom that when a plugin designer sets exports settings using the "updateExportSettings" of the Lightroom SDK all these settings are ignored and default settings are sent for the export job.

When the following code is used, the files are NOT renamed on export. The exported file have the same name as the original files.


updateExportSettings = function( settings )

    settings.LR_collisionHandling = "rename"

    -- Rename settings
    settings.LR_renamingTokensOn = true
    settings.LR_tokenCustomString = ""
    settings.LR_tokens = "{{naming_sequenceNumber_5Digits}}"

end


I do not know if this is the best place to put this, Adobe seems to have deleted the Lightroom SDK forum.
Photo of Allen Gambrell

Allen Gambrell

  • 1 Post
  • 0 Reply Likes

Posted 7 months ago

  • 7
Photo of Bhargav

Bhargav, Official Rep

  • 84 Posts
  • 20 Reply Likes
Hi Allen,

Thanks for reporting the issue.
We'll investigate and get back to you.

Meanwhile, Can you provide a sample script to replicate the issue?

Thanks,
Bhargav

Photo of Gunther Wegner

Gunther Wegner

  • 36 Posts
  • 17 Reply Likes
I can confirm this problem, it's a big issue for me and the users of my software who rely on my Custom Export Plugin for Lightroom.

Here is a sample ServiceProvider script:
local LrDialogs = import 'LrDialogs'
return {
showSections =
{ 'fileNaming', 'imageSettings', 'exportLocation' },

updateExportSettings = function( exportSettings )
LrDialogs.message("Called") -- this will be called,
-- but still the exportSettings
-- won't be changed
-- export will happen in JPG.
exportSettings.LR_format = "TIFF"
end,

processRenderedPhotos = function( functionContext, exportContext )
local exportSession = exportContext.exportSession
local renditions = exportSession:renditions{ stopIfCanceled = true }
for i, rendition in renditions do
success, pathOrMessage = rendition:waitForRender()
end
end
}

If the Plugin is being called by a preset, which sets format = "TIFF", it will show the right format (tiff) in the dialog, but then still export jpgs.

I'd really appreciate if a fix could be provided asap! Thank you!

(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7281 Posts
  • 1655 Reply Likes
This should be resolved by the 9.1 update released earlier today. Please give it a try and let us know if you still see the issue after updating.  Thank you for your patience!
Photo of John R. Ellis

John R. Ellis, Champion

  • 5045 Posts
  • 1422 Reply Likes
"Adobe seems to have deleted the Lightroom SDK forum."

Unfortunately, all of the scripting and SDK forums were merged into their parent forums as part of the ugly migration from the Jive platform to Khoros.   Most of the old LR SDK forum content is still there, though it's much harder to search, and it's much harder for a plugin developer to monitor just SDK content.

Regardless, this forum (the official feedback forum) is the place to post bug reports.
Photo of Oliver Salzburg

Oliver Salzburg

  • 5 Posts
  • 2 Reply Likes
Is it possible that there has been a regression on this? Because I'm seeing the exact behavior where I'm requesting a TIFF to be exported, but I'm receiving a .jpg file after the export. Although I'm only seeing that behavior on OSX, not on Windows.
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 5045 Posts
  • 1422 Reply Likes
Oliver, are you seeing this problem with a plugin you wrote or using the LR user interface?
Photo of Oliver Salzburg

Oliver Salzburg

  • 8 Posts
  • 0 Reply Likes
Posted https://community.adobe.com/t5/lightroom-classic/exported-tiff-images-are-actually-jpegs/m-p/11112413 over there. Also got additional details by now. It's a Lightroom bug IMHO
Photo of Gunther Wegner

Gunther Wegner

  • 36 Posts
  • 17 Reply Likes
With which version of LR are you experiencing this?
Photo of Oliver Salzburg

Oliver Salzburg

  • 8 Posts
  • 0 Reply Likes
9.2.1 and prior
Photo of Gunther Wegner

Gunther Wegner

  • 36 Posts
  • 17 Reply Likes
I cannot confirm this. With my plugin everything works as expected since this bug was fixed in 9.1.
Photo of Oliver Salzburg

Oliver Salzburg

  • 8 Posts
  • 0 Reply Likes
It just seemed like the issues are related and it could be a good starting point for the engineer who looked into your report. Sorry if I caused confusion. And, thanks for checking :)