Redux Isn't Just Lo-Fi: 4 Bass Sound Design Techniques
Redux Is Not Just "The Bitcrusher"
Open Redux in Ableton Live and the first instinct is to slap it on a hi-hat, crank Bit Depth down to 4, and call it lo-fi. That's the version of Redux you've seen in every "lo-fi beats" tutorial on YouTube. It's also the least interesting thing Redux can do for a bass producer.
Redux is a resampling and requantization device — it's not modeling tape, tubes, or transformers like Saturator. It's digitally reducing the resolution of your signal in two independent dimensions: how often it's sampled (Rate) and how many bits are used to describe each sample (Bit Depth). That distinction matters, because it means Redux can add harmonic content, grit, and even rhythmic texture to a bassline in ways a standard saturator can't — if you stop treating it as a "crush everything" switch and start treating it as six separate controls.
The Parameters That Actually Matter
Redux has more going on under the hood than most producers ever touch:
- Bit Depth (1–16) — reduces amplitude resolution. Lower values add quantization noise and harmonic distortion; higher values (12–15) are where the interesting, subtle stuff happens.
- Rate (40 Hz–40,000 Hz) — the resampling frequency. Lowering it below your fundamental starts aliasing the signal into new, inharmonic overtones — this is where "robotic" digital textures come from.
- Jitter (0–100%) — randomizes the resampling clock instead of keeping it fixed, which turns clean aliasing into unstable, noisy grit. This is the parameter most people skip and it's doing a lot of the character work.
- Shape — morphs the quantizer between linear and an A-Law-style compression curve, changing how harsh the bit reduction sounds at the same Bit Depth setting.
- Pre/Post Filter — Pre-filter rolls off content above roughly half the resampling frequency before Redux processes it, which controls how much aliasing you actually generate. Post-filter cleans up after the fact. Toggling these independently is the difference between "digital grit" and "harsh digital noise."
- Dry/Wet — Redux's own internal blend, separate from any parallel routing you set up on a return track.
Most Redux tutorials only ever touch Bit Depth and maybe Rate. Jitter, Shape, and the filter pair are where the actual sound design lives.
Technique 1: The Invisible Harmonic Exciter
Skip the crushed-out robot sound entirely. Set Bit Depth to 14–15 (barely reduced from Live's native resolution) and Rate to somewhere just above your bass's highest meaningful harmonic — for a sub-heavy 808 or reese, that's often in the 4–8 kHz range, well above what you'd expect. At these settings Redux isn't crushing anything audible — it's adding a thin layer of harmonic distortion that reads as "presence" rather than "digital."
Blend it in at 15–25% Dry/Wet, or better, route it on a return track so you keep full control over how much of that harmonic layer sits under the clean bass. This gets you a lot of the perceived loudness and character boost people reach for a saturator for, but with a different, slightly more aggressive harmonic flavor that cuts through a dense low end differently than tube or tape saturation does.
Technique 2: Crush the Mids, Leave the Sub Alone
The biggest mistake producers make with Redux on bass is running the full-range signal through it — which means your fundamental and sub content get quantized right along with everything else, and low end genuinely does not like being bit-crushed. It gets thin, unstable, and loses weight.
Instead, split the signal. Send your bass to a return track with Redux on it, and put an EQ Eight before Redux on that return with a steep high-pass filter around 150–250 Hz — cutting the fundamental and sub harmonics out of what actually reaches Redux. Now Redux is only crushing the upper harmonic content of the bass: the growl, the edge, the character. Blend that return back in under the clean, unprocessed full-range bass on your main track.
You get all the digital grit and aggression up top with none of the low-end instability. This is the same parallel-processing logic used for parallel compression, just applied to a bit-reduction effect instead of a compressor — and it's the difference between Redux sounding like an effect and Redux sounding like a broken bassline.
Technique 3: Building Growl and Robo-Bass Texture
For dubstep- and bass-music-adjacent growls, Jitter and Shape are doing more work than Bit Depth. Start with Rate around 800 Hz–2 kHz on a mid-range bass note — low enough to alias aggressively against the fundamental — then push Jitter up to 30–50%. That instability is what turns a clean aliased tone into something that sounds like it's genuinely struggling, which is exactly the texture growl bass production is chasing.
Switch Shape toward the A-Law end of its range at the same settings and you'll hear the harshness curve differently — less "digital square wave," more "compressed radio static." Automate Rate slowly downward across a sustained bass note and you get a texture that degrades in real time, which reads as tension without touching a filter or an LFO device at all.
Keep Pre-filter on here — without it, the aliasing gets messy and unfocused instead of having a defined edge.
Technique 4: Rhythmic Movement Without an LFO Device
Redux's parameters are all automatable, which means you don't need Shaper, Envelope Follower, or an LFO Max for Live device to get movement out of it. Draw automation on Rate that steps down on every 8th or 16th note under a sustained bass note, then snaps back up — you get a stepped, gated texture that's rhythmically locked to your grid without a single sidechain routing.
This works especially well combined with Follow Actions or simple clip automation on a bass note that's meant to pulse under a build: instead of automating volume or a filter cutoff (which every producer already does), automating Redux's Rate or Bit Depth downward gives you a texture change instead of just a volume or brightness change — genuinely different ear candy in a build that's otherwise all filter sweeps.
Where Redux Goes in Your Chain
Order matters more than people expect. Put Redux before Saturator and you're saturating already-aliased content, which tends to sound harsh and undefined. Put Redux after Saturator and EQ Eight — saturate and shape the tone first, then apply Redux as the final character/grit stage — and you get a much more controlled result, because you're deciding exactly what harmonic content gets crushed rather than crushing raw signal and hoping Saturator cleans it up afterward.
A solid default order for a bass chain: EQ Eight (shape/high-pass) → Saturator (harmonic warmth) → Redux (digital character, parallel or full-range depending on the technique) → a second EQ Eight to tame anything that got too bright.
The Takeaway
Redux's reputation as "the lo-fi plugin" undersells it badly. Used at extreme settings on a full mix, sure, it's a lo-fi effect. Used deliberately — subtle Bit Depth reduction as an exciter, parallel high-passed crushing for growl without losing sub weight, Jitter and Shape for genuine texture, and automated parameters for rhythmic movement — it's a legitimate bass sound design tool that most producers never get past the surface of. The six parameters are all sitting right there in the device; the only thing standing between "crushed hi-hat" and "actual bass character" is turning the knobs you've been ignoring.
For more on getting a bass-heavy mix to translate, see How to Mix Bass-Heavy Music in Ableton Live.