Hi Lily, On 1/17/07, dark141@gmail.com wrote: > what i don't understand, is, if csound can tell you what buffer size it's > supposed to use, WTF can't it just go ahead and use it? I just experimented with the ALSA driver to go ahead and accept what was given by ALSA rather than just failing and reporting to the user. Unfortunately that doesn't quite work by itself. musmon (in Engine/musmon.c) seems to do a lot of checking of -b and -B values before setting, and it does the setup of Csound's inbuffer and outbuffer sizes *before* opening the rtaudio. So, even if it just accepts the value within the Alsa driver, if it doesn't get the exact value that was requested, there'll be a mismatch between Csound and the driver's buffer size. (In the experiment I tried, it would let Csound run but no audio was heard and I imagine a memory leak of some sort was probably going on.) I don't know the setup code there very well but that's the basic issue I'm finding so far. I think a possible change would be to initiate csound's buffer sizes after opening the audio IO in musmon. The drivers would then have to change OPARMS directly so that musmon picks up the change. steven ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net