Page 1 of 1

Rendering at a high sample rate reduces the effect of redux

Posted: Tue Oct 01, 2013 7:25 pm
by re6ter
For some reason when I render at a high sample rate, it seems that the distortion of redux reduces in strength, if not almost removing it. If I export at 44100 this doesn't happen.

Does that have something to do with exporting at a high sample rate?

Re: Rendering at a high sample rate reduces the effect of re

Posted: Tue Oct 01, 2013 8:39 pm
by GregoryTJ
Is it perhaps running bitcrusher/lo-fi type distortion?

Re: Rendering at a high sample rate reduces the effect of re

Posted: Tue Oct 01, 2013 9:32 pm
by SunkLo
If it's doing sample rate reduction relative to the project sample rate and you render at a higher rate, it might only be downsampling it back down to around 44.1k instead of what you'd get rendering at your regular sample rate. In that case just bounce that track out at the sample rate you used to set the plugin's parameters in the first place. It's not like you need to worry about bouncing to super high quality if you're bitcrushing and decimating.

Re: Rendering at a high sample rate reduces the effect of re

Posted: Wed Oct 02, 2013 3:47 am
by re6ter
GregoryTJ wrote:Is it perhaps running bitcrusher/lo-fi type distortion?
I'm regarding to the native vst called redux in aAbleton live. I am not exactly sure if this is what the effect is.

Re: Rendering at a high sample rate reduces the effect of re

Posted: Wed Oct 02, 2013 4:09 am
by GregoryTJ
re6ter wrote:
GregoryTJ wrote:Is it perhaps running bitcrusher/lo-fi type distortion?
I'm regarding to the native vst called redux in aAbleton live. I am not exactly sure if this is what the effect is.

Googled it, it is a resolution decimation type lo-fi effect, read SunkLo's post.

Re: Rendering at a high sample rate reduces the effect of re

Posted: Wed Oct 02, 2013 1:56 pm
by re6ter
SunkLo wrote:If it's doing sample rate reduction relative to the project sample rate and you render at a higher rate, it might only be downsampling it back down to around 44.1k instead of what you'd get rendering at your regular sample rate. In that case just bounce that track out at the sample rate you used to set the plugin's parameters in the first place. It's not like you need to worry about bouncing to super high quality if you're bitcrushing and decimating.
Im not exactly sure what you mean by this, I am using the plug native vst redux in Ableton. The only two paramters there are are 'soft' and 'hard' reduction and a knob for the strength. GregoryTJ said that it is a resolution decimation type lo-fi effect.

Two work arounds if figured out: rendering it at 44.1 for the mastering stage. Another is rendering the channel at 44.1 that uses redux and import the audio file back into my daw. Both ways work.

Is there a way I can still use redux without having to render that chancel separate?

Re: Rendering at a high sample rate reduces the effect of re

Posted: Wed Oct 02, 2013 1:56 pm
by re6ter
GregoryTJ wrote:
re6ter wrote:
GregoryTJ wrote:Is it perhaps running bitcrusher/lo-fi type distortion?
I'm regarding to the native vst called redux in aAbleton live. I am not exactly sure if this is what the effect is.

Googled it, it is a resolution decimation type lo-fi effect, read SunkLo's post.
Thanks for your help!

Re: Rendering at a high sample rate reduces the effect of re

Posted: Wed Oct 02, 2013 3:38 pm
by SunkLo
Well you could also try running your project at the higher sampling rate and then reconfiguring the effect's parameters to sound like they did before.
If you want to keep your project at the usual sampling rate, just leave it how it is and then freeze that track if you're going to bounce out to a higher rate.

Re: Rendering at a high sample rate reduces the effect of re

Posted: Wed Oct 02, 2013 5:10 pm
by re6ter
SunkLo wrote:Well you could also try running your project at the higher sampling rate and then reconfiguring the effect's parameters to sound like they did before.
If you want to keep your project at the usual sampling rate, just leave it how it is and then freeze that track if you're going to bounce out to a higher rate.

Good solution, thanks.