In fact, RMS would probably work better than LUFS for this purpose, but Reaper doesn’t have an out-of-the-box way to accomplish this (I’m sure it could be done very easily with scripts), and LUFS works well enough to get things in the right ballpark. I use integrated rather than short term as this reason I do this is primarily to get all the tracks at roughly the optimum gain to hit my analogue chain, and not to get them the ‘right’ volume, which is typically done in the digital domain, post-capture. My custom ‘set up session’ action in REAPER, that I enact at the start of every mastering session, includes setting every track to -20 LUFS (integrated). I always start with pro-q2 before my analog chain and use the gain knob there to adjust the level by ear. The idea of doing LUFS conversion before mastering is nice, but to be honest, for me it doesn't matter. If the balllad has the same LUFS level, it would pop out to much (too bad about spotify using track normalization.) A ballad will most of the times be lower in level then an uptempo track. On the other had, I don't check LUFS values for an album myself, all done by ear. I make 2 versions, a loud master and a more dynamic master and batch them both to -14 and let them listen withount knowing which is which. I just use this mostly that customers that are worried about if their track will be 'loud enough' on spotify. I made a batch converter where it's just a matter of drag the files in and it processes them to a set LUFS value and saves the new files to a file with for instance -14LUFS after the filename. Thanks!This is already possible in wavelab. Does anyone batch process files to set a even LUFS level throughout an album before mastering? I batch process sample rate to 96khz (either Myriad of Weiss Sacron when i can use it) but wondered if it is techniques used by many people before mastering, or is it too destructive in your opinion? Got a question and was looking some advice on batch processing.
0 kommentar(er)
