Files
Miguel Angel Simon Sierra 6b51d1295e fix(engine): call out a mangled replacement character in ffmpeg path errors
A configured HYPERFRAMES_FFMPEG_PATH/FFPROBE_PATH override that fails the
existence check gives no clue when the real cause is an encoding mangling
issue rather than a typo or missing install: a non-ASCII character in the
original path (e.g. an umlaut in a WinGet Links path on Windows) can get
replaced with U+FFFD before the value reaches this process, so a perfectly
valid ffmpeg install looks "not found" with no actionable signal. The
error now detects a literal U+FFFD in the configured path and points
specifically at using an ASCII/short (8.3) path instead.
2026-07-02 17:23:26 -07:00
..
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-06-16 13:16:09 -04:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00
2026-07-01 14:57:39 -07:00