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

Similar Messages

Hello to all: My iMac has developed a video display problem. It displays everything in cartoon like colors - purple, green, blue. Can this be repaired? Is there a way to output to a different monitor? Thanks in advance! isplays

Hello -
My iMac has developed a video display problem. Everything now appears in a strange, cartoonish way. Purples, greens, blues. Can this be fixed, and if so, any idea how much it might cost? Also, could I output to a seperate monitor? I plan to replace the unit , but cannot right now. Thanks!

Go to System Preferences > Universal Access > Seeing.
In the Display area, reset it to "Black on white" by clicking that checkbox.
You can also reset it by pressing Command-Option-Control-8

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.

Develop module not displaying photos and tool updates.

This problem just cropped up on a previously working install - Windows 7, LR 5.6
The large display of the image in the develop module does not update for any of the actions selected in the develop module. Pick a tool, make an adjustment - you cannot see the results of your adjustment on the large image. The image in the filmstrip does display the results of the adjustment. Selecting the crop tool causes the image to go grey.
Using the simple tools in the library module - they all work and show the proper results.
I have uninstalled LR and re-installed.
I have purged previews.
I have deleted "Lightroom 5 Preferences.agprefs".
What next?
David Hidding

Further info - Full Screen mode in the Develop Module - it's just black, no image. FS mode in the Library module works correctly.
I have tried loading the latest video drivers for my video card, rebooted multiple times, etc. Frustrated.
I should also note that this problem started right in the middle of an editing session, everything was fine, and then suddenly, the image stopped updating.
David Hidding

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!

Sql developer UTF-8 display problems

Hi
I use a development tool that is supposed to allow utf-8 encoding. If you enter text 'ABCDÉFGH' (É is ctrl alt E) through the software it is written to a VARCHAR2 value. When you look at the value using SQL Developer or (Congnos Impromptu) this value is displayed as ABCDÃFGH.
Should Sql Developer convert Ã to É when displaying the value. Or is the problem with the development tool where it is not writing the value to the table correctly.
linux/unix platform.
The following NLS_DATABASE_PARAMETERS are.
PARAMETER VALUE
NLS_LANGUAGE ENGLISH
NLS_TERRITORY UNITED KINGDOM
NLS_CURRENCY #
NLS_ISO_CURRENCY UNITED KINGDOM
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE ENGLISH
NLS_SORT BINARY
NLS_TIME_FORMAT HH24.MI.SSXFF
NLS_TIMESTAMP_FORMAT DD-MON-RR HH24.MI.SSXFF
NLS_TIME_TZ_FORMAT HH24.MI.SSXFF TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH24.MI.SSXFF TZR
NLS_DUAL_CURRENCY ?
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET UTF8
NLS_RDBMS_VERSION 10.2.0.4.0
thanks
andy
Edited by: user8646247 on 21-Jul-2009 06:39

