Thomas Strathmann

I'm trying to create a little vocoder effect, but have not found a way to make something like a sidechain input in Live's built-in vocoder to route an optional carrier signal into the M4L audio device. Is this at all possible and if not what would be the "idiomatic" workaround for this M4L problem? Thanks!

sidechain-input-in-m4l

Are you making a wrapper for Live's vocoder? Or are you making a completely new device? Or is your device making use of some features of Live's vocoder?

If I try to make some conclusions about transfering signals from one device or track to another in MFL I would say that it is possible, but the latency is quite high. If the sidechain is importing a slowly evolving pad, or something like that, delay probably is no issue.

The plugsync~ and plugreceive~ pair might do the trick in cases like this.

If I try to make some conclusions about transfering signals from one device or track to another in MFL I would say that it is possible, but the latency is quite high. If the sidechain is importing a slowly evolving pad, or something like that, delay probably is no issue. 

The plugsync~ and plugreceive~ pair might do the trick in cases like this.


As I wrote I am building a new effect. Why do you think the latency would be high? Sadly the source code to Live is not available so I do not know how exactly they handle audio routing but normally latency should not be an issue at all. Would using plugreceive~ incur some intolarable latency? Do you perchance have an example that demonstrates this?

Here is a thread with some latency tests. You may check it yourself.

https://cycling74.com/forums/m4l-audio-not-sending-to-midi-track

Sidechain input in M4L