On Thu, Jul 15, 2010 at 4:16 PM, Jeremy <autostatic@gmail.com> wrote:

Louigi Verona wrote:

Okay, last message for today.

Eventually I could partially reproduce. If I create a stereo Vocoder track FIRST, then the latter mono carrier and modifier tracks would channel into Vocoder provided I press "monitor" on it. But the output is a weird mix of vocoded signal and the modifier. If I change modifier and carrier places - the signal does not change. Why would track creation matter I do not know. Rui?

The reason why you get a mixed signal could be because you use both outputs of the Vocoder track. The vocoder LADSPA plugin outputs the dry signal on the second output and the vocoded signal on the first output. That's why I connected the first output of the Vocoder track to both inputs of the Vocoder Mix track, like this you have faux-stereo and better control over the output of the Vocoder track.

Ah, this could be the reason. I will recheck carefully. I think I tried routing only one but I am not sure.

Also, when Vocoder does not receive anything, it starts to generate XRUNs, so if you close Qtractor while Vocoder is activated, Qtractor will freeze.

The more bands you select in the vocoder LADSPA plugin, the more CPU it takes, so bigger chance for xruns. I didn't thoroughly test this setup yet so it might be something else.

LADSPA vocoder in JACK Rack has the same problem. Being already pretty experienced in this regard (hehehe) I can say that this is because of an effect which I forgot how is called when the plugin stops receiving the signal but continues to try to process data and starts going into calculations of really small numbers and it triggers a software part of your CPU and it uses a lot of resources, these calculations. The developer should find a way to fix this somehow.

Best,

Jeremy
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev