Jao vdL
Community Expert
Jao van de Lagemaat
Jao van de Lagemaat Photography
Jao vdL
Community Expert
Jao van de Lagemaat
Jao van de Lagemaat Photography
Activity
‎Jul 21, 2025
09:29 AM
As already mentioned, you are going to need a new computer to be able to run the current versions of Lightroom and Mac OS that will allow you to open those files unfortunately. It is possible to trick Mac computers to install newer Mac OS versions by using openCore Legacy Patcher which is probably much further than most people are willing to go as it is definitely an advanced hack.
... View more
‎Jul 21, 2025
09:24 AM
1 Upvote
You will lose the ability to denoise a dng image if it is a HDR merge, a panorama merge, or if it was exported using the lossy compression option. It is also possible that it originally was a raw image shot at reduced resolution in camera. That also creates a linearized raw file. If that later gets converted to dng, you would not be able to denoise that image.
... View more
‎Jul 19, 2025
07:09 PM
Not sure what you mean the new tool works exactly like the old slider but now you can live change the amount of denoise instead of having to generate a new dng file. The slider is exactly the same. 50 means half the full effect, 100 means maximum effect. Just like it did before. Just no new file needs to generate.
... View more
‎Jul 19, 2025
07:06 PM
try creating a new catalog and import a few images. See if that is still slow. It appears you have been upgrading this catalog since Lightroom version 5 so perhaps some problems slipped in.
... View more
‎Jun 28, 2025
06:11 PM
it would make the slider incredibly slow to respond if they didn't store the denoise data as every time it would need to recreate it. The data it stores is a reduced representation of the raw data as seen by the ai. The cool thing is that doing it this way allows them to on the fly dial in different denoise levels. Secondly, when you turn on xmp backups, what Lightroom Classic does is store the exact same data in the xmp sidecar backup as it stores in the catalog files. So this also includes this fast denoise data. This is no different from all the AI masks, AI remove data, etc etc. that all gets stored in the xmp sidecar if you enable the auto xmp writing even if Lightroom or camera raw could easily regenerate those masks. This can make the xmp sidecars really big indeed.
... View more
‎Jun 28, 2025
11:37 AM
Are you sure the xmp files don't get actually updated when you are stepping through? Finder can be extraordinarily sluggish with updating the metadata columns. It certainly seems like Lightroom is saving something seeing how long it takes to count down the number of saves left. Often you have to close and reopen a folder to see any updates.
Anyway, these are clearly bugs with the automatic xmp writing system. That has always been very buggy unfortunately.
... View more
‎Jun 28, 2025
11:23 AM
Normally the denoise result is put in the catalog only. It only gets put as a copy in the xmp when you have automatic xmp writing turned on. This data has to reside somewhere. In previous versions of Lightroom, a separate dng file would get created with the denoise data. In the new version, the denoise data that allows you to charge the amount of denoising after the fact is stored in the metadata in the catalog. Denoising this way unavoidably adds some megabytes that have to be somewhere.
... View more
‎Jun 14, 2025
10:19 AM
2 Upvotes
The way to work is exactly the same as if Classic is the master. Classic simply ALWAYS works as if it is the master of the universe. SO when you want to occasionally use CLassic, know that it will ALWAYS download everything new from the cloud. So be prepared to always have a full copy of everything in the cloud in your Classic catalog if you go this way. There really are only two options when involving the cloud. One go full Lightroom Cloudy and never use Classic again. 2. use Classic as the master, import in Classic and sync smart previews or import in Cloudy on mobile or Desktop, and be prepared that everything always will get downloaded to Classic.
You really cannot use Classic just a bit. It won't work that way.
... View more
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 26, 2025
08:32 AM
‎May 26, 2025
08:32 AM
Open Preferences from the Lightroom menu and navigate to the Cache tab and follow instructions below. Hit clear cache if you want to temporarily lower the amount of space used for images that are stored in the cloud anyway. Also make sure you are actually syncing to the cloud (hit the cloud button in the top right of the screen and ensure it is not paused and that it does so "synced and backed up"). Also when buying Apple laptops (or any really), 512 GB SSD is the absolute bare minimum if you deal with lots of images although 3000 is still a very small amount.
... View more
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 26, 2025
08:21 AM
‎May 26, 2025
08:21 AM
No. The shared album feature relies on the images being stored in the cloud. You can archive images locally but they will disappear from any albums including shared ones you have. There is an undocumented hack using Lightroom classic to replace the online images with smart previews that do not take up any cloud space but this is very much a kludge. If you need the images to stay online after removing from your Adobe cloud account, you should use an independent service such as zenfolio, smugmug, flickr, etc.
... View more
‎May 25, 2025
10:39 AM
>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
‎May 25, 2025
10:33 AM
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
‎May 25, 2025
10:04 AM
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
‎May 25, 2025
07:43 AM
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
‎May 17, 2025
06:42 PM
(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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 04, 2025
09:03 AM
‎May 04, 2025
09:03 AM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 04, 2025
07:43 AM
‎May 04, 2025
07:43 AM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 04, 2025
07:04 AM
‎May 04, 2025
07:04 AM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 04, 2025
06:35 AM
‎May 04, 2025
06:35 AM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 04, 2025
06:24 AM
‎May 04, 2025
06:24 AM
You cannot see Lightroom's storage in the cloud inside the creative cloud storage. The only way to see the images is in the Lightroom app whether on mobile or on Mac/windows or in a browser at https://lightroom.adobe.com. These files are hidden from the rest of the ecosystem probably to avoid them getting corrupted or messed with. The only way to interact with them is through Lightroom.
... View more
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎May 04, 2025
06:19 AM
‎May 04, 2025
06:19 AM
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
‎May 04, 2025
06:03 AM
1 Upvote
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
‎May 04, 2025
05:42 AM
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
‎Apr 24, 2025
12:38 PM
1 Upvote
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
‎Apr 05, 2025
02:47 PM
1 Upvote
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
‎Apr 05, 2025
02:45 PM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎Apr 05, 2025
10:05 AM
‎Apr 05, 2025
10:05 AM
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
‎Apr 05, 2025
09:57 AM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎Mar 28, 2025
02:17 PM
‎Mar 28, 2025
02:17 PM
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
Community Expert
in Lightroom ecosystem (Cloud-based) Discussions
‎Mar 28, 2025
07:57 AM
‎Mar 28, 2025
07:57 AM
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