Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
UPDATE: Problem fixed, new second try
#5
(07-12-2017, 01:04 PM)kapu Wrote: I don't use Reaper, so can't say for sure, but it could be that you froze your source tracks, and the FX return tracks? Then, when bouncing, you get frozen source tracks, frozen FX tracks (reverbs etc) and also the still active FX sends from frozen source tracks basically doubling the amount of FX. Although you should be able to hear this when just playing the project, but if you froze the tracks and rendered straight away without auditioning the project after freezing, this could be the case.

Another possibility. If you encode to MP3 with less than 192kbps most encoders will use M/S processing. Basically this means your stereo image will be narrower, and certain types reverb/room/spatial effects will appear to 'rise up' in the center with slightly worse sound. ^_^

One of Reaper's options for rendering tracks is to "freeze track then mute original," which is how I did it.

I did go back and listen to the frozen tracks and they sounded OK. just like the original. I wonder if the LAME encoder I use could be the problem. Cockos has a link to a different one in the User's Guide, which I installed, but Reaper wouldn't see it, so I had to use the old one I have that Audacity recommends. I'm fairly certain that one is a 32-bit app and I try to run nothing but 64-bit in Reaper to match my laptop.

Thanks for your input.
Reply


Messages In This Thread
RE: I have a slight problem rendering a project to MP3 in Reaper - by MrGroove - 07-12-2017, 07:36 PM