Workernode won’t retain file creation dates

[Rolf Howarth]

What the “set timestamp” option does is set the file modification timestamp of the generated file to the camera date-time information of the recording, if that information is available at the time of import (as it typically is for DV and MXF and DSLR movies, for example). I’m not sure if it uses the original file modification time if there’s no camera record date available but I agree that would be a useful feature, so we’ll make a note to investigate that.

[Bryson Jones]

Rolf,

Could you use DT1 as a variable to give him the original creation date as part of the name for the transcoded file?

I tried a quick test in Worker 3.1.0, but (DT1) and (MD2) both gave me the value for Source Date (SD2). I used the standard ${field ID} syntax.

Can you check that? If it works, he’d get a way to track his creation dates.

bryson

bryson “at” hidefcowboy.com

hidefcowboy.com

[Rolf Howarth]

You could use that for renaming the file according to the date, but not for setting the timestamp.

This will be fixed in Worker Node 4.0 so it uses the first available date when setting the timestamp.

[Jeff Schaap]

Hey Guys,

Thank you so much for you input into this issue. I ended up using a different program, A Better Finder Renamer, to rename all the files in chronological order with iterations… 0001, 0002, 0003, etc. Not the desired way of doing things but hey, sometimes you have to make due. The chronological order in which the files were shot is really the most important thing in this case, not the exact time and date. However, it would be a great feature and make life easier if Worker Node could retain the the camera’s timestap (probably not the right nomenclature) on the file. I realize that some footage formats have this metadata built in but some do not so if it could retain the file creation time and date as well that would be even better.

Thanks,
Jeff Schaap