Bug Reports

Playing this video in Lightroom's Loupe View will case high CPU usage by VTDecoderXPCService(more than 300%) and dynamiclinkmediaserver(more than 80%) process, and always stuck while playing this video.Playing the same file in Bridge 10.1.0.163 is fine, VTDecoderXPCService uses only 3% CPU and dynamiclinkmediaserver uses only 0% CPU.Playing the same file in finder's Quick Lookup is fine, too, VTDecoderXPCService uses only 3% CPU and dynamiclinkmediaserver uses only 0% CPU.I've uploaded the video file here:https://www.dropbox.com/s/ga6co10h4vyw89b/2020-06-26182631.mov?dl=0Environment:macOS Catalina 10.15.5Lightroom Classic 9.3

[This is fixed in LR 8.3 -- John Ellis]LR unnecessarily reduces the precision in exported EXIF GPS coordinates to about 18 centimeters.  A trivial one-line fix would increase the precision of exported coordinates to about 0.004 centimeters.ModernGPS augmentation systems and post-processing can produce coordinates with accuracy at the centimeter level or finer.   For example, this LR user is processingdrone pics for photogrammetry applications: https://forums.adobe.com/message/10936939Thisbug affects coordinates in exported JPEGs and TIFFs but not in raw XMPsidecars, which maintain high precision.WorkaroundAworkaround is to use the Run Any Command plugin to create an exportpost-process action that runs ExifTool with arguments that copy the GPScoordinates from the original to the exported file.Details of the BugEXIFrepresents GPS coordinates with three rationals (fractions) for degrees,minutes, and seconds. The numerators and denominators are stored as 32-bi

I updated Lightroom Classic (MacOS) to 9.0. I'm running MacOS Catalina 10.15.I don't exactly know when it happened, but at some point, LR Classic started to show multiple drives in the import window. I only have one drive on my Macbook Air ("Macintosh HD") and up to a certain point, it has shown only this one. Now it shows three (3) versions of the drive - the first two are very similar in content, the third one is empty (I cannot expand it by clicking on the triangle button).Is this a known bug?

In the passed I managed my video clips in Lightroom CC, since today I have LR Classic CC and it seems, that Adobe took out all video functions. Even I cannot open (to have a look) videos from the old catalogue. Is this a bug, or ist the function not existing anymore?

In the Library grid view or anywhere the filmstrip is displayed, if a cell is too small to display all the badges for an image, clicking on the left border area acts like you're clicking on a badge, even though it's not visible.In the screenshot below, the cursor is in the border area, but you can see the partially hidden GPS/map badge is highlighted and active.  Clicking in that area of the border should just select the image, but instead takes you to the Map module.In this screenshot, the mouse is a little further left in the border and the tool tip shows that the keyword badge is active in that space.  Clicking in that area should just select the image, but instead takes you to the Keyword panel in the Library module.I have "Ignore clicks on badges" turned off in preferences and prefer that behavior, but I would still expect that clicking anywhere in the blank border space would only select the image.I have been able to replicate this on multiple machines with Win10 / Lr C

On first use on an image the guides of the local adjustment tools are not visible (see linked video for a demo)Steps to reproduce: In any library mode, select an image and place the mouse cursor in the central area Press M (or Shift+M) to select the gradient or the radial filter Wait for Lightroom to automatically switch to develop mode, then click and drag to place the filter, release the mouse button ⇒ neither the pin, nor the guides are visible until you hover one of the side panels with the mouse, then go back over the image   Workaround: hovering one of the side panels before dragging to place the filter avoids the issue.Extra info: This issue has been around for a while now, but is still present in R11. There are other steps that can lead to the bug, the ones described are the most easily reproductible Whether the « Show edit pins » option is on « Auto » or « Always » makes no difference. Configuration:MacBookPro / Catalina 10.15.4 / Core i7 2.6GHz / 16GB RAM /

CR2 vs CR3 RAW file | exported jpg file does not have same EXIF data mapping for "Lens" tag

This bug started happening to me probably after the latest 9.2 update. 1) Prepare a flat preset, with all parameters set to their neutral position, and no local adjustments. Let's call this preset "Rawest". Make sure everything is selected when you save it, especially the "Graduated Filters" and "Radial Filters" options. Now, this preset is supposed to restore everything to flat and remove any Gradient and Radial filters when selected.2) Pick a photo, and select the Rawest preset. As you can see, no local adjustments are present and everything is flat.3) Edit the photo and add some Gradient/Radial Filters. Here I added 2 Radial Filters, one on the top-left corner, and one on the face of the horse.4) Now select the "Rawest" preset that you created in the beginning.5) Look at the Radial Filters: they have not been removed. Parameters in various panels have returned to their neutral position as expected, but every the Radial Filters are still there. This was not happening in previous

