Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
jeffreyh96105683
Explorer
jeffreyh96105683
Explorer
Activity
‎Jan 09, 2025
09:50 PM
Picked up some of the reflections but not all. Would help to have a brush to "coach" it as to where the reflections are. Admittedly picture was taken from a bus window, so the reflections are quite complex.
... View more
‎Sep 18, 2024
05:15 PM
4 Upvotes
‎Sep 18, 2024
05:15 PM
4 Upvotes
Moderators, please consider changing this to a bug.
... View more
‎Sep 18, 2024
05:04 PM
3 Upvotes
‎Sep 18, 2024
05:04 PM
3 Upvotes
I'm attempting to see if I can preview and pre-edit my files in Lr on my local disk and then do further edits in LrC. Same problem as outlined above - "File is not editable". Of course it isn't - Lr is supposed to produce a sidecar file with the edits! It seems to produce the .xmp, but every time I edit the photo I get the same error message. Lr is unusable for my use case - returning to using FastRawViewer for preedit and then import to LrC. Per other posts in this thread, Adobe induced this error in an update.
... View more
‎Jun 03, 2024
09:55 PM
3 Upvotes
I am experiencing the same performance degradation on 13.3. I didn't see those on 13.2. As described by other users above, even switching between photos can take 4-5 seconds or even longer. But sometimes it happens quickly. I have shut down syncing to the cloud and also shut down writing of metadata to .xmp and jpg, etc. Please issue a fix to this as soon as possible. Thanks
... View more
‎Jun 25, 2019
09:06 AM
Please let me know if this thread is still being monitored, or if I should start a new thread on this issue. Also please let me know if you can duplicate, or if you want me to supply the pictures affected by this issue. Thanks!
... View more
‎Jun 22, 2019
05:58 PM
I just (6/22/19) noticed this same behavior (painfully slow response from sliders after adding positive dehaze) on two monochrome images in Lr Classic release 8.3.1 (LATEST VER). Unsure if it went away in the earlier release and then came back, or if it has been there all along. Please revisit and if you can duplicate, please repair in future release. Thanks. I will supply affected pictures if you need them - please ask on this forum.
... View more
‎Dec 11, 2018
08:59 PM
I just checked some of the pictures on which I had seen the artifact on the following products: Lr mobile, Lr, Lr Classic and Ps. Like the others who posted I've seen no more artifacts, so Adobe's fix appears successful! Thank you! One note: When I first looked at some of the previously-affected images in Lr Classic Library, I did still see the artifact. However, when I switched to Develop, the artifact was not there. Switching back to Library, it was there. To get rid of it was simple: switch to Develop, then either do a Reset (if you don't care about previous adjustments) or do a small change (increase a slider by +1, for instance). After that, switching back to Library, the artifact is then gone. Perhaps the images that do this were changed in develop while the artifact was present, and the artifact carried into the catalog or the .xmp. At any rate, it is easy to eliminate in the new version. Along these lines one thing I'd really like to be able to do is to wipe Adobe's .xmp data from any file type that accommodates embedded .xmp data, for example, .dng, .tif . There are times when I might want to "reset the file to zero". If anyone from Adobe can explain if this is possible and how to do it, I'd appreciate it. Thanks Adobe - looks as if the current artifact problem is fixed now.
... View more
‎Nov 27, 2018
12:49 PM
At least temporarily I'm editing these files in other photo editors that do render them correctly. I can then export the result in .tif to Lr if necessary.
... View more
‎Nov 27, 2018
08:20 AM
Wanted to follow up with the Adobe employees following this issue - has there been any status update as to timing for a fix? Based on investigation of the problem, in the meantime, is there any workaround available to allow Samsung s7/8/9 DNG files to be correctly edited in Lr?
... View more
‎Oct 27, 2018
02:25 PM
Something to be aware of is that HKEY_CURRENT_USER applies to the current user only. So if you have multiple users on your machine, you may have to apply any HKEY_CURRENT_USER fixes with each user logged on. In my case, I have three accounts on the computer. One account had no problem at all, even with no registry changes. The other two did have the problem. What is needed is for Adobe to provide a more global fix, that would apply to all accounts on a machine and allow all accounts to choose Adobe Photoshop 2019 as the default for .psd files, without need to modify the registry. What I would guess is that there are different levels of items in the registry to handle file extensions, maybe to allow system admins to allow one user the ability to associate a given file extension with a given app, but deny another user the ability to do this. Perhaps the one we've been changing (the user-specific one) overrides the global registry entries - maybe it got set somehow in the past and is not being handled correctly now. This is just conjecture, but points out that Adobe probably needs to clean up registry entries related to .psd, or provide clear instructions to the user how to do this. D Fosse, can you work with your contact at Adobe, shall I write this up as a bug? The one problem I see with writing a bug report is that there seems to be no way to reproduce this with any repeatability. Without a way to do so, the software engineer has to now conjecture with all the evidence presented in this forum and elsewhere, what might be causing the problem. Coupled with the fact that apparently multiple Adobe CC program can claim the .psd extension and perhaps that many registry entries (per machine and per user) can affect file extensions, it is no wonder that this problem has been going on so long.
... View more
‎Oct 26, 2018
11:25 AM
I agree with John. Please go over to the bug report I filed and "me too" it. You may also want to add the image with the purple haze over there. I noticed that the image with purple haze also has the edge artifact under the purple haze. The photo with the clouds looks like a classic case of the problem I filed. I personally did not see the purple haze in my s7 raw photos. At this point though none of us have any idea of what is going on with the rendering for s7 DNG's in Lr, so we cannot rule out the purple haze as being just another symptom of the same problem - that's why I consider it important to add this image to the problem report as a possible additional symptom. See John's post for the link to the problem report.
... View more
‎Oct 25, 2018
11:25 PM
4 Upvotes
Unfortunately the solution given by the adobe document shown in the D Fosse post above didn't work. That registry key may have existed at that time, but it does not exist at this time (10/26/18). However, the solution from chunkysteveo above did work. The entry was "Photoshop.Image.19". I simply changed it to "Photoshop.Image.20", then went back to settings | Apps |Default apps|Choose Default Apps By File Type . I then scrolled down to .psd, and it then allowed me to select Adobe Photoshop 2019. The user should not have to resort to registry editing at all in order to have the psd extension just work - in fact, for someone not familiar with the registry, there is a chance for a misstep. D Fosse said that this is being investigated by Adobe engineers now. Do we have to file a bug report in the feedback/family forum? From forum postings it seems that this problem has been going on for some time. In fact, I've used Win 10 for several years now - this is the first time I've had to resort to this to get a default file extension for a program to work.
... View more
‎Oct 24, 2018
10:06 PM
Adobe has logged this as a bug.
... View more
‎Oct 24, 2018
05:49 PM
Assuming this is a bug, can someone (perhaps a champion or Adobe) please let us know how quickly we might expect a patch or other solution for this issue? If it is going to be awhile, I'll be pursuing a workaround.
... View more
‎Oct 23, 2018
10:05 PM
I'm in process of looking for a solution to doing dng->tif en-masse to work around this situation, since I've got several hundred. I thought of irfanview, but as far as I can tell, it won't do dng. Luckily I've shot RAW+jpeg, so can fall back on jpeg's if absolutely necessary. If I'm able to find a tif solution I'll report back. One possibility is Luminar's upcoming equivalent of the Lr Library, scheduled in Dec. If a number of photos can be selected and exported, that might work.
... View more
‎Oct 22, 2018
09:53 PM
Thanks, Anton. This further confirms the issue and that it seems to have started in the recent upgrade. We'll know more when the champions and possibly Adobe weigh in. As to a workaround, the only one I can think of is to convert the .dng's to .tif. So far I've seen no problem with .tif in Lr.
... View more
‎Oct 21, 2018
08:20 PM
Thanks Steve and Bruce. The results so far are exactly what I would have expected, particularly the previous Lr version showing no artifacts. I posted four new images in the same dropbox area. Each image has a version that is direct from the smartphone and not touched by an Adobe product. The other version was imported into Lightroom. Each version is labelled as to its status. I brought the "Imported into Lightroom 2019" versions into Loupe view in 2019 Classic Library to see the artifact was there. I then entered Develop, made no adjustments, and went back to Library. These photos should have enough details on all sides to make a good analysis, but if not, let me know, and I'll shoot some more during the day. Please let me know what you find and if it looks like a bug, where we go from here. Thanks, Jeff
... View more
‎Oct 21, 2018
02:35 PM
One thing that I forgot to mention is that I did try shutting down use of the graphics card. This had no effect.
... View more
‎Oct 21, 2018
02:18 PM
16 Upvotes
Artifacts at Edges of Galaxy S7 RAW DNG Files in Ps, Lr Classic 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=0 Reproduction: 1. Take a photo in RAW with the Samsung Galaxy S7. 2. Copy the photo to a computer via USB. 3. Import to or open the photo in one of the affectedproducts. Observe that the artifact strip appears at one edge of the photo. Alternately 1. Take a photo in RAW on Galaxy S7, 2. Import the RAW photo into Lightroom CC Mobile 3. Observe the artifact at one edge of the image. Note: theartifact is thin, so it may be hard to see. The artifact isn’t always seen onmobile. If it doesn’t appear, try going back to the library view and openingthe photo once again. Workaround within the Products: None. The only recourse isto either crop out the artifact strip or to convert the DNG to TIFF andreimport the TIFF to the Adobe product. Cropping out the artifact strip is nota trusted workaround, because the artifact strip might reappear in the future,despite the crop. What Has Been Tried/Previous History: 1. DNG photos from two different Samsung Galaxy s7smartphones have been imported or opened, with the same result. 2. About 15 photos have been opened. All exhibit the same result. 3. The DNG photos open normally within Skylum Luminar,Powerlink Media Player for Dell, Android Gallery on Samsung S7 and GooglePhotos without exhibiting these artifacts or any other artifacts. 4. The artifacts appear in Lightroom CC Classis 2019 on bothone desktop and one laptop computer. 5. I cannot say for sure, but I do not believe this problemoccurred prior to Lightroom CC Classic 2019, because I would have seen theartifacts while editing these images in Develop. I don’t remember seeing themon the prior version.
... View more
‎Oct 21, 2018
01:08 PM
Thanks, John. Yes, I'll do that and thanks for the tips on posting there. Unfortunately I didn't have a good, complete handle of what was going on when I started this thread, since the problem causes bound-able but somewhat random behavior. Now I do know how to reproduce step-by-step. The problem is, the only workaround I see is to use another tool to convert several hundred of these pictures into tif and reimport the tif into Lr. I'll lose the adjustments I made to some of them. A friend of mine warned me just yesterday at our digital editing meetup, "don't trust any Adobe format; always convert to tif".
... View more
‎Oct 21, 2018
09:44 AM
I've done some more tests on various images and found: This issue happens with raw .dng images from the rear camera of two different Samsung Galaxy s7 smartphones. Sometimes the photo displays fine in Library. Then I go to Develop and it has the issue. Then I go back to Library and the artifacts appear. I copied a test raw file directly from the smartphone to computer and imported directly into Lightroom. This was to make sure that some intermediate step was not causing some kind of corruption. The image displayed the artifacts. Can't say for sure, but I've edited enough of these images with the previous Lr version that I would have seen it if the issue had been on the previous version. There are a large number of images that I've seen that now exhibit this problem. I don't consider it impossible, but I'm having a problem with the file corruption theory. I'm unsure what an ACP is, but if not an Adobe employee, I'd really appreciate having someone on staff there weigh in. And if there's anyone else that experiences artifacts with .dng's from Galaxy S7's in Lightroom, please also reply.
... View more
‎Oct 19, 2018
06:35 AM
Thanks for the idea. Tried unchecking "use graphics processor" - same result in this case. I'll try some other things as I get the chance in an attempt to narrow this down. If I find anything I'll report back.
... View more
‎Oct 18, 2018
05:03 PM
I thought the same thing - there are two similar pictures, both of which produce the artifact. Before posting I also tried opening this picture in Luminar 2018 - it opens there with no artifact. Same with the Power Media player that is pre-installed on the desktop. In both cases I zoomed in to make sure there was no artifact on the left hand side. Since its is literally no cost, I'll try uninstalling ACR and reinstalling. Sometimes an upgrade has issues. Otherwise let's see if anyone else sees this. And true, it can be cropped out easily. Thanks for the reply!
... View more
‎Oct 18, 2018
01:32 PM
1 Upvote
After the Oct. Lightroom Update I noticed that one of my pictures (a .dng) has a series of artifacts at the left-hand edge in the library module (see arrow on picture). Noticed that this occurs also when opening this same picture directly in ACR in Photoshop, only the artifact colors displayed are different. When switching to the develop module, the artifacts disappear. These artifacts also do not appear in Microsoft Photo or Luminar. Unfortunately I imported this photo only after the Oct. update, so I have no way of knowing if it would have occurred on the Lr version prior to update. Can someone shed some light on what causes this? It appears to be related to ACR, since Photoshop ACR is also affected. More info: It now appears that the artifacts do appear in the Develop module as well. They seem to change - before they appeared as a solid black strip, but now I'm seeing some colored lines as well. I have made sure that the clipping indicator is off. One other piece of information: When I turn clipping on, the blue clipping indicators appear in the areas where the artifact colors do not appear.
... View more
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more
Copyright © 2025 Adobe. All rights reserved.
AdChoices