Bug Reports

Artifacts at Edges of Galaxy S7 RAW DNG Files in Ps, LrClassic and Lr Products Affected: Photoshop CC 2019 ACR, Lightroom CC Classic2019, Lightroom CC 2019, Lightroom CC for Mobile (Android)Description: DNG RAW Photos from the Samsung Galaxy S7exhibit artifacts at one edge after importation or opening in the affectedproducts. The artifact may be solid black or a random set of colors. It alwaysoccurs in a straight strip along one edge of the images. In Lightroom CCClassic it occurs in both Library and Develop modules and sometimes shows up inthe thumbnails on the filmstrip. Sometimes the artifact will not appear inLibrary but will appear there after going to Develop and back.Associated Files:Two affected DNG RAW files from the Galaxy S7, along with ascreen shot showing a typical artifact marked with an arrow are at:  https://www.dropbox.com/sh/73bvkcoxwlmqy7u/AADr1DOYXYzMzA-ad6_FPxeNa?dl=0Reproduction:1. Take a photo in RAW with the Samsung Galaxy S7.2. Copy the photo to a computer

Apple's new color profile: Apple Wide Color Sharing Profile (iOS 10). Filter opens a blank box, but Camera RAW through Bridge opens fine.Converting seems to be a work around (See attached.)I am running a Mac with 10.12 Sierra.

When I convert images to B&W, with some of the Adobe-supplied B&W profiles I see a lot of pixelated banding in the sky of standard previews (when in loupe view after pressing the 'E' key).Rebuilding the preview doesn't help.The only workaround is building a 1:1 preview, either by zooming in or by giving the command to build a 1:1 preview. I can then discard the 1:1 preview and still have a clean standard preview.The preview quality level in the catalog settings is of no influence. My previews are set for 2880 pixels, which exactly matches my screen.I'm using LR Classic 7.3.1 on a 2017 15" MacBook Pro (2.9 Ghz i7, 16GB RAM, Radeon Pro 560 w/4GB RAM) running MacOS 10.13.4 with both images and catalog on the local SSD.Files are .RAFs from a Fuji X-T2. I'm seeing this with at least Adobe-supplied profiles BW 02 and BW 03.Screendump of portion of screen before building 1:1 previewRoughly the same portion of the screen after building and discarding 1:1 previews.Is this normal behavio

When ACR is use as a smart filter on a smart object layer. And later the Canvas size is increased. When I open the smart ACR filter the adjustment brush pins and stroked are wrong. Increase the canvas size again and there wrong. Each time I increase the canvas the Smart filter mask is also increased in size.

The translations of profiles to Swedish are wrong. In Adobe Raw profiles and Camera profiles Portrait is translated to "Stående" which means "standing" and Landscape is translated to "Liggande" which means "horisontal". It's easy to understand why this error was made...Note: This conversation was created from a reply on: Lightroom Classic 7.3 is now available..

This is not just an annoyance - it is a show stopper. When trying to use "Merge to HDR Pro" from Lightroom, it aborts in Photoshop with "Camera Raw Filter is not available" after "Open anyway" was chosen in Lightroom. The same happens when "Camera Raw Filter" is chosen from the filter menu in Photoshop. Photoshop shows Camera Raw is 9.10.0.739 so that's the latest but there's obviously a bug where this is not being recognised as the latest. How do I revert to the previous version of Lightroom and Camera Raw because the use of the Camera Raw filter is part of my normal workflow many times a day.Note: This conversation was created from a reply on: Lightroom Edit in Photoshop warning message since update.

Lightroom 5.7.1 (and older ones like version 3) fail to get the serial number of the Panasonic GH-1 and GH-3 camera bodys from JPEG or RW2 files (the serial number of the lens is read correctly). Why? Nikon cameras seem to work more thoroughly. Free tools like exiftool can read the serial number of the camera body from JPEG and RW2.

P: Leica 35mm 2.4 ASPH not recognised in profile correction

I found out that the presets for WB for Panasonic FZ80/82 are very inacurate and tend to tint pink/purple and green sometimes. Daylight setting is reported as 3300K instead of 5600K and so on. Is it possible to correct that? The first photo is camera WB, the second one Lightroom daylight settings.

