The same error, unfortunately.

Interestingly, with sr=44100, ksmps=100, -B 2048 and either -b 128 or 256, 
ALSA says -b 128 and 256 are invalid, and to use -b 204.

When using -b 204, it says to use -b 320.

When using -b 320, it says to use -b 248.

-b 248 works. (I just wonder *why*.)

Art Hunkins

----- Original Message ----- 
From: "joachim heintz" 
To: 
Sent: Tuesday, November 30, 2010 4:17 PM
Subject: [Csnd] Re: ALSA and -b weirdness


> what happens if you try ksmps=64 and -b 256?
>
>
> Am 30.11.2010 um 22:06 schrieb Art Hunkins:
>
>> I've got the following CsOptions in a .csd:
>>
>> -odac -+rtaudio=alsa -+rtmidi=alsa -M hw:1,0 -m0d --expression-opt - 
>> b128 -B2048 -+raw_controller_mode=1
>>
>> I'm running Sugar-on-a-Stick (Fedora/Linux). *On certain hardware  only* 
>> (particularly an Intel Classmate PC, but others as well) I get  the 
>> following error message in my log (crash):
>>
>> ALSA: opened MIDI input device 'hw:1,0
>>
>> orch now loaded
>>
>> audio buffered in 128 sample-frame blocks
>>
>> ALSA: -b 128 not allowed on this device; use 204 instead
>>
>> *** Error setting period time for real-time audio
>>
>> Failed to initialize real time audio output
>>
>>
>>
>> All works fine on most systems. My SR = 44100 (stereo); Ksmps = 100.  If 
>> I change to SR = 48000 or SR = 32000, no problem. (BTW, changing  to -b 
>> 204 doesn't work either; if I change to the recommended -b  value, *at 
>> the third or fourth recommendation* [each time it  recommends a new 
>> value], it works.
>>
>> Any idea what is happening?
>>
>> 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"
>>
>>
>
>
>
> 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"
> 



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"

Sounds like a dmix thing, which I remember used to do that. Not sure  
if anyone still uses dmix though.
On 3 Dec 2010, at 19:57, Art Hunkins wrote:

> The same error, unfortunately.
>
> Interestingly, with sr=44100, ksmps=100, -B 2048 and either -b 128  
> or 256, ALSA says -b 128 and 256 are invalid, and to use -b 204.
>
> When using -b 204, it says to use -b 320.
>
> When using -b 320, it says to use -b 248.
>
> -b 248 works. (I just wonder *why*.)
>
> Art Hunkins
>
> ----- Original Message ----- From: "joachim heintz"  >
> To: 
> Sent: Tuesday, November 30, 2010 4:17 PM
> Subject: [Csnd] Re: ALSA and -b weirdness
>
>
>> what happens if you try ksmps=64 and -b 256?
>>
>>
>> Am 30.11.2010 um 22:06 schrieb Art Hunkins:
>>
>>> I've got the following CsOptions in a .csd:
>>>
>>> -odac -+rtaudio=alsa -+rtmidi=alsa -M hw:1,0 -m0d --expression-opt  
>>> - b128 -B2048 -+raw_controller_mode=1
>>>
>>> I'm running Sugar-on-a-Stick (Fedora/Linux). *On certain hardware   
>>> only* (particularly an Intel Classmate PC, but others as well) I  
>>> get  the following error message in my log (crash):
>>>
>>> ALSA: opened MIDI input device 'hw:1,0
>>>
>>> orch now loaded
>>>
>>> audio buffered in 128 sample-frame blocks
>>>
>>> ALSA: -b 128 not allowed on this device; use 204 instead
>>>
>>> *** Error setting period time for real-time audio
>>>
>>> Failed to initialize real time audio output
>>>
>>>
>>>
>>> All works fine on most systems. My SR = 44100 (stereo); Ksmps =  
>>> 100.  If I change to SR = 48000 or SR = 32000, no problem. (BTW,  
>>> changing  to -b 204 doesn't work either; if I change to the  
>>> recommended -b  value, *at the third or fourth recommendation*  
>>> [each time it  recommends a new value], it works.
>>>
>>> Any idea what is happening?
>>>
>>> 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"
>>>
>>>
>>
>>
>>
>> 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"
>
>
>
> 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"
>



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"