Content-Type: text/plain; charset=ISO-8859-1
I hoe that I'm not totally out of context,
but wouldn't that introduce latency to the control signal (AD/DA
Why would it be preferable over MIDI in first place?
On Sun, Sep 25, 2011 at 8:13 PM, Renato wrote:
> Hello, I've never used hardware that uses VC, but sometime ago I had an
Content-Type: text/html; charset=ISO-8859-1
I hoe that I'm not totally out of context, but wou=
ldn't that introduce latency to the control signal (AD/DA conversion)? =
Why would it be preferable over MIDI in first place?cheers
Moshe=A0On Sun, Sep 25, 2011 at 8:13=
PM, Renato <renn=
Hello, I've never used hardware that uses VC, but sometime ago I had an=
idea, that probably many others have allready exploited (never heard of
If a control signal is exactly the same as an audio signal,
just very lower in frequency, one could apply all the usual audio
effects to control signal. You could for example turn a knob, have the
signal it generates pass through a delay, reverb or whatever, and then
have it control something (like the frequency of a synth).
This seems an interesting idea I'd like to play with - the problem is,<=
how can you do it in our linux-audio environment, where usually the
knob generates midi CC data? Is it possible with some tricks to convert
this to an audio signal (maybe way downsampled to not uselessly waste
CPU) pass it through rakarrack or ladspa plugins, reconvert it to midi
CC and have it control something?
A more general thought: what about implementing a new type of generic
"control" signal in JACK, and having existing audio apps accept t=
signals in their input? If you come to think of it, there's really no
difference (other than sample rate) between a control signal and an
audio signal, so there's no reason why one shouldn't be able to do =
on control signals.
Linux-audio-user mailing list