ferraus flanger

Flanger

Synopsis

ferraus flanger <input> [options] [-o <output>]

What it does

A very short delay swept by an LFO and fed back, mixed with the dry signal for the jet-plane comb sweep.

This command is also an fx stage and a pipeline op: ferraus fx in.wav -o out.wav --fx "flanger:key=value".

Examples

Default flanger

ferraus flanger drums.wav -o drums_flange.wav

Slow, resonant jet sweep

ferraus flanger gtr.wav --rate 0.1Hz --feedback 80% -o jet.wav

Subtle flanging on a vocal

ferraus flanger vox.wav --depth 1ms --feedback 20% --mix 25% -o vox_flange.wav

Fast flanger with negative feedback for a hollow tone

ferraus flanger synth.wav --rate 2Hz --feedback -70% -o hollow.wav

Options

FlagTypeDefaultMeaning
--ratefrequency0.3HzLFO rate
--depthtime2msDelay sweep width
--feedbackpercent50%Resonance (-95%..95%)
--mixpercent50%Dry/wet: 0% returns the input

Global options

Every command also accepts the global options (-o, --json, --dry-run, --overwrite, --progress, ...). See Global options.

Exit codes

CodeMeaning
0Success
1Processing failed
2Usage or parameter error
3Input missing or unreadable
4Unsupported format or codec
8Cancelled
70Internal error (bug)

Common mistakes

  • Forgetting that outputs are never overwritten: pass --overwrite or a new -o path when re-running.
  • Beat-based times (4b, 1/4) need a tempo: pass --bpm or write 4b@120.
  • Percentages accept 80% or the fraction 0.8; a bare 80 means 80x, not 80%.

For models

  • MCP tool: ferraus_flanger
  • Schema: ferraus schema flanger
  • Pipeline: { op: flanger, args: { ... } } (flag names with _ instead of -)
  • fx stage: yes
{"command": "flanger", "defaults": {"rate": "0.3Hz", "depth": "2ms", "feedback": "50%", "mix": "50%"}}