On 2/14/06, Istvan Varga wrote: > On Tuesday 14 February 2006 20:59, Ben McAllister wrote: > > > 1) "The default is 1024" - is this default (and other cmdline > > defaults) taken from SOLELY from .csoundrc, or is there another spot > > in addition to .csoundrc where these are defined i.e somewhere in the > > source? > > The defaults are in the source code, and depend on platform. For example, > -B really defaults to 1024 on Linux, but the default is 4096 on MacOS X, > and 16384 on Windows (so that MME on Win9x will not have dropouts). > Of course, the settings in .csoundrc (if any) override these, and you can > set there whatever "default" you like. Hmm - ok thanks for the clarification. Could you point me to the file in the source where these are defined? > > > If so, could we externalize it all to .csoundrc? > > So, what would happend then if .csoundrc is removed ? Some defaults > do need to be present in the source code. Good point re: the removal of .csoundrc. I was thinking it could be auto-gen'd if not present. > > > 2) I alluded to this question before, but now I'll ask it outright: > > what is the expected behavior, on Windows, for the interaction between > > the control panel/driver for a given device, and this -B option. I > > would expect the DMA buffer size for my device to be controlled by > > this setting, and it SOUNDS like it is, though the Control Panel UI > > for two different sound cards fails to update. > > In the case of PortAudio, the -B parameter (more precisely, -B / sr) is > passed as the "suggested latency" value. Other than that, Csound has no > control over how PortAudio interprets the parameter. Thanks - I think this is worth putting into the manual, personally. b