Re: [LAU] Confusing qjackctl playback devices, no jackd output

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Len Ovens <len@...>
Cc: linux-audio-user <linux-audio-user@...>
Date: Tuesday, July 8, 2014 - 1:58 pm

--001a11c068fee3b56304fdaefab8
Content-Type: text/plain; charset=UTF-8

On Tue, Jul 8, 2014 at 9:22 AM, Len Ovens wrote:

>

this isn't related to jack sensing. on my main system, opening hw:0,n
provides an 8 channel device with the first two channels on outputs 1+2;
opening hw:0,m provides a 2 channel device with output on 7&8.

--001a11c068fee3b56304fdaefab8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 8, 2014 at 9:22 AM, Len Ovens <len@ovenwerks.net&g=
t; wrote:

HDA audio has a unique "feature" called "jack sensing" =
(jack in this case is not jackd) where it changes how the audio interface i=
s laid out by what it senses you have plugged in. This allows the MB to hav=
e fewer HW jacks while still having lots of i/o. there is an application ca=
lled HDAJackRetask that _may_ help. Be aware that plugging and unplugging t=
hings will change how things are set up. Dirty contacts may effect things t=
oo.
this isn't relat=
ed to jack sensing. on my main system, opening hw:0,n provides an 8 channel=
device with the first two channels on outputs 1+2; opening hw:0,m provides=
a 2 channel device with output on 7&8.
=C2=A0

--001a11c068fee3b56304fdaefab8--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Confusing qjackctl playback devices, no jackd output, Roberto Suárez Soto, (Tue Jul 8, 12:04 pm)
Re: [LAU] Confusing qjackctl playback devices, no jackd output, Paul Davis, (Tue Jul 8, 1:58 pm)