Damselfly not reading correct taken date from image about damselfly HOT 10 CLOSED

The metadata scanning is probably picking up the date from the wrong field when parsing a DNG. I'll have a look. Damselfly falls back to the last-mod date if it can't find a capture date, so I probably just need to fix that.
Any chance you could email me the image, so I can test? ([email protected]). Thanks!

from damselfly.

Thanks! I've pushed a fix - if you want to give it a try, you can pull webreaper/damselfly:dev.

Be aware that there's a few other enhancements that are mid-development in there, but nothing that would put your pics at risk.

from damselfly.

Pushing a patch release with this as 4.0.8.

from damselfly.

I just upgraded my 'prod' install to 4.0.8 and the test image you sent me has indexed fine with the correct date.

from damselfly.

Will do when I'm back at my Mac. I noted that ExifTool doesn't do the reading of data and didn't see DNG support explicitly from the other library.

from damselfly.

Image sent - 20MB (small by modern standards!)

from damselfly.

Was just pulling dev and saw the 4.0.8 image arrive. Thanks!

from damselfly.

Brief and early update - Damselfly appears to not be reading any DNG images now, but I'm going to let it sit overnight and have a think.

from damselfly.

Oh, that's not good. Give it time to fully index and touch a couple to ensure it rescans the metadata. Let me know!

from damselfly.

Something has gone awry, but I don't know what, so I'm going to stop the container, move or delete the existing docker volume contents and restart the container, reset the system and see what it does about the reindexing. Also going to check out all the env variables available in case I want to tweak the config this time.

from damselfly.