Windows AME uses AMEEncodingLog.txt in the version directory.
macOS AME uses Adobe Media Encoder Log.txt in the logs subdirectory.
Updated readAMELogs() to check for both naming conventions:
1. First tries Windows filenames (AMEEncodingLog.txt)
2. Falls back to macOS filenames (Adobe Media Encoder Log.txt)
This allows the job manager to work with either platform.
Also updated docstring to document platform differences in both
log file locations and encoding (Windows uses UTF-16 LE, macOS uses UTF-8).
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Windows Adobe Media Encoder writes AMEEncodingLog.txt as UTF-16 LE with
BOM. The parser was reading files as UTF-8, producing garbled output where
every character had a null byte between it — causing all regex matching
to fail silently and return zero parsed entries.
Added readFileAutoEncoding() that detects UTF-16 LE/BE BOM and converts
to UTF-8 before parsing. Also handles BOM-less UTF-16 by checking for
null byte patterns.
Additionally improved parser to handle Windows AME log format:
- "File Encoded with warning" status lines (not just "Status: Done")
- "Queue Started/Stopped" lines are now skipped
- "Log File Created" header lines are skipped
- Separator lines (dashes) are skipped
- Offline media warnings and missing asset lines are captured
- "warning" status counts as success in stats
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
