aigen/docs/video-batch-continuation.md

Video batch continuation and HostBuffer failure

The September 9 investigation found two separate problems:

1. Automatic continuation defaulted off and its checkbox had moved inside Generation Settings. Paused batches hid their “Run remaining” controls. Resume reused the previous one-shot budget, so it paused again after the next shot. Resume also restored a live flag before the shot queue overwrote it with autoRun=false.
2. The local aigen-headless.log traceback reports comfy_aimdo/host_buffer.py → comfy/memory_management.py while the Qwen text encoder is loading weights. This is not FFmpeg frame extraction. Commits da8d0e4 and 4bf9922 change FFmpeg retries and do not address that model-loader failure.

New video batches now default to automatic continuation. Its checkbox stays outside the settings drawer. Paused batches show “Run remaining”; the bounded action says “Run only shot N”. Resume restores automatic continuation in both the Studio row and shot queue and passes the refreshed run-all policy to the dispatcher. Explicit one-shot / next-three actions remain bounded. Errors still stop the batch instead of silently skipping failed shots.

For the observed Windows HostBuffer failure, the connector now prepares Comfy's supported --disable-dynamic-vram launch flag when that installed version supports it. This selects estimate-based loading instead of AIMDO dynamic loading. It changes memory management, not the generation graph, handoff frame, refinement, model precision, or source segments. It may change loading speed and memory use; GPU inference has not been tested. COMFY_DYNAMIC_VRAM=true on the connector opts back into upstream defaults.

The memory change takes effect only after the connector is reloaded and Comfy is next started. Do not restart either during an active render. No running job or existing queue was changed during diagnosis. The checkbox default applies to new batches; use “Run remaining” on an existing paused batch after deploying the UI fix.