The title pretty much sums it up. Create any combination of Radial Filters, Graduated Filters or Adjustment Brushes on your image. Make the image B&W (V). Toggle the B&W Adjustments off and you lose all of your adjustments. REPRO:- launch LR Classic- D to edit an image- add any combination of Radial Filters (shift+M), Graduated Filters (M) or Adjustment Brushes (K). Just one will suffice. - V to convert to B&W (starting in B&W has the same effect)- turn off the B&W adjustments (this is the HSL tab if the image is in color)RESULT: All adjustments are gone. Poof! EXPECT: All adjustments to remain in place. LR Classic: 9.2macOS: 10.14.6

Develop Auto can produce noticeably incorrect histograms. To reproduce:1. Import this raw file.2. In Develop, click Auto. Observe this histogram:3. Go to Library, then back to Develop on the same photo.4. Observe this histogram, which differs a fair bit in the highlights:Tested on LR 8.3.1 / Mac OS 10.14.5.----------------------------------The bug's cause: Auto doesn't set the following Develop settings, which are normally present in Process Version 5 photos:Brightness = 50Contrast = 25Exposure = 0Shadows = 5Even though these settings are for Process Versions 1 and 2 and don't normally affect Process Version 5, somehow their absence is tripping up the histogram.To prove this, insert these steps:2b. Use  the Show Catalog Metadata plugin to examine the develop settings -- those  four settings are all nil. 3b. Use the plugin to examine the settings again, and notice those settings are now present with their default values.4b. Use an SDK debugger to remove those setting

Develop displays histograms for identical images with small but noticeable differences, and these differences depend on the order in which you edit the files.  By itself, this probably doesn't have any impact on users, but it may indicate a worrisome underlying bug in how Develop caches computations.See this screen recording, and follow these steps precisely:1. Download this sample raw into a folder and make a copy of the raw in the same folder. Rename the two raws A and B.2. In LR, do Preferences > Performance > Camera Raw Cache Settings > Purge Cache. 3. Restart LR.4. Import A and B.5. In Library, select A and make a virtual copy.6. In Library, select A and Cmd-click B (order is important).7. Go to Develop, and use the cursor keys to switch between A and B.  The histograms appear identical.8. Go to Library.9. Without changing the selection, go to Develop, and use the cursor keys to switch between A and B.  The histograms now have small but noticeable

In Lr Classic 8.4 open the Preferences dialog and on the General tab uncheck the "Automatically check for updates" option. Close the Preferences, then close Lr. Relaunch Lr, open the Preferences and look and the "Automatically check for updates" option. I find that it is always checked.I edited the Preferences file and found thatnoAutomaticallyCheckUpdates = true/falseis always set correctly on closing Lr according to whether I have unchecked/checked the "Automatically check for updates" option in the Preferences dialog. The problem is when Lr is launched again, it seems that although the Preferences file option is being loaded, it is not being used to initialise the "Automatically check for updates" check box state.I think it is an initialisation problem because unchecking the option, closing the Preferences dialog and then opening it again shows it unchecked. However, closing Lr when the option is unchecked and relaunching always shows the option as checked, even if internally the op

Hello as a keen birder, I have a multitude of pictures of birds which I classify by Bird family(as title), bird name(as caption) ,date of picture taken and eventually sequence.I used to use the EXPORT function and do a rename of the DNG picture into a new Jpeg file name.As Title I had the format like as example 23.100, which would mean bird#100 out of family #43.So my resulting new Jpeg file name would be 23.100-birdname,date-sequence.Jpeg.However with version 9.1 this does not work anymore. ! ( Not sure when the change occurred as I went recently from 6.4 standalone- which is OK , to classic 9.1)The title with such a numerical format is ignored when I edit the Rename Preset like {title}-{caption},{date}-{sequence}.When I leave out title in the previous string, the rename works ( obviously with just caption,date and sequence).If I leave it in the string, just the first numerical digits before the dot , in the example 23, are shown, without caption, date,sequence !If I change the title

