View Single Post
Old 06-14-2020, 06:36 PM   #1
s wave
Human being with feelings
 
Join Date: Sep 2018
Location: Colorado
Posts: 270
Default Using aconnect, to solve routing problems with midi controller/stand alone soft synth

I just figured I would post this for some people trying to get a stand alone soft synth or midi controller working. Kinda basic, In terminal run
'aconnect -lio'.
If you have a midi controller it should pop it up with a number. If you have a stand alone soft synth like Zyn or Tonelib etc., it willpop up that number too.

So it would look like this:

$ aconnect -lio
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Connecting To: 24:0
Connected From: 24:0
client 24: 'LPK25' [type=kernel,card=2]
0 'LPK25 MIDI 1 '
Connecting To: 14:0
Connected From: 14:0
client 128: 'ZynAddSubFX' [type=user,pid=19137]
0 'ZynAddSubFX

Now if I want to get the Zyn... soft synth connected to the LPK25 (AKAI midi controller) I just enter the command (in terminal) 'aconnect 24 128'

and your keyboard should work with the soft synth.

If you added 'YOUR SOFT SYNTH NAME HERE--exec-after-init "aconnect 20 128"'that would make it automatic but a touch more complicated... you could use this for a lot of integrating and routing. tc
s wave is offline   Reply With Quote