Lightroom Classic

When I publish photos to SmugMug with the plugin, any photos with a recognized face are not marked as 'Published'. They instead remain eternally 'Modified need to re-publish' This is very annoying, since I have faces in a couple thousand photos. Any time I sync my Smugmug gallery, I tries to re-upload all these photos again, even though they're up to date.

I have created a slideshow with a white text overlay that shows the image Title. I reduced the text overlay box to its minimum size, and the resulting text in the slideshow is fuzzy and pixelated, not clean and sharp. Even when the text is larger the outside border of the text (black) is not aliased, and shows ugly jaggies. MacbookPro Retina 15, OSX 10.8.4 using Best for Retina display. However, the text renders smoothly on Win 7.

When trying to select a page layout in the book module of Lightroom, the pop-up menu to select the new layout is visible but the scroll bar is not. All of my Adobe apps are up to date. I am running Windows 7 Home Premium with SP1 installed; I have also installed all recent updates for the OS.

The Pano Module is really strange it it's behavior. Or call it buggy since that's matching too.I have 2 sets of pictures that can't be rendered als panorama because of some "unknown error" in the middle of the rendering process. Images itself look fine.I have at least one set of 10 images that will only be rendered correctly when the last setting used in the module was the perspective one. If I set it to something other or change the setting and go back to perspective the panorama gets messed up quite heavily. (example at http://imgur.com/a/fF2Mo)Sometimes, as in the upper example too, there is a big chunk of the panorama missing - every time on its left side. In the upper example half of the left plane.

The command Map > Tracklog > Set Time Zone Offset is not documented:  https://helpx.adobe.com/lightroom/help/maps-module.html#work_with_photos_and_gps_data. I tediously watched the LR 4 tutorial on that page (10 minutes!), and while the tutorial mentions correcting local times in the Library module, it doesn't mention the Set Time Zone Offset command.

Lightroom: Handling RAW+JPGContext:- Shot RAW+JPG- Import Raw+JPG- Lightroom Settings: DO NOT "Treat JPEG files next to raw files as separate photos"!--> In this configuration, JPEGs are treated as invisible/unaccessible ‘sidecar’ files.The default Lightroom rendering off RAW files may be quite different from the JPEG files coming from the camera.Currently, with this configuration, if you want to have a look at the camera's JPEGs, you can not do this within Lightroom, you need to use a different program!Feature request:Showing the JPG in Lightroom should be possible. Library module: Loupe view, Compare view, (ev Grid view), ... andDevelop module: "Before and After" view --> Possibility to show JPEG in the "Before" part of this view.(Where "Showing" means rendering, not displaying 2 thumbnails.)Mixed mode: I suggest to show (render) JPEGs if no developper settings are present, and Lightroom RAW rendering for photos with developper settings.Thanks a lot,Robert GLOD

Every time I open lightroom 5.6 64 bit, I get an error message that states, "Lightroom encountered an eror when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches." I cannot work on anything! Any suggestions????

LR6 (CC), edit TIF file (imported from PS or NIK). Image "reloads" after almost every Develop module edit. In some cases, all previous Develop module settings are lost, and the image reverts to it's original appearance. Even though the previous Develop module edits are still shown on the History panel - they no longer have any effect. Result - total loss of all user edits. Workaround: disable "Automatically write changes to XMP" in catalog settings. This is what appears to trigger the constant "reloads". Note this does not appear to be related to GPU - the problem occurs exactly the same whether GPU is enabled or disabled. Also note, the problem does NOT occur when editing RAW files. So far, it appears to occur only with TIF files. Lightroom CC, 2015 Release Windows 7, 64-bit, all latest updates AMD Radeon HD 7700, latest AMD drivers

Hi everybody, I experienced a bug in LR scrolling behaviour within the library module. To describe the problem best, I recorded a screencast video with audio comment that I uploaded to my webserver: http://www.silentcreek.de/lrbug/demo.avi In short: Scrolling with the mousewheel over folders in LR's library module doesn't work properly. Here is what I know: 1) The bug doesn't always occur. Sometimes scrolling works for a couple of days, but most times it doesn't, which is annoying, of course. 2) I could only reproduce this bug as shown in my demo video in the library module when trying to scroll with my mousewheel over the folders or publishing services. Everywhere else, it works fine. 3)The bug seems hardware independent: I experienced it on my laptop as well as my desktop (one Win 7 32bit, one Win 7 64bit; two different mice, one by MS one by Cherry). 4) I experienced this bug for quite a while with different versions of LR (currently 3.5, but the earliest version I used was 3.2) I h

