AlsaSeqMidiIO Device Initialization Error

I am using Debian 12 with its packaged Ardour 7.3 and PipeWire on a laptop. I was intending to use PipeWire-JACK as the audio support system because it does ‘more’ and is less buggy than ALSA in my limited experience. However, old information stresses that ALSA is strongly preferred for simple recording of a microphone (my use case with audio interface). I am supposing that advice is still good in late 2023.
To that end, I was compelled to address this error from the Ardour log to get Ardour + ALSA to work or at least to stop troubling me with a flashing red log light:

2023-11-13T11:35:11 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2023-11-13T11:35:11 [WARNING]: AlsaMidiOut: failed to open midi device '144:0'.
2023-11-13T11:35:11 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2023-11-13T11:35:11 [WARNING]: AlsaMidiIn: failed to open midi device '144:0'.
2023-11-13T11:35:11 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2023-11-13T11:35:11 [WARNING]: AlsaMidiOut: failed

After perhaps a few hours I determined that the error message refers to my ‘ALSA sequencer’, a subsystem of ALSA. There is no special Debian package for it (as far as I can tell). The AlsaSeqMidiIO error only occurs when Window → Audio/MIDI Setup → Audio System is set to ‘ALSA’ and subordinate setting MIDI System is set to ‘ALSA sequencer’. I don’t notice any errors related to setting MIDI System to the other two choices, which are ‘ALSA raw devices’ and ‘None’.
I have no way to know if my computer platform is deficient or if Ardour simple expects a MIDI device and makes a big deal out of it. I don’t have a MIDI instrument to plug in. I don’t know what MIDI functionality the built-in Intel High Definition Audio reports itself to have. During my research of this problem, I came across the idea that PipeWire provides a dummy MIDI interface in a certain situation, but I don’t think that would apply for my error using Ardour with ALSA.
I have no good reason to doubt that my ALSA sequencer is not working correctly. Debian is known for stability (not here to argue about PipeWire) and I am able to verify the ALSA sequencer is running on my laptop in the kernel as a module.

[abyss ~]$ lsmod | grep snd_seq
snd_seq_dummy          16384  0
snd_seq                90112  7 snd_seq_dummy
snd_seq_device         16384  1 snd_seq
snd_timer              49152  3 snd_seq,snd_hrtimer,snd_pcm
snd                   126976  19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_pcm
[abyss ~]$ 
[abyss ~]$ sudo modinfo snd_seq
filename:       /lib/modules/6.1.0-13-amd64/kernel/sound/core/seq/snd-seq.ko
alias:          devname:snd/seq
alias:          char-major-116-1
license:        GPL
description:    Advanced Linux Sound Architecture sequencer.
author:         Frank van de Pol <fvdpol@coil.demon.nl>, Jaroslav Kysela <perex@perex.cz>
depends:        snd,snd-seq-device,snd-timer
retpoline:      Y
intree:         Y
name:           snd_seq
vermagic:       6.1.0-13-amd64 SMP preempt mod_unload modversions 
sig_id:         PKCS#7
signer:         Debian Secure Boot CA
sig_key:        32:A0:28:7F:84:1A:03:6F:A3:93:C1:E0:65:C4:3A:E6:B2:42:26:43
sig_hashalgo:   sha256
signature:      9A:3A:E3:B3:BA:88:41:E9:A3:4A:3B:46:11:79:76:F2:04:E5:65:97:
		62:81:D1:54:B0:80:4B:D7:B0:95:A5:F9:B3:9B:01:1D:5C:34:D3:F8:
		E4:BB:44:52:AD:E9:88:EC:46:5B:74:99:D6:4B:91:8B:65:FE:55:AE:
		F9:88:07:8E:66:68:91:71:9A:8C:72:F0:CF:AE:F4:CA:31:BC:9C:86:
		E5:EE:C8:AF:E2:50:BB:8C:8A:8E:A7:F9:C7:18:7D:99:DD:1E:7D:73:
		38:81:73:33:E4:3D:CF:C3:FD:E4:3F:1F:31:F4:81:1D:F1:01:14:63:
		E2:9B:F0:9D:33:9D:AD:68:3E:47:00:3C:47:9C:A2:51:B5:8F:28:A2:
		7C:0C:72:D0:AD:0D:7F:E3:03:2A:4E:69:A7:7D:BC:27:A8:D1:70:08:
		FE:1F:90:02:DA:9F:4C:FE:AA:C5:B1:0E:1C:EC:B2:78:07:33:3F:81:
		DF:87:33:60:39:AB:82:13:70:20:F2:46:BB:9F:B4:AB:50:C3:95:9D:
		D4:51:A2:FB:AA:32:43:E2:57:18:EC:31:9B:8F:71:AB:02:5B:F8:6E:
		25:70:11:20:9E:5E:B0:CF:96:5B:58:DB:27:A7:A2:E5:7B:40:93:C1:
		FD:45:C9:FC:F6:51:B2:06:A6:56:EF:75:C6:54:9F:89
