timesortlong behavior

[wdp]

What is the default behavior of {timesortlong} / {tmsl}, I couldn't find any documented output from it in terms of renaming files.

[wdp]

I guess I should clarify. Is it a 24 hour clock? Are there dashes? How is it formatted? Does it carry sub seconds? Do all cameras support subseconds?

[Kirk Baker]

I guess I should clarify. Is it a 24 hour clock? Are there dashes? How is it formatted? Does it carry sub seconds? Do all cameras support subseconds?

Zero-padded two digit hour (24), followed by zero-padded two digit minute, followed by zero-padded two digit seconds, and if the camera has recorded subseconds, followed by 00-99 subseconds.

Not all cameras support subseconds.

-Kirk

[wdp]

Thanks Kirk!

I generally just do a full date scaffold based on readability for me, but I never got around to experimenting with some of the variable options.

Code: [Select]

.
└── 2022
   └── 01-Jan
      └── 220123

And then just long datestamp my filenames with a sequence variable.

22012213595999_001.RAW

I'm always torn if I want to include variables for which camera it was shot on.  I rarely use 2 cameras on the same shoot though. Sometimes I get stuck trying to presolve a problem that doesn't exist yet.

Today I was thinking about automation and since YYYY-MM-DD is the standard for ISO date formats, and then I was like, shit, would just doing an ISO 8601 type datestamp for the filename make life easier at any stage with scripts.