Develop setting names in LR3 and LR4,5

Hello
I'm trying to work with develop setting.
to get current setting I use
photo:getDevelopSettings()
and for set settings I use
LrApplication.addDevelopPresetForPlugin
photo:applyDevelopPreset
The problem is. If in LR3 (bot Mac and Win) I modify a settings with keyname "Contrast" then it is correctly applied this setting to LR's develop seting "Contrast" and everuthing works as it should.
But in LR 4 and LR 5 it just create an inner plug-in seting with name "Contrast" what has not any affect on LR's setting "Contrast"
I looked throw many pages of this forum and dint meet any mention about same problem. But I met what sometimes in some samples the develop settings are named as i.e "Exposure2012" instead of "Exposure".  There is a some special rules how to use setting's keys to access to standard LR develop settings independly of LR version?

The LR 5 SDK API Reference does mention the process version 2012 settings:
However, as mentioned above, the documentation isn't well-maintained, so you're always better off double-checking it by dumping out the results of getDevelopSettings().  E.g. in LR, take a sample photo, set all the develop settings to non-default values, and then in a script invoke Debug.lognpp(photo:getDevelopSettings())  (using the Debug module from my debugging toolkit for Lightroom).
probably the simplest way is just check some global environment variable with LR version number and use keynames accordingly this value.
Agreed.  You can get the version via LrApplication.versionTable().

Similar Messages

  • LR3 and LR4 Trial version won't launch

    For the last few days each time I try to launch either LR3 or the LR4 Trial version a pop up window appears on my desktop that says:
    Lightroom-Opening Catalog: DSC_1234.jpg.lrcat
    Then a Windows error message appears stating that Lightroom 64-bit has stopped working. I have uninstalled LR3 and re-installed it and also downloaded LR4 trial version. On both versions the above message still appears. I have tried searching for the file DSC_1234.jpg but I cannot find it.
    Does anyone have any suggestions?

    The Catalog name "Lightroom-Catalog: DSC_1234.jpeg.lrcat" is an invalid name for a catalog and has been created because you inadvertantly selected an "image file" to name a new catalog. The .lrcat is the normal extention for "LightRoom CATlog" it is in lower case.
    .LRCAT files are by default in your user > My Pictures> Lightroom folder. Delete the file with the invalid name then you can double click on a valid Lightroom 3 .lrcat or Lightroom 4 .lrcat file to open/boot the relative program.
    You can use a search with *.lrcat (LRCAT not IRCAT) for all your Lightroom Catalog files.
    However I am not sure you can use LR 3 in Trial mode since it has been replaced by LR 4.

  • Edit in photoshop is greyed out in both LR3 and LR4

    Sudenly the edit in photoshop option has been greyed out in both programs It has always worked and for no apparant reason that I can recall this has happened Can anyone advise what has caused this please

    sonsteby,
    You didn't describe any problem, except for not being able to re-install. And your problem is not the same as brownwood1 had.
    Your problem is probably from passing a 16-bit file to Photoshop, and most of the filters only work on 8-bit files. You can change Bit Depth in your preferences:
    or you can change mode in PS on an individual basis:
    Hal

  • LR3 to LR4 Camera Profiles?

    While I am aware that Develop Presets will behave totally differently between LR3 and LR4 due to processing differences I have never specifically seen camera profiles addressed.
    Will custom profiles done in LR3 give different results in LR4?

    Thanks guys.
    If you still have your eye on this thread here is another question. I have available profiles for a camera with the same sensor as my second camera (Sony A55 available - A57 not). Is there away by re-labling profile names to have LR use the one marked for the A55 when it reads that the camera is the A57? Could the files/folders be retitled or is the camera info embedded in the profiles themselves?
    Gary

  • Unable to upgrade a LR1 or an LR2 Catalogue in LR3 or LR4

    Unable to upgrade a LR1 or an LR2 Catalogue in LR3 or LR4.  Both LR3 and LR4 try to upgrade the LR1/LR2 Catalogs but then give an error message saying it is unable to upgrade the catalog just before opening.  Can anyone help?  I'm using all updated versions....

    Problem solved
    There maybe a problem upgrading a catalogue from PowerPC to an Intel.  I finally mangaged to open my (PowerPC) LR1 catalog in (Intel) LR4 by installing the trial version of LR2 on the Intel, opening the LR1 catalog in LR2, and then opening the new LR2 catalog in LR4 which will then upgrade it.  Problem solved.
    LR2 can be downloaded here:
    http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=4672&fileID=4372

  • Upgrade from LR3 to LR4

    Hi,
    I have a few questions before I install and migrate my LR3 Catalog to LR4.
    Is there an Adobe Read Me document that discusses the do's and don'ts?
    Will my settings for LR3 transfer to LR4? Currently my "Lightroom Settings" is saved with my LR3 Catalog.
    Will LR4 save a new LR4 Catalog based on the previous LR3 version?
    Finally, can I run both programs, LR3 and LR4 on the same Mac OS X 10.7.2? I plan to do this just for the next few months and LR3 Catalog will not point to the same photos as LR4.
    Thanks so much for your help.
    If

    Ian,
    Thanks, yes I started to watch Ms. Kost videos, they are always very helpful. I also looked over the read me, http://www.adobe.com/support/lightroom/read_me/Lightroom4_Readme.pdf
    Just a follow, can I keep and run both LR3 and LR4 on the same Mac? They will point to two different catalogs and photo folders. I want to run a couple of comparisons.
    Thanks again,
    If
    Upgrade Notes
      To update your Lightroom 1, Lightroom 2 or Lightroom 3 catalog simply launch Lightroom 4 and you will be able to select and upgrade your previous Lightroom catalog.
      The Lightroom 4 catalog upgrade process does not erase or remove your previous Lightroom catalogs. If you wish to try the Lightroom 4 30-day trial by upgrading your existing catalog, you may always return to earlier versions of Lightroom and continue using your previous catalog.
    o NOTE: Any changes or work completed in your catalog once it has been upgraded to work with Lightroom 4 will not be available in previous versions of Lightroom.
    o NOTE: The upgrade process will modify the image preview information of an upgraded catalog.(This information is stored in the .lrdata file that is located adjacent to a catalog file in the file system) Returning to a previous version of Lightroom will require that the previews be re-rendered. This can be a lengthy process for those with hundreds of thousands of images.
      Upgrading a Library from Photoshop Elements 6, Photoshop Elements 7, Photoshop Elements 8, Photoshop Elements 9, or Photoshop Elements 10 for Windows requires that Photoshop Elements be installed on the computer at the time of upgrade.
      Upgrading a Library from Photoshop Elements 9 or Photoshop Elements 10 for Mac requires that Photoshop Elements be installed on the computer at the time of upgrade.
      Lightroom 4 Beta catalogs may be upgraded using the same methods available for Lightroom 1, Lightroom 2 or Lightroom 3 catalogs.
      If you attempt to upgrade the same Lightroom catalog more than once, Lightroom will inform you of the location of the previously upgraded catalog.

  • Hello!, my name is jan and i am using lightroom 2 for many years. I have an original set-up disk with a 24 digit serial number. I had never problems wih installation of lightroom. suddenly lightroom refuses to start when I try to from a picture i have tak

    Hello!, my name is jan and i am using lightroom 2 for many years. I have an original set-up disk with a 24 digit serial number. I had never problems wih installation of lightroom. suddenly lightroom refuses to start when I try to from a picture i have taken with my nikon D500 and transferred to WINDOWS 8.1.  i have tried to re-install lightroom : the procedure asks for the serieal number , but refuses to accept the number that always worked. PLEASE help!!  jan

    If you are certain you have the right serial number, there really isn't much we can help you with here. You might try downloading and installing the last version of Lightroom 2. It will be the trial version, but when the trial screen appears there is an option to indicate that you have a serial number. Incidentally, Lightroom serial numbers start with the first four digits being 1160.
    Adobe - Lightroom : For Windows : Adobe Photoshop Lightroom 2.7 - English, French, German

  • Packing list - Driver Program and Layout set name for Smartform

    Hi ,
    Anybody knows about print program and Layout set name for PACKING LIST in Smartform.
    Regards,
    Kumar S

    Hi Bhuvaneswari,
    For Creating Adobe Interactive form, you need the below configuration:
    Server side:
    Server running on ABAP/Java stack configured with ADS
    For ADS Configuration, follow the below link:
    https://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=0000894009&nlang=E
    Client Side:
    The required Reader version depends on your usage situation.
    For SAP Interactive Forms by Adobe, we generally recommend the following:
                  Adobe Acrobat Version 7.0. 9 or higher
                  Adobe Reader Version 7.0.9 or higher
    If you require forms for one of the scenarios listed below, you must use Reader 8.1.
    These are:
    Forms in Web Dynpro applications that are integrated at runtime using xACF (Active Components Framework) ZCI (Zero Client Installation).
    Forms in scenarios that use digital signatures.
    If you use interactive forms in Web Dynpro for Java and these interactive forms are included using ZCI (Zero Client Installation) at runtime, you must read Note 1055911. Note 1055911 specifies the required reader version and contains further detailed information.
    Reward points if found helpful.
    Regards,
    Arafat

  • I am having trouble exporting from LR4. After I have developed the photo in LR and export the image, then when I open it in Photoshop, it does not retain any of the developing I just did in LR.

    When I export my image and open in Photoshop CS5, none of the developing I have just done in LR4
    is in the file. It is basically exporting a raw image with no developing.

    Exporting is the wrong procedure.
    In Lightroom, right-click on the photo and select Edit In

  • TREX:  How to set component  and option set names in Tool Area ivew  prop'

    Hi experts,
    My Trex is working fine .  
    I have created component set and option sets . How do i pass component set and and option set names  in Tool Area iview  parameters.
    By default :
    KM Search Advanced Parameters
    layoutSetMode=exclusive&ResourceListType=com.sapportals.wcm.SearchResultList&SearchType=quick&Advanced=true&QueryString=
    KM search componet : pcd:portal_content/every_user/general/eu_role/com.sap.km.home_ws/com.sap.km.hidden/com.sap.km.urlaccess/com.sap.km.basicsearch
    KM sear ch parameters:
    layoutSetMode=exclusive&ResourceListType=com.sapportals.wcm.SearchResultList&SearchType=quick&QueryString=
    where do i give .
    Thanks in advance ,
    Surekha .

    No need to change search component set.
    change KM Search advanced parameter as
    layoutSetMode=exclusive&ResourceListType=com.sapportals.wcm.SearchResultList&SearchType=quick&Advanced=false&SearchPluginName=<your search option set>&SearchCompsName=<your search component set>&QueryString=
    Change KM search parameter as
    layoutSetMode=exclusive&ResourceListType=com.sapportals.wcm.SearchResultList&SearchType=quick&SearchPluginName=<your search option set>C&SearchCompsName=<your search component set>&QueryString=
    hope it helps you
    Raghu

  • I have upgraded LR3 to LR4 and it works. Is it now safe to trash LR 4?

    I have upgraded LR3 to LR4 and it works. Is it now safe to trash LR 4?

    Hi Alan,
    After you ensure that you have migrated everything you need to the latest version, you can delete the previous version.
    Thanks,
    Preran

  • Set CN Name SameAccoutName UserPrincipalName and distinguished name with powershell

    I am trying to set a users  CN, Name, SameAccoutName, UserPrincipalName, and distinguished name to uppercase with PowerShell.
    I can set the SAMAccoutName and UPN but I cannot figure out how to set the other 3 attributes.
    I am only changing the names to all uppercase.  nothing  more.  The names will not change just the case. 
    I have a script i have put together to plug in the info so i just need to do one and i will let the script do the rest.  
    Is this possible to change the mentioned attributes with Power-Shell?
    I know the below piece works fine for those 2 attributes just cant get the other 3. 
    Thanks
    Set-ADUser -Identity $user -SamAccountName $upperSAM -UserPrincipalName $upperUPN
    Lishron

    That will not set anything to uppercase.  You are also missing 90% of the script.  What makes you tnink this will work.
    Her is an example:
    $name='SomeName'
    $name.ToUpper()
    In the modern world of computing we do not use all uppercase.  This pracatice was ended in computing shortly after WWII.  Only military teletype maintained this because 90% ot the machines could only pring uppercase.
    Uppercase is harder to read and is basically counter to all modern computer conventions.  I notice that office clerks and data entry people whoare minimally trained in computer data entry like all uppercase because they hate having to use the shift
    key and being careful to correct text errors.
    Any system that requires uppercase will define an entry method that automatically forces upper case.  AD does not require this.
    For logons and email case is never considered. any case works as all do caseless compares.
    ¯\_(ツ)_/¯

  • I am working in the Develop module of Lightroom 5 and have accidentally bumped a setting and lost the Basic menu and the option to retrieve it.  "Tone curve" is directly under the tool bar now.  How can I retrieve the "Basic" menu?

    How can I retrieve the "Basic" menu on Lightroom 5?  I accidentally bumped something while working in the Develop module of Lightroom 5, and now the Tone Curve menu is directly under the Tool Bar, with no option to click on "Basic." 

    Right-click on Tone Curve and choose basic again or press Ctrl+1 in Develop.
    On Mac (Control-Click or Cmd+1)

  • Question regarding upgrading from LR3 to LR4

    I currently have Lightroom 3 installed on my PC and want to upgrade to Lightroom 4.
    I have not had Lightroom 3 all that long and not too many files are there. I have two questions:
    1. Is it better to uninstall Lightroom 3 and then install a fresh copy of Lightroom 4 or could I just upgrade the current Lightroom 3 to Lightroom 4.
    I know I have heard in the past is is usually better to to a fresh install. As I have only had Lightoom 3 for a few months and few files I wondered if
    this was the way to go or would an upgrade be ok.
    2. I actually have the full version of Lightroom 4 (as opposed to an upgrade edition). Luckily for me, my father-in-law purchased it but turned out it was
    not what he wanted so he gave it to me. Can I use this full version to upgrade (if that is the solution to my first question)? I  know I can use it to do a fresh install.
    Also, if you can recommend any links to directions or video tutorials on migrating from LR3 to LR4 that would be great as I am very new to Lightroom.
    Thanks for the advice.

    Yes, it is very easy, as your existing LR3 installation will not interfere with the new LR4 installation.
    Just download LR4.3 from Adobe.
    Then start it, and go for File-Open catalog, and point to your exsiting LR3-catalog. The program will tell you that it needs to upgrade the catalog, which you confirm. This will create a new version-LR4 of your latest LR3-catalog.
    You might not like the name automatically chosen by this upgrade process, so close LR4 and use Windows Explorer to rename it into something meaningful like "LR4 Master Catalaog" or some such. Then double-click on it and work from there.
    Your previous images will show an exlamation mark in develop module for LR3's old process version 2010. Do not do anything on a batch basis for it, as this is not needed.
    Only for images, for which you do not like your previous LR3-develop results so much, click on the exclamation mark and upgrade it to LR4's process version 2012, and manually tweak from there.
    Cornelia

  • Error while running package ORA-06553: PLS-553 character set name is not re

    Hi all.
    I have a problem with a package, when I run it returns me code error:
    ORA-06552: PL/SQL: Compilation unit analysis terminated
    ORA-06553: PLS-553: character set name is not recognized
    The full context of the problem is this:
    Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
    My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
    select * from nls_database_parameters;
    Result from the old
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    Result from the new
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
    Database Characterset is US7ASCII
    Threshold validation cannot be done before catproc is loaded.
    Threshold validation cannot be done before catproc is loaded.
    alter database character set INTERNAL_CONVERT WE8MSWIN1252
    Updating character set in controlfile to WE8MSWIN1252
    Synchronizing connection with database character set information
    Refreshing type attributes with new character set information
    Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
    Regards

    Ohselotl wrote:
    Hi all.
    I have a problem with a package, when I run it returns me code error:
    ORA-06552: PL/SQL: Compilation unit analysis terminated
    ORA-06553: PLS-553: character set name is not recognized
    The full context of the problem is this:
    Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
    My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
    select * from nls_database_parameters;
    Result from the old
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    Result from the new
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
    Database Characterset is US7ASCII
    Threshold validation cannot be done before catproc is loaded.
    Threshold validation cannot be done before catproc is loaded.
    alter database character set INTERNAL_CONVERT WE8MSWIN1252
    Updating character set in controlfile to WE8MSWIN1252
    Synchronizing connection with database character set information
    Refreshing type attributes with new character set information
    Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
    *********************************************************************This is an unsupported method to change the characterset of a database - it has caused the corruption of your database beyond repair. Hopefully you have a backup you can recover from. Whoever did this did not know what they were doing.
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
    RegardsThe correct way to change the characterset of a database is documented - http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#sthref1476
    HTH
    Srini

Maybe you are looking for