as opposed to, reaper rendering the project at 96khz and then converting the final wav to 44.1khz. I'm guessing that when you render to 44.1, the program is still running in 96khz mode, and what reaper is probably doing when you render a 96khz project down to 44.1, is that it's essentially 'switching' to 44.1khz while rendering. i just wonder what causes it as the "use samplerate to process mixing and fx" is checked (acutally greyed out but checked). its very helpful and basically underlines what we were thinking. Tim answered very fast to the msg (even faster than acustica accepting the question to their forum). Many thanks in advance for any helpful hint. Im sure this must be a typical "doh!" moment, but i dont get it yet. fx/plugins get rendered using project sample rate, export to 44.1 sounds as expected. Tried the same process in Ableton and it behaves there differently, iE without this "issue". have to manually convert it to 44.1 afterwards. Same process but export to 96k directly -> no problem.
TLDR in short: 96k project -> n4 loaded 96k samples -> export to 44.1 (while fx etc should be rendered first automatically at 96k before converting) -> sounds terrible. It should render/export at 96k anyway and convert later automatically to 44.1.
Im not sure if the issue is that n4 wrongly tries to render at 44.1 with 96k samples running or if its something else. Determined that n4 (with 3rd party lib with 96k samples loaded) was "causing" it unless i export directly to 96k and convert it outside of reaper manually to 44.1. (Pan law etc 0db on folders)Įxported result will sound awful. Before exporting the project sounds OK on realtime playback. The option "Use project sample rate for mixing and FX/synth processing" is checked. Project runs at 96k upon "render to file" towards 44.1. im sure soemone must have asked it before) Possibly silly reaper/n4 related question (i just got n4 some days ago and couldnt find the answer.
0 kommentar(er)
