date_resolver: drop -fast2 so MP4 moov-at-end files resolve #82

cameron · 2026-05-07T16:42:04Z

cameron commented

2026-05-07 16:42:04 +00:00

For QuickTime/MP4 files whose moov atom sits at the end of the
file (non-faststart — common for Snapchat exports and any MP4
muxed without -movflags +faststart), -fast2 causes exiftool
to skip the trailer and return no CreateDate /
MediaCreateDate, dropping the resolver to the fs_time
fallback for files that actually have a real capture date.

Reported cases:
Snapchat-477624257.mp4
fs_time: 2026-05-04 (today, file was just modified)
real: QuickTime CreateDate 2018-09-02
action_compound_cc92e65b709d1deb895b4c2a9484fc6a.mp4
fs_time: 2026-05-04
real: MediaCreateDate 2018-03-01

The waterfall pre-filters to files kamadak-exif couldn't read, so
the JPEG fast-path is already covered without -fast2. Paying
full-scan cost on the residual is the right trade. The per-tick
drain re-resolves source = 'fs_time' rows, so existing rows
recover automatically on the next watcher tick after deploy — no
SQL migration needed.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

For QuickTime/MP4 files whose `moov` atom sits at the end of the file (non-faststart — common for Snapchat exports and any MP4 muxed without `-movflags +faststart`), `-fast2` causes exiftool to skip the trailer and return no `CreateDate` / `MediaCreateDate`, dropping the resolver to the `fs_time` fallback for files that actually have a real capture date. Reported cases: Snapchat-477624257.mp4 fs_time: 2026-05-04 (today, file was just modified) real: QuickTime CreateDate 2018-09-02 action_compound_cc92e65b709d1deb895b4c2a9484fc6a.mp4 fs_time: 2026-05-04 real: MediaCreateDate 2018-03-01 The waterfall pre-filters to files kamadak-exif couldn't read, so the JPEG fast-path is already covered without `-fast2`. Paying full-scan cost on the residual is the right trade. The per-tick drain re-resolves `source = 'fs_time'` rows, so existing rows recover automatically on the next watcher tick after deploy — no SQL migration needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

cameron added 1 commit 2026-05-07 16:42:05 +00:00

date_resolver: drop -fast2 so MP4 moov-at-end files resolve c128596470

For QuickTime/MP4 files whose `moov` atom sits at the end of the
file (non-faststart — common for Snapchat exports and any MP4
muxed without `-movflags +faststart`), `-fast2` causes exiftool
to skip the trailer and return no `CreateDate` /
`MediaCreateDate`, dropping the resolver to the `fs_time`
fallback for files that actually have a real capture date.

Reported cases:
  Snapchat-477624257.mp4
    fs_time: 2026-05-04 (today, file was just modified)
    real:    QuickTime CreateDate 2018-09-02
  action_compound_cc92e65b709d1deb895b4c2a9484fc6a.mp4
    fs_time: 2026-05-04
    real:    MediaCreateDate 2018-03-01

The waterfall pre-filters to files kamadak-exif couldn't read, so
the JPEG fast-path is already covered without `-fast2`. Paying
full-scan cost on the residual is the right trade. The per-tick
drain re-resolves `source = 'fs_time'` rows, so existing rows
recover automatically on the next watcher tick after deploy — no
SQL migration needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

cameron merged commit 22e157411c into master

2026-05-07 16:42:09 +00:00

cameron deleted branch fix/exiftool-mp4-moov-trailer

2026-05-07 16:42:09 +00:00

cameron referenced this issue from a commit

2026-05-07 16:42:11 +00:00

Merge pull request 'date_resolver: drop -fast2 so MP4 moov-at-end files resolve' (#82) from fix/exiftool-mp4-moov-trailer into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Apps/ImageApi#82