towsty/aigen
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Clarify output image actions and preserve user VRAM policy

Browse Source
This commit is contained in:
Towsty
2026-09-09 16:38:48 -05:00
parent 6fb87273d7
commit 9b1d8ae798
4 changed files with 97 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/video-batch-continuation.md
+2 -2
View File
@@ -7,6 +7,6 @@ The September 9 investigation found two separate problems:
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 attempted HostBuffer workaround in `badf59d` forced `--disable-dynamic-vram`. The user subsequently reported VRAM allocation failures and a large video slowdown. Their correction in `6fb8727` restores a pass-through memory policy: launch flags are left exactly as the user configured them. The connector must not automatically disable dynamic VRAM, pinned memory, asynchronous offload, or change precision as a retry strategy. The original intermittent HostBuffer fault remains separate from the batch-continuation fix.
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.
A policy change takes effect only after the connector is reloaded and Comfy is next started. A Coolify deployment or replacing the module on disk does not update an existing Node import or Python process. Do not restart either during an active render. The checkbox default applies to new batches; use “Run remaining” on an existing paused batch after deploying the UI fix.