10 Jul
2016
10 Jul
'16
5:30 p.m.
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 here since what I
had in mind was that the streams could accommodate
either 'live' or 'offline file' data, in a 'live realtime' mixing
sense.
A stream info flag could indicate that the stream is in fact
'stretchable' or not.
Thus both 'live' and 'file' input could be mixed agnositcally.
The goal would be to have, say LV2, support time-stretch plugins.
Imagine Rubberband as an LV2 stretch plugin.
The plugin can ask for more or less input data.
It seems this is the only type of processing that can't easily
be supported by current plugin architectures, without building
special embedded support into the application, since it requires
pulling variable lengths of input data.
Thanks.
Tim.
On Sat, Jul 9, 2016 at 6:06 PM, Paul Davis <paul(a)linuxaudiosystems.com>
wrote:
> VAMP does this.
>
> But such architectures are inherently not realtime.
>
> On Sat, Jul 9, 2016 at 5:56 PM, Tim E. Real <termtech(a)rogers.com> 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, for example via some kind of stream?
>>
>> Instead of passing 'run' a block of data, host would
>>
>> pass these streams so that 'run' can pull and push
>> whatever lengths it needs.
>>
>> There would be compatibility information on each
>>
>> stream so that other streams could accommodate.
>>
>> I thought I read of an LV2 extension or something...
>> Or am I imagining something like Pulse?
>>
>> Thanks.
>> Tim.
>>