About John R Ellis - Adobe Community

Exit

John R Ellis

LEGEND

John R Ellis

LEGEND

Activity

No worries, it always helps to have a second pair of eyes checking such details.

"In preferences you have an option to choose comma or space as keyword separator." True, but comma is the default, and the choice of comma or space has always been there. "For years now, I have created hundreds of keywords using both commas and spaces to tag people by last name, first name and towns by city, state." Did you do this in another app and then import the keyworded photos into LR? You could never have entered such keywords in LR.

"14198 x 13459" Hmm. 14,198 x 13,459 = 191,090,882, or 192 megapixels, far smaller than the maximum 512 megapixels. And the long edge 14,198 is much less than 65,000. If you upload the file to Dropbox, Google Drive, or similar and post the sharing link here, we can submit a bug report. (Adobe won't pay attention without a sample image showing the problem.)

At least as far back as LR 3, commas have been the keyword separator in the Keywording panel and not allowed in keywords. If you tried to create a keyword with a comma, LR would complain. However, due to longstanding bugs, LR sometimes creates keywords with commas; e.g. when you import photos containing such keywords, LR doesn't alert you. Spaces have always been allowed within keywords. "...they now say ... spaces are used as a keyword separators. " Where do you see that?

That message accurately states the longstanding limits on pixel dimensions: https://helpx.adobe.com/lightroom-classic/help/supported-file-formats.html What are the pixel dimensions of the problem image?

See this FAQ: https://www.lightroomqueen.com/community/threads/faq-where-are-my-develop-presets.50140/

@Rikk Flohr: Photography: Please consider moving to Bugs. As you can see from all the threads I've identified, there are many reports about LR 14 / Windows 10 hanging when it tries to import from a folder containing video. Some of the people have confirmed they have Windows 10 22H2 as specified in the system requirements.

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-vi...

There's a bug in LR 14 / Windows 10 that prevents it from importing video and importing photos from folders containing video. The only workaround is the one you discovered: Move the videos out of the folders containing the photos you want to import. There is no known workaround for importing videos directly, though you could use the Any File plugin if you want to continue managing videos in your LR catalog. Adobe has not yet acknowledged this issue.

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-video-file/idi-p/14966131

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-video-file/idi-p/14966131

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-video-file/idi-p/14966131

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-video-file/idi-p/14966131

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-video-file/idi-p/14966131

Moderators, @Rikk Flohr: Photography: Please merge with this thread about importing video on Windows 10: https://community.adobe.com/t5/lightroom-classic-bugs/p-import-fails-when-it-encounters-a-corrupt-video-file/idi-p/14966131

Since LR 14.0, I've had several hundred old photos (out of 8K) get marked for republishing to Flickr and Zenfolio. That's a lower rate than before, but it still happens.

Glad you got it resolved. Was it a problem with the display profile?

"DirectX: NVIDIA GeForce RTX 3060 (32.0.15.6590)" There's a newer Studio driver available: https://www.nvidia.com/en-us/drivers/details/235906/ It may not help, but it's good hygiene to be on the latest Studio driver. "F:\Adobe\Catalog\Lightroom4 Catalog\Lightroom 4 Catalog\Lightroom Catalog-2-2-2-v13-3.lrcat" To rule out issues with the F drive, create a new temporary catalog on the C drive, and import a hundred photos into it using the Add option (so you don't move them). If the problem doesn't occur with the new catalog, try moving your main catalog folder to the C drive. If the problem doesn't occur, that indicates a problem with the F drive. If the problem does occur, that indicates a problem with the main catalog.

"The Adobe support website says Denoise now it works with TIFFs and JPGs." Please post a link to where you read that. The Help still says: https://helpx.adobe.com/lightroom-classic/help/enhance-details.html "Denoise helps remove noise easily from an image. Using artificial intelligence, any Bayer or X-Trans RAW files can be processed to reduce noise without losing the image's fine details." Many, many users are awaiting Denoise for non-raws!

In addition to sending a crash report to Adobe (be sure to include the email address associated with your Adobe Id), do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

Try these troubleshooting steps: https://helpx.adobe.com/lightroom-classic/kb/photos-appear-black-gray-rectangles.html

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.] Remove quickly removed the object from your screenshot: Removing objects from the edges of photos requires a little extra attention: 1. Uncheck Detect Objects (on by default in LR 14) -- it doesn't work well, especially with skinny objects and along the edges of photos. 2. Undo any Crop, Lens Correction, and Transform, apply Remove, then reapply those commands. Remove tries to match the unselected cropped-out pixels. If this doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot), so we and Adobe can see the issue in detail. With nearly every of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

Exporting that DNG (with all your settings) works fine on my Macbook Pro M2 Max / LR 14.0.1. That, combined with the fact that it exports correctly on your computer with the GPU disabled, points to a bug in the graphics driver or, possible but less likely, a bug in how LR is using the standard Windows API that only affects this particular GPU/driver (LR doesn't code for particular GPUs). In general, LR uses GPUs much differently than other apps and trips over driver bugs that don't affect those apps. Games generate gazillions of little shaded triangles in real time, whereas LR is executing a complicated rendering pipeline to apply the various non-destructive develop settings to an array of pixels. There are many, many posts here from people who have experienced driver issues with LR but not other app, and updating the driver fixed them. As an immediate workaround, if you set Preferences > Performance > Use Graphics Processor to Custom and uncheck Use GPU For Export, you should get all the other benefits of the GPU except for export. (LR always uses the GPU for its AI commands -- denoise, masking, and lens blur -- ignoring the setting in Preferences.) Historically, new releases of Nvidia Studio drivers have been pretty well tested and don't introduce new problems for LR. But I recall a couple of instances in the past where a new Studio driver has introduced a bug LR tripped over. You could try rolling back to an older Studio driver, say 6 months old, to see if that helps: https://www.nvidia.com/en-us/drivers/results/ Or you could wait for a month or two and hope the problem gets fixed in the next monthly release.

"DirectX: Radeon(TM) 530 (22.19.128.3)" That graphics driver is 7 years old. Update to the latest driver here: https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-22-6-1-LEGACY.html That may help. If it doesn't, though, you're out of luck. LR is very sensitive to bugs in graphics drivers, and AMD no longer supports drivers for the 530 (announced in 2017). And Adobe inexplicably refuses to allow use of the GPU be disabled for LR's AI commands, even though the masking commands run perfectly fine (though a little slower) without a GPU.

@stephenp69774191, glad it's resolved. Was the camera set to High Efficiency* by default or did you set it? That could help others, since it will surely come up again.

@cassandrag56853664: "it keeps generating new, weird, different items in its place instead of REMOVING it by matching the background. " 1. Uncheck Detect Objects (on by default in LR 14) -- it doesn't work well, especially with skinny objects and along the edges of photos. 2. See this article for how to remove objects more reliably: https://www.lightroomqueen.com/generative-remove-replace/ Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot), so we and Adobe can see the issue in detail. With nearly every of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.] @T.S. Photos: "ocassionally it just replaces the selection with a shadow or ghost of it. " These ghosts are caused by applying Remove on top of an AI mask (e.g. Sky). Do the menu command Settings > Update AI Settings to recompute the mask.

Please do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

Please do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.] My LR 14.0.1 can't import that file either: Exiftool shows the pre-production samples using raw Lossless compression, while your .nef is using raw High Efficiency* compression. Try setting the camera's raw-recording compression to Lossless: