Content-Type: text/plain; charset=ISO-8859-1
On Tue, Jul 10, 2012 at 3:58 PM, James Harkins wrote:
> OK... I am having a really strange problem with qjackctl. Ubuntu 12.04,
this is pointless. there is no difference between this and -d hw:1
Content-Type: text/html; charset=ISO-8859-1
On Tue, Jul 10, 2012 at 3:58 PM, James H=
arkins <email@example.com> wrote:
OK... I am having a really strange problem with qjackctl. Ubuntu 12.04, Jac=
k 1.9.8, qjackctl 0.3.8.
I've chosen my USB audio interface for capture and playback -- .jackdrc=
looks like this:
/usr/bin/jackd -P70 -dalsa -r44100 -p1024 -n2 -D -Chw:1 -Phw:1,0this is pointless. there is no difference between this and -=
But, when qjackctl starts jack, it uses -Chw:0 -Phw:0.
What's even more strange is that it was working yesterday. Today, no lu=
ck. No matter what I choose for the capture and playback devices, it always=
uses the laptop's built-in hardware. But, if I run the jackd command i=
n the terminal, it DOES use the right device. So it seems simply that qjack=
ctl is issuing the wrong command.
As another test, I changed the hardware buffer size, but that is used corre=
ctly. So it's only the devices.
I've heard of other problems with qjackctl vs. jackdbus -- is qjackctl =
the wrong tool? What is the right tool?
Sorry if this is too basic a question. jackaudio.org is, unfortunately, no help at all: I would=
have thought the page about "Configuring and running a JACK server&qu=
ot; would explain:
... but it's empty.
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." =A0-- Whitman
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
Linux-audio-user mailing list