Add seventh H3 scene image slot
This commit is contained in:
@@ -17,15 +17,15 @@
|
||||
- Supports filename tokens including `%input%`, `%input2%`, `%date:yyyy-MM-dd%`, `%counter%`, `%width%`, `%height%`, and `%batch_num%`.
|
||||
|
||||
- `Dumas H3 Plan Attach Scene Images`
|
||||
- Inputs: `plan`, `scene_index`, optional `image1`..`image6`
|
||||
- Inputs: `plan`, `scene_index`, optional `image1`..`image7`
|
||||
- Outputs: `plan`, `connected_images`
|
||||
- Attaches up to six optional image sockets to one MiniMax H3 plan scene while keeping the plan JSON-serializable for the upstream archive system.
|
||||
- Chain one node per scene that needs its own six-image bundle.
|
||||
- Attaches up to seven optional image sockets to one MiniMax H3 plan scene while keeping the plan JSON-serializable for the upstream archive system.
|
||||
- Chain one node per scene that needs its own seven-image bundle.
|
||||
|
||||
- `Dumas H3 Plan Extract Scene Images`
|
||||
- Inputs: `plan`, `scene_index`
|
||||
- Outputs: `plan`, `image1`..`image6`, `connected_images`
|
||||
- Reads back the six optional images for a selected MiniMax H3 plan scene, for example by connecting the current `clip_index`.
|
||||
- Outputs: `plan`, `image1`..`image7`, `connected_images`
|
||||
- Reads back the seven optional images for a selected MiniMax H3 plan scene, for example by connecting the current `clip_index`.
|
||||
|
||||
- `Dumas JSON String to Object`
|
||||
- Input: `json_string`
|
||||
|
||||
Reference in New Issue
Block a user