Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > FunUI > FunUI Shot Camera

ComfyUI Node: FunUI Shot Camera

Class Name

FunUIShotCamera

Category
FunUI/Conditioning
Author
digital-garbage (Account age: 1276days)
Extension
FunUI
Latest Updated
2026-11-03
Github Stars
0.02K

How to Install FunUI

Install this extension via the ComfyUI Manager by searching for FunUI
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter FunUI in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

FunUI Shot Camera Description

Rewrites H3 prompt shot blocks with rule-based timing, framing, and camera movement.

FunUI Shot Camera:

FunUIShotCamera is an experimental prompt-conditioning node that applies rule-based shot timing, views, and camera-movement descriptions to the [Shot N] blocks of an H3 prompt. It helps you organize a multi-shot sequence and describe its framing and movement without using a language model. Its timing calculations take the planned video duration into account, allowing the rewriting process to work with the time available across the shots. Each of its main features is off until enabled in Settings ▸ Engine, so it can also leave your writing untouched when no rewriting is needed. This node edits prompt text rather than directly rendering a video or creating a 3D camera. It also supports project-specific focus infusion, which draws on recurring words in a project's prompts, and records eligible rewriting choices when a run identifier is available to support FunUI's learning workflow.

FunUI Shot Camera Input Parameters:

text

A required STRING containing the H3 prompt you want the node to process. This is a multiline field with an empty-string default, so you can enter a complete prompt containing multiple [Shot N] blocks. Those blocks are the documented targets for shot timing, view, and camera-movement rewriting; arbitrary prose is not documented as a substitute for that structure. When rewriting is not required, the node returns this text exactly as received. If the rewriting operation raises an exception, the original text is also returned so that the failed edit does not replace your prompt. No minimum or maximum text length is specified.

length

A required INT specifying the total video length in frames, with a default of 124, a minimum of 1, and a maximum of 100000. The node divides this value by frame_rate to calculate the video duration in seconds and passes that duration to the rewriting process. This gives the timing rules a duration to work with when determining cut times across the shots; it does not itself generate frames or set the length of a downstream video generator. For example, 124 frames at 25 frames per second provides a duration of 4.96 seconds. Match this value to your intended generation length so the prompt's shot timing is based on the correct time budget.

frame_rate

A required FLOAT specifying the video frame rate in frames per second, with a default of 25.0, a minimum of 1.0, and a maximum of 240.0. Together with length, it determines the duration supplied to the rewriting process: the same frame count represents a shorter video at a higher frame rate and a longer video at a lower frame rate. For example, 120 frames represents 4 seconds at 30 fps but 5 seconds at 24 fps. This parameter supplies timing information for prompt rewriting; it does not directly change a video file's playback rate or configure another node. Use the frame rate intended for your actual video workflow.

settings

An optional FUNUI_SETTINGS connection that supplies the FunUI configuration used to decide whether and how to rewrite the prompt. The node description states that cut-time, view, and camera-movement features are each off until switched on in Settings ▸ Engine. If the resolved settings and prompt do not require rewriting, the node returns the original text with the status unchanged. This is a custom settings connection, not a free-text field or a numeric control; no explicit default value, range, or list of accepted settings fields is provided in the node schema. The supplied code does not show the internal settings layout, so configure the relevant features through FunUI's settings interface rather than assuming undocumented option names.

project

An optional STRING identifying the project being made, with an empty-string default and no specified minimum or maximum length. Its documented purpose is to provide project context for focus infusion: the words used by that feature are drawn from the words this project's own prompts repeatedly return to. When rewriting runs, this value is passed to the rewriting process alongside the prompt and duration. Use a consistent project identifier when you want that feature to work with the same project's prompt history. The provided code does not specify the behavior of focus infusion when this field is empty, nor does it establish that supplying a project name enables the feature by itself.

FunUI Shot Camera Output Parameters:

text

A STRING containing the prompt to pass onward in your workflow. When rewriting succeeds, this is the text returned by the rule-based rewriting process, which may incorporate enabled shot timing, view, camera-movement, or focus-related changes. When no rewriting is required, it is the original input text without modification. If the rewriting operation fails, it is also the original input text, providing a fallback instead of discarding your prompt. This output is prompt text, not video frames, camera coordinates, or a 3D camera object; connect it to a compatible text-processing or prompt-encoding stage.

status

