I've got a new .csd that runs without incident via a recent SoaS build on a 
USB stick (Fedora Sugar on a Stick) - on my desktop, several XO's, and an 
eeePC netbook. However, it's doing strange things on a 2goPC netbook.

The values for -b and -B I'm using are tried and true both in Windows and 
(to now) on Linux: -b128, -B2048. On the problem netbook, these values work 
well for 48000, 32000 and 16000 SR, but fail at 44100 and 22050 SR with the 
message (I'm using only ALSA on Linux):
ALSA: -bxx not allowed on this device; use xx instead
where -b128 suggests using 204 instead,
-b204 (in turn) suggests 320
-b320 suggests 248
and 248 works! - indeed it works for *all* the above SR's

OTOH, -b248 doesn't work for all the above SR's on my *other* machines (same 
SoaS stick).

I presume that this has something to do with the way ALSA interacts with 
the -odac on my different machines.

Can anyone shed light on this particular anomoly?

(I presume I should leave the -b128 and -B2048 values that work for most 
machines, as I'm inviting users to try different (lower) SR's when they need 
to [less powerful machines]. This is what I've done previously, especially 
for my work with the XO's.)

Art Hunkins 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"