BiteSizedChunks.comLearn one small thing at a time.
Course contentsShow
← Unreal Engine Game Development
Lesson 595 of 8808. User Interface and MetaSoundsFree lesson

Implementing Procedural Audio Nodes and Wave Players

Utilize wave player nodes and basic math operators to trigger and manipulate raw audio samples within a procedural graph structure.

In this lesson, you will learn how to bridge the gap between static audio samples and dynamic, procedural soundscapes by utilizing Wave Player nodes and mathematical operators within MetaSounds.

The Role of the Wave Player

In MetaSounds, a Wave Player node is the fundamental bridge between a raw imported .wav file and the procedural graph. Unlike traditional Sound Cues, a MetaSound Wave Player provides high-level control over playback—including Start Time, Pitch Scale, and Loop toggles—all of which can be driven by real-time variables rather than static settings.

Manipulating Samples with Math

Once your audio is pulled into the graph via the Wave Player, you don’t have to play it back in its original state. By routing the Audio output through math nodes, you can achieve procedural variety. For example, if you want a sample to sound increasingly "rushed" or "distorted" based on a player's UI interaction (such as a health percentage or stamina bar), you can feed a Float variable into a Multiply node to dynamically adjust the Pitch Scale.

Consider this logic flow for a dynamic UI feedback sound:

  1. Input: A Float value from your ViewModel (e.g., StaminaLevel).
  2. Logic: Use a Map Range Clamped node to map the 0-1 stamina range to a specific pitch multiplier (e.g., 0.8x to 1.5x).
  3. Execution: Connect this result to the Pitch Scale input pin of your Wave Player.
  4. Output: The raw sample now modulates its frequency in real-time, providing an immediate auditory response to UI state changes.

Procedural Graph Structure

When designing these nodes, think of the graph as a signal chain. You are not just triggering a sound; you are constructing a live "instrument." By chaining Wave Player output into Envelope or Filter nodes, you ensure that even simple assets feel deeply integrated into the game state, reacting to the very properties you’ve been binding in your MVVM systems. This turns a static UI click into a contextual, living piece of audio feedback.

Key Takeaway: By feeding ViewModel-driven data into the input pins of a Wave Player node, you transform static audio assets into reactive, procedural elements that respond dynamically to your game’s UI state.