Slow lightroom

My Lightroom has started to become slower the longer I use it. It can now take a few seconds before I can see any adjustment that I make in the develop mode. Is there anything I can do, other than re install? Many thanks.

If you intend to work on a group of images in Develop, you could firstly select them and generate 1:1 previews, which may reduce lags.
Here is a helpful link on how to optimize overall performance:
http://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html

Similar Messages

  • Another SLOW Lightroom Thread

    Just another thread to document the major issues I'm having with Lightroom 4.
    System: Dell Studio XPS running Windows 7 Home Premium, Intel i7-720QM, 8 GB RAM 1333MHz, 500 GB HD, ATI Radeon 4670 1GB with Wacom Intuos 5
    Working in the Develop module has been completely unacceptable and is costing me hours of editing time and frustrating, which means its costing me money.  Everything from navigating between photos to adjusting slider bars seems to be laggy to put it lightly.  After using the Adjustment Brush, making universal changes is taking forever!  And if I got back to create an additional adjustment with the Adjustment Brush tool, it's almost not even worth it because it is so slow to respond.  Similar to the slow downs after using the Adjustment Brush tool, any changes made after making any adjustments in the Lens Correction tab seem to be super sluggish as well.  Oh top of it all, my computer is running extremely hot when running Lightroom, which ever occured in past versions! 
    I've tried several suggestions that I've seen in forums, such as creating a fresh Catalog and importing the files directly into that new Catalog, hiding the Histogram to free up resources, reducing the size of the Catalog to just the working set I'm currently working on... I've now installed the 4.1 RC and do seem to see some increase in response with the sliders within the develop module, but once I start using the Adjustment Brush and Lens Correction, it seems to be back to it's sluggish self.  And after editing a few photos, the entire program is crawling.
    I think it's great that Adobe has such a strong following that people seem to be so understanding and patient about these issues, but find it unacceptable that such an unpolished release was issued to the public.  If the issues are eventually remedied I will be fully on board with Lightroom, once again, because I do think that the revamped develop module has been a major improvement for editing and workflow, but all those improvements are pretty useless when I'm losing so many hours battling with performance issues.

    No changes, nothing at all, in actual fact I don't even have a PC connected to this broadband line it's purely for the games consoles. I have a separate broadband line for my home office etc.
    Just had a call from BT India, with out wishing to sound derogatory I might as well talk to my pet cat. Apparently they were ringing to see if the problem had been resolved, I only reported it 2 hrs ago.

  • Slow Lightroom 4.1

    Why are Adobe taking so long to fix this major problem with Lightroom 4.1.  It's slow slow slow!!  The develop module is so frustrating.  Sticky sliders make this software useless for pro's.  Come on Adobe get this fixed.  A lot of Pro's including myself have renamed this version Shiteroom!! and are heading off to Capture One or Aperture.

    kazcoul wrote:
    Are other people having these issues after upgrading to Lightroom 4? 
    Have you done a forum search for an answer to that question?

  • Organiser Too Slow - Lightroom 3 as Alternative?

    I purchased Elements 9 last year, and one of the things I've always struggled with is the slow Organiser speed.  From the time I click the organiser button on the splash screen to the time that Organiser becomes responsive to any mouse clicks (it's showing the hourglass during this time) is a whopping 4 1/2 minutes.  Worse, I can't even task swap to other applications (eg Firefox which is already running) while Organiser is starting. IMHO, that's pretty unacceptable, and I'd like to find if there's something fundamentally wrong.  I don't have older versions of Elements loaded, and I have loaded updates for 9.0.3.
    My notebook is a Dell Latitude D830, with a Intel Core2 T7500 CPU, 3 Gb Ram.  Win XP SP3. Plenty of free hard disk available on 2 partitions.  No network access to photo files - all stored locally on HDD.
    I've had a browse around this forum and other forums which have comments about Organiser speed, and there seems to be no easy fix.
    So if there's no easy fix, does anyone have any experience using Lightroom as an alternative to Organiser?  Does it integrate well with Elements?  I'd like as detailed an answer as possible - I don't want to shell out more of my hard earned dosh on LR3 if it's not going to provide the functionality and ease of use that Organiser should.

    You will definitely like Lightroom if you shoot in raw. I rarely have to use PSE, except for the more artistic stuff and for adding text etc. But then it’s so easy (Ctr+E from Lightroom Library) to export a PSD or tif from the raw file which includes all the adjustments already made in Lightroom.
    Lightroom 4 can’t be that far off and that would be a good time to purchase if you are also planning to upgrade your computer. In the meantime why not download the 30 day free trial and see if you like the program.
    By the way there is a separate Lightroom forum if you have any more questions.
    http://forums.adobe.com/community/lightroom
     

  • Very slow Lightroom 4.4 to Photoshop CS6 in Windows 8

    I have a problem with my Windows 8 computer. Please notice that on this computer I did not change any of the default settings in the operating system, it is a clean install of Windows 8. I have also installed the latest version of Photoshop and Lightroom directly from my Adobe Application Manager software (I am a Creative Cloud member).
    What happens is that I have to wait 30-50 seconds after I give, in Lightroom, the command "Modify in -> Photoshop CS6" (I have the software in Italian and I hope that this translation is correct. Here is the command that I am using:
    The very strange thing that happens is that Photoshop opens fast (5 seconds, I have an SSD) and Lightroom is very fast too.
    Here is the strange thing. Photoshop opens after I launch the command.
    Then nothing seems to happen for 30-50 seconds (sometimes also more time). After this “long” period of time this error appears in Lightroom:
    It says: "you can't modify this file because Photoshop CS6 can't be started". However, this is not true! Photoshop is running correctly, and it was running! This happens if Photoshop was started from Lightroom and if Photoshop was running before Lightroom command "Modify in -> Photoshop CS".
    Another strange thing is that, after I press "OK" to this error message, the file immediately opens in Photoshop!
    Please notice that this behavior happens also with a series of file. If, for example, I export 10 files from Lighroom, then, after about one minute, I get 10 error messages in Lightroom, and, when I press OK, the files will open in Photoshop (for each "OK" that I press a file opens, so I have to press 10 times OK to open my 10 files!).
    This very strange behavior is eating my time and I am very disappointed! It is very difficult to get in touch with Adobe support and I decided to use this forum to get some help. After you pay monthly for the Cloud software you wish that a good support came included with what you pay, but it seems that this is not true!
    Please help me if you can!

    Vittorio,
    1. At this point my suggestion would be first to check are you the Admin of your system or not.
    2. Try uninstall and Photoshop first and make sure you select the option Remove Preferences when you doing an uninstall.
    3. After that try a fresh install of Photoshop.
    4. If that doesnt help try uninstall and reinstall or LR & PS too by same way.
    -Mandhir

  • Building Previews Appear Slow Lightroom CC

    Since upgrading to CC when I am scrolling through the thumbnails in grid view, the previews appear to building as I scroll down and they are not instant.
    Is this normal or do i have a setting wrong somewhere.

    Let me try to answer your questions.
    1)
    collections created within the Lr Mobile app will be automatically synced to the back-end. You can add photos manually from your camera roll or enable a collection for "Auto Add". With that all future camera shots will be automatically imported to Lr Mobile and synced
    2)
    correct. changes will be synced from Lr Mobile to Lr Desktop - back&forth
    3) local camera roll deletion is not connected to the Cloud back-end. But be carefull that the import/sync is finished before you trigger that.
    4)
    as answerd before. the cloud back-end is not connected to the device camera roll
    5)
    video is not supported yet
    7)
    original resolution images will be  downloaded to Lr Desktop. Preview images will be shown in the Lr Web view Adobe Lightroom
    8)
    when you create a collection within Lr Desktop and add your photos you would like to sync, then you can enable this collection for sync. As soon your are signed-in and start the sync (via the top left activity panel) you will notice a little checkbox beside the collection. When you check this sync start to run. Lr Deskop generates smart previews and uploads these to the back-end (plus thumbnail previews + meta-data). When you open up Lr Mobile app and you would like to make an edit, the Lr Mobile app loads the smart preview form the back-end and syncs back the meta-data or edit setting.
    Hope that helps you to start.
    Guido

  • Lightroom 4 runs too slowly

    I have spent weeks trawling forums now and implementing as much as I can from people's suggestions as to how to try and get Lightroom to run better.
    As an example, alway leave the Details section til last, as it makes a significant impact on slowing Lightroom down.
    I flush the cache before starting any work, I bought a  new 1tb drive, and downloaded a brand new, up to date nVidia driver for my card.
    I've spent some considerable time ensuring that all meta data has been written to xmp and none is outstanding, and all 1:1 previews have been rendered for every image in the catalog. Standard previews are set at their lowest level, and I have set all LR locations including the cache, catalog and preview locations as 'excluded" from MSE, which is the only anti-virus type program I run.
    I have tried using process 2010, then changing to process 2012 when the work is complete and implementing the changes, the same problems occur. Using process 2010 in LR 4.3 does not seem to be any qucker than using process 2012.
    I've been through all Windows services to see which ones I can turn off and which I can't. All those not necessary for the operation of the computer are turned off.
    The cache has been set at everything from 10gig to 150 gig, that doesn't seem to have any effect but it is at present on 100 gig. I flush it regularly when working. I also have tried deleting history from each file I work on, although this doesn't seem to have any positive impact either.
    Now, the issues.
    When using Lightroom, there is a 'hang' or 'lag' of a fraction of a second before any command is carried out. So, if I zoom into full size, grab the small selection box from the view on the left to move it around my image, it is a half a second before it responds.  Often on any task, the cursor doesn't change, as if there is still something going on.
    If I click using the healing brush to get rid of dust bunnies, it is 1-3 seconds before it appears and is editable, then I can move onto another. When using the spot healing tool, after 2 -3 photos have been completed, each time I click on the image the 'target' for the tool appears, but it is in the top corner of a very large black square, which does not disappear for 3-5 seconds.
    I can do an image with maybe 20 of those then it begins to get real slow. If I then use the sliders, it can be up to 4-6 seconds before they respond. During this period, at random times on the top bar of Lightroom I see the message "Lightroom not responding" flash on and off, sometimes for minutes before it clears. If I then go to export the file as a jpg, it can take as much as 3 minutes to export one full size image from a RAW file. During that whole period the processor is toiling away at 100% and LR is using the max amount of memory, which for some reason is only just over 700mb. (I will paste the system info from LR at the end of this.) Once this begins, LR pretty much thrashes away at 100% of processor power for many minutes even when doing nothing, and trying the slghtest thing starts it off again.
    Once I've exported 3-4 images, everything slows down to the point it's really unusable. If I try to export an image at that point, I get a 'not enough memory' message. I can try 5-6 times to export and I always get the same message. My only option then is to shut LR down, and start it up again after a minute or so, flush the cache and start again. Obviously this is an unacceptable workflow.
    So,  I know that LR works fine for some people, so please don't say "It works for me", I know it does. It doesn't work for me though, and I am trying to establish why. If your car breaks down I don't point and say "It must be you cos I have the same car and mine is fine." What I would like is for anyone who has useful suggestions to help. Perhaps someone who it didn't work for and they solved the problem?
    Lightroom version: 4.3 [865747]
    Operating system: Windows 7 Home Premium Edition
    Version: 6.1 [7600]
    Application architecture: x86
    System architecture: x86
    Logical processor count: 2
    Processor speed: 1.9 GHz
    Built-in memory: 3068.9 MB
    Real memory available to Lightroom: 716.8 MB
    Real memory used by Lightroom: 504.9 MB (70.4%)
    Virtual memory used by Lightroom: 506.6 MB
    Memory cache size: 3.8 MB
    Maximum thread count used by Camera Raw: 2
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
    Library Path: J:\Lightroom 4\Master\Master.lrcat
    Settings Folder: C:\Users\G\AppData\Roaming\Adobe\Lightroom
    Adapter #1: Vendor : 10de
    Device : 649
    Subsystem : 1451025
    Revision : a1
    Video Memory : 1007
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (Realtek High Definition Audio)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    Direct2DEnabled: false
    GL_ALPHA_BITS: 0
    GL_BLUE_BITS: 8
    GL_GREEN_BITS: 8
    GL_MAX_3D_TEXTURE_SIZE: 2048
    GL_MAX_TEXTURE_SIZE: 8192
    GL_MAX_TEXTURE_UNITS: 4
    GL_MAX_VIEWPORT_DIMS: 8192,8192
    GL_RED_BITS: 8
    GL_RENDERER: GeForce 9600M GT/PCIe/SSE2
    GL_SHADING_LANGUAGE_VERSION: 3.30 NVIDIA via Cg compiler
    GL_VENDOR: NVIDIA Corporation
    GL_VERSION: 3.3.0
    OGLEnabled: true
    OGLPresent: true
    GL_EXTENSIONS: GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments 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_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment 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_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness 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_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map 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_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding 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_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add 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_Cg_shader GL_EXT_depth_bounds_test 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_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 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_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 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_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_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

    I think the "Available Memory" figure is pretty standard for a 32bit system, which is what I think the OP is running.
    @howmanyetc: A couple of observations: the systems specs would seem to be not much higher than the minimum requirements for LR4, so blazing fast it ain't ever going to be. Also is the J drive the new external drive that you bought? If so I'm guessing that it may be USB2 connected? If so having the catalog on a "relatively slow" external drive is probably not the best idea from a performance perspective. The "red lining" of the CPU during exports is entirely likely, the processor is simply not sufficiently powerful to do the work quickly. As a comparison, exports which take maybe 3-4 seconds on my desktop would take upwards of 30 seconds on my old Thinkpad laptop (similar specs to yours) with both cores at 100% with no deviation (and that was back in LR3, so I can't imagine how slow it would be using LR4). The "getting real slow" after a while is more than likely due to your RAM limitations, especially on a 32 bit system.
    I'm not saying that you should rush out and buy a brand new powerful system, though I do think you might struggle to make significant improvements given your specs. It sounds as though you are doing everything you can to improve things, however as I said, if the catalog is on a USB2 external drive, trying it back on an internal drive would be the first place that I would start. Having the images on the external is probably OK, your bottleneck for things such as Exports is CPU, not I/O.
    Do you need to be writing XMP for all your files? Do you have the "Auto write XMP" setting enabled? If so, turning that off and using Ctrl+S to manually write the XMP at the end of a session may help a little.
    Sorry I can't be of more help.

  • Does LR 3 slow down when there's a lot of photos?

    I've been adding a ton of photos into my catalog recently (I now have 23 thousand photos) and I'm wondering if having a lot of photos in my catalog will slow Lightroom down.
    I've been recently worried about the speed of LR because it has been slow to respond lately, and It's now consuming 850MB of ram when I open a 14Mp Jpg without any adjustments of any kind.
    Thanks, and if you have any suggestions to how to make Lightroom faster, send them this way.

    Some has slow process when a large number of photos are available but I think it's most related to their OS configuration ? Actually it would be a good idea to "optimize" the LR configuration : good RAM value is 4 Gb, memory cache have to be as large as possible, HD's (not all on same disk : system and pictures), SSD and/or RAID aso.. Minimum values indicated by Adobe are really the VERY LOWEST to use. And as other already told : optimize your catalog regularly.
    You'll find on many sites good tips to make the best possible configuration, avoiding in principle a slow response of soft.
    An experienced professional photographer, Martin Evening, has published a (cheap) book about LR3; it could be considered as one of the LR3 bibles. There are many tips given, difficult to transmit in detail on a forum like this one.
    I never have found any problem with slow down of LR. But my biggest library, personally I use several libraries, is under 40000 !
    Cheers.

  • LR: Slow Crop Tool (Retina MBP)

    -Using Lightroom, 2014 Macbook Pro Retina, runs almost instantly for all LR operations
    -However, slow when applying a crop, ~20 seconds (e.g. in Develop module, crop tool, change aspect ratio, move crop area and click 'close')
    -When applying a crop on different resolutions, crops in < 3 secs; great (e.g. 'Best for display' or custom res e.g. 1440x900)
         -Even when using custom resolutions, retina or non-retina, (using autoscript or an app) such as 2560x1600, crop is applied in < 3 secs
         -Only when using 'More Space' (1680x1050) retina option does applying crops slow down
    For others with this 'slow Lightroom cropping' issue, try running your mac at different resolutions [system preferences>displays]
    Any ideas why we are experiencing this odd behaviour?

    Lightroom 6 / Lightroom CC update seems to have completely fixed this issue! Performance is fantastic

  • Question: How to display rating in SURVEY VIEW

    Hi,
    I've been using Lightroom for years. I love to use the SURVEY mode.  But today, I couldn't see the rating stars under each photo in Survey mode; I only see the flag status.  Now, it's probably something I did, like hitting a shortkey or something... but for the life of me, I can't figure out how to bring back that visual information.  After searching online + fiddling around with the settings, I finally thought I'd come here and ask if anyone knows...
    Thanks!
    PS. Lightroom 4.3RC  (why 4.3 RC, because I'm one of those plagged with a super slow Lightroom in develop mode, especially with my D800 files! I'm crossing my fingers with each RC update that the software will be faster... )

    Thanks Rikk!
    your screenshot pointed me in the right direction. It just happens that I had changed the background color of the Survey View, and the stars rating were now blending with the background, creating the illusion of them not being there.

  • I do not understand why LR would not auto look at my primary...

    Why would LR not auto look at my primary folder and not update it's DB with any new folders I might have created outside of LR?
    This makes my work flow far more difficult.
    In this respect "Bridge" does a far better job.
    Is there logic/reason for this?

    Bridge doesn't use a database or need importing. Nor can Bridge let you view or edit metadata for offline images. The logic is simple. You must import into a database.
    In order to do what you want you have 2 options, 1) Have Lightroom constantly waste cpu cycles looking at the drive (and I do mean constantly) or 2) Set up a way of having Lightroom import all new folders when you click (probably right click) on the folder.
    Mark Hamburg has already mooted the first because it would really slow Lightroom down. The second seems like a viable option to me.

  • Lightroom is very slow, utilizes 100% CPU, then freezes or closes program.  How do I fix it?

    I am having a problem with Lightroom 5 being very slow, utilizing 100% CPU, then freezing or closing the program.  How do I fix it?
    I just upgraded to LR5 from LR3 on Sunday as well as CS6 from CS5 (which I have not tried out yet).  I spent several hours talking with Vamil, from LR Support Staff yesterday.  He was extremely helpful and kind and tried everything he could think of while remote-handling my PC and talking with me on the phone.  He deleted preferences, cache, temp files, updated graphics with a new replacement file from AMD site, then re-downloaded and reinstalled LR5. 
    It is still very slow and then freezes and closes down with a message of utilizing 100% CPU.  Within several seconds of using the brush in Develop, I started having lots of problems.  I could not even move the picture around.  The side screens would not disappear like they should.  And I could not move to another picture.  The day before I spent several hours trying to work on just 1 picture.  After all the changes yesterday, I tried to move from picture number 1 to about 130 after having not touched it for 10 minutes, and a half hour later, it still said, "Processing" with no picture coming up, just a blank prieview pane.
    LR Support suggested I get a new CPU though he thought according to specs mine should be ok and other programs were running fine.
    My PC is only 2 years old.
    I talked to HP briefly about CPU updates for my HP PC.  He said I probably do not have a problem but suggested I run self-diagnostics and maybe buy a new CPU anyway. 
    I ran diagnostics listed through the HP Support Assistant connection on my PC.  All was ok. 
    I still researched if I could buy a compatible CPU upgrade.  I cannot even find any CPUs still selling that are listed for my PC.  Best Buy Store said they could not even order a compatible CPU.  They said my Bus speed may not be big enough, so they suggest I get a new PC.  What Bus speed do I need?
    I have the following PC Setup:
         AMD Phenom II X6 1045T Processor 2.70 GHz with 6 Cores
              with 2700 MHz Base, 3200 MHz Boost, and 4000 System Bus Speed, and 95 watts;
         HP Pavilion Elite, HPE-500y, 900 GB Free, new in 2011;
         Windows 7, 64 Bit;
         RAM 16 GB, DDR3;
         Graphics AMD Radeon HD 6450;
         Nikon, D200, with Raw Files;
         External Hard Drive for Original Photos, 600 GB Free;
         LR Catalog and Library are on Main Hard Drive;
         Monitor, Sony CPD-200ES, new in 2004.
    I am thinking of buying a new monitor tonight mostly so I can do better photo work while enlarging the pictures to do it.  I am concerned that while it will help my viewing, it will take more power away, and make my usage of LR5 even worse.  Will a new monitor affect my performance?  I am looking at HP Monitors with IPS.  Is this the best recommended choice for LR and Photoshop CS6?
    I think I would like to stay with a 6 core processor since I need to have several items open for other non-Photoshop functions.  When running LR5, I had everything else closed.  With LR3, I was able to have other things open.
    I do not really want to buy a new computer and know that those I have talked with at this point are only guessing after looking for what they thought should fix it.  4 People from Lightroom Support have all thought I should not be having problems with my setup. 
    I bought one of the best computers 2 years ago.  Is it really obsolete already so that I cannot use LR5?  Is everyone else buying a new PC every 2 years?  I used to go 5-7 years. 
    Even though I have figured out some of what my PC has, I really do not know technically what I am talking about so am at the mercy of other's help.  Are there any solutions that might work short of buying a new computer?
    I also have taken 40th anniversary photos for some people and am waiting to give them as a free gift since I am not a professional at all.  I am hoping to get through this problem soon so that I can provide some nice memories for them.
    I have not gotten any further than trying to adjust 1 picture.  I have no comments on uploading speed, since I did that while still in LR3.
    Thank you for your time and help.

    I'm running LR with no speed issues on an Intel 17-860 quad core with about the same performance as your AMD Phenom II X6 1045T Processor. My system is also an HP, which originally had a single 1TB 7200 HDD. I've since added a second 2TB Black Caviar HDD, which provided no significant difference in LR's performance.
    AMD processors do not implement hyper-threading and don't need it. I'd start debug by process of elimination:
    1) Disconnect all externally attached USB, FireWire, or other externally connected devices except keyboard, mouse, and your single 1280 x1024 display. This includes all externally attached memory card readers, phones, ipads, etc.
    2) Reboot and logon as Administrator.
    3) Remove your Internet connection and turn off all Antivirus and firewall programs.
    4) Open LR and under Catalog Settings set 'Standard Preview Size' to 1440 (slightly larger than your display width). Under the Metadata tab here make sure 'Automatically Write changes into XMP is NOT checked.
    4) Create a 'New Catalog,' Create a new folder and add about 10 raw image file copies to it for testing, and Import it into the new catalog. In the Import module make sure under File Handling 'Render Previews' has 1:1 selected. Wait until all Preview building has completed in the Library module.
    Try editing these image files inside the new catalog as you were previously.

  • Lightroom 5.4 to Lightroom Mobile sync is soooo slow - why no local sync?

    I am testing the new Lightroom 5.4 with Lightoom Mobile. What really annoys me is the fact that all photos are going up to the Creative Cloud. I have private pictures which should be private. Always. No upload. No Cloud sync. It is important!
    Speed is the next major problem. LR 5 is way too slow for a fluid workflow. But this is mentioned from other users.
    What absolutely makes me sad ist the sync speed of LR5.4 to LR Mobile. 100 Photos took up to 4 hours. On a typical wedding I have 2000+ images. Depending on the speed of the first 100 photos I have to wait 80+ hours? Are you kiddding me? This makes LR Mobile unusable. My clients are expecting results fast. Speed is one factor to the next contract.
    Overall, I don't want to sync anything into the Cloud. I want a to use my fast local sync via WiFi or USB. Only those two options. I want to sync photos even without any internet connection successfully and quickly.
    I'm fine with authentication with Adobe servers for licensing verification. But that's it. The rest should be configurable by the users whether they Cloud sync or not.

    Tom, thank you for taking your time to come here and enlighten us with the decision making process behind what was done. Like it was said before here, the Lightroom Mobile so far has been very, very frustrating. I came home very excited to test it and make my dream come true. To be able to take my catalog (or a shoot) with me on the subway, etc and be able to choose the photos on my iPad. See, I am a photographer and I shoot mainly fashion and beauty, so my workflow starts as soon as I finish shooting by importing all images into Lightroom and then going through the painstaking process of choosing which picture to use. I would shoot anywhere between 5-12 looks in a day, around 100 photos per look and at the end of the process I need to choose only one photo from each look. This normally involves going back multiple times to be able to get to only one from each look. The LR Mobile would have been the perfect solution for me, making me able to look at photos while out of the office, on the subway, at home, etc. It would have made my editing process much faster (or less slow). Instead, I've been sitting and waiting for 6 hours so far and only 18 photos showed up on my iPad (from the 500+ that were chosen to be synced from my desktop LR. Now I know it's not my internet that is making it that slow because I have 80+Mbps of download and 40+Mbps upload. And that haven't helped me much as my LR is stuck on "Syncing 527 photos" for the last 5 hours. Most professional photographers that I know deal with a huge amount of photos from a photoshoot. Wedding, fashion, advertising, we all shoot 1000+ images in any given work day. To come home and have to wait 100 hours before we are able to edit on the iPad is just not useful. This will be useful for the amateur photographer that will take photos of their children/dog/flowers and want to be able to show their guests the photos without having to get them in front of the computer.
    Now I understand what you said about having to have a centralized place so that all the clients up to date on the changes, and I think that is great but I also think that it's paramount that there's a different way of syncing, a faster, more efficient way. Even if it is, like mentioned, not a "everything in sync" solution. Something like sync the desktop to the iPad and only those two work together. If both are changed before the next sync, a "the 'blabla' catalog has been changed since you last synced, do you want to overwrite it?" takes care of the problem, much in the same way that Photoshop asks us when we are saving something that has been somewhat modified by some external agent between saves. But the beauty of shooting all day, loading everything in Lightroom at night at the hotel and in the morning catch your flight and edit your shoot on the iPad while traveling, or being able to show the clients on the iPad right after you shot the wedding, or (what I was dreaming was going to be possible just to have my dreams crushed when started to use it) shooting tethered on the job and giving the art director the iPad so that he/she can see the shots without having to stay in front of the computer during the whole shoot. Now THAT would be a game changer! That was what I was expecting from LR Mobile but unfortunately got disappointed. I'd pay for the app alone if it did that!

  • Lightroom 5 is quite slow in importing photos

    Lightroom 5 is quite slow in importing photos from a memory card connected to a reader using USB 3.0! After installing LR5, I didn't change any default settings. Interestingly, this wasn't found in beta testing. LR4 was what I call quick or snappy. Because of LR5's slow performance, I went back to LR4 after paying for the Cloud subscription.
    With substantial difficulty and after some time passed, I eventually was able to speak to Support which offered no fix for this issue. I hope that it can be resolved soon.

    Selecting the Import from below in Files does help speed up the start of the Import as mentioned in the thread you referred to but is still maybe three or so times slower than in LR4. At least it makes using LR5 more bearable.
    Thanks.

  • Lightroom 5.5 Import from Catalog *very* slow performance.

    Importing from a second catalog from a shoot is *very* slow with the last version or couple of versions of Lightroom.  It's been about 20 minutes and the import is moving glacially slow and is only about 20% done.
    Here are as many stats as I have:
    iMac 27" 3.5Ghz Core i7, 32G of ram, 3T fusion drive (the late 2013 model maxed out)
    Master catalog has 117,000 images in it.
    The catalog I'm importing has 948 images in it.
    CPU use during the import is 100% used by lightroom (note that the multiple CPUs can go to more than 100% so this means I think that one CPU is maxed out, though LR can sometimes take 500% of my CPUs during an export)
    Lightroom is using 4.2G of RAM (10G free in activity monitor)
    Hard drive is fairly full, but still has 366G free on it (so about 10%)
    Lightroom Mobile sync is enabled (not on this folder I don't think) but says "service unavailable" at this point.
    Lightroom is fully up to date (5.5) on both iMac and laptop (also a mac in case that matters).  Both are up to date with the latest OS software.
    How I did it was:
    Export the shoot as a new catalog on my iMac
    Transfer it to my laptop (smart previews only, no masters)
    Edit images, metadata, etc
    Transfer the entire folder back (.lrcat, previews, smart previews) to iMac
    In my master catalog do an import from catalog
    Waited for ages for checking for dupes (which I can understand with such a big catalog)
    Selected to import all, changing metadata and develop edits, and selecting to put new images in the folder (not sure why it asked as there weren't any new images)
    The last time I did an import I started it and then went out somewhere so I didn't notice how long it took, but this seems completely crazy.  In the time it's taken to write this up it's now about 20 minutes later and the progress bar is maybe at the 33% range.  It's still working away, it's just crazy crazy slow.
    Anything to help out or debug would be greatly appreciated.  I suspect it's pure size of the catalog, but 120k isn't outside the realm of what I've heard people say works fine, or maybe the Fusion drive (maybe the OS is trying to move files around behind the scenes)? 
    Either way this didn't seem to be an issue until the last couple of versions (I haven't gone and re-installed 5.4 or 5.3 to check) and it's starting to really frustrate me

    Hi Jim,
    Great suggestion! It opens perfectly fine on its own. I even went as far as re-exporting it once it loaded but am still experiencing the same issue. That same catalog loads perfectly fine on my assistant's iMac.
    I can't really think about anything that changed in my environment with the exception of a new Bootcamp partition to run windows on an external Thunderbolt HD but I doubt this is related.
    I'm open to any suggestions while I am trying this again... 10 minutes of 'Checking for changed and duplicate photos'.

Maybe you are looking for