Bug Reports

Using Lightroom CC2015.7 and Photoshop CC2015.5.11 )If Photoshop is CLOSED and then I "Open as Layers ....." the computer will just sit there doing nothing.  If I click Photoshop to open it then the operation will complete and the photos will be layered.  I THINK THIS IS BUGGY BEHAVIOR  As a side note, this BUG affects the Panorama and HDR the same way.   Photoshop has to be opened manually.  The "Open as Smart Object works correctly.  2) If Photoshop is OPEN and then I "Open as Layers ...." the photos will open as layers in Photoshop  3 )If Photoshop is CLOSED and I  "Edit in Adobe Photoshop ..." Photoshop will open and the two photos are loaded as separate objects.  This is the expected behavior. I think this is a change in behavior in Lightroom CC2015.7

After updating to LR CC2015.6 and PS CC2015.5 I have noticed that develop settings applied in LR to TIFFS disappear after editing the TIFFS in Photoshop (e.g. I lose my crops applied in Lightroom). It's a major part of my workflow and very annoying.

I am using the LR Mobile app on my Android phone. Until recently everything was working perfectly. Since the last update to the Android app on July 10 photos I have taken with my LR app camera continue to sync to my Adobe Cloud account but they do not get synced to my desktop LR Classic as they did previously. Photos I take with the native Android Camera app do sync to both Adobe Cloud and to my desktop LR Classic.  Is anyone else having this problem and can anyone help me with a solution? Thanks in anticipation.

Raw image files shot with identical, manual exposure settings are not matching after develop sync is applied (360° panorama shots with nadir shot). I think I've narrowed the problem down to specifically the highlights slider.LR Classic, 8.3.1, CR 11.3, MacOS 10.14.5.An ACP member at Adobe LR Forum verified issue and suggested I post problem here (link to that discussion.)Link below to two Sony raw files, shot with exact same f stop, ISO and shutter speed, manual WB. If you take the highlights slider down to say, -50 on the image ending in 179, and then sync that with the other image (182), the second shot gets much darker. In order to stitch these, I need them to match. (I realize the floor is darker than the walls, but the floor is not matching between two shots after dev sync). Link to raw files.

