Bug Reports

After publishing new photos from Lightroom to Adobe Stock using the provided plug-in, LR asks me if I want to jump to the web site (Adobe Stock) but I got the following message:"Failed to update the collection.An internal error has occurred: bad argument # 1 to 'openUrlInBrowser' (string expected, got nil)".Photos are correctly posted and I can see them in the collection, but I cannot reach the website directly from LR. The obvious workaround is to open the web browser manually and log on AS.Anyone experienced this unpleasant issue ?Thanks in advance.

LR Classic CC auto upgraded from 8.2.1 to 8.3 ... with that the ability to export videos in 'Original' format fails. (The progress bar shows action, but no files are exported.)  It still can export videos in H.264 format (but obviously downgrades resolution from 4K (3840x2160) down to 1080p which is useless to requirement). I tried clearing video cache and disabling metal video acceleration ... neither addressed the issue.I downgraded back to 8.2.1 and the functionality returned as designed.I would suggest that the LR Classic CC 8.3 rev has a functional error with exporting video in 'Original' format.This is on MacOs 10.13.6

Before I first purchased CC I asked on a forum the question, "will it still run if my internet is down", and I was informed yes.I have moved to a small volcanic (desert) island where the internet isn't always good.  So far I have been luck in that it has been off when I have not needed to be at my computer.  This morning was the first time, but I thought it would allow me to catch up with photo processing and art work. Until I got the message that Adobe can't check my subscription!!!   So for most of the morning I might as well have gone back to bed!Now we are hoping to move further inland, where connection problems are more than likely to increase.  I wasn't bothered until this morning, as I thought I would still be able to use Photoshop and Lightroom. :'( So, have finally got internet back on I opened up Photoshop and Lightroom ok.  When it went down again they did stay open so I see that I must just have a connection in order to open them.So I have to a

Not sure if this is the right place for a bug report, if not could anyone direct me to the right place please.Clicking develop module at top right from the Library module opens the photo with film strip and both side bars black empty spaces. Initial few times I had to quit and restart Lightroom but then discovered switching to grid view again and develop keyboard short cut, everything comes back.

Discovered a BUG with selections in Lightroom Publish collections:When you select several photos within the Library Grid the first/most selected photo does not display as the brighter white colour in the grid, it does display correctly within the film strip.(I checked back through several versions of LR: LR7.1, 2015.12 and LR5.71 on Windows 7 and they all have the same bug. Also LR7.1 using Windows 10 on 2nd computer has same problem.)This only affects selections in Publish collections (tested Hard drive publish, Flickr and jfZenfolio collections)Steps to reproduce:  In a Publish collection select first photo (different from the initially selected photo)  Use SHIFT key and select additional photos Result the '1st' photo does not brighten to show it as the 'most selected'It does work for the following:  If you use CTRL key to make the multi-selection  If you use the initially selected photo upon opening the collection as the first photo, then shift selection works

When sorting Library grid view by capture time, LR doesn't sort correctly by fractional seconds -- it ignores leading zeros in the EXIF:SubSecTimeOriginal field.  To reproduce:1. Take three photos directly from a camera: a.jpg, b.jpg, c.jpg.2. Set the DateTimeOriginal and SubSecTimeOriginal field of the three photos using these commands: $ exiftool -datetimeoriginal="2017:01:02 03:04:05" -subsectimeoriginal=0.1 a.jpg$ exiftool -datetimeoriginal="2017:01:02 03:04:05" -subsectimeoriginal=0.01 b.jpg$ exiftool -datetimeoriginal="2017:01:02 03:04:05" -subsectimeoriginal=0.002 c.jpg 3. Import the photos into LR.4. In the Metadata IPTC panel, observe that Date Created shows what was set in step 2:a.jpg: 2017-01-02T03:04:05.1b.jpg: 2017-01-02T03:04:05.01c.jpg: 2017-01-02T03:04:05.0025. In Library grid view, do View > Sort > Capture Time.6. Observe that the sort order is incorrect: a.jpg, b.jpg, c.jpg.   It should be: c.jpg, b.jpg, a.jpg. Most likely the Lua code is doing t

hi folks,just installed LR CC. Rendering in develop module is really slow. Eg. when I move between photos, it takes a good 3 seconds for the photo to fully render. Displays "loading" for about 2 seconds and then a further second or two before the image is fully rendered.This isn't happening in the Loupe view.This is with a new set of photos I just imported, and I had "build 1:1 previews" set during import.Is this an issue or have I got a setting wrong somewhere?It wasn't quite this bad on LR 5.ThanksDave

I have made a number of profiles to be used with Lightroom Classic CC. Two of them (V1 and V2) are made with the same lens and camera, just under different lighting conditions, and with the same X-rite Colorchecker Passport plugin.Only one of them shows up in the Profile Browser; if I move V1 to a different folder and restart Lightroom, V2 shows up in the Profile Browser and vice versa.I'm on the latest versions: Lightroom Classic CC 8.2.1 on MacOS High Sierra 10.14.4.Is there a way to have both profiles available in the Profile Browser? Thanks.

The title says it all. This should be added to the list of bugs I've posted over the last few years.Is anyone going to fix all the API bugs or are you abandoning the API? There's been no update in 3 years!For example, seehttps://feedback.photoshop.com/photoshop_family/topics/list-of-lightroom-sdk-lrdevelopcontroller-bug...https://feedback.photoshop.com/photoshop_family/topics/lightroom-api-bug-most-transform-adjustments-...https://feedback.photoshop.com/photoshop_family/topics/lightroom-sdk-bug-alt-key-ignored-when-moving...Does anyone at Adobe care? There are lots of users of my free software (over 900 youtube videos discussing how to use it), but I'm thinking of pulling the plug if this lack of support and increasing number of bugs continues.

When trying merge 6 images (which have plenty of overlap and merge without issue in Photoshop), Lightroom Classic CC says "Unable to merge the photos.  Please cancel and review your selection."  There is no indication why these photos cannot be merged by Lightroom.

I've tried the dust cover in my latest draft, and the only way I manage to edit it to include left (at beginning) and right (at end) inside covers is by trial and error with front and back covers.   That is, there should be FOUR parts to edit - cover, back, AND left and right inside dust cover.   Plus I can't move anything around on the dust cover.   I have to go back to develop and change/crop size.  Am I not seeing something?   Or should that code be updated to work for the 4 images of the dust cover?

This post needs a body  

I use a laptop when travelling.  I have exported the keyword list from my desktop to the laptop.I added a new photo onto the laptop with the keywords"barkblur' and 'persontest".  They show on the laptop keyword list.  'barkblur' is an exisiting keyword and shows in the folder structure. Whilst 'persontest' a new keyword shows outside the folder structure.I then selected the folder and chose export as catalog and ticked export negative file and include available previews. and saved it to an external hard drive as TEST. Then copied the TEST exported catalog folder to my desktop computer.On the desktop the only one of the keywords show on the photo - 'persontest' only and not 'barkblur'. Person test is a new keyword and bark blur is an exisiting keyword. Image is not available  IN the keyword list the 'barkblur' numbers have not increased and the 'persontest" which is the new keyword does show. Image is not available I hope someone can help with this. Thank you

When deleting files in a folder LR often will not delete one file, even though it is not being locked by another program.  This behavior, at least in Windows, has been present for more than 8 years.  Please, please fix this.If you select multiple images in the loupe view thumbnails you can only change metadata on the first selected image.  You must change to grid view to change them all.  However, other actions, like remove or delete work on all selected images while in loupe view.  This inconsistent behavior is confusing.  Please enable selections for all activities in loupe view.

I was using LR 8.2 today and tried to use the Enhance Details. An error came up saying I needed to update Windows 10 for it to work. I updated Windows 10 and ever since Lightroom Classic CC and CC for Desktop crash upon startup.I have uninstalled Classic CC and gone back to 8.1 and I am able to work. This is very frustrating.

Since I upgraded to V8.3 of Lightroom Classic I can no longer export my files to our Synology Network System, I get the following error message "The specified folder in not writable" After contacting support they were not able to resolve my issue, they maintained that it is a network issue on my side. I could not find any answers here or anywhere on the internet and decided to report this issue.Because I share my processed photos with the rest of the office, my only solution was to un-install V8.3 and go back to V8.2.1, by doing that it resolved my problem.So yes Adobe you have network issues in V8.3 as version 8.2.1 works perfectly when saving files to a network drive.

Hi,I'm noticing an issue in Lightroom Classic CC, in the Library module, when navigating between Collections. This is with the 8.2 release on Windows 10 1803, although the issue was present with 8.1 as well.If I am viewing a collection that is synced with Lightroom CC, and then select a published collection, the grid view in the published collection does not show the groups by publish status (Published Photos/Modified Photos to Re-publish/New Photos to Publish), and hitting the Publish button does not publish any new photos in the collection (e.g. export and upload to Flickr).I can work around this by first going to a non-synced collection, or a folder in the file system view, in which case the published collections work as expected.It is not a work-stopping issue, but it is annoying, especially as I make more and more use of Lightroom CC syncing.Would you be able to help?Thanks!

Several people experience Titles and Captions are removed from images when browsing through synced images in CC mobile for Android. Data is removed in CC classic main catalog as found on main computer with catalog as well. Disappeared for ever.

The documentation lists  photo:quickDevelopSetWhiteBalacne( value ) And that, indeed, is the correct call to set white balance, misspelling and all.So the documentation is correct, and I've had to code it that way in my plugin. Are you planning to fix this by including another properly-spelled function that accomplishes the same thing? Unfortunately, you'll probably have to leave the misspelled version in to avoid breaking current code.

Currently using LR version 8.0 build 1193777I have spent hours designing a book in the book module. Now I am finding many bugs in the program. Some examples:I saved the book, intending to come back to it later for further work. The saved book is essentially not editable.* Try to change a page layout, such as from two photos to three -- the change at first shows but then does not stick; it reverts to the old version.* I decided to change the layout from 10x8 to 13x11. This cannot be done. After as dialog warning of possible unexpected changes -- the thumbnails do not change. Go off to another collection and return to the saved book -- all the page settings show the old size, etc.* After saving the book, there is no longer a "Create Saved Book" button to save changes. I can find no way to get the "save" button back.Searching online I find many complaints of similar problems. Nothing works to fix the problems. The common recommendation is to revert to version 7.5. This works for some peop

This is driving me nuts.  All of my presets aren't working properly.  I reset all of my settings, etc. When I import photos with a specific preset it doesn't apply it properly.  It's like it's applying the old Lightroom algorithm.  This is frustrating.PLUS, it doesn't work when I create a brand new preset in this version of Lightroom.  I setup a new preset that will apply Auto Settings and when I import it still applies old settings, it seems like it's using the Auto Settings from a few versions of LR ago.  It's applying settings on import, but not the correct Auto Settings if that makes sense.  All of the other settings, like Clarity, Sharpening, etc still work.  Oh, and Auto White Balance doesn't work on import at all anymore and hasn't since the update before this most recent one.In the past, what 'fixed' it for me was to go to the user presets file and open one of the presets with Lightroom (right click, open with Lightroom) and then it worke

Importing a file, renaming it in Lightroom, then importing any other file with the same name generates incorrect records and does not import subsequent files. This is happening when scanning to a folder with autogenerated names, then using LR to import the files and rename.1) Scan some slides to a folder named e.g. YYYY-MM-DD-sequence.TIF2) Import into Lightroom (synchronise folder)2) Rename or move those files elsewhere using Lightroom3) Scan more files which are again auto-named, with the sequence restarting at 1 because the first ones are no longer there4) Import the new files (synchronise folder)Actual: LR notices the new files but creates duplicate records for the first set of images, even if they have been moved to a different folder and renamed. Removing one of the duplicate records actually removes both records, requiring a second "sync folder" to re-import correctly.Expected: LR creates new records for the new files in the correct folder.

