Reaper

“Here's a workflow tip, which should apply to any DAW not just Reaper: when I master I always keep a muted “bypass” track at the top of the session, which is just the original unprocessed mix.”

“Let's try turning on Reaper's built-in oversampling. And I can set this to the maximum 16 times oversampling with no problems.”

“Here's a blank Reaper project with a region selected for rendering: let's bounce that out, with 16 bit dither and noise shaping, and re import it back into the project.”

“That's Reaper though: it has particularly good plugin delay compensation. Honestly, that's one of the main reasons I made the switch.”

“Of course I can use the DAW bypass, but it's a bit small and fiddly in Reaper, plus there's a chance of glitching when bypassing a plugin that has latency, so I always prefer to have a built in, guaranteed glitch free bypass button in the plugin.”

“As a Reaper user however, I also have another option available: I can use Reaper's built in oversampling instead.”

“There’s a much bigger difference when it comes to cpu use however: Reapers reported cpu use roughly doubles with the smallest Blocksize, though it still plays back in realtime on my system with no difficulty.”

“I record everything in Reaper.”

“Except, here's a cool Reaper trick. You want to normalize your samples? Bam! Samples are normalized. Done.”

“…but if I add a a comb filter that's very very resonant, Reaper is going to like have a fit.”

“Save a Reaper file Korg stream cheese.”

“So, uh, Reaper the DAW. This is what I use when I'm making music for games.”