Thanks Steven! I have another question or two before I give you a change, but at least now I know who to bug! -=-=-- Here's the manual entry for -B at http://www.csounds.com/manual/html/CommandFlags.html "-B NUM, --hardwarebufsamps=NUM Number of audio sample-frames held in the DAC hardware buffer. This is a threshold on which software audio I/O (above) will wait before returning. A small number reduces audio I/O delay; but the value is often hardware limited, and small values will risk data lates. The default is 1024." 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? If so, could we externalize it all to .csoundrc? 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. If this is 'by design', then I think it's worth noting in the manual. It's confusing when you're trying to debug realtime I/O problems, as I have been recently. Thanks - b On 2/14/06, Steven Yi wrote: > I guess I'm keeping somewhat of a watch over the manual. You'll have > to either register on sourceforge and get added to the project if you > want to commit the change directly, or you can anonymous check out the > manual source and email me modified files or diffs. Otherwise, > there's a README that is in the manual CVS that explains about adding > entries if you think it is necessary. You can also just email me text > to change with instructions on where it should be incorporated in the > manual. > > Perhaps what we need is an FAQ in addition to the manual? (I'm sure > there's got to be a small php tool we could add to csounds.com that > would be easy to setup and maintain.) > > steven > > > On 2/14/06, Ben McAllister wrote: > > "Powers-of-two are a good bet, as a rule of thumb." - not what I was > > taught at university, actually, but I'm glad to know it now. Could we > > update the manual? Who's in charge of that? I'd be happy to check it > > out from cvs at sourceforge and make a modification - is there a > > process I should follow? > > > > Thanks again for your help everyone - b > > > > On 2/14/06, Victor Lazzarini wrote: > > > Yes, that is possible, because different ASIO drivers might > > > have different restrictions for the buffer sizes they allow. Powers-of-two > > > are a good bet, as a rule of thumb. > > > > > > Victor > > > > > > At 23:32 13/02/2006, you wrote: > > > >FYI: I was unable to get rid of clicks unless both -b and ksmps were > > > >powers of 2 >= 128. I couldn't match your results with 400, 200 or > > > >100 for -b. > > > >b > > > > > > > >On 2/10/06, Victor Lazzarini wrote: > > > > > It seems to be with any setting of -b that is an integer > > > > > multiple of ksmps. I originally tested with -b400, coming > > > > > down from -b512 which was giving me clicks. But the > > > > > clicks are there with -b1024 and -b2048, as well as -b4096. > > > > > > > > > > I was thinking about why this is the case, since it does not > > > > > make much sense as you said. Without looking at the code > > > > > (I was on my way home), I speculated whether this is caused > > > > > by the lock mechanism. > > > > > > > > > > The interesting thing (and this is why I thought), is that > > > > > while > > > > > the clicks are there on input, they're not on signals > > > > > generated > > > > > by Csound. On the same performance, an instrument with RT > > > > > input has clicks, while an instrument with say, an > > > > > oscillator, > > > > > does not. So the clicks are being generated at the input, > > > > > possibly at the buffering, and that's why I think the locks > > > > > are involved. Somehow, the buffering needs to be 'in sync'. > > > > > What do you think? > > > > > > > > > > Victor > > > > > > > > > > > > > > > > > On Friday 10 February 2006 19:07, Victor Lazzarini wrote: > > > > > > > > > > > > > But hey, I found out why! > > > > > > > > > > > > > > It just happens that -b has to be a multiple of ksmps. I > > > > > > > have not checked the code, but it's simple. With -b512 > > > > > > > and ksmps=100, clicks are there, but with -b100 (or > > > > > > -b200), the sound is perfect. > > > > > > > > > > > > Are you sure the clicks go away because of the -b/ksmps > > > > > > ratio, and not simply because -b is lower ? What happens > > > > > > if you use ksmps=64 or ksmps=128 with -b 512 ? Also, what > > > > > > is -B set to ? The rtpa plugin does not know about ksmps, > > > > > > and if there is a bug in libsnd.c (where the buffering > > > > > > from -b to ksmps samples is done), it should also affect > > > > > > file input. -- > > > > > > Send bugs reports to this list. > > > > > > To unsubscribe, send email to > > > > > > csound-unsubscribe@lists.bath.ac.uk > > > > > -- > > > > > Send bugs reports to this list. > > > > > To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk > > > > > > > > > > > Victor Lazzarini > > > Music Technology Laboratory > > > Music Department > > > National University of Ireland, Maynooth > > > > > > -- > > > Send bugs reports to this list. > > > To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk > > > > > -- > > Send bugs reports to this list. > > To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk > > > -- > Send bugs reports to this list. > To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk >