Develop module - manual entry invisible

In the Develop module, when manually type in an entry for any parameter (and don't leave the input box), the digits display while typing, but then disappear after about a second, such that you cannot see what you just typed in.  I think the font is just turning white, but since the background is still white (since I haven't left the input box), you cannot see it.  Therefore, you are flying blind if you backspace to change some/all of the value you just typed.
I believe that you don't want it to turn white until after you leave the input box (by pressing enter, clicking somewhere else, or using arrow up/down).
I am using Mac OS X 10.7.2.

Thanks for the report.  We've got that one narrowed down and reported.

Similar Messages

  • Automatic Payment terms without referrring Customer Master nor manual entry

    Hi,
    I have a credit memo with reference to one billing document. It is automatically coming with payment terms which is not maintained in customer master nor manual entry in the document. I had checked all the configuration related settings for the document and payment terms assignment. I had debugged and checked for any user exit or function module.
    I have no clue in this regard and can anybody throw some light regarding to fix the problem.
    Regards
    Sashikanth

    Hi,
    Check if the billing document has payment terms. If yes, even if customer master doesnt contain payment terms the payment terms will be copied to the credit memo through standard copying control maintained in IMG, when you create a document with reference to some document this copying control gets activated.
    Also check user exit RV60AFZZ if there's any code written in it to default payment terms by billing doc type.
    Regards,
    Amit

  • Clearing of manual entries in GR/IR not happening

    Hi All,
    I've made two manual entries in the GR/IR account. The second entry being the reverse of the first, so basically they cancel out each other. But as these arent linked to a PO, the line items arent being cleared by F.13
    I tried manual clearing FB1s and F-04 but it picks up only one line item (the reverse line item i.e. credit item). And so I cant even manually clear these line items.
    Can you please provide a solution?
    Regards,
    Tejas

    Hi Tejas,
    Please have a look at Note : 178487, maybe it helps... it talks about several points like:
    1. In the master data of the G/L accounts, flag "Line item display" or "Open item management" was set for accounts which do not require line items.
    2. Update of FI data from the upstream modules is too detailed.
    3. Problems during clearing
    4. Data is kept too long in the system.
    But I am not very sure whether it answers your exact scenario.
    Coming to the point of clearing open line items 'easy way', as Janani mentioned, there seems to be no easy ways for clearing the open line items. As I understand, the primary reason for this could be because we are dealing with business sensitive data and the open line items are infact open because of some valid reason, and should not be closed using short cuts. What I mean is... a line item could be (or should be) open if there is some business transaction yet to be completed or it is closed if the transaction is completed and its the job of the user who is responsible for the transaction to make sure that the line item is cleared when the transaction is complete.
    In my experience, as you and Janani have experienced, it is normal that we see a lot of documents not archivable because of open items. In my previous experiences, we have handled it this way:
    1. Run the Archive run in test mode (prefarably with 'only incorrect docs in log')
    2. Give the log to the financial users/module owners to analyze the log (you can use FB99 also to see whether individual documents are archivable or not)
    3. Come up with a strategy to close the open items. Distribute the log to respective users (maybe according to doc type) and come out with a time schedule to close these items. It will definately take some time.. say weeks, to analyze each item and close it.
    4. Come up with a strategy so that so many documents are not kept open (unnecessarily) in the furture
    5. FI owners should have a relook whether the accounts managed under open item management are really required in OIM.
    In summary, no short cuts :(.
    Hope this helps,
    Naveen

  • Develop Module Advancements in Lightroom 4 | What's New in Lightroom 4 | Adobe TV

    Learn how to create the highest quality photographs by taking advantage of new and improved global and local adjustments in the Lightroom 4 Develop module.
    http://adobe.ly/x7mwOK

    load an image and open the tone curve panel (you already did this probably).  at the lower right of the canvas you'll see a button with "!" on it.  click the button to convert to "2012 process".  wait.  when it is done if you *still* don't see the channel dropdown click the "edit tone curve" button to hide the sliders and *then* you should see the channel dropdown.
    I found this totally mystifying, but once I found it (luck) I get it...new features, new entries in the database or some other magic.  anyway the video sure didn't give me a hint.
    this will be my 5th try posting an answer to your question, hopefully this time it will work, no thanks to support, 5 times resetting the password, etc etc.

  • Third party plug-ins for develop module

    It's been a while since this has been brought up, so I thought I'd restate this request in the current context.
    One of the major things that's missing from the Lightroom ecosystem is a way for third parties to produce plug-ins/extensions for the develop module. The advantages would be numerous:
    1) Ability to add exotic features that may not appeal to a large audience (although in combination all these features would), such as negative inversion, alternate tone curves, color correction and replacement tools.
    2) Third-party versions of features that users have been clamoring for: color space clipping, lens/perspective correction, multi-parameter noise reduction.
    3) Community buzz (if approached more openly than the Photoshop SDK)
    As for the implementation, maybe it's a good idea to let developers use a combination of Lua and PixelBender (2.0)? The combination would allow for platform-independent code that is still fast. Also, the plug-ins should get to choose from (at least) two entry points: (1) after demosaicing but before color mixing (B&W) & tone curve, and (2) at the end of the pipeline.
    Here's hoping for the SDK appearance in LR3!
    Simon

    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

  • Rendering issue in Develop Module

    Slow rendering has been discussed in many threads, but can anyone explain what is going on with this specific issue I am having?
    If I am working in the Develop Module and I render two raw files at 1:1, after the initial rendering delay I can generally toggle between the two and they are rendered almost instantaneously.   I assume this is because some info has been stored in the ACR Cache and Lightroom can quickly display them.  Now if I render a 3rd raw file at 1:1 and try to toggle between 3 images, one of them always needs 10 seconds or so to load/render.  What is happening here?  I thought the purpose of the ACR Cache was to allow for fast rendering of previously rendered images.  I currently have my ACR Cache set to 10GB and I have recently purged it, so I am nowhere near the limit.  Other system/software specs as follows:
    LR 5.2
    NEF files from Nikon D7100 (approx 30MB)
    iMac 27-inch 2560x1440
    OS 10.8.5
    Processor:  3.06 GHz Intel Core 2 Duo
    RAM:  16GB
    Video Card:  ATI Radeon HD 4670 (256MB)
    Storage:  1TB SATA 7200rpm, 25% full

    LanceBenedict wrote:
    Thanks for the explanation on the RAM caching.  If I am understanding you correctly on the ACR Cache, it sounds like it is essentially useless once you have applied some editing to the image because you need to wait on those edits to be rendered. 
    No, I wouldn't agree that it's useless. When you load an image into Develop you'll be presented first with a brief view of your Library preview, which should quickly be replaced with the ACR Cache "scene-referred" preview that will have any existsing edits applied before you see it. That should all happen quite quickly, and when that preview is loaded the sliders will be activated. When that happens you can start work, even though the full file is being rendered in background, and there is no need to wait until the "Loading" indicator goes out (as I said earlier, you can turn that off if you prefer).
    So the benefit of the ACR Cache entry is that it allows you to start work in Develop whilst the original file is still being fully converted.
    Note that although we are talking specifically about the ACR Cache entry, the same holds true for DNG Fast Load Data and/or Smart Previews. Which one of those 3 is initially used depends on what exists at the time of loading, and what file type is being used. But the same principle applies to all three.
    In terms of reducing the rendering time, that's a more problematical issue as there are various factors in the pipeline which come into play, any one (or more) of which may be sub-optimal. These factors include:
    1. Size of the files being loaded. It should go without saying that 36mp files from a Nikon 800 are going to take quite a bit longer that the 10mp files from say a Canon 40D.
    2. Location of the files and speed of the interface, i.e. expect image files on a USB2 connected hard drive spinning at 5400rpm to be a lot slower to load than if they were on a 7200rpm drive internally connected on a 6gb/s Sata hub.
    3. Once the data has been read, how fast is the CPU.....rendering a raw file will be quite a CPU-intensive task, so the faster the processor the better.
    4. User expectation.....one man's "painfully slow" could be another's "quite acceptable".
    With that in mind, I have no idea if what you are experiencing is "typical" or too slow. Putting it into context, all my original files are on a fast internal drive on a 3gb/s connection, I have an i7-930 quad-core processor (now over 3 years old, so not leading edge by any means), 12gb of RAM. Full loading times in Develop are now about 3 seconds per image when using 22mp files from a Canon 5D3.
    Looking at the things you've tried, purging the ACR Cache and increasing its size would have no effect unless:
    a) There was a problem with the existing cache, and
    b) You regenerated new cache entries
    Discarding old previews and rebuilding would have had no effect on Develop loading times, nor would downsizing the dimensions of the develop window.
    Increasing system RAM should certainly be beneficial to other areas of Lightroom, I'm just not sure it would have a specific benefit to image loading into Develop. That might be dependant upon what else was running in the system at the time.

  • Lightroom 2.3 crashes in Development module

    I am having a brand new problem with LR 2.2 & 2.3 with my Dell 730x 64bit 6GB Ram.  I am running VIsta Home Premium 64 bit.   I have been running LR 2 since it came out with no trouble - until a few days ago.
    I also have a Sony Monitor as the #1 Monitor on the Nvidea GeForce 9800 GT using the Generic PnP Monitor driver from Microsft - 6.0.6001.1800 dated 6/21/2006.
    I have a second monitor which I use for Lightroom: - Dell 2007FP Monitor with Nvidia GeForce 9800 GT Video card with all settings at defaults. The driver is NVIDIA v 7.15.11.7744 dated 7/17/2008. This was the original driver and has been performing well for months
    This has worked splendidly since I bought this high end PC in Feb, 2009.
    . In the last few days, however LR crashes any time I try to use the Develop module on the Dell monitor.  I get "Adobe Photoshop Lightshop 64 bit has stopped working" when I try to crop or use other tools at the top of the Develop list.  The lower tools like exposure changes the histrogram, but not the image. This also happens when I switch the driver on the Dell to the Generic PnP Monitor driver. This happens for NEF and JPG files.
    When I run Lightroom on the smaller Sony screen, the photos don't display - only gray rectangles for photos. However, in the Develop menu, when I try to crop a gray rectangle, the image appears and the crop works OK. When I finish the crop, the image goes back to a gray rectangle. It does not, however crash the program. This makes Lightroom unusable since photos and thumbnails are not visible. I believe this may have been happening for a longer time, but since it worked fine on the larger Dell screen, I was OK.
    All the rest of the LR modules seem to to work. .
    Here's a list of things I've tried with no success - they all resulted in the Develop Module crashing LR.
    The problem started a few days ago, so I went ahead installed the update to go from Service Pack 1 to Service Pack 2.  There was no diffrence.
    I have re-booted with only MS services - no others and no startup using msconfig - same problem
    I have deleted the preferences file and created a new one - no luck
    I have imported new files - same sympton
    I have loaded other catalogs - same sympton
    I have uninstalled 2.3 re- installed ver 2.2 - no luck
    I have uninstalled 2.3 and installed the 32 bit version of LR - same sympton
    I have run chkdsk on my drive - no problems, no difference
    I have removed the Develop Presets, External Editor Presets, Modules lrplugins, Local adjustment Presents from  AppData\Roaming|Adobe\Lightroom directory - no problem
    I have tried to use system restore several times  - to dates prior to recent windows updates, but system restore won't work???
    Photoshop CS4 64 and 32 bit work fine, but it doesn't have the speed of editing NEF files that LR does when it works.
    Any other ideas on what to try? I have completely changed my workflow to do 80%+ Lightroom and loved it. The thought of returning to Photoshop is devestating!

    FIXED!!
    Thanks for the suggestions from those who replied. I spent 90 minutes last night with the Dell support team who provided me with a previously unaccessable new driver for my NVIdia GeForce 9800 CT - this one was version 7.15.11.8130 dated 12/30/2008. They also provided me with the new NVidia Display Control Panel.   This program is in windows/system32/  and runs with the file name: nvsvc.exe.
    Two suggestions were to turn off this program. It was not running, and typically has not been running over the past few months. I started it to see if it made a difference. It did not.  Then I turned off and it still didn't change any LR problems. My guess is that there are some options that can mess stuff up, but I only had the defaults set.
    Another suggestion from KDWAVES: Gray rectangles when using the Sony monitor is a sympton of a corrupt color profile. If you use color calibration, try re-calibrating the Dell. If you are using the default color profile, try changing it.
    My Sony was using some default, so I loaded the Dell Monitor.icc color profile created by my color calibration hardware/software (Eye One Match v3) and appied to the Sony.  It worked and the gray images were displayed properly. Also all the Develop modules worked fine. I was a little disappointed, since the Sony is a smaller moniter and I bought the larger Dell Monitor specifically to be the color calibrated large monitor for photo editing.  So I moved lightroom to the Dell Monintor .....    AND IT WORKED GREAT!!   Thanks much KDWAVES!
    I had only calibrated the one monitor since both monitors were run by the NVidia video card and it seemed to only run one color profile at a time. I didn't bother to calibrate the Sony, but just adjusted the color controls manually to make the screen look like the Dell.  Now that both monitors have the same color calibration file, everything seems fine.
    I've listed all the details for the next person who gets this surprise. I still can't figure why it ran OK for the last few months, on the Dell monitor.
    I can't thank you guys enough for helping. Maybe the next victim won't take the five days it took me to unravel this one.
    This is my first Vista machine and I bought theVista 64bit version and the Intel Core i7:  quad & hyperthread processers for the Adobe 64bit software. When I'm not chasing bugs like this one, the machine and the Adobe software run REALLY FAST. I have been able to double my photo coverage since the Lightroom RAW file import / export / render / edit and everything goes about as fast I can click the keyboard - unlike any of the Adobe stuff has behaved on my prior PC's. I have even switched my sports photos to LR exclusively since it's so fast,
    P.S. CR Henderson's advice on a new Nvidia driver dated May 6th 2009 is great idea. I will be hunting for that next.  I have not had any Photoshop CS4 problems in either 32bit or 64bit versions (except not many plugins run in the 64 bit version). But I didn't buy this PC until I confirmed that my NVidia GeForce 9800 CT video card was on Adobe's approved list.

  • LR3 Fix for Crash when using Develop Module

    Adobe tech provided the following fix for my system which crashed when switching to the Develop module.
    This is the  response I received from Adobe Tech.  
    Recreating the preferences file corrected the problem.
    Their help was right-on and appreciated.
    Ed
    * to Customer**
    06/11/201018:11:12
    Hi Ed,
    Thank you for getting back to us. I appreciate your promptness in
    responding to our email.
    The information provided was really helpful in understanding the issue.
    In order to resolve this issue I would request you to perform the below
    mentioned steps in order to resolve this issue:
    * Remove Lightroom beta from your system as you have the the full
    purchase version Adobe Lightroom 3.0 (Because there may be conflicts
    between the Beta Version and original product)
    * Try to create new Catalog with some new images and check if you are
    facing the same issue with Develop module.
    * Check if other functions are working fine like Slideshow, Print, Web.
    If the problem still exist after removing the Lightroom beta version
    from your PC, then perform the below mentioned troubleshooting steps:
    * Re-create the Photoshop Lightroom preferences file.
    Re-create the Photoshop Lightroom 3.0 and 1.x preferences files to
    eliminate problems that a damaged preferences file might cause. If you
    do not delete your 1.x preferences as well as your 3.0 preferences,
    other issues may occur.
    To re-create the Photoshop Lightroom preferences file:
    1. Quit Photoshop Lightroom.
    1. Rename the Lightroom 3 Preferences.agprefs file (for example, to
    Lightroom 3 Preferencesagprefs.old) and the Lightroom Prefere
    nces.agprefs file (for example, to Lightroom Preferences.old) in the
    Documents and Settings/[Username ]/Application
    Data/Adobe/Lightroom/Preferences folder.
    1. Start Photoshop Lightroom. Photoshop Lightroom creates a new
    preferences file.
    If the problem continues, the preferences file isn't the cause. To
    restore custom settings, delete the new preferences file and restore the
    original name of the previous preferences file.
    * Also Send us the Image size and format on which your are working in
    Lightroom hence resulting in this issue.
    This should resolve your issue. If it does, please let us know, however
    in case it does not; please revert with any new information that you
    might want to add which will help us in resolving your issue.
    You can also try referring to our knowledge base and User to User forums
    by clicking on the following links:
    Knowledgebase: http://www.adobe.com/cfusion/search/index.cfm
    U2U Forums: www.forums.adobe.com

    Creating a new catalogue and importing the images does not resolve the problem.
    The problem is only occuring on a few images from a particular collection.
    Creating a virtual copy also will not edit in photoshop.
    Creating a virtual copy and reseting the develop settings will allow the ctrl-e command to work.
    However, manually re-applying the develop settings once again stops the ctrl-e command working.

  • BAPI_MATERIAL_MAINTAINDATA_RT gives error KM701, but manual entry succeeds

    I have written a program which creates a new material using function module BAPI_MATERIAL_MAINTAINDATA_RT. I get the following error:
    KM701 Profit center K100/12345 does not exist
    However, I can add the same profit center (12345) to the article in transaction MM42 without problems.
    I'm using the same user ID for the BAPI call (via RFC) and manual entry via MM42.

    you probably forgot the leading zeros for the profit center.

  • Using Develop module on NEF stops 'Edit in Photoshop' command from working.

    Started with LR5 CS6 CR8.1
    Suddenly when a raw image has been porcessed by the Develop Module the (ctrl-E) 'open in Photoshop' command does not work for that image. It works for images that have not been 'developed'.
    I have deleted LR preferences several times.
    I have upgraded to LR5.2RC and CR8.2RC.
    As far as I remember this catalog was new as LR5.
    Any ideas please?

    Creating a new catalogue and importing the images does not resolve the problem.
    The problem is only occuring on a few images from a particular collection.
    Creating a virtual copy also will not edit in photoshop.
    Creating a virtual copy and reseting the develop settings will allow the ctrl-e command to work.
    However, manually re-applying the develop settings once again stops the ctrl-e command working.

  • SOLUTION: LR2 Develop Module Keyboard Shortcuts

    Quick access to Develop and Library module adjustments via your keyboard number pad. You'll need www.AutoHotKey.com to use this script.
    >; --------------------------------------------------
    ; Gordon's Lightroom 2.0 Shortcuts Aug-11 2008
    ; www.night-ray.com
    ; Use numpad to perform certain develop and library functions.
    ; This effectively disables the number pad for digit entry
    ; (except 5 and 0) please use the main keyboard instead.
    ; Left/Right - Prev or Next photo
    ; Up/Down - Exposure
    ; Minus/Plus - Fill Light
    ; Page Up/Dn - Contrast
    ; Home/End - Color Temperature
    ; Div/Mult - Color Tint
    ; Enter - Paste Previous
    ; Dot (Delete) - AutoTone
    ; F9 Library Module
    ; F10 Develop Module
    ; F11 Slideshow Module
    ; F12 Web Module
    SetTitleMatchMode,2
    #IfWinActive, Lightroom
    F9::Send ^!1
    F10::Send ^!2
    F11::Send ^!3
    F12::Send ^!4
    #IfWinActive
    ; *** DEVELOP SHORTCUTS ***
    #IfWinActive, Lightroom - Develop
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrdAdd(09)
    numpad2:: lrdSub(09)
    NumpadAdd:: lrdAdd(11)
    NumpadSub:: lrdSub(11)
    numpad9:: lrdAdd(14)
    numpad3:: lrdSub(14)
    numpad7:: lrdAdd(04)
    numpad1:: lrdSub(04)
    NumPadMult:: lrdAdd(05)
    NumPadDiv:: lrdSub(05)
    NumPadDot:: Send ^u
    NumPadEnter:: Send ^!v
    lrdAdd(delta) {
    instance := lrGetControl( Static, "Treatment :", delta )
    ControlClick, Static%instance%
    Send {=}
    lrdSub(delta) {
    instance := lrGetControl( Static, "Treatment :", delta )
    ControlClick, Static%instance%
    Send {-}
    #IfWinActive
    ; *** LIBRARY SHORTCUTS ***
    #IfWinActive, Lightroom - Library
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrlClick(03)
    numpad2:: lrlClick(02)
    NumpadAdd:: lrlClick(11)
    NumpadSub:: lrlClick(10)
    numpad9:: lrlClick(23)
    numpad3:: lrlClick(22)
    numpad7:: lrlClick(-6)
    numpad1:: lrlClick(-7)
    NumPadMult:: lrlClick(-2)
    NumPadDiv:: lrlClick(-3)
    NumPadDot:: Send ^u
    NumPadEnter::Send ^!v
    lrlClick(delta) {
    instance := lrGetControl( Button, "Auto Tone", delta )
    ControlSend, Button%instance%, {SPACE}, ahk_class AgWinMainFrame
    #IfWinActive
    ; Fetch the Control Instance using Type, Title, and Instance Delta
    lrGetControl( type, title, delta ) {
    WinGet, ActiveControlList, ControlList, ahk_class AgWinMainFrame
    Loop, Parse, ActiveControlList, `n
    IfInString, A_LoopField, %type%
    ControlGetText, text, %A_LoopField%
    IfInString, text, %title%
    StringMid, controlbase, A_LoopField, 7
    controlbase := controlbase + delta
    return %controlbase%
    return 999999
    ; End

    Performance enhancement with caching:
    >; ----------------------------------------
    ; Gordon's Lightroom 2.0 Shortcuts Aug-12 2008
    ; www.night-ray.com
    ; Use numpad to perform certain develop and library functions.
    ; This effectively disables the number pad for digit entry
    ; (except 5 and 0) please use the main keyboard instead.
    ; Left/Right - Prev or Next photo
    ; Up/Down - Exposure
    ; Minus/Plus - Fill Light
    ; Page Up/Dn - Contrast
    ; Home/End - Color Temperature
    ; Div/Mult - Color Tint
    ; Enter - Paste Previous
    ; Dot (Delete) - AutoTone
    ; F9 Library Module
    ; F10 Develop Module
    ; F11 Slideshow Module
    ; F12 Web Module
    SetTitleMatchMode,2
    #IfWinActive, Lightroom
    F9::Send ^!1
    F10::Send ^!2
    F11::Send ^!3
    F12::Send ^!4
    #IfWinActive
    ; *** DEVELOP SHORTCUTS ***
    #IfWinActive, Lightroom - Develop
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrdAdd(09)
    numpad2:: lrdSub(09)
    NumpadAdd:: lrdAdd(11)
    NumpadSub:: lrdSub(11)
    numpad9:: lrdAdd(14)
    numpad3:: lrdSub(14)
    numpad7:: lrdAdd(04)
    numpad1:: lrdSub(04)
    NumPadMult:: lrdAdd(05)
    NumPadDiv:: lrdSub(05)
    NumPadDot:: Send ^u
    NumPadEnter:: Send ^!v
    lrdAdd(delta) {
    instance := lrGetControl( Static, "Treatment :", delta )
    ControlClick, Static%instance%
    Send {=}
    lrdSub(delta) {
    instance := lrGetControl( Static, "Treatment :", delta )
    ControlClick, Static%instance%
    Send {-}
    #IfWinActive
    ; *** LIBRARY SHORTCUTS ***
    #IfWinActive, Lightroom - Library
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrlClick(03)
    numpad2:: lrlClick(02)
    NumpadAdd:: lrlClick(11)
    NumpadSub:: lrlClick(10)
    numpad9:: lrlClick(23)
    numpad3:: lrlClick(22)
    numpad7:: lrlClick(-6)
    numpad1:: lrlClick(-7)
    NumPadMult:: lrlClick(-2)
    NumPadDiv:: lrlClick(-3)
    NumPadDot:: Send ^u
    NumPadEnter::Send ^!v
    lrlClick(delta) {
    instance := lrGetControl( Button, "Auto Tone", delta )
    ControlSend, Button%instance%, {SPACE}, ahk_class AgWinMainFrame
    #IfWinActive
    ; Fetch the Control Instance using Type, Title, and Instance Delta
    lrGetControl( type, title, delta ) {
    global lrLastControlBase, lrLastTitle, lrLastDelta
    if (lrLastTitle = title and lrLastDelta = delta)
    ; Cached! Saves time.
    return lrLastControlBase
    else
    WinGet, ActiveControlList, ControlList, ahk_class AgWinMainFrame
    Loop, Parse, ActiveControlList, `n
    IfInString, A_LoopField, %type%
    ControlGetText, text, %A_LoopField%
    IfInString, text, %title%
    StringMid, controlbase, A_LoopField, 7
    controlbase := controlbase + delta
    lrLastControlBase := controlbase
    lrLastTitle := title
    lrLastDelta := delta
    return %controlbase%
    return 999999
    ; End

  • Develop Module image reloading

    While editing a TIFF file in the Develop module, the image keeps reloading (image flashes off and on), and the adjustment sliders revert to neutral settings. Makes any editing very diffficult!  Windows 7  64-bit   8 GB Ram.  Help!

    You probably have <Automatically write changes into xmp> checked in >Edit >Catalog Settings >Metadata tab.
    With this setting every step you do in the Develop Module is written into xmp, and Lr then immediately reloads the image.
    This behavior occurs with TIFFs and PSDs, but not with Raw images.
    The solution: Uncheck the box <Automatically write changes into xmp> when working with TIFFs.
    If you need xmp files - which are not necessary for Lr to work properly - you still can save manually to xmp by pressing Ctrl / Cmd + S after you finish editing a TIFF.
    You can do this manual save for a batch of images by selecting them in the Grid View and then pressing Ctrl / Cmd + S.

  • LR 3.2 Develop module not fluent but CPU not fully taxed

    Hello,
    on my AMD Phenom II X6 2.8GHz (Windows 7 Home Premium 64Bit, 4GB RAM) I experience LR3.2(64Bit)'s Develop module not to be really fluent. Esp. manual lens correction is sluggish. I expected the CPU to be fully taxed but I only see all 6 cores at 55-70% load. I tried overclocking the CPU to 3.2GHz but it doesn't really help. The CPU load decreases to 45-60% but there is not so much of a performance difference. I don't see a difference when I switch off writing metadata to files either. I also tried to exclude JPG, CR2 and lrcat files from the virus scanner's plan. LR uses around 950MB of ram. The catalog is around 15000 files large and I work on Canon 15MP CR2 raws (around 20MB/file).
    Any idea what I could do?
    best regards,
    Fabian

    Samoreen wrote:
    Hi,
    bob frost wrote:
    IME a lot of this slow response to sliders etc is due to graphics card and driver problems.
    Sorry Bob but I fully disagree with this. Most people having these problems with LR3 have up-to-date drivers and powerful systems. Moreover, what if Photoshop CS5, DxO Optics Pro, Bibble 5, LightZone,... work normally without any performance issue on a given system and LightRoom drives you nuts because it sometimes becomes so slow on the very same system? How could one explain that on the same system where the same display drivers are installed, LR 2 works with acceptable performances while LR 3, which is supposed to enhance these performances, brings the system down to its knee under some  circumstances?
    Finally, these performance problems are almost always appearing when using local adjustements on the Mac and on the PC. And this should be caused by a display driver that is not up-to-date?
    I regret that Adobe have been totally quiet about these problems since they appeared and especially since the release of LR 3.2. It's obviously a bug (or a series of bugs) and they could at least advertise that they are working on a fix.
    You can have the most up-to-date graphics drivers and the most powerful systems, but still suffer from bugs in the graphics drivers. Just have a look at the release notes for the latest nVidia graphics http://http://uk.download.nvidia.com/Windows/260.89/260.89_Win7_WinVista_Desktop_Release_N otes.pdf
    This very lengthy document lists all the problems that have been solved and those that are still unsolved, and you will see that the driver has problems with some programs (games mainly) and not others, runs faster with some games and not others, has problems with some graphics cards and not others, etc. It is an absolute minefield of bugs/problems.
    I'm not saying that Adobe can't get round some of these problems themselves, as they have done in the past, and they have co-operated with nVidia in the past to solve some of the problems. They are probably still doing so.
    Local adjustments have always been the achilles heel of LR; when you read how they are done, it is not surprising that anyone expecting to do loads of local adjustments runs into problems eventually. Personally, if an image needs a lot of local adjustment, I take it into Photoshop, which is better able to do this sort of work because of the fundamental difference in the way the program works. Horses for courses!
    If you have a nVidia card, and go to the nVidia Control Panel, under 3D settings you will see a long list of variables that can be altered, and the panel has preselected sets for different programs and games. A long time ago, people showed that some of these settings had a big effect on LightRoom performance.
    I'm sure Adobe is working on all the problems that they know about, and that the next version of LR will have fixes for some of the problems. But they won't cure all of them any more than nVidia, which still has loads of problems in driver version 260! LR is only in version 3 (Photoshop is in version 11).
    Bob Frost

  • Lightroom 2.x - Remapping Library / Develop module keyboard shortcuts (Windows)

    SOLUTION: LR2 Library/Develop Keyboard Shortcuts
    Prepared by: Gordon McKinney
    http://www.night-ray.com
    For windows users - this is the latest update to my keyboard shortcuts for Library and Develop module. It has improved performance through caching.
    Quick access to Develop and Library module adjustments via your keyboard number pad. You'll need
    www.AutoHotKey.com to use this script.
    ; Gordon's Lightroom 2.0 Shortcuts Aug-22 2008
    ; www.night-ray.com
    ; Use numpad to perform certain develop and library functions.
    ; This effectively disables the number pad for digit entry
    ; (except 5 and 0) please use the main keyboard instead.
    ; Left/Right - Prev or Next photo
    ; Up/Down - Exposure
    ; Minus/Plus - Fill Light
    ; Page Up/Dn - Contrast
    ; Home/End - Color Temperature
    ; Div/Mult - Color Tint
    ; Enter - Paste Previous
    ; Dot (Delete) - AutoTone
    ; F9 Library Module
    ; F10 Develop Module
    ; F11 Slideshow Module
    ; F12 Web Module
    SetTitleMatchMode,2
    #IfWinActive, Lightroom
    F9::Send ^!1
    F10::Send ^!2
    F11::Send ^!3
    F12::Send ^!4
    #IfWinActive
    ; *** DEVELOP SHORTCUTS ***
    #IfWinActive, Lightroom - Develop
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrdAdd(09)
    numpad2:: lrdSub(09)
    NumpadAdd:: lrdAdd(11)
    NumpadSub:: lrdSub(11)
    numpad9:: lrdAdd(14)
    numpad3:: lrdSub(14)
    numpad7:: lrdAdd(04)
    numpad1:: lrdSub(04)
    NumPadMult:: lrdAdd(05)
    NumPadDiv:: lrdSub(05)
    NumPadDot:: Send ^u
    NumPadEnter:: Send ^!v
    lrdAdd(delta) {
    instance := lrGetControl( Static, 6, "Treatment :", delta )
    ControlClick, Static%instance%
    Send {=}
    lrdSub(delta) {
    instance := lrGetControl( Static, 6, "Treatment :", delta )
    ControlClick, Static%instance%
    Send {-}
    #IfWinActive
    ; *** LIBRARY SHORTCUTS ***
    #IfWinActive, Lightroom - Library
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrlClick(03)
    numpad2:: lrlClick(02)
    NumpadAdd:: lrlClick(11)
    NumpadSub:: lrlClick(10)
    numpad9:: lrlClick(23)
    numpad3:: lrlClick(22)
    numpad7:: lrlClick(-6)
    numpad1:: lrlClick(-7)
    NumPadMult:: lrlClick(-2)
    NumPadDiv:: lrlClick(-3)
    NumPadDot:: Send ^u
    NumPadEnter::Send ^!v
    lrlClick(delta) {
    instance := lrGetControl( Button, 6, "Auto Tone", delta )
    ControlSend, Button%instance%, {SPACE}, ahk_class AgWinMainFrame
    #IfWinActive
    ; Fetch the Control Instance using Type, Title, and Instance Delta
    lrGetControl( type, typeLen, title, delta ) {
    global lrLastTitle, lrLastCBase, lrLastCache
    if (lrLastTitle = title and lrLastCache > A_TickCount )
    ; Cached! Saves time.
    return lrLastCBase + delta
    else
    WinGet, ActiveControlList, ControlList, ahk_class AgWinMainFrame
    Loop, Parse, ActiveControlList, `n
    IfInString, A_LoopField, %type%
    ControlGetText, text, %A_LoopField%
    IfInString, text, %title%
    StringMid, controlbase, A_LoopField, typeLen+1
    lrLastTitle := title
    lrLastCBase := controlbase
    lrLastCache := A_TickCount + (120*1000)
    return controlbase + delta
    return 999999
    ; End

    latest update... I will work on making the script 'adapt' the LR's changing control IDs. However develop seems reliable. Until then - use this version
    >; --------------------------------------------------
    ; Gordon's Lightroom 2.0 Shortcuts
    ; www.night-ray.com
    SetTitleMatchMode,2
    #IfWinActive, Lightroom
    ; Remap F keys for module change
    F9::Send ^!1 ; F9 Library Module
    F10::Send ^!2 ; F10 Develop Module
    F11::Send ^!3 ; F11 Slideshow Module
    F12::Send ^!4 ; F12 Web Module
    #IfWinActive
    ; *** DEVELOP SHORTCUTS ***
    #IfWinActive, Lightroom - Develop
    ; Use numpad to perform certain quick develop functions
    ; This effectively disables the number pad for digit entry
    ; please use the main keyboard instead.
    ; Left/Right - Prev or Next photo
    ; Up/Down - Exposure
    ; Minus/Plus - Fill Light
    ; Page Up/Dn - Contrast
    ; Home/End - Color Temperature
    ; Div/Mult - Color Tint
    ; Enter - Paste Previous
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    numpad8:: lrAdd( "Static144" )
    numpad2:: lrSub( "Static144" )
    NumpadAdd:: lrAdd( "Static146" )
    NumpadSub:: lrSub( "Static146" )
    numpad9:: lrAdd( "Static149" )
    numpad3:: lrSub( "Static149" )
    numpad7:: lrAdd( "Static139" )
    numpad1:: lrSub( "Static139" )
    NumPadMult::lrAdd( "Static140" )
    NumPadDiv:: lrSub( "Static140" )
    NumPadEnter::Send ^!v
    lrAdd(class) {
    ControlClick, %class%
    Send {=}
    lrSub(class) {
    ControlClick, %class%
    Send {-}
    #IfWinActive
    ; *** DEVELOP SHORTCUTS ***
    #IfWinActive, Lightroom - Library
    numpad4:: Send ^{Left}
    numpad6:: Send ^{Right}
    NumPadEnter::Send ^!v
    #IfWinActive
    ; End

  • I use a Mac, new to lightroom, I purchased the software, and now I cannot get into my develop module because it is telling me that I need to renew my membership ?  Lost !!!  lost in a dark cold cave of lightroom someone please help me !!

    I cannot get into my develop module on lightroom, it is telling me to "please renew my membershipto reactivate the develop module"  I do not understand.  I bought the software must I pay a membership as well ?  Also I do not want to use lightroom mobile and it is trying to sync my photos.  I use a MAC

    Did you purchased the Full Perpetual License from Adobe for $149.00?, if so then what has happened is that you probably downloaded the Creative Cloud trial version which has now expired.
    The license key for the perpetual version will not be accepted to activate the CC version.
    Uninstall the existing Lightroom and then download the one available from the link below. The uninstall process will not affect your Catalog, Preferences or personal files but will just remove the application. Install the new download and you license key will be accepted.
    Adobe - Lightroom : For Macintosh : Adobe Photoshop Lightroom 5.6
    If this is not the situation you face then provide some more details.

Maybe you are looking for