mirror of
https://github.com/storytold/filmcraft.git
synced 2026-11-07 18:02:52 +00:00
Jonathan Cardoso
96d8e22c2d
* fix(export): an image-sequence export reports the stills it wrote An export to `a.png` as an image sequence writes `a000.png`, `a001.png` and so on, but the job's result, `file.exportMedia`'s `path` and the CLI's "exported" line all named `a.png`, which does not exist. The report now names the first still, the name `file.import` and `probe --image-sequence` take for a sequence. `file.exportMedia` and `export.quick` name it as `path` up front, from the frame count `export.resolve` uses, and add `lastPath`. The CLI prints both. A single file keeps its path. Fixes #4009 * fix(automation): a cancelled image-sequence export is cleaned up by its stills' name Since `file.exportMedia` names an image sequence's first still as `path`, the MCP cancel clean-up took `a000` as the stem: it left `a001.png` and every later still, and the `a.srt` sidecar, behind. The result now also carries `basePath`, the name the stills are numbered from, and the clean-up goes by it. * fix(automation): an image-sequence cancel clean-up keeps the base name and finds .jpeg stills An image-sequence export numbers every still, a single frame included, so a file under its base name (`a.png`) is never its own: cancelling one deleted a user's `a.png` if it was saved during the export. The stills of a `.jpeg` sequence were left behind instead, since the extension was read as a format name, and `jpeg` names Motion-JPEG there; `file.exportMedia` keeps `.jpeg` for a JPEG sequence. * fix(automation): a cancelled image sequence removes only the stills it numbered The clean-up matched any `<stem><3+ digits>.<ext>` written during the export, so cancelling an export to `a.jpeg` could delete `a1000.jpeg`, the first still of an export to `a1.jpeg` in the same folder. It now takes the digits and the last index from the result's `lastPath` and removes only those names: `a000.jpeg` to `a120.jpeg` for a 121-frame export.