Thank you, yes the Nektar can be used as a generic USB controller. And as
mentioned it works under other apps using ALSA. I plan to find out the correct
value to put in the settings field for ALSA.
The problem is that the Settings > ALSA Midi Source has a text field only (no
recognition feature, drop-down selector, etc) with a default value of 'default.'
I imagine now I will have to figure out what value to place in that field for
the midi controller to then be recognized and selected for use.
Thanks, I'll take your tips and see what solution I can find and document here
for other users encountering the same head-scratcher.
Dec 31, 2018, 3:17 PM by diego.simak@xxxxxxxxx:
El lun., 31 dic. 2018 a las 18:04, <> distro@xxxxxxxxxxxxxxxxx
<mailto:distro@xxxxxxxxxxxxxxxxx>> > escribió:
Here's a new topic, or a quick question as i did attempt a quick search at
least in mailing ist archives before posting.
So I received my Nektar XL25+ MIDI keyboard controller today. I connected it
via the USB to desktop. Booted up Yoshimi. Looked around and could not
locate any option to enable or set it as the MIDI controller.
Yoshimi > Settings > Jack, Alsa, MIDI tabs - no options. Also basically look
through out GUI and nothing.
I did then open up another linux MIDI virtual app called VMPK (Virtual Midi
Piano Keyboard) and under ALSA, for example, it did recognize while plugged
in naturally and have option to set the device as the input MIDI connection,
Any advice (holding my breath and crossing my fingers here)? Looked in
manual could not locate any section on input MIDI controller settings.
As long as the Nektar is USB Class Complaint you can connect it trough MIDI.
I have a M-AUDIO KeyRig 49 using yoshimi with JACK and it work perfectly.
Please check if you see the Nektar with QjackCtl under ALSA tab, and connect
it to yoshimi using "a2jmidid -e" first (because you need to expose HW MIDI
to JACK MIDI)
This is assuming that you are using JACK for both audio and MIDI.
If you are using yoshimi with plain ALSA you will need to connect both using
for example "aconnectgui" (front end for aconnect)