2011/3/27 Peder Hedlund <peder@email-addr-hidden>
> Quoting Cedric Roux <sed@email-addr-hidden>:
>
> ----- "Paul Davis" <paul@email-addr-hidden> wrote:
>>
>> On Fri, Mar 25, 2011 at 7:09 PM, Cedric Roux <sed@email-addr-hidden> wrote:
>>>
>>> > something. There are issues, like jack refusing to work with
>>> > buffers of less than 512 frames (I am not with a rt kernel)
>>>
>>> when you say "refuse" do you mean "will not start" or "performs
>>> badly"?
>>>
>>
>> jackd -d alsa -C hw:2 -P hw:0 -r 44100 -p 256
>>
>> leads to:
>>
>> jackdmp 1.9.6
>> JACK server starting in non-realtime mode
>> Cannot lock down memory area (Cannot allocate memory)
>> creating alsa driver ... hw:0|hw:2|256|2|44100|0|0|nomon|swmeter|-|32bit
>>
>
> 1. You aren't running jack with realtime priorities and memory locking.
> Make sure you're in the audio group, have "@audio - rtprio 99" and
> "@audio - memlock unlimited" in /etc/security/limits.d/audio.conf and
> start jack with a "-P 70" flag prior to "-d alsa".
>
As it's Ubuntu 10.10, this configuration takes place in
/etc/security/limits.d/audio.conf instead of /etc/security/limits.conf !
jy
>
> 2. Built in Intel soundcards usually work better with 3 periods per buffer
>
> 3. Why are you using different soundcards for capture and playback?
>
>
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@email-addr-hidden
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Sun Mar 27 16:15:03 2011
This archive was generated by hypermail 2.1.8 : Sun Mar 27 2011 - 16:15:03 EEST