There is a forum dedicated to SQL Developer, which is monitored by members of the product dev team. You should consider posting your question there. [Link to forum|http://forums.oracle.com/forums/forum.jspa?forumID=260].
Cheers, APC
blog: http://radiofreetooting.blogspot.com

Lightroom 4.1 Develop Module Preview Problems

Hi All,
I have been using LR4 and now 4.1 since beta and subsequently the first release and now 4.1RC. I too have been irritated by the lack of responsivness compared to LR3.6 but in 4.1 it does seem to have improved. BUT the problem I am seeing is that the preview image in develop module chnages to a lower res and muddier looking version as I drag most of the various adjustment sliders, once the slider is realeased the image refreshed to a better resolution version. This happens in all panels from Basic to Detail and even Effects. It is almost as if Adobe are increasing the apparent speed by applying the adjustment to a low res embedded file first and then to the full RAW data in the background. On detailed images it is more irritating that the slow develop module in LR4.0 as it makes adjustments impossible to preview until the slider has been deslected. The same occurs if you select the slider setting digits and advance using the cursors. Very frustrating indeed. I will be going back to LR4.0 and fingers crossed that this is resolved when LR4.1 is reeased in full.
My PC is fairly good, Win 7 64bit with Quad Intel 9550 cpu (2.83Ghz) with 8Gb ram, GTX-260. I have the same problem at work with a dual cpu (8 cores total) Zeon 5365 (3.0Ghz) and 12Gb Ram & Quadro FX4600. The problem does not seem to manifest in the second display preview but this is laggy and obviously not any use for setting local adjustments.
Anyone else had a similar issue to this? I cant find any reference to it on the web or these forums.
BGhibby

I have exactly same symptoms as Dave Mayfield.
Except I moved images to sub-folders and renamed them, from within Lightroom.
After it locked up, it did not show sub-folders in Library and all the images have question marks on them. If I show it where the file is in Explorer, it does not show any changes.
I Imported one folder and it could see the images in the folder.
Some were without any changes.
Some were the final edited configuration, but not change history shows in Develop. It is if it kept an Exported fersion.
HELP!
Jack Lane

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.

Problem with develop module

I have LR 5.4 running on a mac OS 10.7.5. I am having problems with the software locking up in the Develop module. Sometimes a new image won't open and the preview screen stays black. I go back to the Library module and try to reneter the Develop module and get an error message saying there was an error trying to open the module. The entire LR screen is gray. I have to quit LR and restart the software to continue. I downloaded my software from Abobe and I was wondering if I can download a new version again and use my same serial number to reinstall the software.

Hi Rodney,
No custom print templates and this is a relatively new problem. It just
started about a week ago. I have been using the software steady for months
now. It did it once or twice last week but this weekend and today it has done
it about six times so it seems the problem is getting worse. That¹s why I
think the software may have been corrupted. I didn¹t keep a copy of the
software I downloaded so I can¹t reinstall. That¹s why I was wondering if I
could download it again and use the same serial number as before. I have only
loaded the latest version on my desktop. I also have LR 4 still installed on
my laptop and desktop. I have a big project to complete and this is really
slowing me down.
Michael
Problem with develop module
created by Andrew Rodney <https://forums.adobe.com/people/thedigitaldog> in
Photoshop Lightroom - View the full discussion
<https://forums.adobe.com/message/6445126#6445126>
Do you have any custom print templates? That might be the case, it was an
issue at one time. Delete them and try using one of the default presets.
Crash?
Please note that the Adobe Forums do not accept email attachments. If you want
to embed a screen image in your message please visit the thread in the forum
to embed the image at https://forums.adobe.com/message/6445126#6445126 Replies
to this message go to everyone subscribed to this thread, not directly to the
person who posted the message. To post a reply, either reply to this email or
visit the message page: To
unsubscribe from this thread, please visit the message page at
. In the Actions box on the
right, click the Stop Email Notifications link. Start a new discussion in
Photoshop Lightroom by email
<mailto:[email protected]> or
at Adobe Community
<https://forums.adobe.com/choose-container.jspa?contentType=1&containerType=14
&container=3316> For more information about maintaining your forum email
notifications please go to http://forums.adobe.com/thread/416458?tstart=0.
>

Develop module problem in LR 4 not resolved by upgrade to LR 5

I just upgraded to LR 5. I was having this problem with LR 4 which I hoped would go away with the upgrade, but it hasn't. I'm using Windows 7 64 bit. In the develop module, the sliders change the histogram, but not the image in the main screen. I do see the changes in the filmstrip below, but of course that's not adequate. Also, sometimes in develop module the image doesn't even appear, just a gray rectangle. I found on the forums that others had this problem, but there is nothing current about it, and it doesn't seem to have been resolved for others. I"ve rebooted several times without improvement. Others previously tried a variety of maneuvers without success such as deleting preference file and uninstalling/reinstalling. Please help as I am currently completely dead in the water.

Have you Profiled and Calibrated your monitor using a hardware device such as Greytag Macbeth i1 Display 2 or Spyder one? If not this is possibly the problem.
You can test if this is the problem by doing the following.
a. Close Lightroom and other open software programs.
b. Go to your Control Panel and under Appearance & Personalization click "Advanced settings"
c. In the popup dialog select the "Color Management Tab then click on "Color management"
d. (take a note of the current default monitor profile)
e. In the list of ICC profiles Select "sRGB IEC 61966-2.1" and set as the default monitor profile. (if it is not present click on the add button and a list of addition profiles on your system will popup the sRGB profile should be there select it)
When done you can close all the dialog boxes.
Try using Lightroom and see if the problem goes away. Post what your experience is so that more trouble shooting can be done.
See the screen capture.

Lightroom 4 (and 5) Develop Module Preview Problem

The Develop module in Lightroom 4 (and 30 day trial of 5) is not updating/rendering the preview as I edit RAW image files. It also doesn't show the full size preview unless I zoom in on the image in the Library view first. I do have the latest RAW and the lrdata file is in the same folder as the catalog file. I have the RAW Cache set to 5gb and noticed there is nothing in the RAW Cache folder (doesn't seem to be important for editing anyway. The Navigator window and filmstrip versions do seem to update as I make changes.

Alright,
no replies so far! Anyways, here's some more information which is leading me to the conclusion that the bug causing the effect described above is a combination of Apple's SMB implementation of Mavericks and the way Lightroom is actually using SMB network access:
I did another trial by connecting a USB hard drive to the USB port of my router (Netgear). The connection is quite slow, but moving one of the folders in question (see my 1st post above) to the shared drive connected to the Router made Lightroom on my Windows machine to see the photos again, when I told Lightroom where to find the moved folder!
Everything was working as expected, on the Windows machine again! Moving the folder back again to the Mac Mini fileshare was causing Lightroom on the PC to get blind again for the pictures trying to sync or import. However, accessing and modifying a photo was possible again, like it was before the trial. So it's only the sync and import function having a problem!
I also did some trial in re-building ACLs and access rights on the file server with no luck. So there's got to be a functionality in sync and import of Lightroom which is using a certain SMB feature which is not supported by Apple's SMB implementation!
Any thoughts or hints?
Thanks!

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.

Developer Module only shows blue square with a white cross, images are displayed in the library ok but not im developer Module

Ive just updated to LR 6 from LR 5.
The app seemed to launch ok but as I was looking around none of my photos will open in the developer module, they just have a blue box with white cross??

It seems to be something to do with Lightroom 6 accessing the GPU. I had this problem and under the "Performance" tab in "Preferences" (Edit menu), there's a box that says "Use graphics processor". I unticked this box and now the images are displayed in the developer module. I'll need to investigate further to find out why Lightroom is not working with my GPU but at least I can use it now.

Having problem with develop module

When I take a pic from library to develop module, I get the "loading" message but then it doesn't go off (and doesn't load); this is a new problem; hasn't happened before; I don't know if recent loading of 2.6 version caused a problem. Thanks for any insight.

