Node reference

How to use Sample Sound Frequencies node in Oraphim

Use the Sample Sound Frequencies node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.sample_sound_frequencies.

Updated August 28, 2026

How to use Sample Sound Frequencies node in Oraphim

Type ID: geometry.sample_sound_frequencies
Category: Utility

What this node does

Samples sound frequencies data for downstream field or geometry operations.

The current Oraphim runtime registers 7 sockets and 7 properties for this node. Its main registered inputs are Sound, Time, All Channels; its main outputs are Amplitude. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Sound sound Audio
Time time Float
All Channels allChannels Bool
Channel channel Int
Low low Float
High high Float

Outputs

Socket Key Type
Amplitude amplitude Float

Controls

Control Key Type Group Registry default
Time time Float Inputs 0.0
All Channels allChannels Bool Inputs 1.0
Channel channel Int Inputs 0.0
Low low Float Inputs 0.0
High high Float Inputs 10000.0
FFT Size fftSize Menu FFT 4096
Window Function windowFunction Menu FFT Hann

How to use it

  1. Add Sample Sound Frequencies from node search. Use geometry.sample_sound_frequencies when you need the exact registry entry.
  2. Connect a compatible Audio source to Sound. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Time, All Channels, Channel first so you can see the node's effect in isolation.
  4. Route Amplitude (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 Sample Sound Frequencies. Feed a compatible source into Sound. Change Time away from its registry default and compare the result. Connect Amplitude 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.

Return to the complete Oraphim node reference.