Troubleshooting

When the engine process exits on its own, a red banner appears at the top of the window: The engine stopped unexpectedly, with the exit code or signal and whether a job was running. Show log reveals the engine log file, Restart engine starts it again in place, and Dismiss hides the banner; the last engine log lines are folded underneath for a quick look at the cause. The app recovers on its own where it can: for disk-backed Regenerate jobs a second banner appears (Recovering Regenerate job after engine crash…) while the engine restarts and the job resumes from its checkpoint. A job that was not resumable is marked failed; run it again after the restart. Repeated crashes on the same clip usually mean memory pressure; see below.

The engine validates the license on startup and shuts down if validation fails. Click the license pill for the reason. Fixes, in order: Refresh License from the pill; re-activate from Settings → License Management → Generate License; and if you see a maximum active licenses error, revoke an unused device on your account page and try again.

Failed jobs stay in the Activity pipeline card with the engine's own error text, so the reason is visible without opening the log. A failure right after submit is usually a missing engine: the pipeline needs a model family you have not built, and the error names it, for example No Refocus engine is installed. Build one in the Model Library first. Build the engine, or switch the preset to one that matches what you have installed. If the reason reads The engine lost track of this job (it may have restarted). The output was not confirmed., the engine restarted or crashed mid-job and the app refused to assume the output is complete; check for a crash banner, then run the job again.

Activity flags a running job when its progress has not moved for 5 minutes, or for 15 minutes while it is still at 0% (loading large engines takes time before the first frame). It is a hint, not a verdict: the card's status line says how long it has been quiet. Look at the GPU and memory gauges; if they sit idle and nothing changes for several more minutes, cancel the job, check the engine log, and resubmit. Very large Regenerate-Q tiles can legitimately pause for a while between progress updates.

Expected on Apple Silicon: the UI and inference share the GPU. Enable Settings → Application → Minimize while upscaling or use the compact-view button in the top bar.

Regenerate passes hold significant state per tile, and high-resolution depth generation uses a lot of memory. Close other GPU-heavy apps; prefer Regenerate-Q over Regenerate for long or large clips; keep disk-backed state on; and for depth maps use Preview (fast) or a smaller model size unless you need full resolution.

The Model Library needs your software key to reach the weight catalog. If it reports a catalog error, re-save the key under Settings → License Management, then click the refresh icon on the family page. Interrupted downloads are safe to retry.

The free tier watermarks output. After you purchase or redeem a code, the app picks up the new license automatically (or via Refresh License) and subsequent jobs render without the watermark.

Open Settings → Third Party Libraries → MPV Player and switch the video output to Software (Recommended for macOS). Preview settings never affect the rendered output.