Skip to main content
F
FeedbackCommunityMember
Inspiring
November 5, 2019

P: SDK ignores values set in updateExportSettings function (Timelapse plugin)

  • November 5, 2019
  • 17 replies
  • 804 views

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.

    This topic has been closed for replies.

    17 replies

    O
    oliversalzburg
    Participating Frequently
    May 7, 2020
    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 🙂
    Gunther Wegner
    Gunther Wegner
    Known Participant
    May 7, 2020
    I cannot confirm this. With my plugin everything works as expected since this bug was fixed in 9.1.
    O
    oliversalzburg
    Participating Frequently
    May 7, 2020
    9.2.1 and prior
    Gunther Wegner
    Gunther Wegner
    Known Participant
    May 7, 2020
    With which version of LR are you experiencing this?
    O
    oliversalzburg
    Participating Frequently
    May 7, 2020
    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
    johnrellis
    johnrellis
    Legend
    April 5, 2020
    Some other plugin developers do occasionally participate in that forum. You can tag your post with SDK.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 5, 2020
    The tester who was most specific with the response was using Lightroom Classic 9.2 and was experiencing the issue.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 5, 2020
    I've come across the subject, and a lot of your content, while working on this plugin. Thanks for your contributions by the way.

    I came across this post because it sounded very similar to what I was experiencing, but maybe I just need to do more debugging and was just lucky it working on Windows initially.

    Thank you for the link, but my first impression is that it wouldn't be very fruitful to bring up such a technical subject there. I feel like you share the impression.
    johnrellis
    johnrellis
    Legend
    April 5, 2020
    Also, ask your testers which version of LR they're on (Help > System Info), since the bug of the original post was reportedly fixed in 9.1. Beware that the Creative Cloud app sometimes fools people into thinking they're on "the latest", so insist that your testers do Help > System Info.
    johnrellis
    johnrellis
    Legend
    April 5, 2020
    Publish-service plugins is one area of the SDK for which I'm not expert. This forum isn't the best place to get help, especially for plugin development -- it's more for bug reporting and feature requests.  

    Unfortunately, Adobe in its wisdom merged the SDK user forum with the main LR Classic user forum last fall, which has reduced participation in the SDK forum. But you might post in the LR Classic forum and see if someone else can help.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices