When the remove tool is used on photos taken with high ISO, it ignores the existing noise. The resulting generation may be very good but much smoother than the surrounding area, which makes corrections prominent and visible. It would be perfect if the generative remove tool would recreate the character and intensity of the picture noise / granity.   ... View more

Thank you for the link, I found it already and read it. I figured these tricks on my own already, but sometimes (I can admit, on rare occasions) it doesn't help and modifications of the existing selection don't help, too. In these cases, if I delete the original selection completely and start over, it works properly even if I recreate the original selection in details. ... View more

Generative remove tool: usually it works well. But sometimes, it continuously suggests different versions of objects I'm trying to remove, even with multiple attempts of regeneration. For example, it may again and again draw a different person in the background, instead of removing the original one (and in many cases, the new "person" looks more defined and recognizable than the original). Or just now, when I tried to remove some metal frame from the forest setting, it redrawn it many times into something different but still a metal frame 🙂 Modifications of the existing selection don't help. The only way to make it do right job is to completely remove the selection and start over. LR 14.0.1 - Camera Raw 17.0 (Windows 10 with all recent updates) OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name KRAKOZAVR System Manufacturer To Be Filled By O.E.M. System Model To Be Filled By O.E.M. System Type x64-based PC System SKU To Be Filled By O.E.M. Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. P7.30, 1/23/2018 SMBIOS Version 2.8 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer ASRock BaseBoard Product Z170 Gaming K4/D3 BaseBoard Version Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume2 Locale United States Hardware Abstraction Layer Version = "10.0.19041.3636" User Name KRAKOZAVR\AlexArtPhoto Time Zone Eastern Daylight Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.9 GB Available Physical Memory 10.3 GB Total Virtual Memory 114 GB Available Virtual Memory 76.5 GB Page File Space 82.1 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes ... View more

Hello. "Stacking by time" is a great feature, but many times, it is failing. The problem is: when you shoot exposure bracketing for HDR composing, the time between shots in sequences may vary, and it may be longer than the time between different shoots. A vivid example: you do a real estate bracketing shoot. In a bright room, the sequence duration will be very short, and the sequence duration in a dark basement will be very, very long. Same time, an interval between two sequences taken in the same room, just with a different angle, may be a split second. It makes auto stacking nearly impossible. But the number of pictures in each sequence will always be the same - 3, or 5, or whatever you set. So, why not allow to set auto stacking by this number? "Stack sequences by 3, 5, 7 pictures", and it will work in any situation when you use auto bracketing! ... View more