Connecting Wwise and REAPER with ReaOpen

This time around I wrote about ReaOpen: a free, lightweight tool that lets you select an audio file in Wwise and jump straight back to the REAPER project it came from.

The idea is simple. When you render WAV files out of REAPER with metadata included, ReaOpen can read that metadata off a selected file and use it to open the exact .rpp project that produced it — no more digging through folders trying to remember which session an asset came from. It runs on both Windows and Mac, and it’s built to slot into more than one place in your workflow: Wwise, Explorer/Finder, and REAPER itself.

The Wwise side of the integration relies on custom commands, a feature introduced in Wwise 2018.1.3 that lets you wire your own tools into the Wwise UI. Rather than overriding your existing external editor command, I set up ReaOpen as its own dedicated custom command in Wwise — so your regular “open in REAPER” workflow stays untouched, and ReaOpen is just another option alongside it.

I wrote up the full walkthrough — installation, setup for each integration point, and how the metadata handoff works — in a guest post for the Audiokinetic blog: Connecting Wwise and REAPER: Part 2 - ReaOpen. Head there for the complete breakdown.

This was the second part of a series on connecting REAPER and Wwise. Part one covered WAAPI Transfer, a plugin for exporting audio straight from REAPER into a Wwise project.