For ComfyUI’s Wan Context Windows (Manual) node, choose context_length in real frames using the required 4*n + 1 pattern, then enter context_overlap as a real-frame count. Keep both input values separate from their internal processing values: the node converts window length and overlap independently. The resulting internal counts do not, by themselves, tell you how many output frames a workflow will generate.
Choose values in order
- Confirm the node’s actual type label is Wan Context Windows (Manual). Interface colors are only a clue; use the label, because these rules apply to this specific node.
- Check the requested output
lengthin the surrounding workflow. It describes the generation request, not the context window. Do not substitute latent-frame counts for real-frame inputs. - Pick a
context_lengththat meets 4*n + 1. For example, 81 is valid; 80 is not. The documented input range is 1–16384, with a step of 4, and the default is 81. - Set
context_overlapin real frames. The documented default is 30; the input has no stated upper bound in the node table. Choose it in relation to the selected window and requested generation, then inspect the node’s reported values or workflow behavior where available. The documentation does not prescribe a universal best overlap. - Record each input and its corresponding internal conversion before judging coverage. This helps catch the common mistake of reading a displayed internal count as if it were the real-frame value you entered.
The node input reference defines the valid length pattern and real-frame inputs. Its processing note says the internal window length is ((length - 1) / 4) + 1, while overlap is divided by 4; the node also clamps converted values to minimum valid values. These are separate conversions, not a formula for output length.
Hypothetical 81-frame worksheet
Assume a creator requests an output length of 81 frames. The rows below are arithmetic illustrations of the documented conversions, not a prediction of window placement, frame count in a rendered file, or a tested result. “Coverage” here compares the requested output span with one window’s nominal real-frame length only; the documentation does not define a complete window-count or endpoint-coverage algorithm.
| Candidate context_length (real frames) | context_overlap input (real frames) | Internal length | Internal overlap | Hypothetical observation and decision |
|---|---|---|---|---|
| 81 | 30 | 21 | 7.5 before any minimum clamp | One nominal window matches the requested span; this does not establish how the scheduler partitions it. |
| 41 | 20 | 11 | 5 | A single nominal window is shorter than 81; check the actual schedule rather than assuming the number or exact placement of windows. |
| 80 | 20 | Not a valid input | 5 | Reject the length before interpreting any internal value: it fails the 4*n + 1 constraint. |
The arithmetic follows the processing note in the official node documentation. For odd overlap inputs such as 30, division by four yields a fractional arithmetic result; the documentation does not specify an additional rounding rule, so do not invent one.
Limits and next steps
If a candidate length is rejected, adjust context_length by steps of four until it satisfies the required pattern. If overlap appears inconsistent with the value entered, compare the real-frame input with the documented divide-by-four conversion and account for the stated minimum clamp. Do not “correct” the output length to compensate for context conversion: they are different settings serving different roles.
This node configures context windows during sampling and returns a model with that configuration applied. It also exposes scheduling, stride, loop, and fusion controls, but their names do not imply a guaranteed coverage or quality result. The documentation does not specify exact window start positions, final-window handling, or a universal overlap recommendation. If coverage matters, inspect the actual workflow’s available window information and compare it with the requested output; if that information is unavailable, report the uncertainty rather than inferring a precise partition. These are ComfyUI node instructions, not a claim that Imagild provides this node or interface.
Common questions
Is `length` the same as `context_length`? No. `length` is the requested output setting in the workflow; `context_length` is the real-frame size of a processing window.
Can I enter an overlap of 30 for an 81-frame context? Yes, 30 is the documented default and is expressed in real frames. Its internal arithmetic conversion is separate; the docs do not give a universal recommended ratio.
Does an 81-frame context guarantee one 81-frame output window? No. It describes a window size, not a guarantee about output generation or the scheduler’s partitioning. Check the workflow’s actual behavior.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.