Bug Reports

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.

I'm using Lightroom CC, Sony A7r camera, generating Sony Raw files (AWR) and my problem happens with all of my Sony lenses (all of them have lens Profile Corrections, but I have it turned off on import). I bring the images into Lightroom without lens correction. When I send my bracketed exposures into Merge To HDR with auto align and auto tone turned off, Lightroom automatically applies the lens correction profile. This is not a problem for most of my lenses as I want them corrected EXCEPT for my Sony 16 mm fisheye converter. I don't want lightroom to correct the fisheye distortion. I talked with someone using Nikon RAW files and Lightroom does not correct their fisheye distortion (don't know about other lenes). How can I prevent Lightroom from applying profile correction to my images upon sending them to Merge to HDR? Thanks

I applied the Recover Edges plug-in to some of my Canon 5D MkIII files because Lightroom CC 2015 honored the in-camera crop I set (and did not turn off!). This worked fine to give me back the rest of the sensor info. I reset the files in the Develop module. However, when I try to merge these "full" DNG files to HDR, I get the message "unknown errors" and the merge fails. Could either the plug-in or Merge to HDR be updated to recognize the full sensor files created with the Recover Edges plug-in? HDR merge worked fine on the original "cropped" files. Thanks.

https://forums.adobe.com/thread/2150220It seems that the WB calibration is messed-up for the 1DX Mark II manufacturer color simulation profiles.Forexample, a WB value of 5100 +17 becomes 4300 -13 when using any of the manufacturer color simulation profiles instead of Adobe Standard.This should be a quick and easy fix by your software engineers I guess? Thanks in advance!

God, trying to find an answer without waisting hours going through these options. HDR 32bit conversion not working after the latest upgrade. I use 32 bit a lot and after running through in the normal way when i go to convert to 16bit instead of it going back to camera raw for adjustments i get a "program error message" and nothing more happens, it stays as 32 bit. Any ideas anyone???

Hi, I'm Bruno from Brazil... I use Photoshop CC for MAC. I did the last actualization two days ago... And now I can't open any file in JPEG format. It show this window when I try to open : "Could not complete your request because the file was not found." Can you help me, please?? ! ! ! Thanks for your att.

I noticed some unpleasent artifacs on hard edges in many of my raws captured with Sony. They seem to appear as soon as the clarity value is raised. Here is an example: And enlarged: When leaving the clarity at 0 there are no artifacts visible: The raws were captured with a Sony A7II camera (uncompressed). I do not know if these artifacts only occur with Sony raws or also with raws of other manufacturers. Note: I already posted about this issue here https://forums.adobe.com/thread/20652...

Massive issue after updating to Lightroom 6.3. The “Default Develop Settings” isn’t working, the settings are reset every time you start Lightroom. I’ve got hundreds of default settings for different ISOs saved for a number of cameras, all don’t work. The folder with the Default Develop Settings still contains all my defaults: C:\Users\\AppData\Roaming\Adobe\CameraRaw\Defaults. But they don't load anymore with Lightroom 6.3, so when I hit "reset" on a photo it resets the photo to lightroom default values instead of what I set in the "default develop settings". When I try to set a new “Develop Setting”, let’s say, default develop setting for clarity on ISO100 photos is +10, it works for the duration of my lightroom session, BUT as soon as I close lightroom and restart it, the default develop setting doesn’t work, i.e. when I click "reset" on a photo, it resets the clarity back to 0 which is the lightroom default and not +10 which is my default for the ISO100 photo (this is of course a s

Magenta color in recovery light for 70d http://forums.adobe.com/thread/145922...

Photoshop CC 2014.2.1/Camera Raw/Win 7 SP1 64bit ACR Window is full screen mode - Select adjustment brush, reset all values to default, use adjustment brush - A modal error dialog is displayed BEHIND the ACR window. Even when acknowledged (get to it with windows means since ACR does not allow any control) it immediately comes back and PS application has to be stoppped with task manager. The behavior with ACR window not in full screen mode seems normal and after the error dialog is acked the ACR window allows to make changes.

output format will be jpg. If source file is jpg it works. This happens only(!!!) if "don't enlarge" is checked!

This appears to be a bug in ACR7.2 and Lightroom 4.2RC: When importing RAW shots made with a Sony RX100, in the RAW+JPEG mode, when the JPEG part was set to less than 20Mpixel, Lightroom 4.2RC will misidentify the files as being cropped and will show a crop box centered on the image, even though both the raw and the JPEG did use the full size image. This happens regardless of the used aspect ration, i.e. the crop is not because of the use of a non-native aspect ratio. Other reports of the same issue: http://forums.adobe.com/message/47039... http://forums.adobe.com/thread/1067177 http://forums.adobe.com/message/46788...

Long filenames are truncated to approximately 63 bytes in ACR 8.3/8.4's Save Image... panel. The name truncation happens to the file saved on disk and is visible in the Example Filename area. It doesn't matter what file format is selected. This didn't happen in older versions of ACR, according to the user initially reporting the issue. Examples of truncation are: HIETALAHTI, TENAVAMUSKARI_VAASAN SUOMALAISEN SEURAKUNNAN PÄIVÄKERHO_cpy004_5000_02.cr2 Saving as JPG becomes: HIETALAHTI, TENAVAMUSKARI_VAASAN SUOMALAISEN SEURAKUNNAN P.jpg which is 62 characters but the next character might need a double-byte to represent the vowel points so that would be too long at 64 bytes. And if things are "cleaned up" regarding the comma and Ä then: HIETALAHTI_TENAVAMUSKARI_VAASAN_SUOMALAISEN_SEURAKUNNAN_PAIVAKERHO_cpy004_5000_02.cr2 becomes: HIETALAHTI_TENAVAMUSKARI_VAASAN_SUOMALAISEN_SEURAKUNNAN_PAI.jpg which is 63 characters. Here is a screenshot showing the truncation of the cleaned-up name: The pa

En la sección de Pincel de Ajuste, el comentario que aparece informando de la tecla de acceso rápido sobre la función mostrar mascara, hace referencia a la tecla V y esta tecla esta asignada a la función Mostrar Alfileres, creo que debe cambiarse el comentario, indicando la tecla Y en vez de la V. Saludos.

Lightroom 4.4 bug with new X-Trans handling algorithms. It looks like the blue channel is clipping in some instances, severely distorting handling of highlights. Here's an example: http://forums.dpreview.com/forums/pos... RAW (RAF) file available here: http://dl.dropbox.com/u/37346336/1275... On page five of the thread someone more or less figured out what the issue is (related to camera calibration defaults): http://forums.dpreview.com/forums/thr...