27 Mar
2011
27 Mar
'11
1 p.m.
2011/3/27 Peder Hedlund <peder(a)musikhuset.org>
Quoting Cedric Roux <sed(a)free.fr>fr>:
----- "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
As it's Ubuntu 10.10, this configuration takes place in
/etc/security/limits.d/audio.conf instead of /etc/security/limits.conf !
jy
On Fri, Mar 25, 2011 at 7:09 PM, Cedric Roux <sed(a)free.fr> wrote:
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".
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"?
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(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user