Bug Reports

HiWhen I'm in full screen mode in Camera Raw filter in Photoshop CC when first click almost entire window is going to blank (see attached screenshot), and it gets back to normal when I press K for Adjustment BrushI had the same issue with my old Mac Pro and earlier Photoshop (OS X 10.7), but now I'm running on iMac 27, AMD Radeon HD 6970M 1024 MB, 24 GB RAM.. OS X 10.11.3It happens almost all the time 😕😕Any ideas?Andy

The LR 7.10 and ACR 10.1 Effects panel Post Crop Vignetting Highlights Slider has no effect on the image. It appears to be disabled in the latest update version. I tried resetting LR Preferences file and the issue remains. It has been reported here:https://forums.adobe.com/message/10057058#10057058

For the most part ACR automatically identifies and applies lens profiles for my Hasselblad lenses. However the XCD 45P photos get a warning that says "unable to locate a matching lens profile." The XCD 45P is a newer lens but when I do it manually I can indeed see the matching lens profile and apply it manually. But something is preventing ACR from seeing and applying the profile auotmatically.

I've labeled this as a *problem* because I think I've found a bug (and I can consistently recreate this) in the new photoshop raw. That said, the bug also stems from a very small feature change, that actually has a huge negative impact on my workflow (and possibly others). The feature change: In a recent update to Photoshop Raw, if you're using your keyboard to tab through the editable fields in any of the edit functionalities, it no-longer automatically ads a Zero if you leave one blank. I'll elaborate. If I'm on the main editing field, and I tab down a few times to exposure, and type a "1", it bumps the exposure by a value of one. If I decide I don't like this I used to simply delete the one, and keep tabbing, and it would replace the empty space with a Zero. NOW: when I tab away, I get an error message saying "a value of X..... is required" basically, to remove an edit I've made via the keyboard, I need to both delete the one and add the zero. This may seem

This what i get when merging 3 vertical images in Lightroom  shot with D850 and a Schneider TS 28mm lens. It  used to work fine, but now no longer. It works fine in Photoshop. My other 2 Nikon TS lens 24mm and 19mm work fine on both platforms. Am baffled. Help please.

My PC Windows has 10 updated. I use CS6, Bridge 5.0.0 and ACR 9.1.1 I use DNG converter 10.1 which works fine. The problem is that when I install DNG 10.2 the programme does not open up. The little blue circle rotates for a few seconds but then disappears. Your help greatly appreciated.

The Canon EOS Rebel T7, 1500D, 2000D (same exact model with different country names) camera profiles render properly using the camera's 'As Shot' white balance settings, but display a very high and incorrect Tint value in the LR 8.2.1 Basic panel. In addition when using any of the Basic panel WB presets (Auto, Daylight, Cloudy, Shade, Tungsten, etc.) set for the actual shooting lighting condition the image takes on a strong yellow-green tint shift. More details at the below Lightroom forum post:https://forums.adobe.com/message/11016301#11016301

After the most current update, such presets stopped working in the following applications: Lightroom CC for iPad Lightroom CC (Smartphone) Camera RAW They still work in Classic and in LR CC desktop. We urgently need this to be fixed.

Since upgrading to OS 10.14.6, Lightroom Classic (8.3.1) cannot merge (21 frame) panoramic images. Just sits there forever and does nothing.

I posted this on the adobe.com forums, but it may get more traction here.... Since updating to LR 7.3, all my presets were imported and can be used. But none of them allow the Constrain Crop option under Transform to be set by default. Even if I apply my preset, click Constrain Crop and "Update with current settings" on the preset, it still doesn't re-apply.Running Windows 10 64bit.

When saving a HSL/B+W-Mix adjustments to a preset, the values for magenta and purple then aren't saved to the xmp-file when exporting the preset (these values are always reseted to "0"). So when importing back a previously saved preset into lightroom, the preset doesn't represent the originally created preset anymore. Also I think this leads to not correctly syncing these presets between devices... would appreciate a fix for this behaviour..

NIKON D850 in MOVIE mode, The .nefs taken in Movie Mode 1920x1080p 30 x4 cannot be read by LR or ACR. However, the .nefs taken with the D850 in 1920x1080p 30 (not slo mo) open just fine.

I was super excited about the new Enhance Details feature rolling out today.  However, something about it refuses to work for me.  When I select the feature on an image, the preview pane only shows a completely black pane on the "Enhanced" version.  Furthermore, when I click the "Enhance" button, processor and GPU rev up and the progress bar moves, but ultimately it only renders a completely black DNG.  This seems to happen on any photo in my collection.  I have verified that I am updated to the correct version of windows, and that I am working on a CR2 RAW file.  Screenshots:  Image is not available   Image is not available

Lightroom 8.2 Supported camera Fuji X-T3 has some images come up with exclamation points saying:"Lightroom has encountered problems reading this photo. You will not be able to make adjustments to the photo."It's odd, from one image to the same in the same shoot it fluctuates between what is readable, and what isn't. I'd say file corruption, but they open fine in Adobe Camera Raw 11.2I've checked file permissions, tried on multiple Mac/PC machines. Everything seems normal. Attached screenshot is just example of how some images read/write fine and others have that black bullet with an exclamation point in it.

I was trying out the new Enhance Details function on Lightroom 8.2, and it is working well on some images, but on other images, it creates the new file, but totally messes it up by cutting out a square in one part of the image, and then other green, blue and magenta squares of the same size are placed randomly in other parts of the image. This doesn't happen on all files (and it isn't consistent as to which files...two shots taken minutes apart with the same camera and lens, and one it won't process correctly, but the other it will.  If it messes up on a file, it always messes up in the same way if you try again. It doesn't matter whether GPU processing is enabled or not. Example showing the effect: http://www.jordansteele.com/2019/enhanced.jpgSystem Info: Lightroom Classic version: 8.2 [ 1204643 ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Business EditionVersion: 10.0.17763Application architecture: x64System architecture: x64Logical processor count:

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.