How to use Analyze Text node in Oraphim

Type ID: motion.text.analyze
Category: Text

What this node does

The Analyze Text 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 12 sockets and 4 properties for this node. Its main registered inputs are Text, Index; its main outputs are Text, Segment, Grapheme Count. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Text	in_text	String
Index	in_index	Int

Outputs

Socket	Key	Type
Text	out_text	String
Segment	out_segment	String
Grapheme Count	out_graphemes	Int
Word Count	out_words	Int
Line Count	out_lines	Int
Sentence Count	out_sentences	Int
Segment Count	out_segment_count	Int
Byte Start	out_byte_start	Int
Byte End	out_byte_end	Int
Valid UTF-8 / Index	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Text	text	String	Input	0.0
Segment Mode	segmentMode	String	Segmentation	Grapheme
Segment Index	index	Int	Segmentation	0.0
Advanced Outputs	advancedOutputs	Bool	Output	0.0

How to use it

1. Add Analyze Text from node search. Use motion.text.analyze when you need the exact registry entry.
2. Connect a compatible String source to Text. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Text, Segment Mode, Segment Index 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 Analyze Text. Feed a compatible source into Text. Change Text 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

• Text Template — motion.text.template
• 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.