Lightroom 6.5: File renaming with hour uses am/pm format

  • 2
  • Problem
  • Updated 2 years ago
  • (Edited)
When exporting I have a file renaming template which uses YYYYMMDD~HHMMSS. Before the 2015.5 update this would name my file as 20150323~190745.jpg now it is naming the file as 20150323~7 pm0745.jpg which is not what I want. The Hour element is being used differently and there is no option to change this to only use the 24hour number. My Mac uses, and has always used 12hr time notation.
Photo of Paul Thompson

Paul Thompson

  • 15 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 2
Photo of John R. Ellis

John R. Ellis, Champion

  • 3589 Posts
  • 928 Reply Likes
I'm not able to reproduce that on my LR CC 2015.5 on either OS X 10.11.2 or Windows 10.  This renaming preset works as expected:



This suggests there is something particular to your configuration.  Unless Adobe can reproduce it, it is unlikely to be fixed. 

Which version of OS X, which country is your computer located in, and which language is LR set for?
Photo of Paul Thompson

Paul Thompson

  • 15 Posts
  • 0 Reply Likes
So this is is views of the file name template and two folders on my mac on 20th and 25th March so you can see the difference. I'm running the latest Lightroom on El Capitan 10.11.4 with all language, location and keyboard settings for UK. I've noticed that if I change the Mac to use 24hr time the files look as they should. I've been using Lightroom on my Mac for 4 years without this issue and I'd like it to do what it used to despite my Mac settings.




Photo of John R. Ellis

John R. Ellis, Champion

  • 3589 Posts
  • 928 Reply Likes
The problem also occurs for me on CC 2015.5 / OS X 10.11.4 when I change System Preferences > Language & Region > Region to United Kingdom and uncheck 24-Hour Time.
Photo of Paul Thompson

Paul Thompson

  • 15 Posts
  • 0 Reply Likes
Thanks for confirming that John. It seems to be a combination of CC 2015.5 and OS X 10.11.4 for UK users. Lot's more people are going to start having the issue. I don't know if it's Adobe or Apple but I hope it gets fixed