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.

Similar Messages

Lightroom 4.1 RC develop module slow browsing

I am running Lightroom 4.1 RC on a 2010 iMac 27" with 2.93 core i7, 16GB of RAM and a 512GB Crucial M4 SSD drive (where the Lightroom catalog resides). When I scroll through images in Library, I can move through images very fast, however, when I try to do the same in the Develop module, it becomes really, really sluggish. Probably about 5 seconds between images. I have 1:1 previews generated. Is there a workaround for this?
Thanks.

Hi there,
I totally agree with you. I'm running Lr 4.1 RC2 on Win7Ent64 with i7-2700k, 16GB RAM and catalog and previews on a SSD drive ant all the Develop module is relly really slow and sluggish. I have 1:1 previews generated. Very very bad performances!!! Adobe wakes up!

Development module slow display problem

Hello. I have a weird problem with LR 4.3 when using the development module. When a RAW file loads, it would take a second to load (and says "loading"), after which the photo would be sharp, but then the photo would turns soft again, and after about 5 seconds it would become sharp again. The problem persist for both standard and 1:1 previews. Standard preview is set for 2048 pixel, and the display is set to "fit" screen.
My hardware:
Monitor: 2560x1600.
CPU: i7 950
RAM: 12 GB
Video card: ATI Radeon HD4600 series
OS: win7 Pro SP1.
LR 4.3 is installed on a didicated SSD. The catelogs are also installed on the same dedicated SSD.
I would appreciate some suggestions. I have to edit 500+ photos day. Waiting 5 seconds for each photo to become sharp adds 40+ minutes of wasted time. Please help, thanks.

Found system info:
Lightroom version: 4.3 [865747]
Operating system: Windows 7 Business Edition
Version: 6.1 [7601]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.0 GHz
Built-in memory: 12279.1 MB
Real memory available to Lightroom: 12279.1 MB
Real memory used by Lightroom: 1950.6 MB (15.8%)
Virtual memory used by Lightroom: 1971.0 MB
Memory cache size: 1849.6 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440
Application folder: D:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
Library Path: D:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3\Catalog\2012\2012.lrcat
Settings Folder: C:\Users\johnny\AppData\Roaming\Adobe\Lightroom
Adapter #1: Vendor : 1002
Device : 9490
Subsystem : 20031787
Revision : 0
Video Memory : 1008
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 8192
GL_MAX_TEXTURE_SIZE: 8192
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 8192,8192
GL_RED_BITS: 8
GL_RENDERER: ATI Radeon HD 4600 Series
GL_SHADING_LANGUAGE_VERSION: 3.30
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 3.3.10750 Compatibility Profile Context
OGLEnabled: true
OGLPresent: true
GL_EXTENSIONS: GL_AMDX_debug_output GL_AMDX_vertex_shader_tessellator GL_AMD_conservative_depth GL_AMD_debug_output GL_AMD_depth_clamp_separate GL_AMD_draw_buffers_blend GL_AMD_name_gen_delete GL_AMD_performance_monitor GL_AMD_sample_positions GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_AMD_texture_cube_map_array GL_AMD_texture_texture4 GL_AMD_vertex_shader_tessellator GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_color_buffer_float GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_snorm GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_meminfo GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_buffer GL_EXT_copy_texture GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_histogram GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_explicit_multisample GL_NV_float_buffer GL_NV_half_float GL_NV_primitive_restart GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control

Why do exported JPGs appear darker than the processed RAW in the LR3 Development module?

I have scoured the forums with this question, and I have seen plenty of suggestions about color space and monitor calibration. However, I never seem to find that the issue gets resolved in the forums.
I am using Lightroom 3, and I am exporting to JPG using sRGB. I have noticed that the JPGs appear darker and the prints are also darker. I am using the same monitor to process in LR and to view the exported JPG. Why don't the images look the same, or at least similar? The difference is pretty huge.

