Well, technically, VAMP doesn't really do audio-in=>audio-out plugins at all, but rather audio-in=>metadata out, so that doesn't really count. but fundamentally in != out == analysis not realtime. On Sat, Jul 9, 2016 at 6:06 PM, Paul Davis <paul(a)linuxaudiosystems.com> wrote:

On Sun, 2016-07-10 at 11:30 -0400, Tim E. Real wrote: Adding new port types to LV2 is a possibility, or some other interface to specify that out != in, but I think an arbitrary pull model where the plugin requests data doesn't really make sense in this context. At some level, the host needs to be requesting a certain amount of processing time / amount of input data / amount of output data, and having situations like the plugin asking for amounts that are simply impossible at the current time doesn't lead anywhere good. It seems more reasonable to me, and more in-line with how streaming audio plugin APIs work, to add an interface where the plugin can specify the number of output samples that correspond to some number of input samples (or vice-versa) and keep everything else the same. Though one might question how sensible it is to use a streaming audio API like LV2 in the first place for such things... I think gstreamer has facilities very much like what you are describing, though. -- dr