Import Import file numbers not in sequential order

[cavics]

Lightroom Version Number

13.4

Operating System

1. Windows 11

VERY longtime Lightroom user, so I know what settings to use (hopefully).

Most every time I import photos from my SD card, the file names (numbers) are out of sequence. This happens regardless of the card, camera or catalog.

I have to change the view to capture order and rename the files in sequence.

Also, the start number needs to be manually set based upon the last file that I imported (adding one). It does not automatically default to the next number in the sequence.

My import setting is shown below.

Thanks in advance for any help.

 

[Johan Elzenga]

Yes, that is the way it is. I think that the out of sequence issue is caused by parallel importing of multiple images. For this reason I never rename images using sequence numbers. I always use ‘Original File Number Suffix’ as part of the new file name.

 

[Gnits]

If using the Lr import module to copy images to disk I use this format .

Note that the number of digits configurable.

This should also remember the last number used. I am never sure of the different number formats, but some are designed to start from 1 deliberately.

There can be a lot of reasons for out of sequence numbers.... definitely multi core processing is a factor.

Also, I am not sure if pre-sorting in the import dialogue may help.

A lot of people get into trouble with sequence because their camera may not be capturing precise sub second data (as some current cameras have really fast frame rates).

Footnote 1.
I found this note of mine from years back.
"Sequence # starts from the number you set in the import dialog, where it’s easy to change on the fly.
Image # starts from the number set in Catalog Settings, so it just keeps increasing unless you specifically go to Catalog Settings to change it."

Footnote 2.
I ingest my images from card to disk... outside Lr... so I have full control of the filename format. I use a format where I retain the original camera image number and add a unique sequence number.

 

[karl.nyhus]

For this reason I never rename images using sequence numbers. I always use ‘Original File Number Suffix’ as part of the new file name.

I always rename with capture date, abbreviated ID for the camera used, the original file number suffix, and the original file extension. That's enough to make my filenames unique. (I have only one body of each kind of camera I shoot with.)

yyyymmdd-XXXX-9999. ext

20240801-D750-1234.NEF
20240801-Z50-1234.NEF
20240801-XT4-1234.RAF
20240801-iPxs-1234.HEIC

 

[clee01l]

And I don't care about files names on import. They are always unique when used with a "date name" folder sequence. Since the image is managed by a DAM app (LrC), all of that complicated naming is available in the searchable metadata.

I do rename on publish/export because my exported images are not managed by a DAM app and often arranged in sequences that do not conform to capture date/time. My export file names always contain the original file number suffix to help me tie the exported file back to the LrC managed file.

 

[karl.nyhus]

... all of that complicated naming is available in the searchable metadata.

It's not that complicated. And I get to see it without having to search every time. It is a worthwhile "belt and suspenders" approach. Kind of like backing up our catalogs and images to a locally attached disk drive and to a cloud service.

 

[clee01l]

It's not that complicated. And I get to see it without having to search every time. It is a worthwhile "belt and suspenders" approach.

I guess it can get pretty complicated since I import almost all of my images using my iPadPro, Lightroom and the Adobe Cloud. I have a Smart Collection that will separate every image by Camera, and the folders are in date order. (I think that covers all of that "stuff" you are stuffing into the file name.)

 

[Gnits]

I always rename with capture date, abbreviated ID for the camera used, the original file number suffix, and the original file extension.

That may work if you are not a high volume shooter (eg sports/ wildlife). The Dcim standard in use by camera companies means the camera will create multiple DCIM subfolders once the camera sequence number cycles past 999 (sometimes 9999). I have copied cards that had at least 3 dcim sub folders, which means 1000's of duplicate / triplicate images on the same card, but protected by been in different DCIM sub folders.

This is the DCIM structure on a Sony camera. Canon, Nikon and others will be similar but use slightly different naming conventions.

 

[karl.nyhus]

(I think that covers all of that "stuff" you are stuffing into the file name.)

I like my filenames and I stick to my Mac and my iPhone and avoid the iPad.

The FastRawViewer Mac app handles culling, importing, and renaming images for me on my Mac whether they come from a camera memory card, via wireless transport, or downloaded from file sharing, email, or messaging services. (I used to use Adobe Bridge but find FastRawViewer to be lighter-weight and faster.)

FastRawViewer is made by https://www.libraw.org/about who supply software and APIs to a number of third party vendors of photo editing software (like Affinity Photo, for example).

 

[karl.nyhus]

That may work if you are not a high volume shooter ... I have copied cards that had at least 3 dcim sub folders, which means 1000's of duplicate / triplicate images on the same card

Well, we all are different. Guys like you have special needs and know what needs to be done for your situation. However, Adobe software is not just for high volume and / or professional shooters.

 

[Gnits]

Different people will have different needs.

In many cases the images may have a much more important life outside the safety of a single Lr account.

Consider the following.
1. Multiple photographers working on the same project, with multiple cameras and all using different post processing software / workflows.
2. Images generated for use in third party systems, where there are agreed naming conventions. This can be where images are used to monitor / track, say, construction projects, forensic examinations, project management systems.
3. Long term projects monitoring say a sensitive environmental location.

