I too would hope that we can keep flag differences as minimal as possible
among platforms and situations.  Hopefully, once kinks are worked out,
Csound5 *will* work as much "out of the box" as possible.

In other words, "bulletproof" is a worthy objective.

Art Hunkins
----- Original Message -----
From: "Victor Lazzarini" 
To: "Csound Developers Discussion List" 
Sent: Friday, January 07, 2005 11:38 AM
Subject: [CSOUND-DEV:5649] RE: ASIO full-duplex, update.


> Perhaps there's a better solution: I had a look at
>
>
http://www.portaudio.com/docs/proposals/004-CallbackVariableFramesPerBuffer.
html
>
> Perhaps we should re-think the code to use the frameCount argument to the
> callback and make the callback IO buffers independent of the ksmps value.
> However, this has not been implemented on coreaudio, it seems.
>
> The whole trouble is that some of docs are v.18 and the behaviour of v.19
> seems to
> be very different.
>
> In any case, I think realtime audio should work regardless of the value of
> ksmps and
> nchnls; it shouldn't be the case of having right values for these
parameters.
>
> Victor
>
> At 16:31 07/01/2005, you wrote:
> >I think it only means you have to have the right values for -B, -b, and
> >ksmps. Why should we expect the old flags to work out of the box with a
new
> >driver?
>
>
>
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>