Midi devices not seen

bmentink · 08-15-2018, 05:01 PM

I can't seem to see any midi devices at all in Reaper.
(using version 5.941)

aconnect -l sees my device (ttyMIDI)

Code:

client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 128: 'ttymidi' [type=user,pid=398]
    0 'ttyMIDI         '
    1 'ttyMIDI         '

.. as does aseqdump -l:

Code:

 Port    Client name                      Port name
  0:0    System                           Timer
  0:1    System                           Announce
 14:0    Midi Through                     Midi Through Port-0
128:0    ttymidi                          ttyMIDI

aconnect should show a device advertised by Reaper as well, but nothing.

Any help appreciated

Justin · 08-15-2018, 07:14 PM

REAPER's ALSA MIDI support is via rawmidi, so maybe that's why?

bmentink · 08-15-2018, 07:36 PM

Quote:

Originally Posted by Justin

REAPER's ALSA MIDI support is via rawmidi, so maybe that's why?

do you mean the module

Code:

 snd_rawmidi

? if so, that is loaded, but still nothing ..

Do you have a list of modules that need loading for this to work?
i.e I have loaded snd_seq_oss, snd-mixer-oss, and snd-pcm-oss, not sure if they are needed .. still no device though ..

Jack Winter · 08-15-2018, 10:09 PM

Modules ending with oss probably refer to an ancient linux audio system that's mostly not used anymore. You don't need to use them at all.

Are you using the ALSA backend for audio? If you are using JACK2 for audio you need to run the a2jmidid daemon to bridge between jack and alsa midi. If you use JACK1 that functionality is built in.

bmentink · 08-15-2018, 10:14 PM

I am using bare alsa..

Jack Winter · 08-15-2018, 10:19 PM

Are you trying to use a chroot, if so I guess the problem lies there?

luno · 08-26-2021, 06:49 AM

I see this is an old thread. But I wanted to post my solution:

sudo modprobe snd-virmidi snd_index=1
aconnect -l
aconnect 27:0 128:0

The first command loads the kernel module for virtual-midi devices. They appear also in reaper.
Second command shows the midi devices, including the virtual ones.
After that you can connect a virtual-device to an alsa-midi device (in my case a bluetooth-midi-device). For an unknown reason not every virtual-midi device is visible in reaper, I had to use the last ones.

08-15-2018, 05:01 PM	#1
bmentink Human being with feelings Join Date: Aug 2018 Posts: 26	Midi devices not seen I can't seem to see any midi devices at all in Reaper. (using version 5.941) aconnect -l sees my device (ttyMIDI) Code: client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 128: 'ttymidi' [type=user,pid=398] 0 'ttyMIDI ' 1 'ttyMIDI ' .. as does aseqdump -l: Code: Port Client name Port name 0:0 System Timer 0:1 System Announce 14:0 Midi Through Midi Through Port-0 128:0 ttymidi ttyMIDI aconnect should show a device advertised by Reaper as well, but nothing. Any help appreciated

08-15-2018, 10:09 PM	#4
Jack Winter Human being with feelings Join Date: Aug 2007 Location: Luxembourg/Spain Posts: 1,922	Modules ending with oss probably refer to an ancient linux audio system that's mostly not used anymore. You don't need to use them at all. Are you using the ALSA backend for audio? If you are using JACK2 for audio you need to run the a2jmidid daemon to bridge between jack and alsa midi. If you use JACK1 that functionality is built in. __________________ Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)

08-15-2018, 10:19 PM	#6
Jack Winter Human being with feelings Join Date: Aug 2007 Location: Luxembourg/Spain Posts: 1,922	Are you trying to use a chroot, if so I guess the problem lies there? __________________ Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

08-15-2018, 07:14 PM	#2
Justin Administrator Join Date: Jan 2005 Location: NYC Posts: 15,746	REAPER's ALSA MIDI support is via rawmidi, so maybe that's why?

08-15-2018, 10:14 PM	#5
bmentink Human being with feelings Join Date: Aug 2018 Posts: 26	I am using bare alsa..

08-26-2021, 06:49 AM	#7
luno Human being with feelings Join Date: Aug 2021 Posts: 1	I see this is an old thread. But I wanted to post my solution: sudo modprobe snd-virmidi snd_index=1 aconnect -l aconnect 27:0 128:0 The first command loads the kernel module for virtual-midi devices. They appear also in reaper. Second command shows the midi devices, including the virtual ones. After that you can connect a virtual-device to an alsa-midi device (in my case a bluetooth-midi-device). For an unknown reason not every virtual-midi device is visible in reaper, I had to use the last ones.