4 Dec
2020
4 Dec
'20
12:40 p.m.
Hi!
Installed a new kernel on my Debian Testing machine with
kxstudio-"extension"
:~$ uname -a
Linux mmmaschine 5.9.0-4-rt-amd64 #1 SMP PREEMPT_RT Debian 5.9.11-1
(2020-11-27) x86_64 GNU/Linux
and had a new problem that jack couldn't launched - which bever had been
a problem, so far. Dived into journalctl -f and stumbled upon
Dez 04 11:18:17 machine pulseaudio[1852]: E: [pulseaudio]
module-alsa-card.c: Failed to find a working profile.
Dez 04 11:18:17 machine pulseaudio[1852]: E: [pulseaudio] module.c:
Failed to load module "module-alsa-card" (argument:
"device_id="3"
name="usb-KORG_INC._KONTROL49-00"
card_name="alsa_card.usb-KORG_INC._KONTROL49-00" namereg_fail=false
tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes
use_ucm=yes avoid_resampling=no
card_properties="module-udev-detect.discovered=1""): initialization
failed.
Knowing, that the Korg has no audio-abilities, I checked
:~$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x4001110000 irq 134
1 [Loopback ]: Loopback - Loopback
Loopback 1
2 [DSP ]: H-DSP - Hammerfall DSP
RME Hammerfall HDSP 9652 at 0xa0100000, irq 17
3 [KONTROL49 ]: USB-Audio - KONTROL49
KORG INC. KONTROL49 at usb-0000:00:14.0-2, full speed
Unplugging the Korg Kontrol49 made it possible to launch jackd, again.
My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Is this something happening on kernel level, so *someone*™ has to fix
stuff here?
Greets!
Mitsch
4 Dec
4 Dec
12:02 p.m.
What is your jackd command line?
ALSA is responsible for MIDI as well as audio, and they are all (slightly
confusingly perhaps) handled by the snd-usb-audio module. What you need
to do is make sure Jack is trying to use the appropriate card.
If you're not using something graphical like qjackctl or cadence to launch
jack, you can specify this on the command line, e.g.
jackd ... -dalsa -dhw:DSP,0 ...
(or possibly -dhw:2)
bjb
On Fri, Dec 04, 2020 at 11:39:56AM +0100, Michael Jarosch wrote:
Hi!
Installed a new kernel on my Debian Testing machine with
kxstudio-"extension"
:~$ uname -a
Linux mmmaschine 5.9.0-4-rt-amd64 #1 SMP PREEMPT_RT Debian 5.9.11-1
(2020-11-27) x86_64 GNU/Linux
and had a new problem that jack couldn't launched - which bever had been a
problem, so far. Dived into journalctl -f and stumbled upon
Dez 04 11:18:17 machine pulseaudio[1852]: E: [pulseaudio]
module-alsa-card.c: Failed to find a working profile.
Dez 04 11:18:17 machine pulseaudio[1852]: E: [pulseaudio] module.c: Failed
to load module "module-alsa-card" (argument: "device_id="3"
name="usb-KORG_INC._KONTROL49-00"
card_name="alsa_card.usb-KORG_INC._KONTROL49-00" namereg_fail=false
tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes
use_ucm=yes avoid_resampling=no
card_properties="module-udev-detect.discovered=1""): initialization
failed.
Knowing, that the Korg has no audio-abilities, I checked
:~$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x4001110000 irq 134
1 [Loopback ]: Loopback - Loopback
Loopback 1
2 [DSP ]: H-DSP - Hammerfall DSP
RME Hammerfall HDSP 9652 at 0xa0100000, irq 17
3 [KONTROL49 ]: USB-Audio - KONTROL49
KORG INC. KONTROL49 at usb-0000:00:14.0-2, full speed
Unplugging the Korg Kontrol49 made it possible to launch jackd, again.
My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Is this something happening on kernel level, so *someone*™ has to fix stuff
here?
Greets!
Mitsch
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
12:58 p.m.
Am 04.12.20 um 11:39 schrieb Michael Jarosch:
My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Your system(kernel) wont listen, I am afraid, you could only blacklist
the Korg, but that is stupid, because I reckon, you want to use it.
BUT you can tell Jack explicitly to use the HammerfallDSP as in:
jackd -d alsa -d hw:2 -p128 -n2
This commandline can be stored in $HOME/.jackdrc to serve as the default
for the start of jackd.
There are variants of Jackd to day such as jackdmp that may demand
slightely different settings but are to be handeled the same in principle.
best of luck ;-)
Is this something happening on kernel level, so
*someone*™ has to fix
stuff here?
Greets!
Mitsch
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:08 p.m.
Hey, Zett! Nice to meet you, again!
Am 04.12.20 um 11:58 schrieb Hartmut Noack:
Am 04.12.20 um 11:39 schrieb Michael Jarosch:
Guess, the problem in my configuration is, that pulseaudio won't startup
successfully and therefore hinders jackd to launch. At least that's what
I read out of the journalctl's output. The main problem seams to me that
pulseaudio identifies the Korg as an audio device and that's why I am
asking, what to do about that.
Nevertheless: Many thanks for your fast reply!
Greets!
Mitsch
My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Your system(kernel) wont listen, I am afraid, you could only blacklist
the Korg, but that is stupid, because I reckon, you want to use it.
BUT you can tell Jack explicitly to use the HammerfallDSP as in:
jackd -d alsa -d hw:2 -p128 -n2 
1:12 p.m.
Hartmut Noack <zettberlin(a)linuxuse.de> writes:
Am 04.12.20 um 11:39 schrieb Michael Jarosch:
To make this independent of discovery order:
jackd -d alsa -d hw:DSP -p128 -n2
--
David Kastrup
My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Your system(kernel) wont listen, I am afraid, you could only blacklist
the Korg, but that is stupid, because I reckon, you want to use it.
BUT you can tell Jack explicitly to use the HammerfallDSP as in:
jackd -d alsa -d hw:2 -p128 -n2
This commandline can be stored in $HOME/.jackdrc to serve as the default
for the start of jackd.
1:30 p.m.
Am 04.12.20 um 12:12 schrieb David Kastrup:
Hartmut Noack <zettberlin(a)linuxuse.de> writes:
:~$ jackd -d alsa -d hw:DSP -p128 -n2
jackdmp 1.9.16
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2020 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:DSP|hw:DSP|128|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 128 frames (2.7 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
Okay, then I have to tell more about my system…
Unfortunately, I'm not using it on my own. My machine is also
extensively used by my son and, surely, he is no friend of the command
line. We use the wonderful Cadence to make everything just work after
login (which includes watching youtube-videos via FIrefox and still
getting the output over the highend soundcard and monitoring). So,
Cadence is configured to start jack and deliver a pulseaudio bridge. And
there must be the problem, cause everything works, as long as the Korg
isn't plugged in at startup. Otherwise, I (or he) have (has) to launch
jack via commandline. (I could tell him not to plug the Korg, until
everythings up, but I thought t here could be something to do which
makes the problem just go away…)
Greets!
Mitsch
Am 04.12.20 um 11:39 schrieb Michael Jarosch:
To make this independent of discovery order:
jackd -d alsa -d hw:DSP -p128 -n2 My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Your system(kernel) wont listen, I am afraid, you could only blacklist
the Korg, but that is stupid, because I reckon, you want to use it.
BUT you can tell Jack explicitly to use the HammerfallDSP as in:
jackd -d alsa -d hw:2 -p128 -n2
This commandline can be stored in $HOME/.jackdrc to serve as the default
for the start of jackd. 
6:50 p.m.
On Fri, 4 Dec 2020, Michael Jarosch wrote:
Knowing, that the Korg has no audio-abilities, I
checked
:~$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x4001110000 irq 134
1 [Loopback ]: Loopback - Loopback
Loopback 1
2 [DSP ]: H-DSP - Hammerfall DSP
RME Hammerfall HDSP 9652 at 0xa0100000, irq 17
3 [KONTROL49 ]: USB-Audio - KONTROL49
KORG INC. KONTROL49 at usb-0000:00:14.0-2, full speed
Nothing wrong here. It is the same with any USB midi device. I have:
$ cat cards
0 [M66 ]: ICE1712 - M Audio Delta 66
M Audio Delta 66 at 0xc080, irq 19
1 [AudioPCI ]: ENS1370 - Ensoniq AudioPCI
Ensoniq AudioPCI ENS1370 at 0xc000, irq 16
2 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7c00000 irq 33
3 [AudioFire12 ]: Fireworks - AudioFire12
Echo Digital Audio AudioFire12 v4.8, GUID
0014860268b568f1 at fw1.0, S400
4 [UM1G ]: USB-Audio - UM-1G
Roland UM-1G at usb-0000:00:1a.0-1.4, full speed
But:
$ ls UM1G
id midi0 usbbus usbid usbmixer
This shows that this device is a midi device.
A USB device with audio looks like:
$ ls Device
id pcm0c pcm0p stream0 usbbus usbid usbmixer
notice the two sub directories: pcm0c pcm0p which show this device has
one capture device (pcm0c) and one playback device (pcm0p).
so what do you see when you do:
:~$ ls /proc/asound/KONTROL49
If there is a pcm* sub directory, maybe look through to see what audio
device it thinks it has.
--
Len Ovens
www.ovenwerks.net
8:07 p.m.
Am 04.12.20 um 17:49 schrieb Len Ovens:
On Fri, 4 Dec 2020, Michael Jarosch wrote:
Ah, okay!
Knowing, that the Korg has no audio-abilities, I
checked
:~$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x4001110000 irq 134
1 [Loopback ]: Loopback - Loopback
Loopback 1
2 [DSP ]: H-DSP - Hammerfall DSP
RME Hammerfall HDSP 9652 at 0xa0100000, irq 17
3 [KONTROL49 ]: USB-Audio - KONTROL49
KORG INC. KONTROL49 at usb-0000:00:14.0-2, full
speed
Nothing wrong here. It is the same with any USB midi device. I have:
$ cat cards
0 [M66 ]: ICE1712 - M Audio Delta 66
M Audio Delta 66 at 0xc080, irq 19
1 [AudioPCI ]: ENS1370 - Ensoniq AudioPCI
Ensoniq AudioPCI ENS1370 at 0xc000, irq 16
2 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7c00000 irq 33
3 [AudioFire12 ]: Fireworks - AudioFire12
Echo Digital Audio AudioFire12 v4.8, GUID
0014860268b568f1 at fw1.0, S400
4 [UM1G ]: USB-Audio - UM-1G
Roland UM-1G at usb-0000:00:1a.0-1.4, full speed But:
$ ls UM1G
id midi0 usbbus usbid usbmixer
This shows that this device is a midi device.
A USB device with audio looks like:
$ ls Device
id pcm0c pcm0p stream0 usbbus usbid usbmixer
notice the two sub directories: pcm0c pcm0p which show this device
has one capture device (pcm0c) and one playback device (pcm0p).
so what do you see when you do:
:~$ ls /proc/asound/KONTROL49
id midi0 oss_mixer usbbus usbid
oss_mixer looks suspicious…
Greets!
Mitsch
8 Dec
8 Dec
12:49 p.m.
Hello,
Sorry, people!
Started my machine and today it seams everything's doing fine, again.
Can't tell you why it didn't work, yesterday, despite of rebooting twice.
The OS assigns the sound devices an index in the order they get
connected. This can vary per boot and depends of course on what sound
devices are attached at boot time. You can make this more deterministic
by forcing indexes for the sound devices. On my system I have a file
/etc/modprobe.d/audio.conf with the following content:
options snd-hda-intel index=10 vid=0x8086 pid=0x1e20
options snd-usb-audio index=0,5 vid=0x0424,0x09e8 pid=0x3fb7,0x007c
So my internal sound card gets index 10, my RME Babyface gets index 0
(so it's the default sound card) and my USB MIDI keybaord gets index 5.
You can find out the vid's and pid's of your own devices with the lspci
and lsusb commands.
Best,
Jeremy
9 Dec
9 Dec
7:18 a.m.
New subject: Predictable Audio Interface Names (was: Re: MIDI-controller treated as audio device)
On Tue, Dec 08, 2020 at 11:49:30AM +0100, Jeremy Jongepier wrote:
The problem of device assignment varying per boot also, historically,
used to affect network devices.
In recent years, that problem has been solved (at least for network
devices, in at least some distros) by the "Predictable Network Interface
Names" initiative:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfa…
This avoids the need to manually assign device names/indexes to solve
for boot variance.
Does anyone know: is a similar initiative underway for audio devices?
--
A: When it messes up the order in which people normally read text.
Q: When is top-posting a bad thing?
() ASCII ribbon campaign. Please avoid HTML emails & proprietary
/\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Started my
machine and today it seams everything's doing fine, again.
Can't tell you why it didn't work, yesterday, despite of rebooting
twice.
The OS assigns the sound devices an index in the order they get
connected. This can vary per boot and depends of course on what sound
devices are attached at boot time. You can make this more
deterministic by forcing indexes for the sound devices. On my system I
have a file /etc/modprobe.d/audio.conf with the following content:
options snd-hda-intel index=10 vid=0x8086 pid=0x1e20
options snd-usb-audio index=0,5 vid=0x0424,0x09e8 pid=0x3fb7,0x007c
1446
days inactive
1451
days old
linux-audio-user@lists.linuxaudio.org
10 comments
7 participants
participants (7)
-
Ben Bell -
David Kastrup -
Hartmut Noack -
Jeremy Jongepier -
Len Ovens -
Michael Jarosch -
Sam Kuper