Error: AlsaSeqMidiIO: Device initialization failed

Installation & Configuration Linux
#1

Every time I start Adour (9, but I also had it with 8) I get the following errors:

2026-03-04T07:40:42 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2026-03-04T07:40:42 [WARNING]: AlsaMidiOut: failed to open midi device '142:0'.
2026-03-04T07:40:42 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2026-03-04T07:40:42 [WARNING]: AlsaMidiIn: failed to open midi device '142:0'.
2026-03-04T07:40:42 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2026-03-04T07:40:42 [WARNING]: AlsaMidiOut: failed to open midi device '143:0'.
2026-03-04T07:40:42 [ERROR]: AlsaSeqMidiIO: Device initialization failed.
2026-03-04T07:40:42 [WARNING]: AlsaMidiIn: failed to open midi device '143:0'.
2026-03-04T07:40:42 [WARNING]: AlsaAudioBackend: cannot acquire realtime permissions.

According to aconnect -l 142 and 143 are pipewire devices:

client 0: 'System' [type=kernel]
    0 'Timer           '
        Connecting To: 142:0
    1 'Announce        '
        Connecting To: 142:0, 128:0
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 142: 'PipeWire-System' [type=user,UMP-MIDI2,pid=3015]
    0 'input           '
        Connected From: 0:1, 0:0
client 143: 'PipeWire-RT-Event' [type=user,UMP-MIDI2,pid=3015]
    0 'input           '

Anything I can do to prevent these errors?

#2

I’m experiencing the same problem, and the red messages in the log were bothering me as well. Your post motivated me to look into it, and it seems I’ve managed to get rid of those messages.

There is how the Setup & Calibration dialog under the Audio/MIDI setup dialog → Advanced Settings looks on my system:

obraz
obraz567×525 27.2 KB

As you can see, a couple of MIDI input devices with rather non-descriptive names. Suspected they were causing the errors, so simply disabled them, and the messages disappeared. Everything seems to be working fine now when testing with the ALSA backend.

Hope it works for you too.

#3

You mean the bottom two? I’ve disabled them and the error seems to have gone. We’ll see.

Thanks!

#4

Actually, I had to disable all three ‘inputs’ to get rid of the errors completely.

Glad it helped.