parm:           seq_client_load:The numbers of global (system) clients to load through kmod. (array of int)
parm:           seq_default_timer_class:The default timer class. (int)
parm:           seq_default_timer_sclass:The default timer slave class. (int)
parm:           seq_default_timer_card:The default timer card number. (int)
parm:           seq_default_timer_device:The default timer device number. (int)
parm:           seq_default_timer_subdevice:The default timer subdevice number. (int)
parm:           seq_default_timer_resolution:The default timer resolution in Hz. (int)
[abyss ~]$ 
[abyss ~]$ sudo modinfo snd_seq_dummy
filename:       /lib/modules/6.1.0-13-amd64/kernel/sound/core/seq/snd-seq-dummy.ko
alias:          snd-seq-client-14
license:        GPL
description:    ALSA sequencer MIDI-through client
author:         Takashi Iwai <tiwai@suse.de>
depends:        snd-seq
retpoline:      Y
intree:         Y
name:           snd_seq_dummy
vermagic:       6.1.0-13-amd64 SMP preempt mod_unload modversions 
sig_id:         PKCS#7
signer:         Debian Secure Boot CA
sig_key:        32:A0:28:7F:84:1A:03:6F:A3:93:C1:E0:65:C4:3A:E6:B2:42:26:43
sig_hashalgo:   sha256
signature:      36:C8:C9:16:A0:96:E5:22:0D:F8:DA:E9:A3:DA:4A:C3:B2:D5:94:DB:
		A8:F1:15:F5:D1:48:B1:E6:F2:49:1A:B2:01:24:55:12:8F:97:01:87:
		54:35:93:CA:AE:E6:09:B4:43:EF:BF:BB:56:A2:E5:E1:7C:07:53:71:
		AC:58:85:91:A9:51:DA:A1:B2:8C:54:43:5F:E5:40:EC:22:5A:39:E1:
		A6:D9:70:A6:28:6E:94:CE:D1:47:03:2C:4D:13:07:59:2C:0D:A5:73:
		44:D9:08:6C:91:05:75:30:AA:0E:7C:F4:7F:F3:CF:7B:E1:E0:DA:11:
		B4:E3:B4:99:37:E7:69:57:CB:76:AD:C8:BE:41:A0:59:5D:7C:CE:8B:
		BE:7D:DB:C0:50:AD:1C:99:D3:64:37:F5:3E:80:E1:2E:4E:7B:62:9F:
		6B:B2:72:5A:A1:4F:D6:A3:99:5F:0A:E8:23:53:FE:08:38:D8:A9:23:
		73:B9:1B:0A:B9:58:8F:76:93:50:32:31:90:08:96:BE:49:69:E1:1A:
		1E:AF:7B:4F:54:A8:FE:BF:B9:23:B8:0C:17:2E:4A:A3:48:4D:6C:92:
		8F:CE:48:BF:33:83:34:4A:1D:69:F5:66:BA:16:05:DF:C7:31:83:81:
		11:9B:36:68:B2:20:46:C8:33:AA:47:07:DA:82:84:B2
parm:           ports:number of ports to be created (int)
parm:           duplex:create DUPLEX ports (bool)

Does this error message suggest some special risk to using Ardour with ALSA instead of ‘JACK’ to record a microphone through an audio interface and USB connection?
Should I aspire to directly use ALSA directly rather than PipeWire-JACK (which does not trigger any log errors)?
What does Ardour 7.3 expect that I am not providing when I select ‘ALSA sequencer’?
—Abyss

What MIDI devices are available on the system? Can you post the output of

amidi --list-devices

Could be as simple as you have MIDI selected for an interface with no MIDI capability.
For the MIDI System selection isn’t there a “None” option? Select that and Ardour will not try to intialize the AlsaMIDI device.

@Robin Gareus

[abyss ~]$ amidi --list-devices
Dir Device    Name
cannot determine device number: Inappropriate ioctl for device
cannot determine device number: Inappropriate ioctl for device
[abyss ~]$

Wow. I’ve never seen that before. Searching the web for that error finds some references to chromebook.

I assume aseqdump --list also comes up empty?

@Robin Gareus

[abyss ~]$ aseqdump --list
 Port    Client name                      Port name
  0:0    System                           Timer
  0:1    System                           Announce
 14:0    Midi Through                     Midi Through Port-0
[abyss ~]$

I am using a Tuxedo XUX7-11, a German-assembled laptop with Clevo chassis. I installed Debian 11 with XFCE desktop over what the Ubuntu with Budgie desktop that Tuxedo had on it. Later, I upgraded from Debian 11 to Debian 12. It was not a fresh install of Debian 12.

You said, “Wow. I’ve never seen that before.” So, how bad is it, Doc?

Are there any MIDI devices connected to the PC that are not listed? a USB soundcard with MIDI perhaps?

@Robin Gareus,

You’ve given me something to think about. Maybe I will realize that I am doing something weird. I was using ‘pw-jack ardour’, but even with just ‘ardour’ I get the same problem with ALSA sequencer.

Well, I have a NVidia GPU that has ‘sound’ for HDMI, I think. I generally ignore it. In pavucontrol I have, because of PipeWire I think (and I forget why), an entry for TU 104 HD Audio Controller. It never worked for me, but then I never tried to send video (with audio I suppose) out of a laptop port to a monitor. Apparently, this laptop can do that.

[abyss ~]$ lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller
Bus 001 Device 004: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
Bus 001 Device 003: ID 048d:8910 Integrated Technology Express, Inc. ITE Device(829x)
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 008: ID 06cb:00a8 Synaptics, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[abyss ~]$ 
[abyss ~]$ lspci
00:00.0 Host bridge: Intel Corporation Comet Lake-S 6c Host Bridge/DRAM Controller (rev 05)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 05)
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0
00:15.1 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #1
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1c.0 PCI bridge: Intel Corporation Device 06b8 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 06b4 (rev f0)
00:1d.5 PCI bridge: Intel Corporation Device 06b5 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Device 06b6 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Z490 Chipset LPC/eSPI Controller
00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
01:00.0 VGA compatible controller: NVIDIA Corporation TU104BM [GeForce RTX 2080 SUPER Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1)
06:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
07:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
07:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
07:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
08:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06)
3f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06)
40:00.0 USB controller: ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller
41:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
42:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
43:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Killer E3000 2.5GbE Controller (rev 06)
44:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)
[abyss ~]$ 
[abyss ~]$ lsusb | grep -i midi
[abyss ~]$ lspci | grep -i midi
[abyss ~]$
[abyss ~]$ lspci -vvv -d 10de:10f8
01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1)
	Subsystem: CLEVO/KAPOK Computer TU104 HD Audio Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	IOMMU group: 1
	Region 0: Memory at a4000000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

[abyss ~]$ 
[abyss ~]$ sudo lspci -vvv -d 10de:10f8
[sudo] password for abyss: 
01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1)
	Subsystem: CLEVO/KAPOK Computer TU104 HD Audio Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	IOMMU group: 1
	Region 0: Memory at a4000000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 75W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (downgraded), Width x16
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range AB, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via message, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

[abyss ~]$ 

I think the driver for your audio device is just not quite right, and indicates it has MIDI capabilities when it does not.
Have you actually tried this yet?

@Chris, I realize I can just set ‘None’. I wanted to explore the possibility of having a computer platform problem and fixing it. As far as trying, I have recorded a mic source through a digital interface with PipeWire’s Jack as the audio support system. I got spooked from reading how I should use ALSA, so I am trying to straighten out this use of ALSA. The TU 104 HD Audio Controller does not work for me, but then I have not connected to a monitor. I am not able to converse very intelligently at this level of technical sophistication and I often make bad assumptions, but sometimes I’m close enough to get things done.

I’m tired and will experiment with Ardour 7.3 with ALSA in the next few days. I wanted to see if there was some technical thing I had to fix that someone might know about. The presentation of the error message seems to warrant investigation rather than just ignoring the ALSA sequencer issue, but I am satisfied that I tried and I appreciate all the help. It seems that I will follow plan B and just experiment with Ardour. What scares me is going into production on what I care about only to be making a serious but preventable mistake. Time and resources are not on my side and finishing with anything usable would be success.

Understood, but everything so far points to an error in the driver implementation (or possibly an error in the system UEFI ROM configuration, or even in the chipset configuration by Tuxedo).
Likely nothing to be done, unless there is a driver update in more recent kernels, or if Tuxedo has provided a modified driver in your support account.

