I'm having one issue so far with the MVocoder AU. It shows up as having two stereo audio inputs (one for carrier, one for modulator) in both Plogue Bidule and Live, but not in Numerology. Numerology doesn't seem to have problems with other plugins that can have multiple audio inputs, such as Reaktor. Does the MVocoder AU provide its I/O configuration information to the host in an unconventional way?

I'm not sure whether the problem lies with the plugin or the host, so I've also posted this problem to the Numerology forums at five12.net.

Well, I don't think I have heard about Numerology so far, but it seems working in all other AU hosts, so I'd assume it is problem in it. Don't you have surround enabled btw? Some hosts don't like it (though I'm not aware about any AU host like that). Though our plugins can all have any number of input channels from any input bus up to the maximum, while most plugins are simply 2->2 or something, so maybe that's what confuses Numerology. If they won't know, just let them contact me via info@meldaproduction.com .

Of course! It's simple reverse psychology....



Yeah, maybe...? Except for the (obvious) Chicken Soup question...

you assume wrong.
(but I assume your plugin sucks, am I right?)

You are saying Vocodex is based on filters? Then how it is possible that Vocodex CPU usage grows like 10x when you make band distribution so that most bands are located on higher frequencies? This looks like FFT...

Can this create the classic Cylon sound?

You mean robot voice right? Sure, try using a bass line as main input, something rich, saw-tooth based.

Ok guys, i spent almost 2 hours with this, and i am officially completely lost. i had modulator panned left carrier right, put M vocoder, (tried flipping just in case)

even ran through every preset, i can not get any sound out of it. VST in ableton live.

Never had this problem before it's weird.

It works with Orange this way, etc.

the draft mode (processing lower bands at lower rate) would do that, except not 10x, that's not possible




It's not. Surely you can tell by the lack of latency? To get this precision on low bands you'd need a very big FFT, thus huge latency.
Also if it was FFT-based it'd have the opposite effect of what you describe, all bands on higher freqs would rely on a smaller FFT, thus it'd be faster.

And I would prefer it based on FFT, if it was possible without latency..

tony: ok, but I think the idea was correct - higher frequencies would be based on more FFT bins.

ttoz: I think the problem must be in routing in Live. I'll check it out, but so far it looks working just fine in all tested hosts.

ok well it's my only non reason host installed now

i have the reason and ableton vocoder examples ready just need to get the melda one... the vocal and pad is ready

I spent some time searching but I don't see how to use a side-chain with any plugin with Live. Can you give me a few hints?

I'm sure there are more efficient ways, but you can have the carrier signal in one track, the modulator in the second track and then make the third track an empty audio track with MVocoder as an effect. In the first track, route the audio (using Audio to) to the the third track, Track in. In the second track, route the audio to the third track, 3/4-MVocoder. This works for me.

ok that's what i thought i did.

I might have to install the AU then for native ableton sidechain though. But i did the routing pan left and right method

MVocoder now doesn't support left/right routing, it's just mono, seems too limited. I think you will have to use AU version in Live, because VST support for side-chains is kind of clumsy.