T5TokenizerOptions
_for_testing/conditioningExperimental
T5TokenizerOptionsExperimental: This node is experimental and its behavior may change without notice.
Example
JSON Example
{
"class_type": "T5TokenizerOptions",
"inputs": {
"clip": [
"node_id",
0
],
"min_padding": 0,
"min_length": 0
}
}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 | CLIP | required | - | - |
min_padding | INT | required | min: 0, max: 10000, step: 1 | 0 |
min_length | INT | required | min: 0, max: 10000, step: 1 | 0 |
Outputs
| Index | Name | Type | Is List | Connection Reference |
|---|---|---|---|---|
0 | CLIP | CLIP | No | ["{node_id}", 0] |
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 T5TokenizerOptions node in your workflow, and output_index is the index from the table above.
Example
If this node has ID "5" in your workflow:
CLIP (CLIP):["5", 0]
Was this page helpful?