Crop tool not functioning properly. It seems other people are having a problem too when using the crop tool with a Wacom tablet (i have Intuos 4) in camera raw. When trying to crop from the side, it shows the two little arrows as it should but instead of cropping it moves the whole picture in the direction I want to crop. This does not happen when cropping with the mouse. It seems to be happening since a recent camera raw update. Has anyone found a solution? Thanks.

I have installed the new Lightroom 4 to import my RAW files from the canon 5d mark iii. I have also installed the Adobe Labs 4.1 release to help fix the bugs. I still cannot get the images to import. It automatically says "No photos or video found to import" and nothing happens. Is there something that I'm missing or are the mark iii raw files still not yet supported by lightroom 4?

Since update of Lightroom to CC2015.10  and Camera Raw to 9.10 (within Photoshop CC2017.1), I am getting a warning message when using Ctrl+E to Edit in Photoshop. The message states that camera raw 9.10 may be required, even though CC desktop app confirms camera raw is up to date and Photoshop "about plug ins" confirms that ACR 9.10.0.739 is installed.

I have my Leica M9 lens selection set to Summilux 35mm 1.4 (the non-ashpherical selection), and in the metadata in Lightroom the photos show as taken with a Summicron 35mm VI. This is a bit annoying. 🙂 I am assuming this is a bug, and I can't find any previous reports on this specifically.

