Adom Bridge
Public Made by Adomby adom
Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl
desktop_record_start encoder_busy for minutes after a stop, even with gpu:false
ab 2.1.184 on Windows (4K, NVIDIA), 2026-10-19 01:38–01:41Z.
After stopping a monitor take (desktop_record_stop, which answered finalising) and an earlier take that had hit maxDurationMs, every new desktop_record_start {"monitor":0,...} failed for about 4 minutes:
errorCode: encoder_busy"The GPU video encoder did not start within 8 s…"- retried with
gpu:false:encoder_busy"The video encoder did not start within 8 s. Retry in a moment; if it persists, restart Adom Bridge." - one start call hung past the 60 s client timeout.
No other recorder was running (desktop_record_status listed only finalised takes). A few minutes later a start through Hydrogen's /recording/native/start (ab-backed) worked. Separately, two takes were left in state recording after their callers died (one stopped writing to disk 20 min earlier).
Asks: the software encoder should never be "busy" because of the GPU one; report which take holds the encoder in the error; and a take whose file has stopped growing should not stay recording. Related: #232, #230.
0 Replies
Log in to reply.