How to use Text Template node in Oraphim

Type ID: motion.text.template
Category: Text

What this node does

The Text Template node is registered in Oraphim's Text category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 8 sockets and 5 properties for this node. Its main registered inputs are Template, Value 1, Value 2; its main outputs are Text, UTF-8 Bytes, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Template	in_template	String
Value 1	in_0	String
Value 2	in_1	String
Value 3	in_2	String
Value 4	in_3	String

Outputs

Socket	Key	Type
Text	out_text	String
UTF-8 Bytes	out_length	Int
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Template	template	String	Template	{0}
Value 1	value0	String	Values	0.0
Value 2	value1	String	Values	0.0
Value 3	value2	String	Values	0.0
Value 4	value3	String	Values	0.0

How to use it

1. Add Text Template from node search. Use motion.text.template when you need the exact registry entry.
2. Connect a compatible String source to Template. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Template, Value 1, Value 2 first so you can see the node's effect in isolation.
4. Route Text (String) into a compatible downstream node, viewer, or output path.
5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Text Template. Feed a compatible source into Template. Change Template away from its registry default and compare the result. Connect Text to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

• If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
• If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
• If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
• If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Related nodes

• Analyze Text — motion.text.analyze
• Transform Glyphs — motion.text.glyph_transform
• Format Number — motion.text.format_number
• Text Selector — motion.text.selector
• String to Curves — geometry.string_to_curves

Return to the complete Oraphim node reference.