When I use the targeted HSL Saturation tool to select a color, the Magenta slider gets highlighted, but as I move the cursor, it's the Red slider that does most of the moving. Then the undo bezel shows "Magenta" as getting undone (even though the changes to Red get undone also).  Here's a screen recording:https://www.dropbox.com/s/kvnxhcs0v0iehda/lightroom-hsl.2018.08.29.mov?dl=0Tested in LR 7.5 / Macos 10.13.6..

Hi, I've noticed this issue with LR Classic 8.1 and Win 10 (1803). I had experienced this problem on a few occasions, but couldn't notice a pattern until now: it only happens with desaturated tiff images (maybe with psd's too). Then I found this report, but I see that, in theory, it was fixed with v7.5.Anyway, I've captured this small video to show the issue, so that others can check too:https://youtu.be/AmBHYC90McsIs it me or is this same problem back? I've also tried disabling GPU, it didn't seem to make a difference.Thanks.Note: This conversation was created from a reply on: Lightroom Classic: Luminance range masks do not work for grayscale images.

Using LR 8.1with Windows 10 ver1803 when exporting a JPEG file to DNG file format the DNG file does not appear in the LR catalog and the Library module’s Import and Synchronize Folder functions become grayed-out and unusable. Closing and reopening LR restores the Import module and Synchronize folder functions and the DNG can be imported. The DNG file is being created, but not added to the catalog. Using any other file format (raw, TIFF,PSD) works as expected with no issues. I uninstalled LR 8.1 and chose the option to ‘Delete All Preferences,’ but the issue remains!The JPEG to DNG file format export fails as described above when using the below Export module settings. If 'Add to Stack’ in the Export module's 'Export Location’ pane is NOT checked the JPEG to DNG Export works as expected.