What happens if Verismo closes before a recording finishes?

The project bundle already exists on disk. At the next launch Verismo scans unfinished projects, reads the playable fragmented video when available, restores the real duration, and leaves anything that still needs review visible in Library.

What if a microphone is disconnected during recording?

Verismo attempts to route to the current default input, pads the gap to preserve timeline alignment, and marks the lane degraded if recovery cannot complete. A degraded optional track does not masquerade as a successful audio capture.

Does Verismo guarantee that macOS hardware and media frameworks never fail?

No software can honestly guarantee that. Verismo promises inspectable state, explicit failure, recovery paths, validation before success, and complete-then-commit export behavior.

← Verismo

Boring reliability · Verismo 1.15

Record works. Export finishes. File lands.

Q: Can a failed export replace my existing file?

No. Verismo renders to a hidden temporary file in the destination folder. It replaces or moves to the chosen filename only after the media writer finishes successfully; cancellation and failure remove the temporary file.

A screen recorder earns trust between the red button and the file in Finder. Verismo makes that path inspectable: persist early, finalize once, recover visibly, validate before success, and commit only a complete export.

Inspect the contract Run the checks ↓

01Project exists firstvideo.mov · system.m4a · cursor.binwriting
02Interruption stays visibleLibrary · Needs Attention · recovery.jsonrecoverable
03Complete, then commit.verismo-export-* → walkthrough.mp4landed

No silent disappearance.The project, the failure, and the destination all have an inspectable state.

CAPTUREProject bundle created before recording

RECOVERYUnfinished work remains visible in Library

EXPORTDestination changes only after completion

The contract

Five checkpoints, not one hopeful progress bar

Each checkpoint has a stored artifact, a validation rule, or an explicit state the app and user can inspect.

Persist before capture

Verismo creates the .osmoproj folder and atomically writes placeholder edit metadata before recorders begin. Video, microphone, system audio, webcam, and cursor data then stream into that project.

RecordingBundle.createNew()

Finalize exactly once

Stop, repeated stop requests, app termination, and discard share one in-flight finalization task. Capture resources finish before Verismo announces success.

finalizationTask

Validate the actual media

A recording is not ready because a button was clicked. Verismo checks frames, duration, readable file size, and a real video track before clearing recovery state.

validateFinalRecording()

Recover into view

On launch, Verismo scans unfinished projects. A playable fragmented video can restore missing duration; unresolved work remains in Library under Needs Attention instead of disappearing.

CrashRecovery.sweep()

Complete, then commit

Export renders to a hidden temporary file in the chosen folder. Only a successful writer finish can replace the destination. Failure and cancellation clean up the temporary file.

.verismo-export-*

Recovery, made visible

The red button is not the only state that matters

00:00

Recording

Files stream into a real project bundle on your selected recordings drive.

STOP

Finalizing

Every active lane is stopped and flushed; the primary video is validated before ready state.

REOPEN

Needs Attention

If finalization was interrupted, Library shows the project and its recovery reason.

100%

Landed

A completed temporary export moves into the filename you chose; only then does progress become 100%.

Why this is a product feature

A beautiful recording that cannot ship is not finished.

Export and audio failures are category-level risks, not a reason for cheap shots. Screen Studio’s own changelog has documented fixes for exports stuck at 95%, audio errors during export, shorter exports with audio, and continued reliability work. Verismo’s answer is an inspectable completion path.

Read Screen Studio’s official changelog ↗

Reliability is not “nothing went wrong on our demo Mac.” It is what the product does next when a framework, device, disk, or process does go wrong.
The boring part is the feature.

Verify the promise

The behavior is the receipt

You do not have to trust a diagram. Use a disposable take and check each artifact on your own Mac.

01 · CAPTURESee the project while REC is liveStart a disposable take, open the recordings folder, and inspect its .osmoproj bundle before stopping.edit.json · video.mov · cursor.bin

02 · RECOVERYSee interrupted work returnWith a disposable take, interrupt the app, reopen it, and check Library → Needs Attention when automatic recovery cannot clear the state.recovery.json

03 · CANCELSee the old destination surviveExport toward a copy of an existing file, cancel before completion, and verify that the existing destination remains unchanged..verismo-export-*

04 · COMPLETESee the final file landFinish the same export. The chosen filename changes only after completion and progress reaches 100%.walkthrough.mp4

Implementation map for 1.15: RecordingBundle.createNew() · finalizationTask · CrashRecovery.sweep() · ExportPipeline.run()

The honest guarantee

No recorder can promise that macOS, storage, cameras, microphones, or media frameworks never fail. Verismo promises that success is validated, failure is explicit, interrupted work has a recovery route, and an incomplete export does not replace your destination file.

FAQ

What happens when something goes wrong?

What if the app closes before a recording finishes?

The project bundle already exists. On the next launch, Verismo scans unfinished projects, restores duration from a playable fragmented video when possible, and keeps anything unresolved visible in Library.

Can a failed export replace my existing file?

No. The destination changes only after the temporary export completes. Cancellation or failure removes the temporary file and leaves the previous destination untouched.

What if my microphone disconnects?

Verismo attempts to recover onto the current default input and pads the gap to preserve alignment. If that cannot succeed, the optional microphone lane is marked degraded instead of being presented as a healthy recording.

Where can I see work that needs recovery?

Open Library → Needs Attention. Recoverable or unreadable projects remain discoverable with explicit state instead of vanishing from the normal workflow.