How to use Text Selector node in Oraphim

Type ID: motion.text.selector
Category: Text

What this node does

The Text Selector 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 10 sockets and 13 properties for this node. Its main registered inputs are Index, Count, Start; its main outputs are Weight, Inverse Weight, Selected. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Index	in_index	Int
Count	in_count	Int
Start	in_start	Float
End	in_end	Float
Offset	in_offset	Float
Progress	in_progress	Float

Outputs

Socket	Key	Type
Weight	out_weight	Float
Inverse Weight	out_inverse	Float
Selected	out_selected	Bool
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Units	units	String	Range	Normalized
Start	start	Float	Range	0.0
End	end	Float	Range	1.0
Offset	offset	Float	Range	0.0
Progress	progress	Float	Range	1.0
Softness	softness	Float	Shape	0.0
Shape	shape	String	Shape	Linear
Edge Ease	ease	String	Shape	Smooth
Invert	invert	Bool	Shape	0.0
Randomize Order	randomizeOrder	Bool	Order	0.0
Seed	seed	Int	Order	1.0
Index	index	Int	Element	0.0
Count	count	Int	Element	1.0

How to use it

1. Add Text Selector from node search. Use motion.text.selector when you need the exact registry entry.
2. Connect a compatible Int source to Index. 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 Weight (Float) 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 Selector. Feed a compatible source into Index. Change Units away from its registry default and compare the result. Connect Weight 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

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

Return to the complete Oraphim node reference.