Re: [LAD] Plugin buffer size restrictions

From: Fons Adriaensen <fons@email-addr-hidden>
Date: Sat Jun 02 2012 - 01:56:45 EEST

On Fri, Jun 01, 2012 at 06:42:01PM -0400, David Robillard wrote:
> On Fri, 2012-06-01 at 22:22 +0000, Fons Adriaensen wrote:
> > On Fri, Jun 01, 2012 at 06:09:06PM -0400, David Robillard wrote:
> >
> > > LV2_Buf_Size_Status
> > > get_block_length(LV2_Buf_Size_Buf_Feature_Handle handle,
> > > uint32_t* min,
> > > uint32_t* max,
> > > uint32_t* multiple_of,
> > > uint32_t* power_of);
> > >
> >
> >
> > > This callback just describes reality to the plugin at instantiation
> > > time.
> >
> > That 'to the plugin' confuses me - isn't this supposed to be
> > the plugin telling the host what it (the plugin) needs ?
>
> This is a host-provided callback which the plugin can use at
> instantiation time to figure out the block length characteristics,
> whatever they may be.

(Maybe it's just too late for me to grok this...)

So it's the plugin asking the host what it can expect ?
Isn't the LV2 way to do this via features (i.e. the plugin
checking which features the host provides) ?

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
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Sat Jun 2 04:15:02 2012

This archive was generated by hypermail 2.1.8 : Sat Jun 02 2012 - 04:15:02 EEST