How to use Transform Glyphs node in Oraphim

Type ID: motion.text.glyph_transform
Category: Text

What this node does

The Transform Glyphs 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 14 sockets and 22 properties for this node. Its main registered inputs are Glyph Geometry, Start, End; its main outputs are Geometry, Glyph Count, Affected Glyphs. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Glyph Geometry	in_geometry	Geometry3D
Start	in_start	Float
End	in_end	Float
Selector Offset	in_selector_offset	Float
Progress	in_progress	Float
Translation	in_translation	Vector3
Rotation	in_rotation	Vector3
Scale	in_scale	Vector3
Opacity	in_opacity	Float

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
Glyph Count	out_glyph_count	Int
Affected Glyphs	out_affected_count	Int
Diagnostic	out_diagnostic	String
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Units	units	String	Selector	Normalized
Start	start	Float	Selector	0.0
End	end	Float	Selector	1.0
Offset	selectorOffset	Float	Selector	0.0
Progress	progress	Float	Selector	1.0
Softness	softness	Float	Selector	0.0
Shape	shape	String	Selector	Linear
Edge Ease	ease	String	Selector	Smooth
Invert	invert	Bool	Selector	0.0
Randomize Order	randomizeOrder	Bool	Selector	0.0
Seed	seed	Int	Selector	1.0
Translate X	translateX	Float	Transform	0.0
Translate Y	translateY	Float	Transform	0.0
Translate Z	translateZ	Float	Transform	0.0
Rotate X	rotateX	Float	Transform	0.0
Rotate Y	rotateY	Float	Transform	0.0
Rotate Z	rotateZ	Float	Transform	0.0
Scale X	scaleX	Float	Transform	1.0
Scale Y	scaleY	Float	Transform	1.0
Scale Z	scaleZ	Float	Transform	1.0
Opacity	opacity	Float	Style	1.0
Advanced Outputs	advancedOutputs	Bool	Output	0.0

How to use it

1. Add Transform Glyphs from node search. Use motion.text.glyph_transform when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Glyph Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Units, Start, End first so you can see the node's effect in isolation.
4. Route Geometry (Geometry3D) 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 Transform Glyphs. Feed a compatible source into Glyph Geometry. Change Units away from its registry default and compare the result. Connect Geometry 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
• Format Number — motion.text.format_number
• Text Selector — motion.text.selector
• Text Template — motion.text.template
• String to Curves — geometry.string_to_curves

Return to the complete Oraphim node reference.