Whilst ExifTool supports Reconyx's makernote users of Reconyx cameras currently have no way of populating the datetime of their images from metadata. Timelapse does not process this bit of metadata automatically for them and all common metadata fields are datetimes and therefore unusable as they do not map cleanly to Timelapse's Date or Time fields.
Preferred implementation of is to use Metadata Extractor 1.5, which dropped to nuget.org an hour or so ago and runs in app domain rather than requiring command line communication with an external process. This is coded in feature/images, including support for reading DateTime from metadata. This is a breaking change in that Metadata Extractor and ExifTool use different names for metadata fields but that is probably OK; Metadata Extractor conforms to the relevant standards whereas ExifTool tends to try to use friendly names and therefore refers to substantially different things by the same name or uses names which have little to do with the actual field name.
Cleanup of metadata dialog code needlessly duplicated between Timelapse and the editor would be nice, though, and some additional unit test coverage is desirable.
Whilst ExifTool supports Reconyx's makernote users of Reconyx cameras currently have no way of populating the datetime of their images from metadata. Timelapse does not process this bit of metadata automatically for them and all common metadata fields are datetimes and therefore unusable as they do not map cleanly to Timelapse's Date or Time fields.
Preferred implementation of is to use Metadata Extractor 1.5, which dropped to nuget.org an hour or so ago and runs in app domain rather than requiring command line communication with an external process. This is coded in feature/images, including support for reading DateTime from metadata. This is a breaking change in that Metadata Extractor and ExifTool use different names for metadata fields but that is probably OK; Metadata Extractor conforms to the relevant standards whereas ExifTool tends to try to use friendly names and therefore refers to substantially different things by the same name or uses names which have little to do with the actual field name.
Cleanup of metadata dialog code needlessly duplicated between Timelapse and the editor would be nice, though, and some additional unit test coverage is desirable.