interpretation of filename in automated versioning

Post Reply
peter wijn
Posts: 45
Joined: 24 Oct 11 19:55

interpretation of filename in automated versioning

Post by peter wijn » 22 Feb 18 17:42

Hi there,

The one type of work I would like to automate faultless, is versioning. In principple it should be simple on my photo's, since I want only two entrances in a set of versions:

1) the original NEF or TIF, and 2) an associated 100% RGB jpeg ready for viewing.

The file is named PW <YYYYMMDD_UUMMSS*>
The * giving an added 2 digit index _01 (time-based), only when more shots were made per second.

The Nef would be edited in
* Capture NX2 (only one NEF file, no versioning)
* In Lightroom (NEF and JPEG extension filename_LR5)
* in CaptureOnePro (NEF and JPEG extension filename_COP).

Automatic versioning ( filename*.* ) works great unto the point were multiple shots were made in one second.
The automatic versioning is not starting it at the _COP point, but one stage earlier at the 2 digit index putting all sequential shots from within a second (like a flying bird) in one version. (This will imply a lot of manual work when I eventually will get to visit a garbage dump in Arabia again: Eagles flying around every where.)

Question:
Is there a possibility to steer versioning that it understands where to start looking?

(I guess this software is so flexible one could make his own versioning script... , Well I have no idea how and where to start to do that.)

Well,
thanks for reading

sanphotgn
Posts: 428
Joined: 26 Aug 07 18:06

Re: interpretation of filename in automated versioning

Post by sanphotgn » 22 Feb 18 21:55

I use this:

Code: Select all

%yyyy%mm%dd%hh%nn%ss%zzz.%FileExtension
Photo Supreme 3.3.0.2602 (64 bits) (Windows)

peter wijn
Posts: 45
Joined: 24 Oct 11 19:55

Re: interpretation of filename in automated versioning

Post by peter wijn » 23 Feb 18 13:56

thanks,
Do you use this in the rename protocol in PSu?
What does zzz mean? at which point does it start?
I would wish the counter to restart at each second. Like a sequence would be

20180223_135000_001
xx _135000_002

xx _135001_001

xx _135003_001
xx _135003_002
xx _135003_003

Are you sure the version doesn't take all photos 001, 002 and 003 from 135003 in one version? That's what's happening now.

(Probably camera's like D5 and 1Dx and the new Sony record time in 100" of seconds: 00,00 to 59,00. If these extra digits could be read, instead of truncated, all would be good)

sanphotgn
Posts: 428
Joined: 26 Aug 07 18:06

Re: interpretation of filename in automated versioning

Post by sanphotgn » 23 Feb 18 19:13

I use during import to rename files. I typically have some stuff before date-time info.

zzz = Milliseconds.

My two Nikons reliably write milliseconds.

Here is a sample of the file names:

Code: Select all

20161001170227620.NEF
20161001170228110.NEF
20161001170229530.NEF
20161001170229690.NEF
20161001170229860.NEF
20161001170230500.NEF
Each file name was made into a version with its corresponding JPG.
Photo Supreme 3.3.0.2602 (64 bits) (Windows)

peter wijn
Posts: 45
Joined: 24 Oct 11 19:55

Re: interpretation of filename in automated versioning

Post by peter wijn » 26 Feb 18 18:45

great, that's what I was looking for.

Now how...

Ha, I did it myself. Dead easy. I feel much less as a dump user now, just a simple fool :).
Thanks, sanphotgn.

Post Reply