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

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?

Is that because it cannot be called in the realtime thread?
-- 
 joq

1297791387.24951_0.ltw:2,a <AANLkTikHS1_NvXd0sCwhMEAU3RDWn6ppa7UW35LO9Jcq at mail dot gmail dot com>