Lackluster-Shot Queue V2
A ten-shot queue built from named camera presets
- prompts
- prompt_text
- camera_info
- queue_count
If you're building a shot list for a character or product video, the last thing you want is to type coordinates for every angle. Lackluster-Shot Queue V2 is the preset-driven version of the pack's shot queue: fifteen named cinematography shots you can add to a queue one at a time, then execute all at once. It's the node for people who think in shots, not degrees.
How it works
You pick from the camera_preset dropdown - front close-up, front medium, front wide, low-angle hero, low-angle close-up, high angle, over-shoulder, left/right profile, back view, three-quarter front, dutch angle, aerial, extreme close-up, cowboy shot - and then work the queue with three boolean buttons:
- add_to_queue - flip to True to push the selected preset onto the queue (up to ten shots)
- run_queue - flip to True to execute everything queued, sequentially
- clear_queue - flip to True to wipe the queue
Each preset expands to its stored azimuth/elevation/distance and becomes a prompt with custom_prefix (default <sks>) prepended. The queue itself lives in sequence_json, so you can also hand-edit or inspect it.
Outputs, one set for the whole queue:
- prompts (STRING list) - one prompt per queued shot, triggering sequential execution
- prompt_text (STRING) - all prompts joined
- camera_info (
LOAD_3D_CAMERAlist) - 3D metadata per shot - queue_count (INT) - shots currently queued
The workflow rhythm
The buttons being booleans is the fiddly bit. You're not clicking a button and getting instant action - you set add_to_queue to True, run once, and it queues. Set it back to False, pick the next preset, run again. Same for run_queue and clear_queue: they're edges you trigger, not states that persist. It feels clunky for the first three shots, then it clicks - and for a ten-shot turnaround it beats hand-writing JSON every time.
Which one did you grab again?
Remember: this pack has two Shot Queue nodes. This one has the camera_preset dropdown and the three queue buttons. The other, "Lackluster-Shot Queue (v2 3D Widget)" (LacklusterShotQueueNode), is the interactive-3D-scene one with raw angle sliders. Different files, different inputs - if you were expecting a 3D scene and got a preset dropdown, you found the other one.
Notes
- queue_count is your friend - a stale queue silently carries shots over between runs, so glance at it before executing.
- Same light install as the whole pack: ComfyUI Manager → "ComfyUI Lackluster Nodes", deps are just
requests+numpy. No models to download.
Inputs (6)
| Name | Type | Default | Description |
|---|---|---|---|
| camera_preset | COMBO | front_medium | 15 options: front_close_up, front_medium, front_wide, low_angle_hero, low_angle_close_up, high_angle_shot, +9 |
| add_to_queue | BOOLEAN | false | Add the selected preset to the queue |
| run_queue | BOOLEAN | false | Execute every queued shot sequentially |
| clear_queue | BOOLEAN | false | Clear all queued shots |
| custom_prefix | STRING | <sks> | Prefix for each generated prompt |
| sequence_jsonopt | STRING | [] | JSON array of queued shots |
Outputs (4)
| Name | Type | Description |
|---|---|---|
| prompts | STRING | — |
| prompt_text | STRING | — |
| camera_info | LOAD_3D_CAMERA | — |
| queue_count | INT | — |