Inspiring

Question

Exporting pictures (RAW) not working

Forum|Forum|1 year ago
April 15, 2024
2 replies
1482 views

Hi All,

I am a professional photographer, and know Lightroom pretty much inside and out. However, since a few months now, I am having difficulties exporting photos, which are located on my NAS, but I even copied the raw files over to my external SSD (Sandisk extreme Pro V2 4Tb) and still, it is exporting images upto a certain point and then stops the export. Some collections export as expected, while some just "hang".

I am just exporting edited raw files to jpeg (high res) with jpeg mini plugin installed to limit file size, but I have also turned off jpeg mini pro and tried the export that way, but it doesn't help either. I can't see weird things in my RAW images in LR and the pictures/RAWs are all linked correctly. Some had a metadata issue, but I have overwritten the metadata of the files with issues in LR, which also doesn't do anything...

I have even tried to export the collection in smaller parts (24 images, but even that 'hangs'). Seems it is often hanging on the same image, but as stated, when I look that up, I can't find anything wrong with the RAWfile.

Any other ideas I can try?

Thank you in advance, I really need to get some of these images to a few clients.

Best regards,

DrBobke

macOS

This topic has been closed for replies.

D

dj_paige

Brainiac

I suppose that the usual things to try apply here

Turn off the GPU for exporting (uncheck the box shown below)
Reset preferences https://www.lightroomqueen.com/how-do-i-reset-lightrooms-preferences/

RobertSmitsAuthor

Inspiring

Hi dj_paige,

Thanks for chiming in. I have also tried exporting the edited raws on my WIN11 desktop PC and in one folder, I noticed one issue on 2 PSD files. Both showed a Black exclamation mark on the photo (library view - "Lightroom has encountered problems reading this photo), which I don't think I have seen when I was on my MBP (but it could have been there, as I didn't check in detail). When I went through explorer and viewed the files, tried opening them in PS, I had another error (photoshop could not open because an unexpected end-of-file was encountered). I have then looked up the two PSD files from an old backup, copied them over to the ext SSD (where I put the rest of the files) and all exported without issues...

However, I still have two other old folders that I need to export, which don't have the same error with the black exclamation mark. I did however, copy over all the RAW files, incl the xmp files to the ext SSD location, but the export still encounters issues and I think it's always the same virtual copies that have the issue.

What is weird, is that in grid view, all images appear, but when I go through them in the library or develop mode, some virtual copies, don't appear, the screen stays grey (background colour).

Those virtual copies, along with the "working" virtual copies, do not appear to have any metadata (lens/camera info, date/time,..) Also, the metadata options (rightclick) on the virtual copies (working and non-working), stay greyed out, the originals are fine to change (save metadata to file/ read metadata from file).

There are no errors to be seen on the files or virtual copies in the grid view, but I do think that images where I don't see the image of the virtual copy in library/develop mode, is then ones the export is hanging on.. This is partially confirmed by the fact that when I select "Attribute" and then "kind - originals" and export those, I have NO issues with the export.

I have disabled my hardware GPU acceleration, but that didn't help either (Nvidia GeForce RTX 2070 Trio Super 8Gb). But that seems to have been weird, as it also happened on my MBP, which obviously uses different hardware.

I did not reset my preferences yet, as I have a lot of custom stuff setup, which I don't want to loose or having to setup again on a "maybe" (add-ons, publish services, self-made presets, bought presets, etc). Especcially because I feel it's having to do with the virtual copies, not the originals themselves...

D

dj_paige

Brainiac

I have disabled my hardware GPU acceleration

Using the LrC Preferences dialog as I showed?

If you have customized preferences, make a copy before you try deleting the preference file. Then give it a try; if it doesn't work then restore the customized preferences. I keep a "Known Good" copy of a good preferences in a place where LrC won't change it at all times, so I can always get back to them if needed.

GoldingD

Brainiac

Where is the catalog kept?

RobertSmitsAuthor

Inspiring

Hi GoldingD, since Adobe doesn't want you to keep LR Cats on a network drive, it is on my internal SSD (and then synced through Synology Drive to the Synology and then to my Desktop PC). But, I have been using only my MBP for months now and the sync with Synology Drive has been 'suspended' for the last 40 days, as I would sometimes get corrupted catalogs, which I think is the reason (synology drive sync, or possibly a network glitch which causes an issue - I haven't had an issue when it was 'suspended').

I have however, always been able to successfully rebuild the corrupted catalog(s), the only thing was, that I always had to rebuild the smart previews and update the AI settings (local adjustments using subject selection). I have also noticed that virtual copies seems to have lost some of the metadata (which lens, focal lenght and camera settings, I think date and time are still there, yet it always puts the virtual copies (b&w) in my library first, grouped together, then followed by the original raws, after all the B&Ws. whereas it should be original (colour), followed by a B&W image...

The catalogs work fine for the rest of the time, just exporting is an issue (even when it's on the external SSD, but I have also tried moving the raws to my internal SSD in the past, to no avail).

RobertSmitsAuthor

Inspiring

There used to be (and I think still is, but it is long ago that I last needed to do this) an issue with repairing a corrupted catalog. During that process Lightroom renames the previews and smart previews (and apparently also the masks). That should be a temporary rename action in my opinion. When the catalog has been successfully repaired, the previews, smart previews and the .lrcat-data should be renamed again so they match the catalog name again, but that did 't (and still doesn't?) happen. You can do it manually, however. That will bring these things back.

Interesting, I didn't have so many corrupt catalogs in years, it was only after looking for a more centralized option of storing photos on a NAS, that I am sometimes running into these corrupt catalogs, but as said, when I turned off Synology Drive backups (40 days), I didn't have any issues with corrupted LR catalogs. And to be honest, I don't always do a backup of my catalogs when shutting down, as I often switch between 2 master catalogs (work and private) and sometimes another 'travel/on the road' catalog. My master catalogs house around 70k RAWS and the other around 160k (reason for getting the NAS is that those images eat a lot of HDD space 🙂 ).

In my case, apparently, it does not rename the catalog after the repair. I am intrigued by the manual operation though - Do you mean that after repair, I have to check the name of the catalog (it often renames itself to "Lightroom Catalog private-v13_MacBook-Pro-van-Robert.local_Dec-25-185107-2023_Conflict-2" the bold text is what is added by LR. I have sometimes deleted the "new" part in the past and checked the other "sidecar" files for naming and if applicable, changed those too, but that still didn't "attach" the smart previews, local adjustments etc to it again.

Is it something like that what you mean? All the help is greatly appreciated!

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded