>My LrC also says the lens correction is applied but it really hasn't. So - are you sure the lens correction is applied correctly?   Turns out you are right. It is applying the lens correction incorrectly. I could only really see that by comparing the merge from the full res images to the merge from the reduced res images as you can see below (HDR gets blown out in screenshots. The window actually has all the detail when viewed on my display) It is correcting but only partially which you can see by toggling the correction on and off. Sorry for missing this initially. This is clearly a bug indeed. Just directly merging to HDR is much faster for me but that might depend a lot on your hardware and might not be a solution for you. ... View more

P.S. I timed what it takes to export, reimport and convert to HDR vs just creating HDR directly and it is faster to just create the HDR from the original files:   Reduce size by export to dng using a export preset-> automatic reimport -> merge to HDR: 35 seconds Direct merge to HDR: 13 seconds   The actual process is faster for the direct merge but I counted the right click to get to the HDR dialog.   Now I tested this I can see that you are right that even though the interface says it is correcting for the lens distortion and vignette, it isn't actually doing that for the reduced size export image. It seems to only correct about 50% of the distortion! So there might be a bug here indeed. That said, just doing it from the orginal raf files is a lot faster anyway so that is what you should do. Interestingly if you merge to HDR using the raf files and then export to reduced size dng from there, the lens correction is correctly applied to the final file, so this is indeed some kind of effect from the merging to HDR using reduced-size dng files.   It will be even faster if you have a folder full of brackets and just select all -> enhance-> merge to HDR and it will automatically merge all HDR brackets. ... View more

Thanks, I tried to reproduce. I imported these three raf files. Exported them to lossy dng v16 with long side at 3000 pixels to same folder with automatic reimporting them to the catalog. Hit create HDR on the new files and the result came in fully corrected with the lens correction set correctly as you can see in screenshot below LR Classic 14.3.1 on MacBookPro M1 Max.  This seems to work correctly on my machine at least with the release version of Classic. Also tried this in Cloudy and it comes in fully corrected with the right profile: No clue why this wouldn't work correctly on your computer. Perhaps a hardware dependent bug. ... View more

Can you share a few raw files that this happens to? People here (and perhaps some Adobe folks) can try and follow along and see what the issue is. Upload to a cloud service such as Dropbox and share the link. ... View more

(note I am assuming you do not have the HDR option enabled in Develop) Any edited image in Lightroom is already tone mapped. The tools you use to do highlights, shadows, masks, etc are effectively ways to lower the dynamic range of an image into something that can be represented in a 8-bit image. So the equivalent of the HDR toning dialog box is simply the develop settings. If you can see the image on your typical display and it looks good, it is already ready to be exported to an 8-bit jpeg. ... View more

I have a similar M1 Max machine, same version of Classic but I run Mac OS 15.4.1 . This file denoises just fine on my machine both in Classic and in Lightroom Cloudy. Perhaps you need to update your mac os version. There were several GPU related fixes in the recent updates.  P.S. for screenshots one trick is to just type screenshot in the upper right hand corner looking glass icon. It will give you a built in screenshot utility that saves screenshots to your desktop. Very handy. ... View more

Ah. Yeah forget about anything you do in finder or what it shows on the icon, that has nothing to do with your issue. As Jim says, that is just the file type association in finder. It is annoying but Lightroom (classic clearly) does not care about any of that. What is going on here likely has more to do with your hardware and software. What version of Lightroom are you running? What computer hardware and what operating system version? Easiest is to post a result of "system info" from the help menu. ... View more

Topaz can save its output as a dng. This is the default behavior if you open through the menu item. Is the d you are talking about actually in the filename or us it in the icon in finder? ... View more

That d at the start of the file name likely means they were indeed run through topaz. Share a link to an affected dng in this thread for us to check. You do this by uploading the image to iCloud Drive, Dropbox, creative cloud drive, or similar file sharing service and sharing the public link here. The forum does not allow posting of dng/raw files (they are too big typically). by the way, since you are talking about file names and opening in preview, it sounds like you are using Lightroom classic, not the cloud based Lightroom that this forum is about.  ... View more

If the image at any time was run through topaz Denoise, you won't be able to use the built in denoise on it anymore. It sounds like the dng files you are working with might have been run through topaz at some point in time. Make sure you are working with an original raw not one that was run through denoise already.  ... View more

Make sure you follow the trouble shooting steps above as this is undoubtedly a bad monitor profile or a gpu driver issue but wanted to comment on this: >I've researched the problem and it seems that the Develop module and the Library module use different color profiles?  - Unless I'm missing something, how is that a good idea?  Why would your own platform use two different color settings between tabs?    there is a very simple reason for this difference. The non-develop modules all render from jpeg previews. The develop module renders directly from raw in the widest color space available. It uses a color space that has prophotoRGB primaries but linear gamma (since raw is a linear capture). When converting to a jpeg preview, you cannot use that colorspace as you always need to employ a gamma curve in jpeg. Also jpegs in prophotoRGB space tend to show banding, so Lightroom uses a smaller color space to avoid this banding. It is likely that the red color you dialed in is way outside of standard color spaces such as sRGB, AdobeRGB or displayP3 and that causes the color shift you observe. This color shift will also occur therefore if you export your images for sharing. Instagram for example is sRGB only and there is no way it can display this red. In the develop module you can soft proof your images for these standard color spaces. Try turning it on and use sRGB for the proofing space. You will see the same shift. This is simply a limitation of the color spaces that you might be exporting in. lastly if you are editing in HDR, which allows far brighter saturated colors, be aware that you need to enable hdr previews in library. Also, be aware that it is not super likely anybody you share the images with will see the hdr. This only works right if you know what you are doing and if you control the image chsin completely from you to viewer. So for most people it is still best to avoid hdr if you're looking for consistency. ... View more

One important setting to change is in Lightroom classic's preferences to change raw defaults (in the presets tab) to 'camera settings'. This will make the default rendering after import similar to the camera generated jpeg by automatically choosing the corresponding profile and by doing a few settings that mimic the jpeg engine in the camera. This will only affect newly imported images. For already imported images, hit reset and it will do the same thing. You can also apply the 'camera settings' preset.  note that the point of shooting raw is that you have complete editing latitude. With just a few edits, you can make your raws look far better than the in-camera jpeg. Just try the auto button, or use an adaptive profile to get some automatic edits that will immediately make your image look better. ... View more

Sharpening in the develop sliders, whether in masks or global is all done before any resampling on export. It is one of the very earliest things in the develop chain. This is why there is an output sharpening control that is meant to compensate for any softening due to the scaling. ... View more

Correct. You need to use a separate backup method for your images. The catalog backups only include the edit instructions and metadata since that is the only thing stored in the catalog. ... View more

You did it the correct way and your images are likely still there. Just check the drive in explorer. Using this method (which is method one in the link) you WILL retain all edits as those are stored inside the catalog. What likely has happened is that moving the drive back and forth between computers has changed the drive letter and now Lightroom doesn't know where to look for them. You want to probably give it a fixed drive letter at some point which I think (I am not a windows user) is possible. For now just right click the top folder in the left bar in Lightroom Classic and update the folder location to point to the correct location with the correct drive letter. It should rediscover the images and not show the question marks anymore. This changing drive letter thing is a common problem for windows Lightroom Classic users. ... View more

This problem cannot be fixed currently unfortunately. Perhaps with some future AI photo editing tool but this is much more difficult to correct after the fact than almost any other kind of edit. Check the video above for avoiding it next time you shoot something with similar LED light sources. This really can only be fixed when you are shooting. ... View more

Not sure I understand what you did exactly. It sounds like you reimported already existing images into Classic and pointed the import to the folder on your internal drive where those images were? If so that would indeed not lead to anything imported as those images are already in the catalog and the default action is to not import already existing images. You can circumvent that by unchecking the "do not import suspected duplicates" option but this really is NOT the way to move images. It inevitably leads to loss of edits.   The best way to move images to another drive is to move them in Explorer/Finder by copying them to the other drive. Then inside Lightroom CLassic, you right-click on the top-most folder in the hierarchy you moved and select "Update folder location" and now point at the corresponding folder on the external. Check that the folder now shows up listed on the other drive in the left bar in Classic and that all images are there and now you can delete the folder on your internal drive. Here is a visual guide: https://www.lightroomqueen.com/move-photos-another-hard-drive-leaving-catalog/ - use option 2.   You can also do the move inside Lightroom but many consider this less safe than using the operating system's native file browser.   If all your images are really gone now from both locations, you should restore from your backup that you hopefully have. ... View more

What are you using to view the file? If the viewer is correctly color managed, you should not see any difference between Lightroom and the export especially if you are using P3 color space. Also, make sure you don't have HDR enabled in the Lightroom app when you are editing and not when you export. Not every (i.e. basically none) app understands HDR exports. ... View more

Hi Vijay, the problem is the color space you export to is fairly narrow and cannot represent the most saturated colors  especially reds. Most displays nowadays are able to display colors more akin to displayP3 color spaces, so if you export to sRGB, you cut off a chunk of colors that you might have had in your original. To retain this, use wider color spaces such as P3 or adobeRGB for your export, but be aware that not every program color manages correctly especially on windows where lots of software is not color managed. Luckily almost all web browsers nowadays are and on Macs basically everything is color managed.     ... View more

AFP was deprecated by Apple quite a few years ago and is no longer being developed nor supported by them even though it still works. The official line by Apple is that you should use SMB for filesharing. That is still somewhat buggy but there are a few settings you can do to optimize smb on the synology and on your Macs to make it faster and more reliable but usually it is fine out of the box. I also highly recommend the automounter utility (it's on the App Store but website here: https://pixeleyes.co.nz/automounter/ ) as Mac OS tends to constantly unmount any mounted shares if your mac goes to sleep. Incredibly annoying but this utility fixes it.  ... View more

In mobile, use the import button and import from wherever you have the file. It can import from an attached card reader or camera or from files in your photostream or in a files app.  On the Macbook pro, hit the plus (add photos) sign in the Lightroom screen in the left bar and select where to import from. You can import from your hard disk or from a connected card reader or camera. ... View more

You know now how to wipe what's in the cloud now. You should not use the standard migration tool if you only want a subsection of your images from Classic to end up in cloud-based Lightroom. The migration tool will upload the entire classic catalog. There are many ways to accomplish that however. One way is to export a new catalog from your old catalog with just those images and collections you want in the cloud and to migrate that catalog. Another way is to export those images as originals from Classic and just drag those into cloud-based Lightroom. Yet another is to use classic to make your cloud selection (which gives you just smart previews in the cloud) and then drag the raws for those images into cloud-based Lightroom which will associate the raws with the already existing smart previews.  There are a number of other methods but these are the most workable. ... View more

What is street TV? Googling that gives 1000's of different results that don't seem to be related to your question. It sounds like it is a specific device? ... View more

Are you in a folder that is offline? I can only think of the possibility that the folder your image is in is on a disk that is not currently mounted. Otherwise it should work anywhere.  ... View more

What you saw first was an embedded jpeg preview in the raw file that the camera generated. After a while, Lightroom will render its own preview using its own raw default settings. I always recommend people change those raw defaults (in preferences->Presets) to "Camera Settings" to avoid this confusion. This setting will choose a more camera specific profile or the embedded profile if these are dng files by default instead of Adobe default. This applies to newly imported images. For already imported images try using the "camera settings" preset on them.  Also, just hit Auto and your images will look great again. The default rendering for raw data is usually pretty bland and boring. Raw images almost always need editing. ... View more

make sure you give lightroom full disk access in System settings->Privacy & Security -> Full Disk Access. The first time you start the program it should ask you but that sometimes doesn't happen or you might have clicked it away thinking it was spam. ... View more

Try turning off gpu acceleration in the preferences - performance section. There have been reports of very similar weird posterization artifacts with other AMD Radeon graphics cards.  ... View more