please focus on this issue
+++ i am #1 you can't hide under a ultra-dweeb mentality. I clearly and in
detail-specified a scenario, from a normal lay person perspective, and one that
relates to the overwhelming majority of linux GUI applications.
you need to connect the nektar to yoshimi
nektar is HW MIDI
yoshimi can be configured to use ALSA (HW MIDI) or JACK MIDI
+++ No kidding, did I not already state this clearly. Yes I did. And I
acknowledged there was in fact an area in settings with out practical option to
interface with ALSA or JACK concerning connecting a MIDI.
This is lacking in the GUI and ideally should be something to improve for the
average linux user.
if you are using ALSA MIDI and if the nektar is class complaint just connect
both using aconnectgui
+++ Yes, that is ANOTHER EXTERNAL FRONT-END. Not ideal and I was hoping that I
wouldn't have to install that. Should I? Not ideal. Sorry, I out of all the
multimedia apps on my systems, never had to use it before.
if you are using JACK MIDI for yoshimi, you will need to expose hardware MIDI
i.e. Nektar to JACK MIDI
so you will need to run first "a2jmidid -e" to expose HW MIDI to JACK MIDI as I
explained before
+++ I clearly already understood that.
in this step you will see in QjackCtl under MIDI Tab "a2jmidid" and "yoshimi"
expand "a2jmidid" and you will see the Nektar, connect the Nektar to Yoshimi
using QjackCtl, and that's it
+++ Thank you for that info. Either with ALSA- utilities I assume that
aconnectgui package exists, I don't know I tried running it as a command in
terminal and quick repo search on system and don't see it.
But I guess give 5 minutes.
Also, as far as focus and that other guy, my focus was on 2 levels:
Posing a simple question and getting some simple answers in order to not only
solve for myself but other REGULAR people in the world coming to use linux and
Yoshima.
2. To document and generate feedback on something that could be improved
without depending on external dependencies that some system or users may not
have access or ability to easily reach.
Valid point I think so, Jackasses like the other guys who try to ridicule or
put down my own experience, which is pretty in-depth outside of A/V on linux,
probably more than his.. and the fact that in the modern world and linux, we
have GUI for a purpose and it is crucial to not act elitist, self-absorbed and
be able to explain and outline a process. Some people are not necessarily
familiar or work with audio utilities, every day, make sense?
ANY. I guess I will figure it out, see if I can locate the aconnectgui on my
system or dig around until I find the ulility launcher etc. I am sure I will
get it to work and then even share my information on the mailing list. But if
one has to use a more complicated and externalized approach to simply specify
the midi controller, leaving the current setting simply to 'default' - then why
is it even there, it only serves to confuse and is relatively useless at least
for the basic user, unless you can in fact specficy the controller, which I am
guessing you can actually do with the right value.
Stay tuned, any other advice or comments would be appreciated only if they
simple enumerated instructions minus elitist or wise-ass commentary.
Thanks
Dec 31, 2018, 3:32 PM by diego.simak@xxxxxxxxx:
El lun., 31 dic. 2018 a las 18:24, <> distro@xxxxxxxxxxxxxxxxx
<mailto:distro@xxxxxxxxxxxxxxxxx>> > escribió:
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
<mailto: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, and worked.
Any advice (holding my breath and crossing my fingers here)? Looked in
manual could not locate any section on input MIDI controller settings.
#
Hello
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)
Good Luck!
please focus on this issue
you need to connect the nektar to yoshimi
nektar is HW MIDI
yoshimi can be configured to use ALSA (HW MIDI) or JACK MIDI
if you are using ALSA MIDI and if the nektar is class complaint just connect
both using aconnectgui
if you are using JACK MIDI for yoshimi, you will need to expose hardware MIDI
i.e. Nektar to JACK MIDI
so you will need to run first "a2jmidid -e" to expose HW MIDI to JACK MIDI as
I explained before
in this step you will see in QjackCtl under MIDI Tab "a2jmidid" and "yoshimi"
expand "a2jmidid" and you will see the Nektar, connect the Nektar to Yoshimi
using QjackCtl, and that's it
