Hide new millisecond display in release 15.0?

[DaveMilton]

Lightroom Version Number

15.0

Operating System

1. Windows 11

I don't want to see the milliseconds on timestamps, they're just clutter for me. Is there an option to hide them?

 

[Paul McFarlane]

I assume you mean in the Metadata panel?

If you customize the display, and change from separate Date and Time to a combined one, it doesn't then include the milliseconds.

 

[John R Ellis]

If you want to disable fractional seconds in the capture time displayed on thumbnails in Grid view, there's no way to do it. Add your feedback to this thread in the Adobe forums:
https://community.adobe.com/t5/ligh...m-classic-display-of-millisconds/m-p/15573420

I expect that the moderator will move it to the forum's Ideas section soon, to make it easy for people to vote for it.

 

[John R Ellis]

I assume you mean in the Metadata panel? If you customize the display, and change from separate Date and Time to a combined one, it doesn't then include the milliseconds.

Do you mean "Capture Date/Time"? My LR 15.0 / Mac OS 26 / US shows milliseconds:

 

[Paul McFarlane]

Do you mean "Capture Date/Time"? My LR 15.0 / Mac OS 26 / US shows milliseconds:

I do and mine didn't - then I realized I'd checked it using a TIFF file (I know dumb!) - on a genuine raw/dng it's exactly as you mention, John!

 

[Gnits]

I have been conscious for years re sub second limitations within Exif timestamp fields and the need to store this in a separate field.

I am thrilled that milliseconds are now catered for within Lightroom …. but I do agree…it seems sensible to have an option to suppress their display.

I often wondered how many cameras record sub second times. And … I must check how plugins like ListView /Transporter and others now cater for this.

 

[John R Ellis]

I often wondered how many cameras record sub second times.

I just ran Excel on my test catalog containing raws from 22 makes and 313 models, going back over 15 years. Results:

• Brands whose models mostly have fractional seconds: Apple, Canon, Nikon, Panasonic
• Brands with recent models having fractional seconds: Sony, Fujifilm, Leica
• Brands with most models without fractional seconds: DJI, Hasselblad, Huawei, Olympus, Om Digital Solutions, Ricoh, Sigma

 

[Gnits]

Excellent. Well done.

Having the sub second data in the time stamp will improve ability to integrate to other apps, which can be used for all sorts of purposes. Your analysis is one example but I cam think of lots of others, especially with high frame rates

I was testing the settings of the A9iii in relation to precapture and was so swamped by the volume of data (ie number of images captured and proximity of each timeframe) that I gave up.

I can understand the need to fine tune how this data should be presented.

 

[clee01l]

Is there any other reason other than burst mode that you want or need sub seond Capture times? As cameras get the ability to shoot mre fps, sub second capture times to more decimal places becomes critical.

 

[DaveMilton]

I assume you mean in the Metadata panel?

If you customize the display, and change from separate Date and Time to a combined one, it doesn't then include the milliseconds.

No, not there, sorry I should have clarified before. I mean in the view options in Grid or Loupe view as here:

Capture Date/Time will always show mS if they are available. The extra info clutters up these views.
The same applies in Develop module too.

 

[Gnits]

I extracted the relevant metadata for a sample file using Exiftool.exe.

and the separate exif fields which record sub seconf time.

I hope to upgrade to V15 in the next week or so.

I have just double checked the plugs ListView and Lr/Transporter (using LrC 14.5.1)

Both export the time with no sub seconds info. And , so far, have not found a separate field.

So.. for people exporting metadata of images to integrate into other apps (or simply list images in date sequence) then not having the sub-second info makes it difficult to sort images in the original time sequence (for frame rates greater than 1 frame per second).


Some photographers use yymmddhhmmss variations in their filenames. Again .. if these photographers shoot faster than 1 frame per second then when they sequence images (by file name ) they will have incorrect sequences for batches of images within the same second interval.

I intend to test this more fully when I do upgrade to V15 (or 15.01).

 

[John R Ellis]

if these photographers shoot faster than 1 frame per second then when they sequence images (by file name ) they will have incorrect sequences for batches of images within the same second interval.

There's a popular feature request for file renaming templates to include fractional seconds:
https://community.adobe.com/t5/ligh...field-in-file-naming-templates/idi-p/12249692

An Adobe employee recently updated its status:

The MAX release for Adobe Photography products includes an update addressing the requested feature that addresses part of this feature request in selected fields. The team is working on the rest of it.

 

[Gnits]

All good. Ultimately reflecting the reality of modern camera capture frame rates.

I remember coding COBOL apps.. where every digit was significant (and the dismay of mainframe programmers with the arrival of such a wasteful concept of xmp and need to build gui apps in front of mainframe batch systems).

 

[camner]

I remember coding COBOL apps.. where every digit was significant (and the dismay of mainframe programmers with the arrival of such a wasteful concept of xmp and need to build gui apps in front of mainframe batch systems).

Isn’t putting a GUI in front of a COBOL backend pretty much putting lipstick on a pig anytime after about 2000?

 

[Gnits]

It was worse than that. Early days… allowed simple tasks such as basic master data maintenance … main batch jobs still ran in the background…and traditional mainframe system designers trying to cope with the emerging client server model.

 

[BobT]

Don't forget, you have the file numbering sequence to sort high burst images.

 

[Gnits]

People with high burst rates regularly use more than one DCIM subfolders per session, where the camera applied suffix number resets…

Also.. I am not 100% sure but LrC does not necessarily import in strict capture time sequence as multiple cores are running in parallel. (See **below.) So, I would check if using one of the native LrC filename template sequence numbers will be in capture time sequence.

Ultimately, best for LrC to fully support sub second capture time and provide options for users to determine if they wish to see or hide the sub second elements when displayed.

I also understand why there might be requests to support use of sub seconds in file naming templates… as a lot of people have built file naming schema based on hhmmss and have discovered this may not be sorting images now as they wish.

** Note. One of the reasons I built my own ingest app to copy cards to disk is I make sure all images are copied to disk in strict capture time sequence, working thru all the DCIM subfolders in correct camera suffix number sequence and allocating a unique sequence number to each image imported.