What's New
Persistent conversion log (#19)
New optional CONVERSION_LOG_PATH environment variable. When set (e.g. /data/conversions.log, requires a volume mount), every completed conversion appends one JSON line with everything for that title in one place:
{"title":"My Audiobook","itemId":"li_abc123","startedAt":"2026-07-13T10:20:00.000Z","finishedAt":"2026-07-13T11:20:00.000Z","requestedBitrate":"64k","before":{"fileCount":12,"path":"/audiobooks/Author/My Audiobook","codec":"mp3","bitrate":"128k","channels":2},"after":{"fileCount":1,"path":"/audiobooks/Author/My Audiobook/My Audiobook.m4b","codec":"aac","bitrate":"64k","channels":2}}- Logs file path, codec, bitrate and channels before and after each conversion
- For multi-file sources,
before.pathis the containing folder andbefore.bitratethe highest bitrate among the source files - A completion summary is now also written to the container log regardless of whether
CONVERSION_LOG_PATHis set:
Conversion completed: My Audiobook (12 file(s), mp3 @ 128k -> aac @ 64k) - Failed conversions are handled by the existing failure tracking and do not produce log entries
- Completion is detected on the next cron cycle after the encode task finishes; tracking is in-memory, so conversions running during an app restart will be missing from the log
See the README for setup details.
Full Changelog: v1.5.0...v1.6.0