Develop Module Problem

Can not open basic panel  while in the  develop module   HELP  thanks.

R-click on the header of any other subpanel on that side and just tick the basic panel and, voila, it will appear.
Tony Jay

Similar Messages

  • 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 6 / CC - Intel HD4400 (and others?) - fix for blue square in Develop module

    Just a note for anyone using an Intel HD4400 GPU (or possibly other Intel GPUs) - I've found that I need to Turn Off the Conservative Morphological Anti-Aliasing in the 3D section of the Intel Graphics Control Panel to get rid of the blue square in the Develop module problem.

    I'm one of the people who talked about how fast it is. BUT after a few solid hours of using it I'm noticing that the interface is still unbearably laggy. Certain things quicker, gradients for example.  One thing that was unbelievably slow for me today was waiting for it to draw a 1:1 preview - it took a minute from a d800 raw file (and it was doing nothing else). Other times its taking ~15 seonds (twice as long as previously).  In the develop module it takes 4-6 seconds before I can edit an image.
    In the meantime my system has gone from a xeon x5650 to an i7 960. I expect things will speed up again when I reinstall the xeon. 

  • 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

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

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

  • 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

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

  • Lightroom 4 Beta crash problem-Develop module

    I have a problem importing a set of .cr2 photos taken in 2010. There are about 75 photos and when I import them and go to the Develop module, the controls are showing those for Lightroom 3 (recovery, fill light, etc.). Then the program encounters a problem and stops working and I have to shut down. I have checked my desktop icon and the path is looking to LR4 (I don't have LR3).
    Now this problem seems to be happening only with this group of photos since I've tested others. There is nothing different from any other raw files I import.

    So "Relative", in this case, is similar to Absolute/Relative?  It would appear to be the case. The "Absolute" color choice is in the Photoshop print dialog, as are the other choices.
    I think.

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

  • Color label setting problems in Develop module

    Today is the first day with Lightroom 3, where I have over 200 photos from an event, that I am walking through each photo.  I am in the develop module and I am setting the color label to red or blue.  What seems to be constantly (not every time) happening is when I click the color for the label, LR will move to the next photo, but not apply the color label.
    As I write this I'm trying it out to notice a pattern.  What I see is photo 1, I click on the red label and the photo is labeled red and LR moves to photo 2.  I click on the red label and LR does not set any color label and moves to photo 3.
    Another thing that happened is I was then at photo 3 and clicked on the blue label.  LR did not set the blue label but jumped to photo 4 and put the blue label on that photo.
    This is very annoying.
    Where might I report this bug to Adobe?

    Same bug as with ratings. http://forums.adobe.com/thread/679696?tstart=0
    Flagging via the toolbar, also shows this problem.
    As noted above, use keyboard shortcuts.

  • 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

  • Problems losing quality when going from develop module to library module ??  anyone have a fix

    Problems losing quality when going to library module from develop module.  Sharpness and color quality decrease

    This is normal. There will be a difference as you are comparing Library Previews with the image in Develop which accesses the original file, although the difference is usually slight. Real results need to be judged from exporting after selecting the output sharpening e.g. for glossy paper, if printing or screen sharpening for web images or emailing.
    The idea with sharpening is to apply capture sharpening so that the image in Develop looks just sharp but not over sharp. Lightroom then uses the correct algorithm for output sharpening based upon image size and quality settings etc.

  • Problems with LR4 -  Develop Module - Edit in CS5

    I've just upgraded from LR3 to 4
    When I make adjutments on a RAW or JPEG file in the develop module, and then send it to PS5 for more work, not all the adjustments show up in CS5.
    Example, I cropped an image, and then made local exposure adjustments using the 'brush' tool.
    Exported to CS5 using 'Photo' 'Edit in', and the image goes to CS but only the crop adjustment is showing.
    I've done all the updates on CS, but this is a pain.
    I'm running a MAC with Snow Leopard OS
    Can I uninstall the upgrade and reinstall..?  Would that be any use...??

    I was greatly confused by all this for a while, but think I finally figured it out, thanks to CSS Simon and others here (I'm new to Lightroom, having only used Ps/ACR previously).
    What happens is that "render using Lightroom" doesn't involve ACR at all. It goes straight to Photoshop (and puts the rendered file alongside the raw). The other option, "open anyway", renders the file through ACR. But ACR 6.6 and before can't read PV2012, that's why you need to install the ACR 6.7 Release Candidate, which can (although it doesn't give you access to the 2012-specific sliders).
    Another thing that tripped me up at first was that no Lightroom edits at all would show up in Bridge or ACR, even with ACR 6.7 installed. I finally discovered that I had to set Lightroom catalog settings to "automatically write metadata changes to xmp" - otherwise all Lightroom edits would just exist in the Lightroom catalog and not be visible to other applications.
    This is of no importance if you only use Lightroom, but it certainly is if you have a mixed workflow with Photoshop and Bridge.

  • Problem Navigating from Box to Box in Develop Module

    Hello,
    In the Develop Module I normally am able to go from adjustment to adjustment (i.e. from Exposure to Recovery to Fill Light) when one is active by hitting the Tab key. Suddenly, the Tab key is bringing me to the slider control rather than directly to the numeric panel that would allow me to input a specific number. So now I need to Tab twice to get me to that box. I don\'t know what changed, but I tried deleting the preference file and that still hasn\'t changed this situation. On my other computer the Tab still brings me from box to box so I can just type in a number to input the desired number... Could you please tell me what has happened and how I can revert it back so that the Tab will bring me directly to the box and I can just type in a number like \"33\" for instance rather than needing to Tab twice between each box to get there? I look forward to hearing back from you. Thanks for your help with this.
    Thanks,
    Andy

    Sorry Andy!
    I can't think of anything that would be causing this. Especially since it appears to be intermittent. There is no toggle switch for the TAB key's behavior in LR that I can find. Without having clicked in one of the number fields to start with TAB will hide and show the side panels. It shouldn't bring the focus to a slider.
    If you first click in a number field and then hit the TAB key does it take you to the next number field or send the focus to a slider?
    Do you have any utilities running on your Mac that may influence the TAB key's operation?
    It is a mystery!

Maybe you are looking for