rasu wrote:
… What do you mean by export in an mp4 wrapper? Do you mean export it as an mp4 format instead of H264?? …
no, exactly I did NOT meant that.
that's why I phrased 'wrapper':
a bit confusing, but there's mpeg4, the codec, and there's mp4 the wrapper or media-container:
• use your .mov you have already exported, which has the right colors.
• download/install the free tool Mpeg Streamclip
• open your mov, go straight to 'save as' and choose from drop down mp4
• save and upload that mp4 for comparison to Vimeo
• (tell us, wether you notice any difference, as said, just an assumption)
What will that do?
your h264 encoded material is actually in a .mov-wrapper
Streamclip unwraps that, and puts it into a .mp4-wrapper
this does NOT encode/transcode/affect your h264 material!
it just changes the box, not the chocolate!
What's NOT working is changing the suffix in a Finder operation - that does NOT affect the 'atoms' of the wrapper = a re-named mp4 will be 'noticed' by many programs/players as a mov anyhow! You HAVE to go the 'long' way with Streamclip - due to the simple re-packing operation, that process needs only seconds
I'm using this process to 'convert' my FCPX/iMovie .mov-exports to a readable format for my son's Playstation3 ... mov is a nogo, re-named suffix is a nogo. only re-wrapping to .mp4 works. excellent.
... but, as mentioned, I do care very little about gamma and luma as an hobbyist, my 'products' are under-exposured and veeery colorful anyhow

Very different color noise between develop module and library

There is a marked difference in the appearance of an image when viewed in the library versus the develop module. The color noise in the library module is very bad, while in the develop module, the noise reduction is doing a pretty good job. This is strictly a view problem, because if I export from the library, the proper color noise reduction is applied and it appears as it does in the develop module. This is not the first time that I have found this problem between the two modules. Any idea why this is happening? And, is there a fix in the works? It makes it hard to view images in the library.
If I boost the color noise reduction up to 100, the library image starts to look ok, but that doesn't account for the huge difference at lower settings.
There is also a dramatic slow down in the develop module when trying to make any of these changes in noise reduction and more, and also in side-by-side when trying to scroll around in the image to compare areas. Things really crawl. There is a definite two or three second delay before things respond. I have 8gigs in this mac pro, which worked beautifully with LR 3.6

And, is there a fix in the works?
Try rendering 1:1 previews for noisy images.

Unreasonably Slow Develop Module LR 4.3/5.3

