Re: [Jack-Devel] buffer size callback, revisit

On Tue, Feb 15, 2011 at 12:36 PM, Jack O'Quin <[hidden]> wrote:
> On Tue, Feb 15, 2011 at 11:21 AM, Paul Davis <[hidden]> wrote:
>
>> this is true EVEN IF the client registered a buffer size callback. why
>> so? despite the suggestion in the API docs for the buffer size
>> callback, existing implementations do NOT guarantee to call the
>> client's buffer size callback from within jack_activate(). this means
>> that there is no reliable way for a client to know the port buffer
>> size before its first process callback. the buffer size callback will
>> notify it of later changes to the size, but not the initial size when
>> it gets its first process() call.
>
> Perhaps a stupid question: why not ensure the buffer size callback
> *is* invoked before the first process callback?

that's part (2) of the proposal.

the problem is that clients can't know whether a given implementation
will do that or not. so they cannot rely on their callback correctly
setting the value(s).

1297792021.26392_0.ltw:2,a <AANLkTimpVZxfY1+BK3PkWZKVNQWvKnZ_3GhC5-myJCkt at mail dot gmail dot com>