On Mon, May 28, 2012 at 12:00:36AM +0300, Stefano D'Angelo wrote: > So far so good, but in practical terms how could a plugin API allow > all use cases without requiring the plugin writer to do twice the > work? The only solution I can think of is "getting future values" in > case a host can provide them, but maybe there is a better way?
If you really want 'sample accurate' control for bandlimited controls then the host must provide future values. Which is not more difficult than providing latency compensation for audio signals, at least not if the control rate is fixed. It's not at all an issue for the plugin code and you certainly don't need two versions of it. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow) _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
