On Wed, Mar 2, 2011 at 8:54 PM, David Robillard <d@email-addr-hidden> wrote:
> On Wed, 2011-03-02 at 20:36 -0500, Paul Davis wrote:
> [...]
>> well, almost. as i mentioned, AU doesn't really route parameter
>> changes via the host, it just makes sure that the host can find out
>> about them. the nicest part of the AU system is the highly
>> configurable listener system, which can be used to set up things like
>> "i need to hear about parameter changes but i don't want to be told
>> more than once every 100msec" and more. its pretty cool.
>
> Do you think this could be adequately expressed as a few fixed cases,
> like "full data transmission", "rapid updates" (very roughly once every
> few blocks and/or screen refreshes), "moderate updates" (very roughly
> every second or so), "slow updates" (very roughly every few seconds)?
well, as we've discussed on IRC, its a bit more than that. its also
"inform me via the following event loop". but yeah, i suspect that
your reduction would be sufficient for all purpose. the event loop
part .. that seems a bit harder to do in a neutral way.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Thu Mar 3 04:15:05 2011
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2011 - 04:15:06 EET