@Chris and @Robin, thanks for your insights. One less complete unknown to worry about then. I suppose I’ll will look for a better driver later. Slowly, I will determine a workflow by experimentation. At least I know how to stop the repetitive the red log flashes.

In general, I would avoid using things like Hdmi and HDA audio devices for music production.

They should, generally, work OK, but they can be very quirky and not that great quality. They are designed to be cheap and cheerful, and to support general desktop computing work.

If you are using them casually and happy to accept the quirks, they should work.

But if you are trying to get "professional "results I would recommend investing in an external audio interface.

You can pick reasonably good ones starting from under 100 USD and these will be a step up in quality, stability, and usability from the audio built onto your PC motherboard.

Cheers,

Keith

1 Like

I am just trying learn and create a viable platform and workflow. I plugged in the SSL 2 digital audio interface and set it to the input and output devices with ALSA and ALSA sequence but got the same flashing log error with the ALSA sequencer.

This is interesting I suppose.

[abyss ~]$  # After reboot. My SSL 2 is not plugged in to USB port.
[abyss ~]$ amidi --list-devices
Dir Device    Name
cannot determine device number: Inappropriate ioctl for device
cannot determine device number: Inappropriate ioctl for device
[abyss ~]$ 
[abyss ~]$ # Here I plugged in my SSL 2 audio interface.
[abyss ~]$ amidi --list-devices
Dir Device    Name
[abyss ~]$ 
[abyss ~]$ # Here I unplugged in my SSL 2 audio interface.
[abyss ~]$ amidi --list-devices
Dir Device    Name
[abyss ~]$

I tried a configuration directive under /etc/modprobe.d per a Ubuntu help webpage and it did not help. I installed the Debian 12 package ‘firmware-misc-nonfree’, which includes firmware for the NVIDIA TU104 Audio Controller. I did not notice any difference, but I am glad to have it. Selecting ‘SSL 2’ as the input and output devices does not prevent the Ardour log error about the ALSA sequencer failing to initialize. Nothing has worked. I guess I won’t be using the ALSA sequencer. Maybe I have learned something that will prove useful later. Thanks for your help, Robin, Chris, and Keith.

You have no MIDI interface! Why do you insist on trying to configure the ALSA MIDI sequencer when you have no MIDI interface? When you have no MIDI interface connected to your computer the appropriate MIDI system to select is “None.”

3 Likes

Hmm, there are two possible devices you might be using:

  • “Solid State Logic SSL2 2x2 USB Audio Interface” (no MIDI ports on the back)
  • " Solid State Logic SSL2+ USB Audio Interface" (MIDI ports on the back, costs ~70 USD more)

If the one you are using is the first one, then @ccaudle is correct: your system doesn’t have any MIDI connectivity, and the ALSA MIDI sequencer won’t work. Once you plug in something which does support MIDI (e.g., a keyboard / controller with its own USB cable), you will be able to configure ALSA midi.

If your interface is actually the “SSL2+” version, then we’d need to look further.

@tseaver, no need to investigate further. It is the SSL 2 not the SSL 2+. I don’t expect to get harassed by the blinking red light unless something is fundamentally wrong. I suppose that when I or the initial Ardour configuration set the system audio to ‘ALSA’ the first however many times, I did not worry about ‘Advanced Settings’ hidden by a collapsible UI panel. I am guessing that the MIDI System setting was initially set to ‘ALSA sequencer’. My Ardour is 7.3 from the Debian 12 package.

I like to understand how things work and don’t work, especially if they are my things. Why would an error setting be an option? It seemed reasonable to investigate the appropriateness of my computer platform based on the urgency of the error warning. The flashing red light is designed to require user attention. I have done the investigation as far my abilities allow.

As soon as I can, I will resume experimenting with recording with Ardour 7.3. Perhaps if I simply plug in a MIDI device the correct way or at all, the ‘ALSA sequencer’ setting will not trigger a log error. If so, that’s news to me. I am satisfied that the error does not result from a problem with my computer configuration that I can or should fix. I don’t know if I’ll ever use a MIDI device, but of course I’d like that option and a proper computer set up. I will go with what I’ve got for now and simply use ‘None’ to avoid the ‘error’. Thanks, everyone.

1 Like

We would much prefer that you resume experimenting with Ardour 8.1 …

There clearly is something wrong, as shown above:

Inappropriate ioctl for device

is likely caused by an incompatibility of the kernel and libasound (ALSA driver/userspace) on your system. unrelated to Ardour.