Lightroom: Mixes up the order of the images shot with high-speed consecutive shooting (using an OM-D E-M1 Mark II)

  • 1
  • Question
  • Updated 2 years ago
  • (Edited)

This conversation has been merged. Please reference the main conversation: Lightroom: Sort by capture time should use filename when times are equal

When I tried importing images shot with high-speed consecutive shooting, Lightroom CC mixed up the order of the images. Suppose the actual order of images is 1, 2, 3, ..., 10. Lightroom numbers these images, for example, in the following order: 3, 2, 1, 6, 5, 4, 10, 9, 8, 7. More specifically, I shot images of a person running (forward). If you slideshow the images in the order sequenced by Lightroom, the person will look as if she is running backward, and then suddenly leaps forward and starts running backward again.

I used an Olympus OM-D E-M1 Mark II to shoot these images. I wonder if this problem is specific to this model of camera or happens with other cameras as well.

How can I avoid this problem?
Photo of brazil


  • 3 Posts
  • 0 Reply Likes
  • confused and a little frustrated.

Posted 2 years ago

  • 1
Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 420 Posts
  • 147 Reply Likes
Thanks for reporting. We are investigating a similar issue.
Are you renaming the files while importing? 
Could you please provide us with those images? I have sent you a personal email.

Photo of brazil


  • 3 Posts
  • 0 Reply Likes
Yes. I change the names of image files using the following format: <Date>_<Custom String>_<Sequential Number>.
Photo of Shane Betts

Shane Betts

  • 161 Posts
  • 54 Reply Likes
Are you sure this isn't the old trick of LR resetting sort order by Added Order rather than Capture Time? In Library mode, go to View>Sort>Capture Time.
Photo of brazil


  • 3 Posts
  • 0 Reply Likes
Thank you for the reply. I checked the sort option and found that "Capture Time" was checked all right. Not sure, but I wonder if those files numbered in reverse order by Lightroom sharing the same capture time might have caused the problem. Apparently the forward leap occurs every time one second passes.
Photo of Alastair Monk

Alastair Monk

  • 7 Posts
  • 2 Reply Likes
Perhaps the time differential isn't fine enough (all 3 images appear to share precisely the same timestamp?) - perhaps manually edit the final "seconds fragment" so that they are separated?

This conversation is no longer open for comments or replies.