A STRING reporting the outcome of the node's processing. The exact value unchanged means the node determined that no rewrite was needed; it is not an error by itself. After a successful rewrite, the value is the descriptive message supplied by the rewriting engine, whose exact wording is not included in the provided source. If rewriting raises an exception, the status starts with left as written and includes the exception message in parentheses, explaining why the original prompt was preserved. Check this output alongside the returned text to distinguish intentional pass-through behavior from a failed rewriting attempt.

FunUI Shot Camera Usage Tips:

  • Enable the features you need in Settings ▸ Engine before expecting changes. Cut times, views, and camera moves are individually off until enabled; adding the node alone does not activate them.
  • Use an H3 prompt with clearly marked [Shot N] blocks. These are the documented targets for rewriting, so test with a known working shot-based prompt before troubleshooting a more complex sequence.
  • Match length and frame_rate to your planned video generation. For a six-second sequence at 24 fps, set length to 144 and frame_rate to 24.0 so the rewriting engine receives a six-second duration.
  • Enable one feature at a time while developing your prompt, then compare the returned text with your original. This makes it easier to identify which rule-based feature is responsible for a change.
  • Keep project consistent across prompts belonging to the same project when using project-specific focus infusion. The documented source of its focus words is recurring language in that project's prompts, not merely the project name.
  • Inspect status during testing. unchanged indicates that rewriting was not required, whereas a status beginning with left as written indicates that rewriting was attempted but failed.
  • Be aware that the node deliberately runs again whenever it is going to rewrite, even if its visible inputs have not changed, so that run choices can be recorded. This can also cause downstream prompt processing to run again; when rewriting is unnecessary, the node avoids forcing that extra work.
  • Treat this as an experimental text-conditioning feature and review important prompts before long renders. It describes camera behavior through prompt text rather than directly controlling a physical or 3D camera.

FunUI Shot Camera Common Errors and Solutions:

unchanged

  • Explanation: This is an informational status, not an error. The node determined that the current settings and text do not require rewriting. The documented camera-related features are disabled until you enable them.
  • Solution: If you expected edits, check Settings ▸ Engine, enable the intended shot-camera features, and confirm that your prompt uses the documented [Shot N] structure.

left as written (exception details)

  • Explanation: The rewriting process raised an exception. The actual exception text appears inside the parentheses, and the node returns your original prompt rather than stopping the workflow because of this rewrite failure.
  • Solution: Read the full status and check the ComfyUI log for the entry labeled FunUI Shot Camera with the context rewriting the prompt. Retry with a simpler shot-based prompt and enable features one at a time to isolate the cause. Keep the original prompt available while troubleshooting.

FunUI Shot Camera — remembering this run

  • Explanation: This is the logging label and context used if recording the run's rewriting choices fails; it is not a guaranteed complete error-message string. The source explicitly treats this as a loss of learning information, not a failure of the generated prompt, so the rewritten text can still be returned successfully.
  • Solution: You can continue using the returned prompt if it is correct. Inspect the accompanying exception in the ComfyUI log to identify the recording problem; if it repeats, include that exception when reporting the issue to the FunUI maintainer.

Shot timing does not match the intended video duration

  • Explanation: This is a possible configuration symptom rather than a literal error message. The node calculates duration from length / frame_rate, so a mismatch between these inputs and your actual video workflow gives the timing rules the wrong duration.
  • Solution: Set length to the actual frame count and frame_rate to the intended frames per second, then verify their ratio. Keep length within 1–100000 and frame_rate within 1.0–240.0.

Missing or incompatible required inputs

  • Explanation: This is a workflow-validation issue rather than a specific message defined by this node. The node requires text, length, and frame_rate with the declared STRING, INT, and FLOAT types. The optional settings connection must use the custom FUNUI_SETTINGS type.
  • Solution: Supply all three required inputs, keep numeric values within their documented ranges, and connect only a compatible FunUI settings output to settings. If you are diagnosing a settings-connection problem, disconnect the optional connection temporarily to isolate it.

Prompt changes but no camera object or video is produced

  • Explanation: This is expected behavior, not a processing error. FunUIShotCamera returns edited prompt text and a status message; it does not output a 3D camera, images, or video.
  • Solution: Connect the returned text to the appropriate prompt-processing stage of your video workflow. Use separate generation or 3D-camera nodes when you need rendered frames or an actual camera object.

FunUI Shot Camera Related Nodes

Go back to the extension to check out more related nodes.
FunUI
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.