Are there any plugin architectures that allow
input data length different than the output length
such that the 'run' function can ask for more or less
input data, for example via some kind of stream?
Instead of passing 'run' a block of data, host would
pass these streams so that 'run' can pu
VAMP does this.
But such architectures are inherently not realtime.
On Sat, Jul 9, 2016 at 5:56 PM, Tim E. Real wrote:
> Are there any plugin architectures that allow
> input data length different than the output length
> such that the 'run' function can ask for more or less
> input data, fo
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
wrote:
> VAMP does this.
>
> But such architectures are
On Saturday, July 9, 2016 6:07:37 PM EDT you wrote:
> 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.
The term 'realtime' would be a bit muddy
On Sun, 2016-07-10 at 11:30 -0400, Tim E. Real wrote:
> On Saturday, July 9, 2016 6:07:37 PM EDT you wrote:
> > 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 ==
