Skip to content

Free, open-source AI video generator for Mac. Run LTX-2.5 and MiniMax H3 (Hailuo) locally on Apple Silicon: text-to-video and image-to-video with sound, lip-sync, character LoRA training, songs from lyrics (YuE2) and image editing (Qwen-Image-Edit). One-click install via Pinokio. Offline: no cloud, no API key, no NVIDIA GPU.

3.2 KB
Raw Blame

Recovering an unfinished update

The studio and Pinokio Update share a local update record. Update fetches a candidate, keeps a Git reference to the previous source, moves to the candidate, and runs its dependency repair. It reports the update as prepared until that candidate starts and binds the studio listener. A restart request alone does not count as success.

If an update stops, use Try again in the existing update banner or run Update again in Pinokio. The same candidate resumes. A second request cannot replace a candidate awaiting repair or restart. After a successful boot, a new Update can fetch a newer candidate.

Local tracked edits, local commits and conflicting untracked or ignored files are kept. Save or commit edits before retrying. Divergent history now stops for manual reconciliation instead of resetting local commits. Update never runs git clean, stashes changes, or resets the source with --hard.

What the record preserves

The checkout's Git directory contains phosphene-update.json. Find that directory with git rev-parse --absolute-git-dir from the app folder. The record gives the phase, exact candidate SHA and previous_ref. The reference keeps the previous Git source reachable even if Git expires its reflog. This is source recovery, not a backup of installed Python packages.

A failed dependency command records its exit code and the exact retry command. It keeps the candidate in place so retry uses the same repair scripts. Completed repair is skipped on retry. If a process dies after a command finishes but before its completion is recorded, repair must run again. Package commands therefore need to tolerate retries. No exactly-once package installation is promised.

Do not restore source and assume the Python environment was restored with it. The old process can still be running while packages on disk have changed. An unfinished update blocks new queued renders and restart; repair must finish first. Models, outputs and settings are not transaction storage.

If Git itself was interrupted

Update refuses to reset a partial checkout or remove an index.lock for you. Keep the update record and edited files. Inspect git status and git diff from the app folder. The record's previous_ref identifies the complete previous source; git show <previous_ref>:<path> reads an original file without changing the checkout. You can export that source to a separate archive with git archive <previous_ref> --output=<new-archive-path>.

Resolve the Git interruption while preserving your edits, then retry Update. If source moved outside the recorded previous/candidate commits after replacement began, Update stops and names the retained reference. Do not remove the journal to bypass the check after dependency work has started.

Scope

This applies to the Git-based studio updater. The native Mac app's own updater is separate. Historical launchers execute their already-loaded update logic on the first update that brings in this change; that first hop does not acquire a transaction record retroactively. Linux still uses its separate install script. A successful startup receipt proves studio startup, not a render or a complete from-zero release validation.