Previously I used LrC 12 (and other versions). Recently I installed LR 14.1.1 on a new system. Now the suggested names on recognized face regions look bad. I attached screenshots to show the issue, unfortunatly the screenshots do not show the whole extent of the problem; They look a little bit softer than the original LR interface on the monitor.    System Details: Windows 10 22H2 nVidia GeForce RTX 4070 S GPU driver version: 566.36 (studio driver) DirectX 12 24" LCD with 1920 x 1200 px resolution / 22" LCD with 1680 x 1050 px resolution (both 8bit, 60Hz) Issue happens when Windows UI scaling is set to 100% (default) as well as when it is set to 110%.   Manually added person tag – a bit blurry but ok:   Suggested person tags – double letter edges or something, seemingly on some backgrounds more than on others (but sometimes more on dark and sometimes more on bright backgrounds), mostly on letters with straight lines:  after accepting a suggestion it looks a bit blurry but ok:    Suggested person tag – strange looking color/brightness shifts, seemingly on unsteady background:   Other texts within Lightroom with similar size look fine:           [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.] ... View more

In the last few weeks / current LR Classic versions, I experience a new issue, when doing 2 operations simultaniously.   Steps to reproduce: 0a. Have multiple image root locations (multiple drives/main folders/...) + Have images in them. 1. Move a (sub-)folder / images from location A to location B (in LR, lefts sightbar, folder pane) 2. Start an import from somewhere else* to a new folder in location A + activate creation of default previews 3. wait a little * I usually import from another device/PC connected via LAN. But I think this is not relevant to trigger this issue. My current LR version: 11.2 Build 202201281441-a5b5f472 My OS: Windows 10.0.18363   At first, all looks fine, but after few moments, all 3 operations (moving, import, preview creation) just hang and I have to manually abort them and restart them (for the rest of the images).   I usually do this for 2 reasons: I have not much free disk space left (new disk is ordered) AND I work with a super fast SSD for current projects + large HDDs for older projects / archive.   ... View more

Issue: image gets deselected after changing/removing color lable Lightroom Classic Version Number: 11.0 Build 202110120910-0bccc70d  OS Version Number: Windows 10.0.18363 Steps to reproduce: Have some images in your current folder/collection/... Activate attribute filter and select some color labels there (including "none") Select one image and open in Loupe View Change color label of selected image (maybe change it a few times - can be done fast or slow. Issue only occures sometimes.) - use only color labels that are selected in color filter Expected result: Color label should change, image should stay selected all the time. Actual result: Color label changes, but sometimes imge gets deselected. Loup view says that no image is selected and I have to go back to grid view and select it again. (I guess the color label filter leads to a complete refresh of the images as if I change the filter.)   Issue never occured befor the last update. ... View more

I just upgraded from LR 6 to LR Classic CC (LR 7.4) an was pleased by the improved performance. But the more I use it, the more frustrating it gets. With Lightroom 6 it was possible to edit presets within an text editor. One could just remove one code line that way and Lightroom ignored the respective setting when the preset was applied. Now – with Lightroom 7 and XMP presets – this doesn't work anymore if one uses such a modified preset as import preset. The missing value now is reset to Lightroom's default value (mostly to 0), not even to the configured "defaults specific to camera ISO setting". It also doesn't makes a difference if I remove a code line or if only the value within the "" is removed in the xmp file. If one reassigns such a preset, it still works fine and the removed settings aren't touched anymore by Lightroom. I suppose, the import setting behavior is a bug, since the preset acts like before when applied later on. The old behavior gave the option e.g. to only change the overall sharpening value without changing the other values (and thus it was able to combine presets with Lightroom's camera/ISO-specific base values). This "trick" in general e.g. was described here: - Custom preset that modifies RGB channels but not the main curve? - https://blog.thomasfitzgeraldphotography.com/blog/2017/10/manually-editing-lightroom-preset-files-in-bbedit Of course one could modify his workflow from: 1) Import with development preset & generate previews ! to: 1) Import without preset -waiting-> 2) manually assign preset -short waiting-> 3) manually start preview creation This workaround at least works until Adobe maybe changes the behavior of development presets also when they are manually applied. Until then it only costs more time and you need to wait in front of your computer. If this was an intentional change, then Adobe really just managed to make the presets even more useless. How is this even possible?! For years customers ask for better preset-features (like relative presets), but now Adobe even reduces the possibilities. I will continue the test period but I already consider downgrading again. If a software attempts to manage all my photos from many years, I'm really sensitiv for bugs and inconsistent behavior/possibilities. ... View more