Since updating Photoshop and Lightroom, I've noticed that the aux:lens metadata field is being deleted from my images on import, such that there is no lens listed after import. I've determined that it's Camera Raw 9.5 that seems to be the culprit, as lens metadata is retained if I use an older version of the DNG Converter v8.8 to import the same images.For example, I had an image shot on a Sony RX100 III at 8.8mm. If I import this image with the old version of DNG Converter, and then open the converted DNG in Photoshop, the lens is reported with the full-frame equivalent focal lengths, i.e., 24-70mm F1.8-2.8, and the raw metadata has the correct aux:Lens field (24-70mm F1.8-2.8).Conversely, if I import the same image directly into Photoshop or Lightroom, the metadata will display the correct focal length, but will not display the lens information; Lightroom reports this only as "unknown lens," and in Photoshop the aux:Lens field is missing completely.For now, I will use the old ve

The LR CC Soft Proof RGB values shown in the Histogram are incorrect when the cursor is hovered over a specific area of the image. It does not matter what color profile is used or if the ' Graphics Processor option is enabled or disabled in LR Preferences. The values remain the same and incorrect regardless of the Profile selected in the Soft Proofing panel. The Soft Proof Histogram appears to display the LR Native Color Space values (Melissa RGB) without RGB data conversion to the Profile color space setting in the Soft Proof panel. Please see this post for further details: https://forums.adobe.com/message/7489...

Lightroom 6: When running an Impromptu slideshow from the develop module - the first image looks very pixelated - like an upsized thumbnail, very soft, with no fine detail at all. Other images in the slideshow look like 'normal' slideshow images - still unacceptably softer then the image is displayed in the develop module, but much better than then first image. Playing the slideshow from the slideshow module generates 'normal' slideshow images. Also an impromptu slideshow from the library module does not show the problem on the first image. Changing the slideshow quality setting appears to make no visible difference. Also turning on or off use of the graphics processor makes no difference.

After the 6.5 update, I can no longer merge to HDR from images in a collapsed stack. Previously, I was able to create stacks of images, then collapse the stacks and then I would highlight the stack, and click ctrl+shift+h to perform the HDR merge. Now when I do that same combination on collapsed stacks, I get the error "An internal error has occurred. Unknown errors occurred."I CAN however select each individual image in an uncollapsed stack and perform the merge to HDR. Is this a feature that was purposely taken out of 6.5, or is this an error?

After the Lightroom 2015.5 (march 2016) update, Lightroom doesn't work anymore. Ask to change permission of folders in library manually. I did as told and it still doesn't work...

After upgrading from 2015.4 to 2015.5, there is a change in behaviour of the keyword box in Library module.When you have entered keywords and press Ctrl/Cmd+RightArrow to move to the next photo, in the previous version the focus would remain in the keyword box so you can keep adding keywords. In 2015.5 the focus is lost and you need to press Ctrl/Cmd+K to re-focus on the keyword box, slowing down the tagging process.

LR Mobile doesn't correctly handle capture dates when the time zone of the phone changes.   LR Mobile adjusts the displayed capture date to the new time zone rather than showing the original date/time as LR Desktop does and is specified by the MWG's Guidelines for Handling Image Metadata (2.0). Here are the steps I followed on iPhone 6 / iOS 9.1 / LR Mobile 2.2.1 / LR CC 2015.5 / OS X 10.11.4: 1. Add a photo from the camera roll.  LR Mobile correctly shows its capture date as 3/31/16 2:33 pm.  The photo synced to LR Desktop shows the same date.   2. Terminate LR Mobile. 3. Change the time zone of the phone from Cupertino (UTC - 7) to Boston (UTC - 4) via Settings > General > Date & Time. 4. Start LR Mobile. The photo now shows an incorrect capture time of 3/31/2016 5:33 pm, adding the three-hour difference between the new and old time zone. 5. Make an adjustment to the photo and wait until it syncs to LR Desktop.  The capture time in LR Desktop still

