[LAD] CV data protocol in apps.
paul at linuxaudiosystems.com
Sat Feb 20 12:46:55 UTC 2010
On Sat, Feb 20, 2010 at 7:23 AM, <fons at kokkinizita.net> wrote:
> For example it would be quite hairy to use discrete
> events to create a C1 continuous control signal -
> C1 means no 'jumps' and no 'corners'. It can be done
> but would require a level of complexity that breaks
> the charms of the basic idea and would make most
> potential users run away screaming. Just combining
> (adding) two such streams with non-coincident events
> would be a real nightmare.
i don't think that anyone is suggesting that a continuous control
signal is a bad idea. the issue is whether its worth providing an
intermediate level of resolution between "audio rate" and "arbitrarily
timestamped events", since the latter case can be used to provide the
exact same level of data "density" as anything else.
> Having non-power-of-2 period sizes complicates the
> picture. When and why was this allowed ? I'm pretty
> sure it will break a lot of code (including some of
> mine, including probably Aeolus and Jconvolver).
USB devices function much better with periods based on the h/w period
size of 1msec.
More information about the Linux-audio-dev