Camera Shot Presets

Here's a fact the KB's prompt-engineering essay calls "the highest-leverage phrase there is": naming a real camera - lens, angle, movement - is one of the most reliable ways to steer a modern video model, because the encoders were trained on real captions that describe cameras exactly this way. UC_CameraShotPresets turns that into a dropdown.

You pick a shot, and it hands you a ready-made camera_shot_prompt describing framing, angle, and movement in proper film vocabulary. The default is BIRDS_EYE; the list covers the shot grammar you'd actually want - establishing angles, close-ups, tracking moves, overheads, and the rest of the standard set. It's the same template as the other preset nodes: one preset dropdown, one escape_parentheses boolean ("prevents errors from parentheses left in the prompt"), one string output. Drop it into your video prompt's camera section and let the model worry about the pixels.

The reason this works is worth internalizing, because it changes how you write prompts. A "camera shot" isn't just an aesthetic garnish - it's geometric information. Framing (what's in frame, how much of the subject), angle (where the camera sits relative to the subject), and movement (how the camera behaves over time) are all things a video model has to decide, and it decides them much more reliably when you hand it the words that live in its training captions than when you hand it vibes like "dramatic, dynamic." A preset is a curated way of saying "here is the exact vocabulary for this shot."

Where it sits in a workflow: alongside the pack's other preset nodes, as one block of a structured prompt - bonus style, camera shot, edit target, edit operation - rather than as a whole prompt. On Qwen-family and MiniMax H3 video encoders, that block structure reads as an instruction, which is exactly what you want. And because the preset is a fixed string, it gives you the same reproducibility the other presets do: change the shot name and everything else stays constant, so you can actually see what the shot change did.

The trap is mild but real: a camera prompt is a request, not a guarantee. If you ask for a slow orbit and your sampler's at 7 steps on a distilled model, you may get a locked-off camera with motion hinted in the lighting. This node gives you the right vocabulary; it can't give you the steps back.

Install is pack-standard: ComfyUI Manager search "ComfyUI-UtilsCollection", or git clone https://github.com/silveroxides/ComfyUI-UtilsCollection into ComfyUI/custom_nodes and restart. No models, no downloads. If you're already running the pack for its encoder or MiniMax H3 nodes, this is the freebie that makes camera prompts a one-click edit.