I've submitted an issue for this with Adobe but, perhaps because of some communication issues, they have reported that they are unable to reproduce the problem. My question to the community is - can anyone else verify the following - using my steps and explanation? Environment: iMac 27" with only the single monitor. OS 10.8.2. Lightroom 4.2 Basic Description of Problem: After invoking the window for a "second monitor" - which pops up on top of my main display screen, I can close the second window and click on items which were hidden under the second window. If, however, I switch to another "Desktop Space" on the Macintosh and switch back, the area where the second monitor window was located becomes a "dead space" where mouse clicks to select something no longer work. My current workarounds: 1. Open and close the secondary window again - and the area "covered" by the window will start responding (problem is - you need to do this every time - a pain if you set up something like PhotoShop

When you export a TIFF or JPEG with Color Space: AdobeRGB (1998), LR 5.7.1 includes an incorrect value for EXIF:ColorSpace. It should be set to Uncalibrated. But on Windows, it is set to sRGB, and on Mac it is missing entirely. (Note that when Photoshop CC 2014 saves a file in AdobeRGB (1998), it correctly sets EXIF:ColorSpace to Uncalibrated.) This bug probably has very small impact in most cases, since it's likely that most color-managed applications ignore EXIF:ColorSpace when an ICC_Profile is present. But this did cause confusion for one person examining the color space with Windows File Explorer, which shows EXIF:ColorSpace but not ICC_Profile in its Properties window: https://forums.adobe.com/thread/1806639

After last update to Lightroom CC 2015.4 (in Spanish, on Mac OS X El Capitan in Spanish), when importing photos using dates to create folders, the names of the months are in English, messing all the previous folder structure (previous versions of LR used names of the months in Spanish). Happens the same after uninstall / reinstall with clean preferences.It seems a bug in new LR 2015.4

In Lightroom 5.x after the same action CTRL+ALT+S worked Lightroom version: CC 2015.3 [ 1052427 ] License: Creative Cloud Operating system: Windows 7 Version: 6.1 Application architecture: x64 System architecture: x64 Logical processor count: 8 Processor speed: 2,8 GHz Built-in memory: 6135,0 MB Real memory available to Lightroom: 6135,0 MB Real memory used by Lightroom: 1690,9 MB (27,5%) Virtual memory used by Lightroom: 1774,2 MB Memory cache size: 764,2 MB Maximum thread count used by Camera Raw: 8 Camera Raw SIMD optimization: SSE2 System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 1920x1200 Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No Graphics Processor Info: Check OpenGL support: Failed Vendor: NVIDIA Corporation Version: 3.3.0 Renderer: GeForce GT 610/PCIe/SSE2 LanguageVersion: 3.30 NVIDIA via Cg compiler Application folder: C:\Program Files\Adobe\Adobe Lightroom Library Path: T:\L

Just updated to the newest lightroom cc version and now the sliders in the develop mode do not respond to small slider adjustment clicks in either direction. I can move the slider in small increments all the way to either end with no change to the image I'm editing. I have to either use the + - keys or click very large increments.

Lightroom 6 users the old font which results in too small menus under OS X 10.11.

Lightroom CC 2015.4 locks up on my iMac running MacOS X 10.11.3. I had to force quit the application. I've tried several solutions, like uninstalling and then installing the stand-alone installer and the 6.4 updater, and uninstalling and installing LR CC2015.4 from the CC app, but nothing seems to work. The update runs fine on my MacBook Air with MacOS X 10.11.2, so I wonder if it's the combination of both updates that causes the problem.

After installing the 2015.4 update today, I can no longer scroll through images in Loupe view with the mouse. Keyboard scrolling via arrows works, mouse does not, to go from one image to another. Scrolling in the Grid view works fine. I tried two different mouses to make sure. This has never happened in any of the previous versions on the same computer. Any ideas? Thanks

In LR6 if I use the straighten function and make a crop after that and try to straighten again, the crop will be reset. This is very frustating. In LR5 this works fine. If I make a crop at first and straighten after that it woks as expected, but not if I straighten the picture as the first step.