Nodes/IAMCCS-nodes/FL2VA CONTINUOUS AV · Shotboard Interval (Legacy ID)
ComfyUI Node

FL2VA CONTINUOUS AV · Shotboard Interval (Legacy ID)

The legacy ID for the Shotboard interval reader

By IAMCCS·Created 11 months ago·Updated about 17 hours ago· 113
FL2VA CONTINUOUS AV · Shotboard Interval (Legacy ID)
  • cine_linx
  • first_frame
  • last_frame
  • prompt
  • width
  • height
  • duration_seconds
  • is_first
  • total_segments
  • report
segment_index0

This is the second of the two Herrgotts* names in this pack, and it is the same trick: the legacy identifier maps to the same class object as the current node, in this case IAMCCS_MiniMaxH3ContinuousAVSegment (displayed as "FL2VA CONTINUOUS AV · Shotboard Interval").

Same two inputs - cine_linx and segment_index - and the same nine outputs: first_frame, last_frame, prompt, width, height, duration_seconds, is_first, total_segments, report. Because it is the same class, there is no behavioural difference to find, and no "legacy mode" with different defaults.

The (Legacy ID) suffix you see in the display name is the pack telling you on the canvas which one you're looking at, so you don't have to notice the class name. If your graph shows Shotboard Interval (Legacy ID) and you were expecting the new one, that's a graph that has never been re-saved since the rename - harmless, and worth updating when convenient so you're not the last person on the old path.

Do you need to change anything?

For an existing workflow, no. It resolves, it queues, it reads the shot plan exactly as the new ID does. There is no migration step and nothing to re-render.

For new work, prefer IAMCCS_MiniMaxH3ContinuousAVSegment. Notes, tutorials and the pack's newer nodes all use that name, and while both will keep working, debugging is easier when you're on the identifier the rest of the ecosystem is talking about.

Don't wire both into one graph. They will both read the plan and both produce the same nine outputs, which is harmless but makes for a canvass full of duplicate wiring and a confusing report when you're trying to work out which branch fed what.

For what the node is actually for - reading one authored A→B interval out of the Shotboard plan, the validation that catches a missing keyframe before you render, and the stand-in first_frame behaviour on continuation intervals - the canonical page has the detail:

Install

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Or ComfyUI Manager → search IAMCCS → install → restart. Like the current node, this one needs nothing downloaded and nothing extra installed: no models, no optional packs. It needs a cine_linx upstream that actually resolves to a shot plan, because there is no other source of the interval list.

CategoryIAMCCS/MiniMax H3/FL2VA Continuous AV

Inputs (2)

NameTypeDefaultDescription
cine_linxIAMCCS_SUPERNODE_LINX
segment_indexINT00–1000000

Outputs (9)

NameTypeDescription
first_frameIMAGE
last_frameIMAGE
promptSTRING
widthINT
heightINT
duration_secondsFLOAT
is_firstINT
total_segmentsINT
reportSTRING