builders · review · first seen Nov 4, 10:33 UTC
ComfyUI adds MiniMax-H3 support and video saving options
ComfyUI 0.44.0 shipped ProRes video saving and different chroma subsampling options for video saving. Builders with a video handoff can now test whether those output choices meet their requirements.
In short
- ComfyUI 0.44.0 shipped ProRes video saving.
- ComfyUI 0.44.0 shipped different chroma subsampling options for video saving.
- Check the saved files before changing a production handoff.
What shipped
ComfyUI 0.44.0 shipped support for saving video as ProRes. That is an output capability, not a claim about how video is generated or edited before export. For a builder, the relevant change is at the point where a workflow produces a video file. The claim does not describe which saving control exposes ProRes, which variants are available, or how an existing workflow selects it. I would inspect those details in the installed release rather than assume them from the format name. [1]
The release also shipped different chroma subsampling options for video saving. The claim confirms that choices exist, but it does not name them, identify a default, or say which video formats accept each choice. I would find the available settings in the video-saving interface and record the selection used for each test output. That gives a builder a comparison they can repeat without inventing option names or assuming that every setting works with every format. [1]
These are two shipped saving capabilities. They do not establish that an existing workflow will produce a different file without someone changing its settings. They also do not establish that ProRes can be paired with every chroma subsampling choice. The supported reading is narrower: ComfyUI 0.44.0 offers both capabilities for video saving. I would keep the format decision and the subsampling decision separate until the installed interface shows how they work together. [1][2]
Why it matters if you build
If a workflow's handoff depends on its saved video file, the save step is where this release may matter. I would test ProRes using the workflow I intend to keep, then inspect the resulting file against the handoff requirement. Support for saving ProRes does not tell us whether a downstream tool accepts that file, how much storage it uses, or how long saving takes. Those can be costs of a decision to adopt it, but the supplied claim gives no measurements. The builder has to check them in the workflow that will actually be used. [1]
Chroma subsampling is another output choice to make deliberately if a team needs repeatable video files. The shipped claim is about available settings, not a promised improvement in appearance or size. I would compare files saved with the choices the release exposes and review them where the files will be used. No supplied result quantifies a quality difference, file-size difference, or processing cost between choices. Without that evidence, I would not label one setting the best choice for every workflow. [1]
This points to a bounded test rather than a broad workflow change. Keep the rest of a video workflow fixed, inspect its saving settings, and test the files against the intended handoff. If the needed combination is not exposed, the two claims do not provide an alternative procedure. Likewise, the existence of new saving choices is not evidence that a production output should change immediately. Confirm the selection and examine the saved result before making that decision. [1][2]
How to try it today
- Open a video-saving workflow in ComfyUI 0.44.0 and locate its output settings.
- Check how that workflow exposes ProRes saving; do not assume a particular control or variant.
- Find the available chroma subsampling choices and note the current selection.
- Save a test video as ProRes if the workflow exposes that choice, and record the settings used.
- Save comparable outputs with the exposed subsampling choices, then inspect the files for your handoff.
What we checked
Every claim below was walked down the source ladder. The rung is how close the source is to the thing itself; the tense is the source's own.
-
shipped L0 · primary
ComfyUI 0.44.0 supports ProRes video saving.
per GitHub releases · comfyanonymous/ComfyUI (L0) -
shipped L0 · primary
ComfyUI 0.44.0 supports different chroma subsampling options for video saving.
per GitHub releases · comfyanonymous/ComfyUI (L0)
What is not confirmed
The supplied claims do not identify ProRes variants, named chroma subsampling choices, defaults, compatible combinations, saving controls, file sizes, save times, or downstream compatibility. They do not provide a visual comparison of saved outputs. I would not turn any of those unknowns into a release promise. The claims establish that the capabilities shipped; they do not establish the result a particular builder will get from a particular set of settings. [1][2]
Who should act, who should wait
Move now if you build a video workflow and need to decide whether ProRes saving or selectable chroma subsampling belongs in its output stage. A test in ComfyUI 0.44.0 can answer that question for your workflow. Wait before changing a production handoff if the decision requires a specified ProRes variant, a guaranteed pairing of settings, a measured cost, or confirmed acceptance by another tool. Neither claim supplies those assurances. My recommendation is to test the save step, then adopt only settings whose resulting files you have checked against your own requirements. [1][2]
Sources
- v0.44.0 — GitHub releases · comfyanonymous/ComfyUI L0 · primary