Skip to content

Cutline v0.8.5 — Disk-backed Windows export

Choose a tag to compare

@ahpah-dev ahpah-dev released this 08 Oct 11:10

Cutline 0.8.5 — Disk-backed export

The biggest practical reliability gap identified in Cutline was output-size memory growth: the entire encoded video lived in RAM and was copied again through desktop IPC. This release adds automatic disk-backed export on Windows.

  • Pick the destination before rendering. Cancelling the save dialog starts no export.
  • MP4/H.264 and WebM/VP9/VP8 output writes in chunks of at most 1 MiB. Acknowledged disk writes apply backpressure to encoding; the finished file is not rebuilt in renderer memory or copied wholesale through IPC.
  • An exclusive temporary file is created beside the chosen destination. Native code validates session ownership, positions, chunk sizes and final file size. Encoding/frame validation and disk flush finish before an atomic same-directory rename replaces the approved destination.
  • Cancel and ordinary errors preserve existing videos and remove temporary output. Orderly shutdown waits for cleanup or an already-started final commit. Full/locked drives give actionable errors. The success view shows the saved location and size.
  • No extra runtime/model download, paid service or export watermark. Resolution, frame rate, effects and audio mixing are unchanged.

Verification: 93 unit/component checks, 15 font/Codex protocol checks, 6 native disk-writer checks and 90 render/export checks pass, plus the server-rendered shell (205 total). The production Windows UI, including the packaged app archive, streams exactly 960 frames at 60 fps with audio, starts disk writes before rendering finishes and limits chunks to 1 MiB. Destination cancellation, mid-export cancellation and simulated writer failure preserve the existing destination. Actual streamed files are decoded in all three formats under slow-writer backpressure. Tests cover seek-back header writes, cross-session rejection, final-size failure, shutdown races, full-drive errors and offsets beyond 4 GiB. The large-offset check is not a multi-gigabyte encoded video or a memory benchmark. Desktop/web builds, type checking and scoped lint pass; earlier live AI and Whisper checks were not repeated.

Limitations: browser downloads still assemble output in RAM; use the Windows app for disk-backed output. Decoded sources, codecs, surfaces and container metadata still need memory. MP4 is regular/seekable with metadata at the end, not Fast Start optimized for progressive web playback. Large projects still require adequate disk space and processing time; this does not provide proxy preview or repair choppy source footage. Forced termination/power loss may leave a .cutline-export-*.partial beside the destination; it is not published as a finished video. Final atomic commit cannot be cancelled. If temporary cleanup fails, the UI names the folder.

Windows x64 builds are unsigned and may trigger SmartScreen. Verify Setup/Portable downloads with SHA256SUMS.txt. Projects and original media are not changed by installing an update.