Import Glitch with renaming preset

[NickC]

Lightroom Version Number

14.2

Operating System

1. macOS 15 Sequoia

My workflow involves importing Nikon NEF files into LRC using a template that generates "custom text"_date_sequence (you can see the generated filename in the grayish border at the top of the screenshot). Been doing that for years with no issues. Within the past few months, I've had isolated and inconsistent cases where a small number of imported files fail to rename. I get the following error. I imported roughly 50 NEF's today but 3 of them didn't rename.

As can be seen, files aren't necessarily sequential. I can edit and export as normal. I can't manually rename nor can I delete them (only 1 of these 3 is a keeper)

Camera is a Nikon D7200 I've had for years. I've used SanDisk 64 or 128 GB cards for years. I just started using a new card within the past week. First few imports were fine but not today.

Any ideas or thoughts?

Thanks,
Nick

 

[Gnits]

Have you still got the card. Are there multiple DCIM subfolders. A new DCIM subfolder is created on the card in a number of scenarios.. most usual is when the camera sequence number reaches its 999 or 9999 limit and needs to reset to 1. If you are a high volume shooter then your card could contain multiple images with the same suffix number ( but stored in different DCIM subfolders).

That is less likely here as you would expect more than 3 images to have this condition.

Another scenario is that the card was not formatted and some images may have been imported already. There may be other scenarios.

 

[Califdan]

I don't think this is a card issue.

As Matt suggested, if these images are being placed into a preexisting folder that folder may already contain an image with the new file name.

