jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
linux-hwe-5.4 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi,
it isn't easy to describe but i will try and give you all information
which seem to interfer with the bug ..
Sorry, my system is running with german language output.
First my environment :
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Kernel:
5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
alsa:
$ apt list --installed|grep -i alsa
alsa-base/
alsa-utils/
libsox-
libzita-
jackd:
apt list --installed|grep -i jackd
jackd/bionic,
jackd2/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,
libjack-
libjack-
My interface (Omega) :
$ aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC887-VD Analog [ALC887-VD Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: PCH [HDA Intel PCH], Gerät 1: ALC887-VD Digital [ALC887-VD Digital]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: PCH [HDA Intel PCH], Gerät 7: HDMI 1 [HDMI 1]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: Omega [Lexicon Omega], Gerät 0: USB Audio [USB Audio]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: Omega [Lexicon Omega], Gerät 1: USB Audio [USB Audio #1]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
The problem:
I try to record some audio, using the usb-audio-interface Lexicon Omega.
This interface has 4 capture channels, but all efforts to get them working/configured failed.
Here is the commandline wich is working (but only two capture-channels !)
$ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i2 -o2
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
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
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservati
Acquire audio card Audio1
creating alsa driver ... hw:Omega|
configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: use 3 periods for playback
The same with 4 capture-channels fails:
$ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i4 -o2
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
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
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservati
Acquire audio card Audio1
creating alsa driver ... hw:Omega|
configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: cannot set channel count to 4 for capture
ALSA: cannot configure capture channel
JackTemporaryEx
Released audio card Audio1
audio_reservati
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
So, one could say the interface is broken, but i tested on an older system (Ubuntustudio 16.04):
$ uname -a
4.10.0-
$ apt list --installed|grep -i alsa
alsa-base/
alsa-tools/
alsa-tools-
alsa-utils/
gstreamer1.
libsox-
libzita-
$ apt list --installed|grep -i jackd
jackd/bionic,
jackd2/bionic,now 1.9.12~dfsg-2 amd64 [installiert]
jackd2-
libjack-
libjack-
jackd is configure via qjackctl, no specification of channelcount (only default-value:0 ).
Here's the output of jackd starting (finding 4 capture channels + 2 playback channels)
--- snip---
Tue Nov 17 12:23:43 2020: Starting jack server...
Tue Nov 17 12:23:43 2020: JACK server starting in realtime mode with priority 10
Tue Nov 17 12:23:43 2020: self-connect-mode is "Don't restrict self connect requests"
Tue Nov 17 12:23:43 2020: Jack: JackPosixThread
Tue Nov 17 12:23:43 2020: Jack: JackPosixThread
Tue Nov 17 12:23:43 2020: Jack: capture device hw:Omega
Tue Nov 17 12:23:43 2020: Jack: playback device hw:Omega
Tue Nov 17 12:23:43 2020: Jack: apparent rate = 44100
Tue Nov 17 12:23:43 2020: Jack: frames per period = 256
Tue Nov 17 12:23:43 2020: Jack: JackDriver::Open capture_driver_name = hw:Omega
Tue Nov 17 12:23:43 2020: Jack: JackDriver::Open playback_
Tue Nov 17 12:23:43 2020: Jack: Check protocol client = 8 server = 8
Tue Nov 17 12:23:43 2020: Jack: JackEngine:
Tue Nov 17 12:23:43 2020: Jack: JackEngine:
Tue Nov 17 12:23:43 2020: Jack: JackLinuxFutex:
Tue Nov 17 12:23:43 2020: Jack: JackEngine:
Tue Nov 17 12:23:43 2020: Jack: JackGraphManage
Tue Nov 17 12:23:43 2020: Jack: JackConnectionM
Tue Nov 17 12:23:43 2020: Jack: JackGraphManage
Tue Nov 17 12:23:43 2020: Jack: JackDriver:
Tue Nov 17 12:23:43 2020: Acquired audio card Audio1
Tue Nov 17 12:23:43 2020: creating alsa driver ... hw:Omega|
Tue Nov 17 12:23:43 2020: configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods
Tue Nov 17 12:23:43 2020: ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
Tue Nov 17 12:23:43 2020: ALSA: use 2 periods for capture
Tue Nov 17 12:23:43 2020: ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
Tue Nov 17 12:23:43 2020: ALSA: use 2 periods for playback
--- snip--
The attachment shows you there are 4 capture-channels.
The bug is described here by another person too:
https:/
My opinion is that somewhere in development of kernel alsa has lost it's
capability to configure more than 2 capture-channels.
I wonder why nobody else is complaining, maybe because it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
HibernationDevice:
RESUME=none
#RESUME=
InstallationDate: Installed on 2017-05-20 (1277 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
IwConfig:
lo no wireless extensions.
enp0s31f6 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
Bus 001 Device 002: ID 05e3:0716 Genesys Logic, Inc. USB 2.0 Multislot Card Reader/Writer
Bus 001 Device 004: ID 046a:010e Cherry GmbH
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
Package: linux-hwe-5.4
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.173.19
RfKill:
Tags: bionic
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-11-23 (726 days ago)
UserGroups: adm audio cdrom davfs2 fax lpadmin netdev netzuser plugdev sambashare scanner sudo vboxusers video wireshark
_MarkForUpload: True
dmi.bios.date: 05/16/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.
dmi.board.name: H170-PRO/USB 3.1
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1904566/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]