^The exception is when you enable "gain compensation (boost pans)" which achieves the same result (panning loudness being balanced), but instead of reducing the center to match the sides, it boosts the sides to match the center. Thusly, changing pan law changes the center volume by reducing it some.
Remember, pan law changes the center, because normally summing left and right speakers would result in something louder than just being left or right. Like I said, you don't have to pan for pan law to change volume! If you take a track panned to center, press play, change the pan law from 0 to -3, the volume will change. I'm not panning anything, so pan laws shouldn't be applied here. Reaper doesn't seem to be behaving in the way I would expect it.
I've been using this same limiter plugin (UAD Precision Limiter) set to an output ceiling of -0.1 for about ten years now in Logic, and never had this issue. I thought maybe it was the way Reaper's meters interpret a clip, but the fact that a bounced audio file from Reaper put in to Logic ALSO shows a clip (when the file in Logic isn't clipping), it must be something with Reaper. This happens whether I put the limiter on the individual track or the master bus. I've even bounced the limited track from Reaper (where it's clipping) and imported in to Logic, and now Logic is showing it is clipping also. If I do this exact same process in Logic, using the same source audio file and same limiter plugin, it never hits 0.0 and never clips. If I put a source audio file in Reaper, apply a true-peak limiter on it with an output ceiling of -0.1, Reaper shows this as hitting 0.0 and clips (keep in mind I'm not brick-wall limiting, this clipping is coming from some percussive transients).
Audio peaking in reaper for mac pro#
I'm using the latest version of Reaper on OSX, previously coming from Logic Pro X. I'm having an issue with limiting in Reaper. I've searched the forums for this sort of thing and can't find quite the exact discussion.
0 kommentar(er)
