Use WanCameraEmbedding when you want ComfyUI to generate a camera-trajectory embedding from a selected movement. Consider Wan Uni3C when you already have an RGB video rendered from a camera trajectory, plus a compatible Wan model, Uni3C patch, and VAE. These are different conditioning routes, not interchangeable ways to feed the same asset. If you have no rendered guidance video, Uni3C’s documented input contract is not met.
Choose a route and wire it
- Name the control material. If your plan is a preset move such as pan left, zoom in, or clockwise rotation, start with WanCameraEmbedding. If you have a rendered sequence that depicts the intended camera path, evaluate Uni3C. A rendered clip is an input requirement for that route, not proof that the model will reproduce every scene detail.
- For the embedding route, set the sequence geometry. In
WanCameraEmbedding, choosecamera_pose, then setwidth,height, andlengthto the intended video geometry. The node documents a trajectory tensor and returns the dimensions and length it used. Setspeedonly if you want to scale the selected movement;fx,fy,cx, andcyare advanced camera-intrinsic inputs. Check the downstream workflow’s required geometry rather than assuming defaults fit. - For Uni3C, verify types and compatibility first. Connect a Wan
MODEL, aMODEL_PATCHthat is actually a Uni3C ControlNet, the VAE used to encode this guidance video into latents, and the rendered clip atrender_video. Confirm the model is Wan-based and its internal dimension matches the patch. The input is expected as RGB; the node uses only its first three channels. Node color can help locate a connection, but rely on the displayed type label. - Set the Uni3C control window.
strengthsets the control signal strength;start_percentandend_percentspecify when that signal begins and stops during denoising. Their documented ranges are -10 to 10 and 0 to 1 respectively. Choose values as controlled workflow settings, not as guaranteed fixes for a visual defect. - Compare outputs against the same brief. As an author-recommended comparison, hold the source image, prompt, output geometry, and other workflow settings constant where the workflow permits. Change only the conditioning route. Judge whether the camera move matches the intended direction and whether the scene remains coherent; this comparison method is not a documented node behavior.
Record the compatibility decision
The following is a hypothetical planning example, not a software test or expected result. A creator wants a leftward move for an 81-frame, 832-by-480 shot. They have both a preset-move plan and an RGB render, and identify a Wan model and Uni3C patch whose documented internal dimensions match. The table records route eligibility and observations to check; it does not predict output quality.
| Check | Hypothetical record | Decision |
|---|---|---|
| Desired control | Preset pan left; also evaluate a rendered path | Compare routes only if both inputs are available |
| Embedding geometry | 832 × 480, length 81 | Enter these intended values in the embedding node |
| Uni3C media and types | RGB render; Wan model, Uni3C patch, VAE identified | Eligible to assemble, subject to actual type and dimension checks |
| Control window | Strength 1.0; start 0.0; end 1.0 | These are documented defaults, not quality recommendations |
| Review observation | Hypothetically, the rendered route bends the background in one sample | Record the observation; do not infer that strength alone caused it |
Limits and next steps
The Uni3C apply node is documented as experimental. The documentation specifies its accepted inputs and compatibility checks, but does not promise that either route will preserve scene geometry, reproduce a render exactly, or outperform the other. It also does not define an automatic conversion between a camera embedding and a rendered guidance video.
If Uni3C raises a compatibility error, check the actual node input types, confirm the patch is a Uni3C ControlNet, verify the Wan model family and matching internal dimensions, and confirm the guidance frames are RGB. If the workflow has no suitable render, use the embedding route when its preset movement meets the task; otherwise prepare a render through a separately available workflow and verify that it is accepted before proceeding. If output motion is undesirable, record which route and settings were used, then change one control at a time. Do not treat a parameter change as evidence that missing scene information can be recovered.
Workflow boundary and sources
This is documentation-based guidance with constructed examples, not a reported generation or application test. Use Imagild Film Script for a written plan and inspect the actual supported input roles in Film Prompt before reference-video recreation. External software controls belong to their named products. No exact reconstruction, native analyzer, existing-clip repair or ranking result is promised.
- ComfyUI WanCameraEmbedding — Preset trajectory embedding with video geometry and camera-intrinsic inputs.
- ComfyUI WanUni3CControlnetApply — Experimental RGB rendered-video guidance, Wan model/patch/VAE compatibility and denoising control window.
- Runway Image to Video Prompting Guide — Motion planning and source/temporal review principle
Editorial revision: November 13, 2026.