The Presence subpanel of Develop's Basic panel doesn't display properly when the process version is 2:Tested on LR 9.0 / Windows 10. It occurs with someone else using different graphics hardware and an up-to-date driver, so almost certainly not a driver issue:https://community.adobe.com/t5/Lightroom-Classic/v9-0-for-Windows-not-displaying-Texture-or-Dehaze-Sliders/m-p/10726166#M162655

When a raw that's been rotated 270 degrees CW in the camera and flipped horizontal in LR is opened in Photoshop from LR, it opens upside down. To reproduce:1. Turn off the option Catalog Settings > Metadata > Automatically Write Changes Into XMP.2. Import a raw that's been rotated in the camera 270 degrees CW (90 degrees CCW). Make sure no .xmp file for the raw is present before you import. (The raw should have EXIF:Orientation = Rotate 270 CW.)3. Do Photo > Flip Horizontal.4. Do Photo > Edit In > Edit In Adobe Photoshop 2020. 5. Observe the photo is upside down in Photoshop.Tested in LR 9.2 / PS 21.1 / Mac OS 10.14.6.

When using a lens with a max. aperture below 1.0 (e.g. 0.95), the exif data seems to be recognized, but it's not usable in the Library Filters, in the text-bar below the histogram and also not in Smart Collections.It seems as if the code simply doesn't support values below 1.0.Please contact me for further details if needed.

LR's use of "|", "<", and ">" as hierarchical keyword separators is not documented.In the User Guide section Add Keywords To Photos, it should say:"Type keywords in the field labeled Click Here To Add Keywords in the Keywords area of the Keywording panel. Separate keywords using commas. Use vertical bar |, <, or > to indicate hierarchical keywords, such as animal|dog, animal > dog or dog < animal."(Text to be added in italics.)In Preferences > File Handling, it currently says:That should be modified to:"The vertical bar |, <, and > are automatically recognized as hierarchy separators."

Camera specific profiles missing once updating from Lightroom Classic 9.1 to 9.2https://community.adobe.com/t5/lightroom-classic/missing-camera-profile-since-9-2-with-z6/m-p/10929699?page=1#M177187

If do you clic on GOOLE word in map modul, Google Map is open in external browser, this is OK, but if do you presse on shift + clic, Google map is opened in the LR windows and no possibility to close that, I do closed the LR windows !!!LR 9.0 on macOS 10.15.3

I'm breaking up my master catalog into individual years so they're smaller and run faster. I created a new catalog (say 2019) then choose "import from another catalog", which I choose my master. It takes a while, then compiles a list of files to import (they are originally all checked boxes). I uncheck all the boxes, then select only files from 2019...this works really well...until I get to a file that has a large number of images (say around 8000 or higher). It refuses to allow a checked box on these large files (even though they were originally checked). Seems to be a bug, I've tried everything to work around this. Any suggestions?

after moving the original files to another directory and want to create HDR or Panorama, these functions do not work! I have to restart Lightroom to use these functions !!

There is an issue (buck with the slideshow exportation:If you sync edits of a big amount of pictures, or read metadata from file, LR does generates a slideshow (video) WITHOUT taking the edits into account, UNLESS being charged before.By charged before, I mean being displayed and thus rendered, OR 1:1 preview generated.This is quite a big bug, imho.

When importing photos and videos to Lightroom from disk (copy, add) from a particular directory, the import of the .mov files would fail with a message indicating that the connection was lost with the dynamicmediaserver.exe process.  Once the dynamicmediaserver.exe process hung, I had to kill the process to get Lightroom import working properly again.  However, every time I tried to import .mov files from the particular directory, it would hang again.  The problem appeared to be a very small .mov file with only a single video frame.  When I removed this file the dymanicmediaserver.exe process would not hang, and the import proceeded normally.

The color filter squares in the filter bar above the bottom thumbnail bar do not have color on a 4k monitor. They show as the background color with a little white dot in each square. Floating over each little square pops up a dialog with the color I'm hovering over, but that is not an efficient UI.The color picking squares in the upper filter bar above the gallery view do show the colors. Can we get color added back to the lower color selection squares?

If you open Lightroom Publishing Manager, the Video Format in Video section is not updated correctly when you switch between publish services.See the video   1. Change the video format setting to H.264 in the Hard Drive publish service.2. Switch to Flickr publish service while saving the previous change.3. The video format setting is originial in case of Flickr.4. Switch back to Hard Drive.Actual result:the video format setting changed to original in Hard Drive publish serviceExpected result:the video format setting stays H.264 as it was set previously