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

PrevNext  Index
DateTue, 15 Feb 2011 12:21:12 -0600
From Jack O'Quin <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] buffer size callback, revisit
Follow-UpPaul Davis Re: [Jack-Devel] buffer size callback, revisit
On Tue, Feb 15, 2011 at 12:13 PM, Paul Davis <[hidden]> wrote:

> you have a client. it registers a buffer size callback. it relies on
> it to get the current buffer size.

Ah. I was assuming it had to initialize things, first.

Clearly not an elegant interface, but that's what it requires, right?

> you compile it.
>
> you (or someone) runs it.
>
> how do you know if the callback will be made before the first process callback?
>
> obviously you can find out if it *was* made, but that falls into the
> category of "less correct" approaches that i mentioned.

You'd have to code it to work correctly either way. I'm still not
quite sure why that's not possible.
-- 
 joq
PrevNext  Index

1297794089.30736_0.ltw:2,a <AANLkTi=WwSWftBbSXaDYELHawTsyMNoqYXFM8_fTDooy at mail dot gmail dot com>