[LAD] "enhanced event port" LV2 extension proposal
nedko at arnaudov.name
Fri Nov 30 10:36:11 UTC 2007
Lars Luthman <lars.luthman at gmail.com> writes:
> On Thu, 2007-11-29 at 14:55 +0200, Nedko Arnaudov wrote:
>> Lars Luthman <lars.luthman at gmail.com> writes:
>> > On Thu, 2007-11-29 at 05:59 +0200, Nedko Arnaudov wrote:
>> >> Also, i doubt we need three "count" members in Event_Port_Buffer
>> >> structure. used_size - number of used events is perfectly fine by
>> >> itself. I dont see why plugin should know whether buffer is actually
>> >> larger.
>> > It needs to know that for an output buffer.
>> Well, port is either input or output, why not use same variable/member
>> (with appropriate naming)?
> You could, but there isn't really much to gain from it. The host will
> want to keep track of the buffer capacity in some way so those 4 bytes
> have to go somewhere, and I think having the same variable mean
> different things for input and output buffers makes things more
And supplying things to plugins that they should not (and do not) care
about is not confusing? And we assume that plugins would be more than
hosts after all...
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 188 bytes
Desc: not available
More information about the Linux-audio-dev