Skip to main content
Reagent works with Wwise Authoring on your computer through the Wwise Authoring API (WAAPI), with or without REAPER running. A helper called the Wwise subagent investigates your project and reports back. Reagent itself makes any changes.

​
Connect to Wwise

You need Wwise 2021.1 or newer (Windows or macOS) running on the same computer as Reagent, with your project open.
Reagent searches your project with WAQL, the Wwise Authoring Query Language.
On macOS, Wwise is the Windows version running inside CrossOver, a Windows compatibility layer installed with it. When Wwise reports a Windows path such as Z:\Users\..., Reagent’s audio tools look for the matching file on your Mac.
1

Turn on WAAPI

In Wwise, open Project > User Preferences and turn on Enable Wwise Authoring API.
2

Check the ports

Keep the WAAPI ports at their defaults: 8090 (HTTP) and 8080 (WAMP, used by live mixing). If you changed either, set it back.
3

Restart Wwise and open your project

Restart Wwise so the change takes effect, then open your project. Reagent finds Wwise on its own.
4

Check the connection

Ask “Is Wwise connected?” There’s no status light, so asking is the quickest check. If you sent a message before Wwise was ready, Reagent can take up to 30 seconds to notice. Wait, then ask again.
For connection errors, timeouts and unsupported versions, see Wwise Connection Problems.

​
Using Your Wwise Selection

With each message, Reagent tells the AI model what’s selected in Wwise (up to 10 objects), so you can say “these objects” or “the selected bus”. While Wwise is connected to a running game, Reagent ignores your selection for requests about a sound you heard. That way, an object you clicked earlier isn’t changed by mistake. To use the selection anyway, say “selected” or “selection”.

​
Explore and Debug Your Project

The Wwise subagent reads your project and live profiler data from a connected game, then reports back. It shows in the chat as a collapsed step.
To investigate, the subagent uses:
  • WAAPI queries and read-only scripts to read your project.
  • Knowledge articles: hand-written articles on troubleshooting, best practices and version migration, looked up on reaperagent.com.
  • Reference for your Wwise version: WAAPI, object and WAQL reference for your version, looked up on reaperagent.com.

​
Audio Analysis on Wwise Source Files

Reagent can measure the source files your Wwise Sounds use: loudness (RMS), silence (for example, dead air left by trim points), transients, waveform shape and metadata. The Wwise subagent finds the file paths, then Reagent runs the Audio Analysis file tools on your computer. The tools can measure part of a file, so you can ask Reagent to stay within Wwise’s trim points.

​
Make Changes

Reagent can create objects, set properties and references, import audio, and run a script for batch changes across many objects.
Reagent treats Wwise changes as high risk, so it asks before each one in Default permissions and Auto-review, but not in Full access (Permissions). The approval card names the action (Apply Mix, Mutate Waapi or Mutate Script) but not the target object or the new value. Read what Reagent said it’s about to change before you click Allow or Deny.
In Default permissions and Auto-review, Reagent may also ask on a Use Wwise subagent card. This happens when the task Reagent writes for the subagent contains a word such as “set”, “create”, “delete”, “apply”, “change”, “run” or “trim”, even for a question such as checking trim points. The subagent itself only reads your Wwise project, even though the card says it may modify it. Any change the subagent leads to still gets its own approval.

​
Undoing Changes

To reverse a change, use Edit > Undo in Wwise. A task done as several separate changes needs one Undo per change. If a later change fails, the earlier ones stay in place.
  • Mutate Script: one Undo reverses the whole script, which Wwise’s undo history names after the script’s description. If the script fails partway, Reagent undoes it automatically.
  • Apply Mix and Mutate Waapi: each is a single change, with no automatic rollback if it fails.
Wwise undoes in order, most recent first. Undo Reagent’s changes before you make other edits you want to keep.

​
Live Mixing

While Wwise is connected to your running game, describe a sound you just heard and how to change it. Reagent finds the object that played in Wwise’s profiler data, not your Wwise selection. It also reads the Switch, State and RTPC values in effect, so it can tell apart variations such as footsteps on different surfaces.
1

Connect and start capture

Connect Wwise to your running game, then start Profiler capture (press F5 in Wwise).
2

Play the sound and describe the change

Trigger the sound in the game. Reagent looks back over up to the last five minutes of the capture. Say what to change and by how much. A number in dB gives the most predictable result.
3

Approve the change

If more than one object could match, Reagent lists the candidates and asks which one you mean. Click Allow on the approval card, and the change applies right away.
Example requests, including a question that changes nothing:
Without a game connection, Reagent can’t tell which sound you heard, so name the object instead, as in the last example. When capture is on, Reagent also adds a line to the profiler capture log, so you can see where each change came from:

​
What Reagent Sends

Reagent connects to Wwise on this computer (127.0.0.1). To work on your request, it sends Wwise information to the AI model, which is Reagent’s hosted service on individual plans:
  • With each message: whether Wwise is connected and its version, and up to 10 selected objects (name, type, path and ID) plus a count of any others. While a game is connected, it sends the number of selected objects instead, plus the connected game’s name, whether capture is on and, while capturing, how many voices played in the last few seconds.
  • During Wwise tasks: what Reagent and the Wwise subagent read from your project and what Reagent changes in it, including live capture details, the results of changes and measurements of source audio files.
  • Lookups: the search text the Wwise subagent writes goes to reaperagent.com, which sends it to Voyage AI to find matching articles and reference. Your Wwise version also goes to reaperagent.com to fetch reference for that version, including the WAQL documentation each time the Wwise subagent starts.
On Enterprise accounts, the AI model is your organization’s own endpoint instead.

Example Workflows

Wwise prompts alongside other common tasks.

Privacy & Security

What Reagent sends, and where.