8 Oct
2013
8 Oct
'13
7:15 a.m.
On 09/19/2013 04:20 PM, Erik Steffl wrote:
On 09/19/2013 02:46 AM, Clemens Ladisch wrote:
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1228727
created the bug above, turns out there is a way to make qjackctl work
but it involves clicking on the mysterious '>' buttons next to the
dropdowns (the dropdown menus in question are: Interface, Input Device,
Output Device in the Setup dialog)
The tooltips for '>' buttons do not explain much (they seems to be
pretty much the same as tooltips for dropdowns.
Details in the bug, here's the summary of what the tooltips say and
what the menus (dropdown and '>' buttons) offer:
Interface dropdown tooltip: 'The PCM device name to use'
Interface '>' tooltip: 'Select PCM device name'
Input device dropdown tooltip: 'Alternate input device for capture'
Input device '>' tooltip: 'Select input device for capture'
Output device dropdown tooltip: 'Alternate output device for playback'
Output device '>' tooltip: 'Select output device for playback'
The values for all dropdown menus are:
- (default)
- /dev/dsp
- /dev/audio
- plughw:0
- hw:0
The values for all '>' menus:
- hw:0 HD-Audio Generic
- hw:1 HDA ATI SB
- hw:1,0 ALC892 Analog
- hw:2 BR-80(AUDIO)
- hw:2,0 USB Audio
- (default)
Anybody knows what's going on here? Pointers to explanations? Why are
there TWO list of devices to choose from?
thanks!
ero
Erik Steffl wrote:
started qjackctl after the device was plugged in,
starting jack manually seems to be working (also tested wiuth
ardour2, both recording and playback works).
Does that mean there is a bug in qjackctl? Using the version in
Ubuntu 13.04 which is qjackctl 0.3.9-2
Here's what jackd prints out when started manually:
erik@jojda:~$ jackd -d alsa -d hw:2
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:2|hw:2|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback aplay -l
card 2: BR80AUDIO [BR-80(AUDIO)], device 0: USB Audio [USB Audio]
Boss Micro BR-80 seems to be recognized properly
but qjackctl does not
list it in Set under any of Interface, Input Device, Output Device
choices, I only see /dev/dsp, /dev/audio, plughw:0 and hw:0.
"hw:2" should appear in those lists. Did you start QjackCtl before
plugging the device in? Can you start Jack manually with
"jackd -d alsa -d hw:2"?