Add reapertowwise&NuendotoWwise behavior request Please

Nuendo
1

Purpose / Motivation

This request proposes adding a Wwise Event Simulation Layer inside Nuendo, inspired by the ReaperToWwise custom script workflow.
The goal is to allow sound designers to test and trigger Wwise events, switches, and RTPCs directly within Nuendo’s timeline, without requiring a connected game engine.

This would be extremely useful during early pre-production, educational setups, or implementation testing, where a full game environment is unavailable.

Current Limitation

Currently, Nuendo users must either:

  • Export content manually to Wwise and test inside Soundcaster or game engines, or

  • Use Reaper + ReaWwise + custom scripts like ReaperToWwise to simulate game implementation behavior.

Nuendo, while having excellent game audio and middleware export support, does not yet offer a way to simulate real-time Wwise event triggering, switch or RTPC automation directly on its timeline.

Proposed Behavior

Add a Game Audio Simulation Layer to Nuendo that enables:

  • Direct triggering of Wwise Events from timeline markers or regions.

  • Support for Switches, States, Triggers, and RTPC control through automation lanes.

  • Ability to connect to Wwise projects (via WAAPI) using local communication ports (similar to ReaWwise).

  • Optional floating window UI to display connection status, event names, and current game sync states.

  • Real-time feedback (visual or log) showing triggered events and Wwise responses.

Example usage flow:

  1. The user inserts a “Game Event Marker” (e.g., e/Footstep) on the Nuendo timeline.

  2. During playback, Nuendo sends the corresponding WAAPI command to Wwise.

  3. The event is triggered in Wwise, allowing for synchronized playback and testing.

This system effectively transforms a Nuendo project into a flexible, timeline-driven Soundcaster session.

Benefits

  • Enables sound designers and implementers to validate Wwise logic early in the design process.

  • Reduces dependency on game engine integration for testing.

  • Simplifies education, training, and demonstration of adaptive audio concepts.

  • Positions Nuendo as a complete Wwise implementation sandbox, not just a sound design tool.

  • Bridges the workflow gap between Reaper’s scripting flexibility and Nuendo’s industry-standard post-production environment.

References

  • ReaperToWwise (Custom Lua Script, 2024) – by independent sound designer
    Allows event/switch/RTPC triggering from Reaper to Wwise via WAAPI.

  • ReaWwise by Audiokinetic – official REAPER extension for Wwise integration.

  • Soundcaster in Wwise – a similar concept, but not timeline-integrated.

2 Likes
2

https://www.audiokinetic.com/en/blog/reapertowwise/

3

is what you are asking for similar to this new feature I haven’t had a chance to test it out. maybe not as advance but a start. Previewing Audio Assets via Wwise • Nuendo Help • Reader • Steinberg

4

You’re right — this is just the beginning, but it’s still in a pretty rough state.
In the current setup with Wwise and Unity connected, it takes about 2 seconds for playback to start from Nuendo.
Also, based on what I can see from Nuendo’s playback engine, it seems to only support triggering one sound at a time, instead of being able to trigger multiple different instances quickly like in the game engine.