Issue link: https://digital.copcomm.com/i/1538144
84 M PS E . O R G Production Speed Gains Are there specific use cases where the REAPER-to-Wwise pipeline with ReaWwise has significantly reduced iteration time? How are teams leveraging that tight integration to stay agile during game development? Simon Pressey: With the introduction of Wwise Auto-Defined SoundBanks, it is possible to swap sound assets live while Wwise is connected to the running game. Using the script "Open Associated REAPER Project" and ReaWwise, you can open REAPER and update your sounds in real time. It really can't get much faster—the transfer is only as fast as your connection via WAAPI. This workflow is available to everyone using Wwise and REAPER. If you are not yet using it, you will likely experience significant improvements in integration speed and iteration once you start. It's a kind of "there's no going back" experience. Pro Tools Compatibility For sound editors used to building sessions in Pro Tools, how does working with Strata compare or complement their existing workflows? Simon Pressey: A popular workflow is to run REAPER as an insert with Pro Tools. The cost of REAPER is often less than many plug-ins, and game studios are increasingly requesting REAPER projects for asset delivery or in Wwise projects, so having REAPER in the toolbox is something I am seeing more often. When using REAPER as an insert in Pro Tools, designers are opening Strata projects, syncing REAPER to their Pro Tools picture source, tweaking the Strata project, and laying back REAPER's output onto tracks in Pro Tools. Fundamentally, a DAW is a DAW. Each has its unique approach. A Strata REAPER project acts as a shortcut to using REAPER, as it's a well-organized, clearly named, and fully labeled session. This means you don't have to learn a bunch of "REAPER's ways" to just start using it effectively. This can take some of the sting out of using it for the first time. It almost makes it too easy. In minutes, you can be doing productive audio design with less of the awkward, unproductive "new tool" feelings. Hybrid Workflows on the Rise Do you think this ease of integration is helping more teams transition toward hybrid workflows with REAPER and Pro Tools? Have you seen this influence on how sound teams structure their editorial or implementation pipelines? Simon Pressey: For sure, when you open a Strata project, there is a clear understanding of the similarities between Pro Tools and REAPER, such as the general everyday structure of tracks and sounds on a timeline. This helps reduce the "fear of the unknown DAW" effect. With the Strata project, you can immediately do productive work in REAPER. Even if you have The "Propulsion Hover" subproject from Strata's Robotic collection open in REAPER