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.

Similar Messages

  • 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.

  • Lightroom 3.0 Develop Issue: Can't Access Develop Module

    Hello.  Need to tap you guys' expertise!
    Went into develop module on my Lightroom 3.0 run on Windows Vista.  Did some editing with the color, closed the color I was working with, opened and used a new color, went to erase and the pic disappeared!  Screen faded.  I closed the program, re-entered my LR and this message showed up on a wide empty screen:
    ?:0:attempt to compare number with string
    I exited the message box and went into my Library.  Then, after finding pics, hit the develop module tab, would not come up.  Same message appeared.  I can access everything else in my LR but the develop module.  I have tried to reboot the computer and re-access LR, not successful as message still appears.  Tried closing and re-opening LR, but the same thing happens.  Not sure what happened as this never happened to me before.
    Can anyone offer any insight as to what may have happened and what I can do to fix this problem?  I am pulling my hair out as I have pics to finish and cannot make any changes on any of them!  Ugh!  HELP!!!!!     Grrrrrr...........

    Just wanted to point out that re-installing Lightroom hardly ever solves a problem.
    Updating to the latest version usually will do.
    Should the preference file deletion not solve the issue, try to create a new catalog and just import the images you need to get ready urgently.
    Better to start over with them than not getting anything done.
    You can always import from this partial catalog afterwards, when you  will have restored the rest.
    This should address catalog corruption.
    For same root cause you could also try your last backup(s) of catalog.
    User presets could be the culprit, as well (move them hiding from LR).
    Worst case: LR is an early detection means for damaged RAM...
    I wish you a speedy solution,
    Cornelia

  • Develop module, 1:1 and Export don't look the same, color issues

    Hi everybody
    I'm using the last version of Lightroom (3.6 if I'm not wrong) and I'm facing a very uncomfortable issue with the Develop module.
    I adjusted precisely every color luminance and saturation so it looks rather good in the Develop preview (set to fit), and did an export...
    The preview I worked on and the export simply don't look the same.
    I work with NEF files from my NIKON D3100 DSLR on a Mac OSX 10.7 MBP.
    This cannot be the external display profile not correctly adjusted since I viewed every pictures on the same screen.
    I unchecked every boxes from the presets tab in the settings window.
    Here are some screenshots and exports.
    Fit preview in the Develop module (left) and the actual export of the same picture (right)
    Please note I didn't activated any lens correction option and adjusted any color. This is the RAW file and its direct export.
    Screenshot of the preview window on top of noise correction options (left) and the same area once I zoomed in in the main preview (right)
    I hope this can be corrected or I'm doing something wrong.
    A couple of days before today I was using Camera RAW from PS CS5 to correct my NEF and was only keeping exports in JPEG. I decided to use LR 3 on my entire workflow and I'm being skeptical...
    Oh right and please forget about every single mystake in my post, I'm a french student.
    Thanks !
    EDIT : i can join any required file or screenshot if required. I have some other shots having tthe same issue (a lot of ones indeed...)
    EDIT 2 : i just found out the picture has much more acurate colors (relatively to the export ones) in the Library module in fit preview (Loupe I guess)

    I have the problem on another photo.
    I made a screenshot on the screen of my MBP, but it looks the same on any other screen :
    Here is the export config :
    If you need any other information I can send you them.

  • Hello, my develop module has been disabled at the end of the trial period but I have purchased Creative Cloud 2 days ago.  Anyone have any assistance on this issue?

    How do I reactivate my develop module? I already have Creative Cloud but it keeps telling me to renew my membership.

    You will have to clear the cache mentioned on this advisory:
    Lightroom doesn't launch or returns "Develop module is disabled" error after 5.5 update

  • Lightroom 2015 cc Develop module Display issue

    I have just upgraded to Lightroom 2015 cc.
    When I go into the develop module, it will not display the image, I just get a solid blue image.
    I can see the image in the navigator panel and if I go full screen, plus you can see it in the library module.
    I have tried creating a new catalog, but the same thing happens again

    <moved from Creative Cloud Download & Install to Photoshop Lightroom>

  • Images in library module aren't as sharp compared to develop module.

    For some reason images in the library module aren’t as sharp compared to the develop module. If I’m in develop images are nice and sharp but as soon as I select the library you can see the image quality drop and image becomes less blurry!
    I’ve had a look on here and other people have this issue and I’ve tried the various fixes suggested with no success at all.

    It sounds like the library module is using a lower quality preview. If you are using minimal or embedded previews, they could look different than what you saw in the Develop module. Do other changes you make seem to be in the preview, just lower quality? Like if you applied a heavy vingette, do you see the that in the preview? If you don't, that could mean LR isn't updating the previews it uses in the Library module and you might want to look and purging your cache. If you do, try rendering a 1:1 preview for the image and see if the preview looks better.
    Another thing to check is to make sure your standard preview size is appropriate for the size of your monitor. If you've got a huge monitor but have a small preview size, you'll notice a difference.
    Choose Edit >  Catalog Settings (Windows) or Lightroom > Catalog Settings (Mac OS), and then select File Handling.
    For Standard Preview Size, choose the amount that is closest to the longest edge of your screen resolution, but not shorter than it. For example, if your screen resolution is 1920 x 1200 pixels, choose Standard Preview Size > 2048 Pixels.
    For Preview Quality, choose Low or Medium, which equates to the low- or mid-range of the quality scale for JPEG files.

  • Develop Module: Inaccurate Preview in Detail

    So the develop module is producing a different rendering than the library module is in regard to sharpening and noise reduction.  In develop the image is extremely blurry where in loupe view it seems to be previewed correctly. So I tested by bringing the image into PS (cmd+E) but processing the DNG in LR.  I then quit PS, leaving an untouched PSD that should be identical to the DNG. In Loupe view the DNG is close to identical, though still a little softer. In develop, the DNG is obviously more blurry than the PSD.  So I pulled my preview file, forcing LR to re-render the previews and the images were the same as before.
    PSD in Develop:
    DNG in Develop:
    PSD in Loupe:
    DNG in Loupe:
    This issue is making it really dificult to perform sharpening and noise reduction.

    There are two issues. One there is a bug with the rendering in Develop in LR 3. After you move a slider, the develop view will lose all sharpness only to regain it after zooming in and out to 1:1. See this thread: http://forums.adobe.com/message/2898311#2898311
    No solution for this yet. The Develop view is supposed to now be able to give you a preview of what the image should look like after proper output sharpening, but it doesn't really do that correctly yet.
    The second issue is that you should NEVER try to optimize sharpening (and noise reduction) in the Fit/Fill zoom views. You should only do this at 1:1. The reason is that the sharpening is supposed to be a capture sharpening meant to deal with loss of sharpness due to the demosaic process and some lens blur, meaning that it works at the pixel level, not at the very low res zoomed out level. Do not attempt to deal with sharpness at the scaled down level. This is done at the export stage and has to be done in different levels depending on the output medium (screen or print). You cannot accurately preview capture sharpening and noise reduction in a zoomed out view. It is just physically impossible due to the low res display.
    Lightroom does not show capture sharpening and noise reduction in Develop in anything but the 1:1 (and higher) zoom levels in order to make the program usable. It would be completely glacially slow if it would have to rerender the entire image at 1:1 (otherwise the sharpening has no real effect) including all the settings you apply and scale down for display. Even on the fastest computers that would take a few seconds and be unacceptably slow as a result. In Library you see some effect because the view in Library is rendered from a jpeg preview, not from the original data. This makes it much faster to display, but not as accurate.

  • Do we need a Library and Develop Module?

    Do we really need a Library and Develop module? There's lots of dissatisfaction with Lightroom speed and one of the problem areas is when switching from Library, when in standard preview or 1:1, to Develop and the 'loading' message appears or as on my mac the dreaded spinning beach ball goes crazy. Even with all the previews created it's still slow.
    So, if we have a standard preview or 1:1 loaded why can't we automatically be ready to apply any adjustments and save an extra step to another module? The quick develop in the library seems unnecessary and I've never used it. That leaves the metadata and keywording panels requiring a new location, but again these are not something I need to refer to on a regular basis.
    Anyone else any similar thoughts?

    > ...but I'm pretty darn sure there won't be any back-stepping to REMOVE or substantially alter LR's basic premise...pretty sure Develop will always be about dealing with a single image adjustment (and applying that adjustment to other images if you wish).
    And I'm okay with this premise, but it needs additional functionality, such as the ability to apply relative adjustments. It already has this via the keyboard shortcuts while hovering. It just needs a UI adjustment (I once did a mockup of this, and I think it works) and the ability for autosync to recognize them as relative adjustments to the other images.
    It also needs additional views. Grid, survey and compare would be nice, but you're only adjusting a single image's RAW data rendering at a time - the others are shown as previews and adjustments to them are rendered that way (like Library does).
    The issue is, many people like me end up switching modules far too often. I generally go back and forth between Library and Develop hundreds of times per day. That's way too many times to be suffering the module-switching penalty. I'd prefer to select the images I'm working on in Library, and never see that module again until I'm done working on them. For now, grid and survey are too often needed, and so are relative adjustments.
    Develop already has most of the needed functionality. Relative adjustments are already available to one image, a grid is available but only at 1 row (film strip supplied by Library) and a quick-render (the image in the upper left) is available as well. This just needs to be expanded and adjusted so that going back and forth to Library isn't as necessary as it is now. Ideally, you'd import in Library, to your metadata stuff there or in other related modules, choose the image group you want to work on using filters/folders/collections/find, then go to Develop and work on them until you are done.

  • Lightroom 5.4 64-bit crashes when switching to develop module (and during random other functions)

    This seems to be a new issue that has developed over the past few days. I have been using Lightroom for multiple years without too many issues. Within the last 90 days I have upgraded to Lightroom 5. Today, upon loading up Lightroom (either 3.6 or 5.2) they both crash upon switching over to the develop module. I have upgraded 5.2 to 5.4, uninstalled 3.6, restarted my computer; still crashes with error message: "Adobe Photoshop Lightroom 64-bit has stopped working - A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." Which upon clicking "Close Program" it simply closes the program. Any ideas as to why this is happening and a possible fix? This is greatly impacting workflow. Following is a copy of my System info from Lightroom.
    Lightroom version: 5.4 [955652]
    Operating system: Windows 8.1 Home Premium Edition
    Version: 6.3 [9600]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 2.3 GHz
    Built-in memory: 7944.2 MB
    Real memory available to Lightroom: 7944.2 MB
    Real memory used by Lightroom: 298.6 MB (3.7%)
    Virtual memory used by Lightroom: 268.0 MB
    Memory cache size: 103.5 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.4
    Library Path: C:\Users\Joshuah\Pictures\Lightroom\Lightroom 5 Catalog.lrcat
    Settings Folder: C:\Users\Joshuah\AppData\Roaming\Adobe\Lightroom
    Installed Plugins:
    1) Behance
    2) Canon Tether Plugin
    3) Facebook
    4) Flickr
    5) Leica Tether Plugin
    6) Nikon Tether Plugin
    Config.lua flags: None
    Adapter #1: Vendor : 8086
        Device : 416
        Subsystem : fa721179
        Revision : 6
        Video Memory : 0
    Adapter #2: Vendor : 1414
        Device : 8c
        Subsystem : 0
        Revision : 0
        Video Memory : 0
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (Conexant SmartAudio HD)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    CardID: 1046
    Direct2DEnabled: false
    GPUDevice: D3D
    MaxTexture2DSize: 8192
    OGLEnabled: true
    Renderer: Intel(R) HD Graphics 4600
    ShaderModel: 11.1
    Vendor: Intel
    VendorID: 32902
    Version: 8086:0416:fa721179:0006

    I have had this same issue now. I have been away from my pc for a week or so and now i cannot use the Develop button
    Lightroom version: 5.4 [955652]
    Operating system: Windows 7 Business Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 3.5 GHz
    Built-in memory: 32651.3 MB
    Real memory available to Lightroom: 32651.3 MB
    Real memory used by Lightroom: 366.3 MB (1.1%)
    Virtual memory used by Lightroom: 328.1 MB
    Memory cache size: 205.9 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080, 2) 1920x1080, 3) 1920x1080
    Seeming this seems to have stopped around the 21st of May and its now the 9th of June, does this mean we just do nothing about it and hope and pray that one day Adobe, who are very quick to take our money every month, can resolve this ? Has there been a fix noted for this yet ?

  • Strange phenomenon when scrolling through develop module images in LR6

    I just upgraded to LR6 and so far like what I see as far as performance increases.
    Noticed a strange phenomenon today while scrolling through the images in the develop module. These are all rendered images with a preset applied to them.
    I notice when I use the arrow key to go to the next image, the image first displays very "flat" or basic and then the rendered image appears a second or two later. If I scroll back the image displays normal rendered.
    It is only when I go about 2-3 images back it starts to display the same issue of non-rendered to then a rendered image. If I scroll forward to images I have not seen yet it does the same thing of showing a non-rendered image to a rendered image.
    I think I narrowed this down to the "Use the graphics processor" option. If I turn this off  the image loads a lot slower but only displays the rendered version and not the flat and then rendered version.
    Turning the GPU option back on immediately does the dual image version. Strange and hard to explain but not sure if anyone else has seen this.
    Here are my system specs from the LR Performance tab:
    Lightroom version:  CC 2015 [1014445]
    License: Creative Cloud
    Operating system: Windows 8.1 Business Edition
    Version: 6.3 [9600]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 16
    Processor speed: 2.6 GHz
    Built-in memory: 32691.8 MB
    Real memory available to Lightroom: 32691.8 MB
    Real memory used by Lightroom: 4451.9 MB (13.6%)
    Virtual memory used by Lightroom: 4594.8 MB
    Memory cache size: 6002.1 MB
    Maximum thread count used by Camera Raw: 8
    Camera Raw SIMD optimization: SSE2,AVX
    System DPI setting: 144 DPI (high DPI mode)
    Desktop composition enabled: Yes
    Displays: 1) 3840x2160
    Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
    Graphics Processor Info:
    GeForce GTX 680/PCIe/SSE2
    Check OpenGL support: Passed
    Vendor: NVIDIA Corporation
    Version: 3.3.0 NVIDIA 350.12
    Renderer: GeForce GTX 680/PCIe/SSE2
    LanguageVersion: 3.30 NVIDIA via Cg compiler
    Application folder: C:\Program Files\Adobe\Adobe Lightroom
    Library Path: E:\Lightroom Catalog\Lightroom CC\Lightroom CC.lrcat
    Settings Folder: C:\Users\Toby\AppData\Roaming\Adobe\Lightroom
    Installed Plugins:
    1) Adobe Revel Plug-in
    2) Behance
    3) Canon Easy-PhotoPrint Pro
    4) Canon Print Studio Pro
    5) Canon Tether Plugin
    6) Facebook
    7) Flickr
    8) HDR Efex Pro 2
    9) Perfect B&&W 8
    10) Perfect Effects 8
    11) Perfect Enhance 8
    12) Perfect Photo Suite 8
    13) Perfect Portrait 8
    14) Perfect Resize 8
    15) Show Focus Points
    16) Upload To Pictage
    Config.lua flags: None
    Adapter #1: Vendor : 10de
      Device : 1180
      Subsystem : 96910de
      Revision : a1
      Video Memory : 1987
    Adapter #2: Vendor : 1414
      Device : 8c
      Subsystem : 0
      Revision : 0
      Video Memory : 0
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (SB Recon3D PCIe)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    Direct2DEnabled: false
    GPUDevice: not available
    OGLEnabled: true
    Thanks for any thoughts,
    Toby

    Here is where you asked this before:
    http://www.adobeforums.com/webx/.59b79139/0

  • Noise reduction won't display properly in LR 3.4.1 Develop Module

    I encountered this issue first time last night - noise reduction will not show in "Fit" view of the Develop module for pictures that have a graduated filter applied as well. Having said this,
    - The pictures display correctly in Library Loupe view (Fit and 100%)
    - The pictures display correctly in Develop module when zooming in to 100%
    - The pictures display correctly in Develop module when clicking in history on Luminance smoothing (first picture). Selecting the next step in the history, Add Graduated Filter, displays the picture without noise reduction (second picture - I tried on a virtual copy the other way round - first have a graduated filter and then apply noise reduction, but doesn't work either. Noise reduction just won't display in Develop module / Fit View once a graduated filter is applied as well.
    Has anyone else seen this behaviour or, even better, found a solution? I already tried purging the raw cache, no success. Working on Windows 7 / 64bit.
    Thanks,
    Andreas

    Jeff, I had difficulty understanding this same issue as presented at the link I posted above. With my low-noise Canon DSLR RAW images I simply couldn't see the onscreen rendering issues they were talking about. It even appeared this might be unique to Mac platforms and Windows 32 bit OS, since my Windows 7 64bit system didn't appear to have this issue.
    Following suggestions to shoot a picture at -4 F stops and then increase exposure by +4 F stops in LR helped me get a better understanding:
    http://forums.adobe.com/message/3857767#3857767
    Granted this is an extreme shooting situation, but it helps demonstrate what happens when using exposure, fill and HSL sliders to increase exposure significantly (+2 to +4 EV) in specific areas of the image. Now you have noise that will be visible in smaller exported scaled images, perhaps even those sized for posting to the web.
    The issue is at lower ISO settings (camera specific), view sizes less than 1:1 have no noise reduction applied (Mac & Windows) or sharpening applied (Mac & Windows 32). There appear to be platform differences in the way sharpening is applied, because on my Windows 7 64bit system sharpening is applied at all ISO and all view sizes including "fit" view, but noise reduction is only applied at higher ISO settings – the same as all others have described. I wanted to point this out since it is one of the reason I had difficulty duplicating what the OP was seeing.
    We know sharpness and noise reduction settings interact with each other, so it is important to have both applied in the onscreen image to determine their affect. Using images with additive Exposure, Fill and HSL slider settings approaching +2 to +4 EV, there is simply no way to see accurate rendering without both noise reduction and sharpness applied at all view sizes, including “fit” view. This can occur with low ISO images, not just at some predetermined camera specific high ISO where noise becomes predominant.

  • Lightroom 5 Develop Module Not Responding

    The LR5 develop module will flash not responding after about 5 minutes of use.  I have to shut down LR and restart it to get it to respond, but it gets kind of old having to do it every 5 minutes.  Photoshop CS6 had the same issue with ATI drivers and, as far as I know, that issue has not been resolved.  The workaround was to turn off hardware rendering, but there is no option, that I can find, in LR to do that.  Anyone else experiencing the same issue?  Any temporary solutions other than dropping ATI altogether?
    System Info:
    OS Name
    Microsoft Windows 7 Home Premium
    Version
    6.1.7601 Service Pack 1 Build 7601
    Other OS Description
    Not Available
    OS Manufacturer
    Microsoft Corporation
    System Name
    JOHN-PC
    System Manufacturer
    Gigabyte Technology Co., Ltd.
    System Model
    GA-880GA-UD3H
    System Type
    x64-based PC
    Processor
    AMD Phenom(tm) II X6 1055T Processor, 2800 Mhz, 6 Core(s), 6 Logical Processor(s)
    BIOS Version/Date
    Award Software International, Inc. F7, 11/24/2010
    SMBIOS Version
    2.4
    Windows Directory
    C:\Windows
    System Directory
    C:\Windows\system32
    Boot Device
    \Device\HarddiskVolume1
    Locale
    United States
    Hardware Abstraction Layer
    Version = "6.1.7601.17514"
    User Name
    John-PC\John
    Time Zone
    Eastern Daylight Time
    Installed Physical Memory (RAM)
    16.0 GB
    Total Physical Memory
    16.0 GB
    Available Physical Memory
    12.4 GB
    Total Virtual Memory
    32.0 GB
    Available Virtual Memory
    28.3 GB
    Page File Space
    16.0 GB
    Page File
    C:\pagefile.sys
    Video
    Adapter Type
    AMD Radeon Graphics Processor (0x68D9), Advanced Micro Devices, Inc. compatible
    Adapter Description
    ATI Radeon HD 5570
    Adapter RAM
    1.00 GB (1,073,741,824 bytes)
    Installed Drivers
    aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dl l,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Driver Version
    12.104.0.0

    If lightroom downloaded and installed without any errors, you will get better help with program questions in the program forum
    If you start at the Forums Index http://forums.adobe.com/index.jspa
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll
    http://forums.adobe.com/community/lightroom

  • LR3 "Develop Module" slowing related to noise removal

    Hi all. As many fellow early adopters to the full release of Lightroom 3, I have been experiencing very slow rendering and response times when editing in the Develop module. I am on a very powerful machine that meets and exceeds the requirements by a long shot--quad core, 8 gigs ram, 64bit win7 and a solid state drive. There is absolutely no reason on my end that I should be experiencing any kind of slowing, especially when I would get a flawless experience in LR 2.x, and even the early LR3 betas.
    So I did some fiddling and I believe I may have pinned the slowing down to the adjustment brush, and even more so with the new noise removal. It appears the algorithm being used in the new noise removal tool is a system resource hog. I ran a few "tests" to see if the issue is in fact related to noise removal, and it seems so. When I have an image open at default settings, there is no visible render time--its instant. But when I add noise, I find the render time to jump exponentially. Every 10% increase on the slider adds about half of a second on the render time, and my CPU usage jumps, and likewise I see an increase in memory usage. The higher on the slider, the slower the render time and the more memory is being used.
    What I suggest for everyone experiencing the slow loading times is to entirely disable noise removal while editing, and see if it results in faster editing. If the noise removal IS the culprit, wait until you have edited all of your images in a set and then copy the noise removal onto each image in a batch as the very last step before exporting for print/web. 
    Hope this helps others, as it truly did help me.

    JayS In CT wrote:
    No problem..  would be interested in what you find turning it on and off on your machine.
    Sadly, turning it off doesn't help me. I haven't tried to not use it instead of using it and turning it off afterwards yet, but I suspect that won't make a difference either.
    I'm experiencing terrible lag with the adjustment brush on images where I have done lots of edits already. I create a stroke and 2 seconds afterwards it is actually drawn.
    Playing with your suggestion, I discovered that I can address the lag by reducing the image size. Either exiting "full screen" mode and making the program window rather small or by adding the film strip back to the Develop view, I can reduce the lag to the standard "not ideal since not immediate but acceptably fast" speed.
    I've read elsewhere that reducing the displayed image size addressed performance issues.
    I haven't tried to use "1:1 previews" whether these may make the perfomance image display size independent.
    I hope this issue will be fixed in the future. It is so nice to be able to switch off the top and bottom panel (sometimes even the left side panel) in Develop mode. It would be bad to be forced to have them all in -- or even exist "full screen" mode -- just to address the performance issue.
    As for the Flickr issue, did you let Adobe know formally?
    I have just submitted an official bug report.
    During the BETA forum days that didn't seem to be necessary as Community Professionals would try to reproduce bugs and then forward them on to the programmers. They also confirmed that they did it. That was really nice.

  • Histogram Edit Delay in Develop Module in LR5.2

    Hello Everyone!
    I have been using Lightroom from version 4 without any issues. I have updated to LR5 and love the app, but I have problem in the develop module.
    I load a RAW file pretty quickly and every edit I make on the photo is very quick, apart from the Histogram. For every image the histogram is loaded istantly, however I cannot do any modification for the first 4/5 seconds.
    When having to deal with large amount of images (I shoot weddings and events as well), multiplying 500 images for 5 seconds means 45 minutes lost.
    My machine performs well and I have no other slowdowns.
    Anyone with a possible solution? This is driving me crazy!
    Carlo

    Bob,
    You have me at a disadvantage because other than "Undo" I know of no way to "clear" individual edits in an image. Sure you can step back in History, but that clears everything above it in the stack. If you mean Undo then be aware that it applies to module changes, ratings, image switching, labels, etc etc etc etc So, Undo is worse than useless for removing History steps.
    Something worth mentioning because it obvious from some previous posts that some folk don't appear to understand what it is they are looking at in History or how it works:
    Left column = actual adjustment applied to parameter by step
    Right column = running sum of step adjustments to parameter
    In practice this means (left column value):
    Step 1 Exposure = -5
    Step 2 Blacks = +8
    Step 3 Fill = +4
    Step 4 = Exposure = +2
    Step 5 Black = -5
    Will result (right column) in the following being applied to image on rendering:
    Exposure = -3
    Fill = +4
    Blacks = +3
    Edit: i.e. the final slider positions.
    Based on above I'm not sure of the benefit of allowing one to remove a history step when all that's needed is to dial it out at the top of the stack.
    Furthermore, it doesn't matter the sequence that you apply the edits because it's the
    total for each
    parameter that's applied to the render, the final psd, tiffs will be identical irrespective of the order in each adjustment is applied.
    BTW: all above is easily confirmed by looking at the ACR outputs as displayed in Bridge.
    Pixel editing and Parametric editing are
    different

Maybe you are looking for

  • Concept of the change document table BWFI_AEDAT ???

    concept of the change document table BWFI_AEDAT and the use of the 60 day (user definable) parameter ??? does this table hold the time stamps for deltas ??? Could anybody elaborate on this ?? Was going through some of the posts and came across this..

  • Posting Date logic

    Hi experts, Have a question to all. Why does the PO history show only the Posting Date of Receipt & Invoice docs.why not the creation date. Say,i create a document today with posting date one week ago. How can you have a posting date before a documen

  • Two libraries instead of one?

    Hi, I want to keep my classical music collection separate from everything else and would like to build a separate library for it. How do I do that? Also, is there better way to keep them apart? I know I can edit the information and keep them separate

  • Appending a blocklist to /etc/hosts

    Is it possible to append a blocklist (er... redirectlist) to /etc/hosts somehow? For example, mvps has been supplying a very nice list of known parasite websites for years.  Basically, it just uses 127.0.0.1 to redirect known bad websites so they don

  • Problems with updated certificate

    I have finally managed to get a certificate update with the same details as the last one, but now when I sign the application and try and install I get an error saying the application with that name already exists in the destination. What am I doing