That way the subsecond timestamp is preserved and the process does not lose information. (For JPG, ~every camera saves timestamps in EXIF metadata as well, but filenames are ~100x faster to parse, and they are indexed by Everything app.) The datestamp is really nice to quickly get to in a file folder by typing it out (in Windows or most Linux GUIs or terminals).
The subsecond timestamp is ugly and TMI and I have thought about trimming it down to the second. I’ll have to query my ~10,000 JPEGs and see how often two photos happen in the same second. There’s a certain elegance to every timestamp being the same length, so I probably don’t want to trim some to the minute and others to the second.
The goal is not perfect disambiguation but creating high enough signal relative to the noise (800k files with “program” in the path is a lot of noise when I’m e.g. searching Everything).
For the photo case, I will run the rename program after the day ends. So I can take in a list of numerically sorted files (oldest to newest) and output filenames that retain that sorting (admit -> zinc). In cases where I know how many files are being renamed, I’ll check if there are <156, <278, or <2500 (BIP + SLIP) and choose the wordlist accordingly.
For my situation, cycling the wordlist (zinc -> back to admit) is not a problem after the day has rolled over. It’s slightly annoying if it happens in the span of 4 hours (>156 photos in the span of 4 hours). The root purpose is disambiguation. Photos not taken on the same day are very different, but in the same hour I might be in the same location.
The intended filename format is:
src: 20261019_12345678.jpg out: 20261019_zest_12345678.jpgThat way the subsecond timestamp is preserved and the process does not lose information. (For JPG, ~every camera saves timestamps in EXIF metadata as well, but filenames are ~100x faster to parse, and they are indexed by Everything app.) The datestamp is really nice to quickly get to in a file folder by typing it out (in Windows or most Linux GUIs or terminals).
The subsecond timestamp is ugly and TMI and I have thought about trimming it down to the second. I’ll have to query my ~10,000 JPEGs and see how often two photos happen in the same second. There’s a certain elegance to every timestamp being the same length, so I probably don’t want to trim some to the minute and others to the second.
The goal is not perfect disambiguation but creating high enough signal relative to the noise (800k files with “program” in the path is a lot of noise when I’m e.g. searching Everything).
For the photo case, I will run the rename program after the day ends. So I can take in a list of numerically sorted files (oldest to newest) and output filenames that retain that sorting (admit -> zinc). In cases where I know how many files are being renamed, I’ll check if there are <156, <278, or <2500 (BIP + SLIP) and choose the wordlist accordingly.
For my situation, cycling the wordlist (zinc -> back to admit) is not a problem after the day has rolled over. It’s slightly annoying if it happens in the span of 4 hours (>156 photos in the span of 4 hours). The root purpose is disambiguation. Photos not taken on the same day are very different, but in the same hour I might be in the same location.