I was running LR 4.3 (updated version) on an iMac with OSX Mavericks w/ only 4GB of RAM but that hasn't been a problem in the past, 350GB of free space on the desktop hard drive, and 200 GB of space on the external drive where the images and catalog are located. Working on a wedding with RAW files, CR2 (Canon 5D Mk II) and NEFs (D700) (about 700 images total). Develop module takes 60+ seconds (up to several minutes) to load each image with the "loading" window, then an additional 60+ seconds for the image to load completely from a pixellated preview. This also happened on my Macbook Pro wth 16GB of RAM. Tried to auto-sync develop settings (Basic exposure settings, lens profile corrections) for ~45 photos and it took over 3 hours on the MBP. Haven't been running any other programs, ran a cleanup on the desktop to clear unnecessary files. Cleared the RAW cache, increased the size of the RAW cache, optimized the catalog, rendered the 1:1 previews (took many hours), and even created a new catalog with the images on the desktop. When all of this didn't work, I upgraded to LR5.3 and I'm still having slow (not quite as slow as before, but still infuriatingly slow) reaction times from Develop. I've wasted so many hours and I can't pinpoint where the problem is coming from.
Also receive an error message that "another program is using ____ Catalog" for several other catalogs. Could that be related to this?
Is my only option to get a new computer? This iMac (21.5") supposedly doesn't support any additional RAM...or so I've heard.

myhrmar wrote:
I just had a chat with the adobe support team and they say Lightroom is working perfectly, because the changes show up in Bridge and LR. And the people from ACDSee say that the lightroom edits are Adobe specific.
Correct. That's proprietary processing with the LR engine which has yet to be done (rendered and exported). The preview in those Adobe app's understand this and show you the edits but ACDC can't. You have to render an iteration as a TIFF or similar with the edits applied for another app to 'see' that. ACDC has not access to those preivews so it doesn't show you what will be applied upon export.

Sharpening and noise defaults in the Develop Module

Capture Sharpness
I’m getting my head around sharpening and am of the understanding that there are three distinct phases: Capture Sharpening, Creative Sharpening and Output sharpening
With regards to Capture Sharpening I’ve noticed that when I import a CR2 file into Lightroom 3.6 there is an Adobe pre-set in the Develop Module. Is this a form of Capture Sharpening default?
Sharpening
Amount: 25
Radius: 1.0
Detail: 25
Noise Reduction
Luminance: 0
Colour: 25
Detail: 50

In Lr, "capture" sharpening is global sharpening, and "creative" sharpening is local sharpening (or sharpen masking on global basis but tailored to the image), or at least that's one way of looking at it.
in other words, if you're sharpening raw data non-destructively, such that first round of sharpening isn't being baked in, there is no need to separate capture sharpening from creative sharpening, in your mind, or in the software you use.
Put another way, the notion of capture sharpening comes from days when first round of sharpening was baked in, e.g. shooting jpegs, or in raw workflows where first pass yields a baseline tiff, and 2nd pass is artist's choice...
That said, what's needed for artistic sharpening (creative effects) can differ from what's need for baseline sharpening (initial "capture" sharpening, if you will).
Capture sharpening: just make stuff look reasonably sharp, since without it things don't.
Creative sharpening: sky's the limit... - some people consider Clarity to be a form of creative sharpening...
Note: since Lr's sharpening settings can't be varied (there is no way to apply high-radius sharpening in one region, and low-radius sharpening in another), and since its algorithm is aimed primarily at countering inherent and/or subtle/limited unsharpness, some people consider Lr's sharpening to be "capture-only". On the other hand, capture sharpening is, almost by definition, global, so since Lr supports local sharpening, and sharpen masking, those aspects can be considered "creative".
In my opinon, it's best not to get too hung up on semantics/terminology, but in a nutshell, conceptually:
* Capture sharpening needs to be done so stuff looks reasonably sharp, and is often done across the board, not dependent on image content (this is why most people apply a default amount of sharpening in Lightroom).
* Creative sharpening is going beyond initial/default sharpening, generally on an image-by-image basis, although not necessarily. Note: it may involve removing all global "capture" sharpening in favor of no sharpening, or local sharpening only (raw data required).
* Output sharpening depends on resolution and medium etc, and therefore needs to be done last - tailored to output device and such..
Sorry if this post had too high of an answer to question ratio .
Rob

Remove a line from develop module history

Hi, is it possible to remove a line (and the action related to it) from the history of the develop module ?
As I explain in another thread, Lightroom reinit all my modification after a "Read metadata from file" and I want to remove this action.
Thank you !

Hi Booby,
You could use an XSL-mapping for this purpose:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
    <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
    <xsl:template match="/">
        <xsl:copy-of select="."/>
    </xsl:template>
</xsl:stylesheet>
Sorry, i didn't read that you dont want a map, if you dont find the adapter solution you can use this map
I've seen this option in the module adapter, but i dont test it:
Regards
Message was edited by: Iñaki Vila

Why is Lightroom 5.7.1 so slow in develop module?

Lightroom CC slows right down and becomes unbearably slow when in develop module and working with brushes, or zooming/panning.
My computer is not the problem...running 32GB RAM and dual Nvidia GeForce GTX 780M graphics cards...

Lots of adjustment brushes and lots of spot removal can bog things down. Your best bet is to move those takes to the end of your develop cycle.

Since updating to LR5.5 it crashes about every 5-10 images while working in the development module. Computer is PC Windows 7 Home Premium. I have been using this computer for several years with zero problems. Is this related to the updating? What is the f

Since updating to LR5.5 it crashes about every 5-10 images while working in the development module. Computer is PC Windows 7 Home Premium. I have been using this computer for several years with zero problems. Is this related to the updating? What is the fix?

Do you get an error message? If so, what does it say?
Do you get a Blue Screen?
Does something else happen?

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.

Noise reduction not showing in develop module

I have noticed today that when I am reducing the noise in the develop module, the changes are not being represented on the image I am working with, except in the top left hand corner... too small for me to see clearly. But when I switch to Library module, the changes have indeed taken place. Has anyone experienced this? I need a fix because it's a bad guessing game adjusting my slider without seeing results until I switch modules. Haven't had this problem before. A lot of my work is turning out tooooo smooth!! I appreciate any help I can get with this.

Without question noise reduction and sharpening should only be adjusted at 100% view magnification. Hopefully the OP understands why now.
I tried viewing both 21Mp and 6Mp RAW images at 'Fit' magnification in the Develop module on my office system:
Vista Home Premium SP2 64bit
Lightroom 3.4.1
1280 x 1024 Monitor (Calibrated with i1 Display 2)
The 'Fit' size image on my 1,280 x1024 display with side panels up is 650 x 430. I increased the side panels for a 400 x 266 picture size, and tried it with side panels off for a 1,000 x 666 picture size – Noise reduction and sharpening is clearly applied in the Develop module for all of three view magnification sizes!
I would be interested for others to try this and report what they are seeing. I used a High ISO 128,000 RAW image so I could easily see the affect of noise reduction and sharpening controls at the 'Fit' magnification. If you don't see any change, try moving the Sharpening Amount and Luminance controls to 100 and then down to 0.
Note to the OP – Regardless of what you are seeing at 'Fit' view size, only adjust Sharpening and Noise Reduction at 100%. I'm just suggesting that you may in fact have a problem with your system. What Camera and file type are you using, LR version, operating system, and monitor(s)?

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.

Noise reduction, I want it in the develop module

I keep reading how Neat Image would like to make a module for LR once the SDK is out..... I like that Neat Image is willing to work on something for us (I like NI!) But I do not want a separate module just for noise reduction. This is something that should be properly implemented in the develop module. After all, if we start seeing modules for all different types of image manipulation can you imagine how cluttered the module picker will become!!! Not to mention how cumbersome th workflow would become! And we most likely would not get keyboard shortcuts for these modules. I know I don't want that.

I am sure someone from Adobe will corect me if I am wrong, but quite pssibly once the SDK is out some third party functionality may be able to be added into existing modules ather than as completely separate ones. The something like what you want would be possible.
Or it would be like working in QD in Library and hitting R to crop and then hitting G to go back. For Noise redux, it might be N (actually already used for something else) to take to to the Noise Module and hit G or D to go back.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
http://donricklin.blogspot.com/

Relative Adjustments in Develop Module and Presets...

Hi there,
the new Lightroom 4 beta is great and has some really good improvements inside (e.g. the "new" shadows/highlight or the new possibilities in the adjustment brush).
But what I really miss is the possibility to make relative adjustments in the Develop Module. Primary this is useful in presets to make steps of correction. I can do very limited relative adjustments for single parameters partially in the Library Module, but it goes not far enough and I can not save any preset from that or even combinations of adjustments.
An Example:
I have an image which is nearly perfect. All adjustments are almost done. Now, I want to give the image a +10 in Clarity or -3 in Brightness relative to all current adjustments. Those relative adjustments are perfectly to increase or decrease simple adjustments stepwise, but also really helpful for stepwise bringing in or out more complex adjustments.
Another Example:
I have an image with no corrections. No I can push Clarity, Shadows/Highlights, Saturation etc. from a preset which brings in more and more of a complex set of adjustments, which are just right for this type of image.
I think, a small checkbox behind a slider would be perfect to set relative or absolute adjustments. This settings should be saved within a preset to make some/all adjustments relative to the exisiting ones, or - if deactivated - absolute adjustment, like in the current version of Lightroom.
What do you think about that? It would be great to see that in future betas or the final Lightroom 4 product.

If they've been discussed at length, I'm surprised not to see them. Much has been provided that I would have guessed has received less requests.
And while I understand that Adobe might simply want feedback on what they have provided, what would be the best forum for letting them know what we feel has not yet been provided.

LR3 "Develop Module" slowing related to noise removal

Similar Messages

Maybe you are looking for