SV3D Batch Schedule

KJNodes/experimental

SV3D_BatchSchedule

Allow scheduling of the azimuth and elevation conditions for SV3D. Note that SV3D is still a video model and the schedule needs to always go forward https://huggingface.co/stabilityai/sv3d

Example

JSON Example

{
  "class_type": "SV3D_BatchSchedule",
  "inputs": {
    "clip_vision": [
      "node_id",
      0
    ],
    "init_image": [
      "node_id",
      0
    ],
    "vae": [
      "node_id",
      0
    ],
    "width": 576,
    "height": 576,
    "batch_size": 21,
    "interpolation": "linear",
    "azimuth_points_string": "0:(0.0),\n9:(180.0),\n20:(360.0)\n",
    "elevation_points_string": "0:(0.0),\n9:(0.0),\n20:(0.0)\n"
  }
}

This example shows required inputs only. Connection values like ["node_id", 0] should reference actual node IDs from your workflow.

Inputs

Name	Type	Status	Constraints	Default
clip_vision	CLIP_VISION	required	-	-
init_image	IMAGE	required	-	-
vae	VAE	required	-	-
width	INT	required	min: 16, max: 16384, step: 8	576
height	INT	required	min: 16, max: 16384, step: 8	576
batch_size	INT	required	min: 1, max: 4096	21
interpolation	ENUM 4 options linear ease_in ease_out ease_in_out	required	-	-
azimuth_points_string	STRING	required	-	"0:(0.0), 9:(180.0), 20:(360.0) "
elevation_points_string	STRING	required	-	"0:(0.0), 9:(0.0), 20:(0.0) "

Outputs

Index	Name	Type	Is List	Connection Reference
0	positive	CONDITIONING	No	["{node_id}", 0]
1	negative	CONDITIONING	No	["{node_id}", 1]
2	latent	LATENT	No	["{node_id}", 2]

How to connect to these outputs

To connect another node's input to an output from this node, use the connection reference format:

["node_id", output_index]

Where node_id is the ID of this SV3D_BatchSchedule node in your workflow, and output_index is the index from the table above.

Example

If this node has ID "5" in your workflow:

• positive (CONDITIONING): ["5", 0]
• negative (CONDITIONING): ["5", 1]
• latent (LATENT): ["5", 2]

Package: comfyui-kjnodes