Is there anyone that can help? This is frustrating to say the least. The edits are taking effect, but only showing on the filmstrip. If I go back to library the edits are there, and will then show in develop when I take it back again. This makes it just about impossible to apply anything like cloning, or minute edits, because I can't see them when they happen!!

Lightroom 2.2 Develop Module Lockup Problems

I have a Windows XP SP2 system with the following specs:
AMD 64 X2 4400+ processor
2GB of Ram
Nvidia 6600GT Graphics (128mB ram)
NView shut off
3D settings: performance
Norton Internet Security 2009 with Lightroom, cache and image file types excluded from scans
The problem that I am experiencing is as follows:
When I am editing an image in the develop module, the Lightroom application will randomly freeze. When the application freezes, the title bar of the Lightroom application window will revert to the blue bar that is the default for the active window within Windows and the cursor symbol will switch to the hourglass and the Lightroom will be completely unresponsive. Sometimes, the problem will clear itself in 30 60 seconds time and the program will become operational again. But, on other occasions it will remain completely locked up and will require a forced shutdown and restart of Lightroom using Control-Alt-Delete.
This problem started with Lightroom 2.0 but occurred infrequently. With Lightroom 2.1 and 2.2, the lockups occur much more often. Also, I have had one instance where the computer completely locked and I had to do a forced shutdown of the entire computer with the power button. When I attempted to restart Lightroom, it complained about not being able to read the database and shut itself down. I started the application again and it came up but appeared to have reverted to an older database backup as I lost all of the edits that I had made during this working session.
I havent been able to determine any specific task that triggers the lock up but I am using the develop module and am doing tasks like selecting another image on the filmstrip, making an adjustment or selecting another tab in the develop pane.
I have updated my nVidia driver to the latest released version as I thought that this might help but I didnt see any changes following the update.
This problem never occurred with Lightroom versions 1.x and my system is very stable otherwise. I treated the temporary lockups as an annoyance but having the database not be readable after the forced shut down of the computer is extremely concerning to me.
I love the idea of Lightroom and plan to stay with it but I need help in resolving this issues. Thanks in advance for your suggestions.
Dave Mayfield

I have exactly same symptoms as Dave Mayfield.
Except I moved images to sub-folders and renamed them, from within Lightroom.
After it locked up, it did not show sub-folders in Library and all the images have question marks on them. If I show it where the file is in Explorer, it does not show any changes.
I Imported one folder and it could see the images in the folder.
Some were without any changes.
Some were the final edited configuration, but not change history shows in Develop. It is if it kept an Exported fersion.
HELP!
Jack Lane

Development module slow display problem

Similar Messages

Maybe you are looking for