I am using lightroom Classic CC 7.0.1 and Camera Raw 10.0. Is there a limit to how large a file can be and still be able to create a 1:1 preview?  I have a 16 bit TIFF that is 26246 x 2899 pixels.  When I try to view it at 1:1 or any other size except "Fit" in the Library module, it refuses to draw (Fill works so long as I don't try 1:1 first).  I just see a grey box. I can view it in any size in the Develop module or Photoshop, but not the Library module.  Does the Library module have a size limit, and if so, what is it?  I also checked the Task Manager and it showed the CPU and disk had little or no activity, and memory was using 15GB which is not unusual on my system. I have 3.67 Terabytes of unused disk space. I have an i7 6700K processor running at 4.00GHz and 32GB of DDR4 Sdram memory and Windows 10 version 1703.

In Color Treatment mode, when an image has at least one Graduated or Radial Filter local adjustment, then activating the TAT on the HSL/Color panel results in Convert to Black & White No being added to the History panel.In Black & White Treatment mode, when an image has at least one Graduated or Radial Filter local adjusted, then activating the TAT on the B & W panel results in Convert to Black & White Yes being added to the History panel.This problem does not occur when there are no Graduated or Radial Filter local adjustments, nor does it occur when the only local adjustments are Local Brush Adjustments.These are meaningless steps being inserted into the History panel every time the HSL/Color or B & W TAT is activated after a Graduated or Radial Filter has been added.Yet another annoying new bug in LrC 9.3 for which I use Undo to remove from the History panel every time it occurs.

Now if I tap on an existing Graduated Filter pin, it adds Update Graduated Filter to the History list every time I tap on the pin.MacOS Mojave 10.14.6MacBook Pro 14.3

Clic droit sur un ou plusieurs photos sélectionnés....Peut-être des erreurs de traduction de l'anglais vers le français !Si activé sur une photo dans un dossier sélectionné = "Retirer", si plusieurs photos = "Supprimer" ?????Si activé sur une photo dans une collection sélectionnée = "Supprimer", si plusieurs photos = supprimer, ce qui n'est pas logique, car par défaut, dans une collection, l'image ou les images sont retirées de la collection.... Il serait préférable de mettre "Retirer"....La version anglaise utilise toujours le mot Remove !Il faudrait aussi modifier les intituler du menu PhotoSupprimer de la collection devient Retirer de la collectionSupprimer les photos sélectionnées de Collection devient Retirer les photos sélectionnées de CollectionLa version anglaise utilise toujours le mot Remove !

P: gpu issues

... won't turn off. See screen caps. What else do I need to do to stop it?Thanks

At some point, Lightroom set the blue color label on my photos to "blue" instead of the standard "Blue". This results in the toolbar filters & smart collection by color label not picking up these values. The only way to find the photos is to use the Attributes filter at the top of the grid, which will display the text values of the color labels, both "blue" and "Blue". At this point, the color labels of the incorrectly marked photos can be updated to the correct labels (via keyboard shortcuts or menu option). Going forward, all the photos will then be able to be found via all the filter options.I've reported this as a Lightroom bug, but it might help someone so I'm reposting this problem & solution here.See below the screenshots, illustrating the issue- Notice the two highlighted blue photos- Notice the filter results, filtering for blue photos, do not include these two photos- Notice the attribute value of "Blue" in the filter list for the photos, matching the Blue color label

In Library mode, any attempt to display a 50 Mpx RAW image in any 1:n magnification results in a grey box. Image appears only in FILL and FIT views. This renders the library mode useless for culling ultra-high-resolution images for fine focus or motion blurr so I'm basically forced to use a non-Adobe product for that simple function.I've tested this with images shot on Canon 7D, 5D mkII, and 5D Sr. Images from the 5D Sr are the only one's that have a problem and it's only since the new Classic CC 7.0 release that this has come up.PLEASE GIVE US BACK THE OLD VERSION OF Lightroom CC. It may have been slow but at least it worked.

Many digital cameras prepopulated the "Caption" field of images. My Olympus annoyingly does this with "OLYMPUS DIGITAL CAMERA", and this is one of many cameras I've owned that has this "feature".Luckily I can create a Metadata preset for Import in Lightroom that sets this field blank.However, when these photos are then later synchronised to LR Mobile, this field gets reset back to "OLYMPUS DIGITAL CAMERA".As each photo is uploaded the Caption field gets populated. I suspect it's copying the value from the "Video : Description" field which has the same manufacturer's prepopulated text.Camera prepopulating Caption field:When LR Mobile uploads, I think it is looking (wrongly) at this Description field even if you've set Caption to another value:

All the time that I worked with Lightroom I saw one annoying problem: curves is very slow. I mean very slow response to my mouse move. If I'm using curve in Photoshop in file of any size time response between my mouse move and image is perfect it's real time. If I'm using curve in Bridge (open file in ACR of any version) time response also perfect. But in Lightroom using curves is much slower like "oh... may be I come back to old days with 486 PC" 🙂I'm opening same images in ACR and Lightroom and in same windows size.Also I should add that size of curve in Lightroom is smaller then in ACR so it's harder to make precise adjustments.

Hey there, following problem exists with export function and setting limit file size to" on Lightroom 4.0. Description to reproduce: Trying to export the sample file as jpg with max. width of 600px and limit file size to 150k. Current behavior: Export will not be done. The error message "Could not create a JPEG that met your limit of 150k bytes" is shown. Expected behavior: JPEG quality should be automatically be adjusted to create a file with size of 150k or lower. Manual export setting: Doing manually the export without using "limit file size to" and setting quality to 80, the result is an file of 142k bytes. So reaching a file with correct size is absolutely possible. This problem can be also reproduced on LR 4.1 RC1 and 2. Seams that only files with hight high white content are affected. Please tryout the problem yourself with the sample file and promote for this bug. Thanks Jörg

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