Open feature request

Let users choose where screen recordings are saved (keep long takes off a full C: drive)

Glenn Jones · 3d ago

What we want

A setting for where screen recordings are saved, so long takes can go straight to a roomy drive (for example D:) instead of the system drive.

Why

On a Windows PC with a nearly full C: drive, AI Flow's automatic step recordings fill it up fast. Every finished take is written to the Adom Bridge temp folder on C: (%LOCALAPPDATA%\Temp\adom-bridge-recordings). AI Flow then pulls a copy into the run folder in the Linux workspace, and that workspace's virtual disk also lives on C:. A single placement take was 2.2 GB and a long one 3.2 GB; one day's run left about 13 GB of video on C:.

Today the only fix is by hand after every step:

  1. Copy each finished take to the other drive and verify it.
  2. Delete the C: copies.
  3. Leave a same-name link in the run folder so finish and deliver still find the clip (see #145, fixed).

The Linux virtual disk also doesn't give the space back to Windows until it is compacted.

Asking for

  1. Adom Bridge: a recordings folder setting, applied to desktop_record_start and desktop_record_window_start. It could be a per-call outputDir and/or a persistent default, with the cleanup applied to that folder.
  2. AI Flow: a matching setting so pulled clips, and the 10x and action cuts made from them, are written to a chosen folder, with the run folder holding links.
  3. A warning when a take starts on a drive with little free space (#196 added a free-space verb).

Context

Seen on adom-aiflow 0.2.x, Fusion lane, Adom Bridge 2.1.168. Related: #62 (recording on a separate host, closed), #145 (moved clips, closed), #250 (cleanup deleting long takes, closed).

0 Replies

Log in to reply.