Device Details


Name | Version: FFT Vocoder 1.2
Author: Sanders
Device Type: Audio Effect
Description: With the advent of multi-channel routing capabilities in Ableton 10, I thought it was high time for a neat little FFT phase based vocoder. Simple, but very effective!

To set it up simply put it on the audio track to be 'vocoded' and select the carrier channel and insertion point. You can play around with the buffer size and overlap. Low buffer sizes and overlaps will make things more grainy and dirty, with a lower CPU load and a fast reaction time, while higher values will keep things crisp and crystal clear, but will demand more. The buffer size determines the amount of latency as well.

For those who care: I tried to keep to the m4l 8 standard as much as I could regarding the approach to wet/dry, audio routing and so on.

Hope you enjoy!
If you encounter a problem, have a question, or just want to say hi, you can find my contact details inside the device ;)

p.s.: IMPORTANT: this device will only work from Ableton 10/Max 8 onwards, as it uses the new routing system!

Update 1.1:
- fixed bug that prevented the parameters from loading up properly after saving and reloading a liveset.
- fixed tiny bug turning the volume sliders of each copy of the device to grey when one of them was deactivated

Update 1.2:
- changed name from "Phase Vocoder" to "FFT Vocoder": although it is a vocoder making use of the phase of FFT bins, an actual phase vocoder is a different thing altogether, and has a different use and functionality from a classic vocoder
- slightly less CPU-heavy, should be less prone to any crashes too
- fixed bug that could stop the device from working upon loading in a liveset until changing the buffersize or overlap parameters


Live Version Used: 10.0.2
Max Version Used: 8.0.0
Date Added: Jun 04 2018 02:03:26
Date Last Updated: Dec 11 2018 09:13:33
Downloads: 2606
License: AttributionShareAlike
Average Rating (2)

Log in to rate this device



Device File: FFT vocoder 1.2.amxd


this device is quiet when placed on both a midi and an audio channel while also being routed to from a midi channel carrying kontakt. How can I solve this?

Login to comment on this device.

Browse the full library