Probably for the majority of cases, a very basic filing / naming system will work.

But I regularly see issues where people caught on a) Multiple DCIM sub folders and b) frame rates where multiple images are captured per second, but depend on something like yyyymmddhhmmss to keep the image unique.

 

[karl.nyhus]

where multiple images are captured per second, but depend on something like yyyymmddhhmmss to keep the image unique.

But isn't that a good argument to keep the original file number suffix in your naming scheme?

 

[Gnits]

FastRaw Viewer has a very good file naming toolkit. Their filtering tools on the right hand banner are also decent, but sub optimal. A few small tweaks would make this filtering tool superb. The last time I was in contact with them they indicated not to expect improvements in this area any time soon. I have checked for updates a few times and hope they will tweak this area in due course.

A good advantage of FastRawViewer is that the apps run on Mac and Windows.

 

[Gnits]

But isn't that a good argument to keep the original file number suffix in your naming scheme?

I disagree.

I have been on large and unique trips with many very experienced photographers. At some time on such trips, at least one photographer will get their cards mixed up and will be unsure if the images have already been downloaded, are their cards safe to overwrite, has a photographer got some one else's card, etc. Real world scenarios happen all the time.... a photographer runs out of card space and borrows a card from another photographer while at the top of a mountain or deep into the jungle.

Having the ability to reconcile a card backed up to a hard drive to the original sd/cf card can be a life saver.

Again, for most people working as individuals this is unlikely, but I have seen it happen in the real world.

 

[karl.nyhus]

The last time I was in contact with them they indicated not to expect improvements in this area any time soon.

They are too busy trying to keep up with new raw formats and new cameras. I'm willing to bet LibRaw.org has only a tiny fraction of Adobe's resources and money.

 

[karl.nyhus]

I disagree.

I do not doubt or question your experience. It just is not applicable to an amateur photographer like me. I certainly never meant to recommend my workflow and naming practices to "very experienced photographers on large and unique trips." I was hoping some of the beginners on this forum might find value in alternative suggestions.

 

[Gnits]

They are too busy trying to keep up with new raw formats and new cameras. I'm willing to bet LibRaw.org has only a tiny fraction of Adobe's resources and money.

Understood. That is ok.... and their choice..... it means that the app I built to injest images from card to disk is still my preferred means to complete this task (as it is most efficient for me).

I do hope they will give some time to add a few simple tweaks which will make their app more attractive to a wider audience.

 

[Johan Elzenga]

That may work if you are not a high volume shooter (eg sports/ wildlife). The Dcim standard in use by camera companies means the camera will create multiple DCIM subfolders once the camera sequence number cycles past 999 (sometimes 9999). I have copied cards that had at least 3 dcim sub folders, which means 1000's of duplicate / triplicate images on the same card, but protected by been in different DCIM sub folders.

Correct. If you shoot more than 9999 images between two downloads, then you’ll have images with same number suffix. A real problem!
That is why I also use the capture date and time in the file name. None of my cameras can shoot at 9999 fps, so that solves it.

 

[Gnits]

I was hoping some of the beginners on this forum might find value in alternative suggestions.

And that is very valuable.....

My background is large scale enterprise technology... my instinct is to cover as many operational risks as possible.... so I am some time nervous of certain scenarios( because I see people caught so often with either the DCIM or using yyyymmddhhmmss gottchas).

 

[Johan Elzenga]

because I see people caught so often with either the DCIM or using yyyymmddhhmmss gottchas

That is why my advice is to combine both: YYYYMMDDHHMMSSOriginalFileNumberSuffix.

 

[John R Ellis]

I think that the out of sequence issue is caused by parallel importing of multiple images.

Yeah, the out-of-sequence numbering started when Adobe changed Import to import photos in parallel. It would have taken only 20 - 40 lines of code to maintain the original sequence numbering while importing in parallel, but Adobe didn't do it, despite many votes for the old feature request.

 

[Philippe Coudé du Foresto]

I do rename at import. This is important because I want to keep the link between the original and the file I've send to other (in case I'm requested to send it again or get a question about the image).
To garantee a unique file name, I use the following rule :
{Date (YYYY)}{Date (MM)}{Date (DD)}-{Import # (01)}{Sequence # (001)}
Since the import # is increased at each import, this avoid the risk of duplicates name. From time to time, I reset the import# in the preferences.

 

[Johan Elzenga]

To garantee a unique file name, I use the following rule :
{Date (YYYY)}{Date (MM)}{Date (DD)}-{Import # (01)}{Sequence # (001)}

I believe this whole thread started because the OP does something similar, but found out that this will not guarantee that your images will be renamed in the same order that they were shot…

 

[clee01l]

I believe this whole thread started because the OP does something similar, but found out that this will not guarantee that your images will be renamed in the same order that they were shot…

The LrC import process is multi threaded and several files will be in the import queue simultaneously. Instead of {Sequence # (001)}. Use {OriginalNumber Suffix} It will guarantee the file name to be as unique as the original files in the import.

 

[bobsomrak]

Rename after import and your import preset will work correctly. Just select previous import and then use rename.