I have some problems with orientation in combination with external editing. - I import my CR2-files in Lightroom (5D II files, full size, DNG or CR2 doesn't matter) - I go to Develop - I right click and do Transform -> Flip Horizontal - I right click and do Edit In -> Edit In Adobe Photoshop CS 5.1 - In Photoshop, the photo opens upside down and I have to rotate the image 180 degrees, to get it right. The problem exists in Lightroom < 3.3, 3.4, 3.4.1 but also in 3.5 RC. A video (sorry for the grey scrambled first seconds) from the february situation of 3.3 is here: https://www.youtube.com/watch?v=UYk4bf... Specs: Lightroom version: 3.5 RC [769362] Version: 10.7 [1] Application architecture: x64 Physical processor count: 2 Processor speed: 2,4 GHz Built-in memory: 4096,0 MB Real memory available to Lightroom: 4096,0 MB Real memory used by Lightroom: 163,3 MB (3,9%) Virtual memory used by Lightroom: 2136,1 MB Memory cache size: 38,6 MB Displays: 1) 1680x1050 Adobe Photoshop Vers

Adobe products wont open converted DNG files from Canon EOS 70D. Other RAW editors open it just fine. It happen because of "wrong" exif data. If you rename exif data from "Canon 70D" to for example "Canon 60D", it opens fine.

I'm having consistent issues with the Lightroom profile corrections for my Nikon 24-120mm f/4 (on a D750). The vignetting correction is inaccurate and produces white arcs inset from the corners of the photos, which are most noticeable in shots with a blue sky. It becomes especially problematic when I'm doing an HDR or applying higher levels of Clarity or Dehaze. I cranked up the Dehaze to 100 to accentuate it in this image.

One of my favorite features in LR/PS was the ability to quickly export a set of images from LR into Photoshop using the Open as Smart Object in Photoshop which would create a new PS document with a smart object layer composed of the exported images. Thus I could use the Smart Objects > Stack Modes to do time lapse composites or various other effects with the various stack modes. This stopped working with the latest updates to LR/PS in CC. Now I have to export them into PS as layers which is much more tedious and time consuming when all I really need is them to be referred to via the smart object. Please bring back the proper behavior. It would be best to have it go to a single smart object layer OR perhaps with the shift key to modify the behavior to individual documents with each image as a smart object but for my needs, I usually want to export the whole batch into a single smart object layer. I know many photographers use this tool and we've been teaching it to others for awhile

In yesterday's version (6.9) the problem with auto applying the lens correction profile for the Batis 85 was solved. But the profile itself is still problematic. In my opinion the distortion correction that the profile applies is way too much. From slight pincushion it takes the photo to a big barrel distortion. Furthermore, the vignetting correction is way off. It can be tested on a gray, even image. The resulting corners will be too bright compared to the center after the correction.

Hi, I've just found a really bad issue occurring in Lr 5 (but also in all other Lightroom versions) under Mac OSX 10.9 with a calibrated monitor: dark shadows (from a value of 20 to 0) are all clipped (pure black with no detail and no textures) while the histogram remains ok, indicating NO clipped shadows at all. This issue afflics also ACR. Photoshop for now is the only software under MAC that reproduces dark shadows correctly: Library Module shows a bit darker and shifted shadows than Ps but acceptable, Develop Module is really bad showing brutally clipped shadows (but you work in the Develop Module right?!). The same problem occurred also in OSX 10.8 but it was related only to LUT profiles, creating a Matrix based profile problems were solved. Now the issue occurs with both Matrix and LUT profiles, v2 and v4. There's no apparent way to make Lr working right. Under Windows no problems at all: Bridge, Photoshop, ACR, Lr (Library Module and Develop Module) show the same correct NOT cli

PSDs exported from photos created by Photo > Photo Merge don't have a completely correct compatibility layer, causing InDesign to think that such a PSD is missing a compatibility layer. A user reports that having many such PSDs in an InDesign document causes it to slow down quite a bit, presumably because it is using a slower, more general code path to interpret the layers of the PSD.The cause of the problem is that, when exporting a PSD, LR fails to include a Version Info resource block (id 1057) with the "hasRealMergedData" flag. Normally, this doesn't confuse applications, since most exported PSDs have just the compatibility layer, and applications ignore the "hasRealMergedData" flag. But in the case of photos created by Photo Merge, the PSDs have two layers, the compatibility layer and a second layer containing the transparent pixels (compatibility layers can't store transparent pixels).  Because there is no "hasRealMergedData" flag, InDesign must assume there isn

Hi,the lens Sigma 10-20 mm F3,5 EX DC HSM for Pentax is not identified by LR. The LensID="8 11".But there is a lens correction profile for this lens. I assume LR should know the lens? In the EXIF section it only says "unknown lens". Is there a way to make LR identify this lens? I know the way to make Lightroom choose the right Correction each time but I am looking for a possibility LR writes the lens information in the exif (e.g. for filtering).If I take a look in the source code of the file there is an entry "xmp:Label="Sigma 10-20 mm F3,5 EX DC HSM"Why is LR not able to display this information?Thanks in advance. LR Version is 6.6.1btw. Apple Fotos is able to identify the lens correctly 🙂

I have been unsuccessful at merging Leica M Monochrom Typ 246 raw images. Leica M Typ 240 color images - no problem at all. I have started a chat discussion with Adobe, and the local Leica store actually duplicated the problem on their computer. I am using Lr 2015.6 Windows 10.  I have tried 2, 3 and 4 images and always get the same message: "Unknown errors occurred"  Merge using Photoshop CC does work with the Monochrom images

Hello, I’m having some trouble with Photoshop CC, specifically with the Camera Raw Filter. I have created multiple ACR presets that I use to apply various photo effects to my images. When I created these presets and saved them, I specifically didn't check any of the settings relating to the Transform, Lens Profile Corrections, Chromatic Aberration, Lens Vignetting and the Camera Calibration panels. I did this because I don’t want those settings to change when I apply one of my presets. The settings in those sections are generally related to the workings of my equipment and I don’t want to have to redo those settings if I decide to apply an effect to my image. This method generally works with one significant exception. Even though I have specifically left Lens Corrections out of my saved settings (by not checking that box when saving the preset), some settings in the Lens Correction panel (specifically the Defringe Purple Hue and Green Hue sliders) always get reset to the default values

Just installed the new Lightroom CC 2015.6 / 6.6 update and i have a really strange issue. All my files are in DNG format. Everything works fine except the files from my Fuji X-E2. Lightroom and Photoshop can't read these anymore! The files get's a black exclamation mark next to them. See the screenshot. All files from the other Fuji X-series cameras works just fine. It's only X-E2 files that doesn't. The files work just fine with any other software and i tried them on a different computer which has the previous version of lightroom CC and there they work just fine!Is there a way to make a roll-back to previous version?

Update to latest LR: Now, moving sliders causes image colors to dim and brighten in a psychedelic way!. Not good. Makes you think video card is going.