3 Aug
2010
3 Aug
'10
12:06 a.m.
On Mon, Aug 2, 2010 at 5:15 PM, Arvind Venkatasubramanian
<mdu.arvind(a)gmail.com> wrote:
[Arvind@laspr-01 ~]$ jaaa -J -d hw:Intel -r 16000
Connected to JACK with 4 inputs and 4 outputs
mlockall: Cannot allocate memory
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That's the error in that instance.
However for higher sampling rates, I am able to open
JAAA without even
issuing jackd command to start JACK separately.
[Arvind@laspr-01 ~]$ jaaa -A -d hw:Intel
Not suprising, since you're EXPLICITLY telling jaaa to use its own
ALSA backend, and not to use JACK.
While JAAA is running, I am not able to start Jdelay.
Once JAAA operates
alongside other Jack applications, I will be able to patch the output of
JACK requires more-or-less exclusive access to the audio interface. If
jaaa is using it (via its own ALSA backend), then JACK cannot run.
You seem quite confused about the role of JACK and ALSA.
--p