Another possibility is a timing error. In this case LrC told the OS to copy/move the image file from the card to the desitnation folder and then issued a second command to the OS to rename the file (I'm not 100% sure it works that way but it may). But, the initail "move" had not completed prior to the rename being reuqested. As such the OS returned an error that it could not do the rename to LrC which LrC presented in the screen shot.

In your renaming template it looks like you put a 3 digit sequential number at the end of the file names. For the images that were correctly renamed, did it leave a gap in the sequential number where these 3 should have gone?

 

[NickC]

Have you still got the card. Are there multiple DCIM subfolders. A new DCIM subfolder is created on the card in a number of scenarios.. most usual is when the camera sequence number reaches its 999 or 9999 limit and needs to reset to 1. If you are a high volume shooter then your card could contain multiple images with the same suffix number ( but stored in different DCIM subfolders).

That is less likely here as you would expect more than 3 images to have this condition.

Another scenario is that the card was not formatted and some images may have been imported already. There may be other scenarios.

Thanks Matt although I don't think any of this applies to my case. Card is new and was formatted in camera prior to use. In total, it has roughly 300 images on it (Nikon rolls over after 9999).

I changed cards awhile back thinking it was a card issue. And the new card behaved so thought the old one got buggered up somehow. Now seeing the same thing. It's the inconsistency and unpredictability that has me scratching my head.

 

[NickC]

I don't think this is a card issue.

As Matt suggested, if these images are being placed into a preexisting folder that folder may already contain an image with the new file name.

Another possibility is a timing error. In this case LrC told the OS to copy/move the image file from the card to the desitnation folder and then issued a second command to the OS to rename the file (I'm not 100% sure it works that way but it may). But, the initail "move" had not completed prior to the rename being reuqested. As such the OS returned an error that it could not do the rename to LrC which LrC presented in the screen shot.

In your renaming template it looks like you put a 3 digit sequential number at the end of the file names. For the images that were correctly renamed, did it leave a gap in the sequential number where these 3 should have gone?

Nope. The correctly numbered files are true to the preset nomenclature. Here's a screenshot of two successive images, one good the other not.

The timing error is an interesting idea although I have no idea how I could confirm that (or worse, how to fix if that is the case).

I could very well import another 50 images tomorrow and have the same thing happen or with all 50 imported with no problem. No consistency at all.

Thanks for taking the time and for the ideas. Would welcome any other thoughts.

Nick

 

[clee01l]

Can you post the exact file naming preset? And the Creation Date and the Original File Name field of the DSC_1800 file. and the one beside it in the grid screen shot as posted in the Metadata panel?

I am inclined to think the problem is either the Naming preset or the metadata in the files that are failing.

 

[Califdan]

I am inclined to think the problem is either the Naming preset or the metadata in the files that are failing.

To test this theory, can you select the 3 that didn't rename and run the rename preset manually (F2 on the keyborad, then select the preset).

 

[clee01l]

To test this theory, can you select the 3 that didn't rename and run the rename preset manually (F2 on the keyborad, then select the preset).

I'm not the OP. I have asked for information details about the files that have been used to illustrate the problem.

 

[Califdan]

@clee01l - Yes, I know, I was giving the OP a suggestion of how to test your idea that there is something amiss in the template or in the image metadata. If your hypothesis is correct then manually running the rename template will fail. But it it succeeds, then I'd say that demonstrates that the problem is not in rhe rename template or the image metadata and lies elsewhere.

 

[NickC]

Can you post the exact file naming preset? And the Creation Date and the Original File Name field of the DSC_1800 file. and the one beside it in the grid screen shot as posted in the Metadata panel?

I am inclined to think the problem is either the Naming preset or the metadata in the files that are failing.

Here's the naming preset. I've been using this template since my early days of LR, going back to 4.x No problems until late 2024.

The two files as requested. To avoid any confusion regarding DSC1800, I inadvertently hit the shutter while in a parking lot. Minimum focus distance with the lens is 20 ft so the resulting image of the asphalt is soft gray. Not equating the file number issue with the gray image.

Thank you Cletus.


Nick

 

[NickC]

To test this theory, can you select the 3 that didn't rename and run the rename preset manually (F2 on the keyborad, then select the preset).

Doesn't work - see below.... Error message when trying to rename manually.
'

 

[NickC]

@clee01l - Yes, I know, I was giving the OP a suggestion of how to test your idea that there is something amiss in the template or in the image metadata. If your hypothesis is correct then manually running the rename template will fail. But it it succeeds, then I'd say that demonstrates that the problem is not in rhe rename template or the image metadata and lies elsewhere.

Thanks all for your ideas and suggestions. I want to restate to be clear - I've been using the same template for as long as I've been using LR. The only change is when I change the year in my copyright notice. Otherwise, it's the very same preset.

Thanks,
Nick

 

[Califdan]

Your tempalate adds a 3 digit at the end of the file name.

Is it possible that you tried to import more than 999 images for a single day? If so I'm not sure what that "Sequence # (001)" does after it reaches 999. If it circles back to 001, then that would be a duplicate file name probably in the same folder.

The only change is when I change the year in my copyright notice. Otherwise, it's the very same preset.

I don't see anything in the template that relates to a copyright notice field so chaning the year on a copyright field in a preset would not impact the file name.

The entire path name is not visilbe in the error message (3 dots in the middle) but perhaps the path + file name is too long. But that's not likely if other photos in the same import batch are going into the same folder. Unless, perhaps, LrC is using, say, a spelled out month name in the folder path and those 3 images were shot in a month with a longer name than the others. Again, unlikely.

Using Finder, can you try renaming one of these images to the exact same path/file name as the template is trying to create for it to see if the issue is with the OS?

 

[Gnits]

Just something to eliminate.

Are there any images in the folder which are not imported ( ie and are not visible when the folder is viewed in Lr Library). Try right click on the folder and resynch the folder. Such files might be preventing the rename.

Also, the images may not be imported in the sequence expected… as the import process may be using multiple threads.

I need to check this… is the sequence number reset just for this batch of import images or is this sequence number counting the number within the overall catalog (ie ability to create a unique image number per imported image.

Either way… I agree with Califdan re use of only a 3 digit seq number.

 

[NickC]

Your tempalate adds a 3 digit at the end of the file name.

Is it possible that you tried to import more than 999 images for a single day? If so I'm not sure what that "Sequence # (001)" does after it reaches 999. If it circles back to 001, then that would be a duplicate file name probably in the same folder.

There are perhaps 200 images on the card. As mentioned above, I've been using the same preset for 10 years or so. I've never tried to import 1000 plus images at a time (high volume might be 500-700 images after a race weekend but typically, I'm importing less than 100 images at a time).

I don't see anything in the template that relates to a copyright notice field so chaning the year on a copyright field in a preset would not impact the file name.

The entire path name is not visilbe in the error message (3 dots in the middle) but perhaps the path + file name is too long. But that's not likely if other photos in the same import batch are going into the same folder. Unless, perhaps, LrC is using, say, a spelled out month name in the folder path and those 3 images were shot in a month with a longer name than the others. Again, unlikely.

I'm not aware of file length restrictions. I'm sure if I expand the window, the complete file path would be visible.

Using Finder, can you try renaming one of these images to the exact same path/file name as the template is trying to create for it to see if the issue is with the OS?

I'll try that. I hadn't thought of that. Quick to note that's a good diagnostic but I don't want to start renaming files outside of LR....

Thanks.

 

[NickC]

Just something to eliminate.

Are there any images in the folder which are not imported ( ie and are not visible when the folder is viewed in Lr Library). Try right click on the folder and resynch the folder. Such files might be preventing the rename.

Not sure, but I'll try later today when I've got some time.

Also, the images may not be imported in the sequence expected… as the import process may be using multiple threads.

I need to check this… is the sequence number reset just for this batch of import images or is this sequence number counting the number within the overall catalog (ie ability to create a unique image number per imported image.

The sequencing starts from "001" on each import (actually, the "start number" is user selectable in the preset)

Either way… I agree with Califdan re use of only a 3 digit seq number.

I'm not convinced - keeping an open mind and I'm appreciative of the help. I just have a hard time thinking it's the numbering scheme when the same scheme has been used for years without any problem.

Thanks all for your help.
Nick

 

[clee01l]

Here's the naming preset. I've been using this template since my early days of LR, going back to 4.x No problems until late 2024.

View attachment 25903

The two files as requested. To avoid any confusion regarding DSC1800, I inadvertently hit the shutter while in a parking lot. Minimum focus distance with the lens is 20 ft so the resulting image of the asphalt is soft gray. Not equating the file number issue with the gray image.

View attachment 25904

View attachment 25906

Thank you Cletus.


Nick

I see nothing amiss with the information that you sent. I also asked for the Original File Name field. This is not included in the EXIF preset that you are using but is included in the "Default".

I see that you have "Automatically write Changes into XMP" checked in Catalog preferences. This is an unnecessary step and has caused problems sing LrC v13.3 . I don't know if this is related but it would not hurt to test with "Automatically write Changes into XMP" unchecked in Catalog preferences.

 

[Califdan]

'm not aware of file length restrictions. I'm sure if I expand the window, the complete file path would be visible.

I don't know about Mac's but on my Windows machine I've hit a limit of the total number of characters in a complete path when moving files/backing up files. I'm not sure if the limit is enherant in the OS or was in the SW I was using to do the move/backlu.

In addition to trying the rename using Finder (with the image file in the destination folder specified for the import), try typing the new file name in the File name field in the metadata panel and see if that works or generates the same error.

If all else fails, reset your preferences and/or re-install LrC

 

[clee01l]

I don't know about Mac's but on my Windows machine I've hit a limit of the total number of characters in a complete path when moving files/backing up files. I'm not sure if the limit is enherant in the OS or was in the SW I was using to do the move/backlu.

In addition to trying the rename using Finder (with the image file in the destination folder specified for the import), try typing the new file name in the File name field in the metadata panel and see if that works or generates the same error.

If all else fails, reset your preferences and/or re-install LrC

I think that WindowsOS limit is 256 chard for the full path including the file name. Or used to be. I don’t know about a lime on MacOS but suspect it is about the same.

However this is not the case as the file naming template is the same for the image that work and those that don’t. As they are going to be renamed the same varying but a different sequence number and in the same file (path)


Sent from my iPad using Tapatalk

 

[NickC]

Your tempalate adds a 3 digit at the end of the file name.

Is it possible that you tried to import more than 999 images for a single day? If so I'm not sure what that "Sequence # (001)" does after it reaches 999. If it circles back to 001, then that would be a duplicate file name probably in the same folder.

I don't see anything in the template that relates to a copyright notice field so chaning the year on a copyright field in a preset would not impact the file name.

The entire path name is not visilbe in the error message (3 dots in the middle) but perhaps the path + file name is too long. But that's not likely if other photos in the same import batch are going into the same folder. Unless, perhaps, LrC is using, say, a spelled out month name in the folder path and those 3 images were shot in a month with a longer name than the others. Again, unlikely.

Using Finder, can you try renaming one of these images to the exact same path/file name as the template is trying to create for it to see if the issue is with the OS?

Partial screenshot from finder. The unnamed files (1800 and 1789) have little padlocks associated with them and I can't rename. I can rename any of the other files already named per the desired naming scheme. Funny thing is when I double click on 1800, it opens DXO PhotoLab. I'm guessing there's a setting somewhere causes that but I'm not going to try to figure that one out....

 

[NickC]

I see nothing amiss with the information that you sent. I also asked for the Original File Name field. This is not included in the EXIF preset that you are using but is included in the "Default".

Here you go -

I see that you have "Automatically write Changes into XMP" checked in Catalog preferences. This is an unnecessary step and has caused problems sing LrC v13.3 . I don't know if this is related but it would not hurt to test with "Automatically write Changes into XMP" unchecked in Catalog preferences.

Unchecked XMP. I get a note indicating that changes made in LR will not be automatically recognized by other programs. I don't know what the potential implications of this might be. I tend to do everything in Lightroom but use DxO infrequently and have tried Photoshop but my workflow is primarily LR. I'm assuming this isn't a big deal.

Someone else mentioned that reinstalling LR might be the way to go which might make the most sense. My photo computer is a Mac Studio which replaced an iMac. These were "family computers" - the Apple ID associated with the Studio is my wife's email. Realistically, I'm the only one using the Studio. After retiring recently, I replaced my work Windows laptop with a Mac Air. That is associated with my Apple ID. I am thinking it might make the most sense to reconfigure the Studio as my primary computer, using my Apple ID for the Studio and the Air. Reinstall LR on the Studio and go from there. I don't envision using the Air for photo processing (we travel a fair bit) but I do see value in dumping a days worth of photos onto the laptop when traveling, more as a back up than anything else. I can see the benefit of this approach (and presumably fix the naming snafu) - I just am not 100% sure how best to do all that.

Sorry for the long winded explanation - any suggestions, questions, or cautions you wish to offer would be appreciated.

Thanks,
Nick

 

[Califdan]

The unnamed files (1800 and 1789) have little padlocks associated with them and I can't rename. I can rename any of the other files already named per the desired naming scheme

I think that's it. The OS is showing the image as locked which prevents alteration of the file - including renaming it. I believe that in most cases, locking an image in the camera will cause it to also be locked when that image is copied from the SD card. It's probably not related, but at least 1800 is also set at "rejected". Use your OS to unlock the image (a Mac person will have to tell you how if you don't know on your own) and I suspect your problem will go away.

However this is not the case as the file naming template is the same for the image that work and those that don’t. As they are going to be renamed the same varying but a different sequence number and in the same file (path)

I think that having the file locked in the OS is the issue, but before seeing that, I had the same thought as you that the only varible in the rename template is the sequence number value which doesn't affect the number of characters in the path. But then I pondered what else could change the number of characters in the full path. The only thing that came to mind is if using the "by date" option on import with a template choice that used the full month name. So an image shot in "May" would have a shorter total path than a photo shot in "December" and that could potentially throw it over the limit. A real long shot but possible.

 

[NickC]

I think that's it. The OS is showing the image as locked which prevents alteration of the file - including renaming it. I believe that in most cases, locking an image in the camera will cause it to also be locked when that image is copied from the SD card. It's probably not related, but at least 1800 is also set at "rejected". Use your OS to unlock the image (a Mac person will have to tell you how if you don't know on your own) and I suspect your problem will go away.

Bingo! Just checked the camera and 1800 is indeed locked. Didn't check, but I'm sure the other two unnamed files are locked as well. That's been a thorn with the D7200. I love the camera but it's easy to hit the lock button when reviewing files. There's no connection with the rejected status as I had done that after the image was imported into LR (it was an accidental shutter actuation).

Thank you all for taking the time brainstorming on this. Very much appreciated!

Nick

I think that having the file locked in the OS is the issue, but before seeing that, I had the same thought as you that the only varible in the rename template is the sequence number value which doesn't affect the number of characters in the path. But then I pondered what else could change the number of characters in the full path. The only thing that came to mind is if using the "by date" option on import with a template choice that used the full month name. So an image shot in "May" would have a shorter total path than a photo shot in "December" and that could potentially throw it over the limit. A real long shot but possible.