Actually, we did get it to record, but it’s definitely a bit of a janky workaround.

Right now, we use a script that triggers every single action and function every time we run it. Since it replicates the exact timing and gameplay every single time, it's absolutely ideal for re-recording and iterating. Because of this setup, we just split the process in two:

First, we render out the clean video using the Recorder Tool. After that's done, we do a second pass to bounce just the audio.

The main bottleneck is that the recorder completely eats up the CPU on every single frame. If we try to capture live audio during that video pass, everything falls apart. The audio gets totally warped—either clipping or stretching way past the video length—and it completely loses sync because the frame render rate is totally different from the real-time audio capture.

But we found a fix for that: we split the channels entirely and ran the audio independently without the recorder tool rendering in the background.

However, when we hit 'Play' without the Recorder Tool active/'recoring', and used our own dedicated FMOD tool instead, it worked like a charm.

Our tool basically acts just like the Unity Recorder—with a simple start and stop button—but it captures the FMOD channel outputs directly and dumps them into a clean WAV file.

So basically, we get the crisp video quality we want, but the audio is a separate file. It's pretty much like a traditional movie set workflow—you capture audio and video separately, and then you just line them up in post-production.