Home News Store Community Docs
Menu

Midi connection manager

#9

That’s normal, system config files are usually with restricted permissions for safety and inconvenience purposes :).

Do:

sudo nano /etc/amidiauto.conf

to run the editor as root, paste in the contents, hit ctrl+x, then hit y to save and exit.

1 Like
#10

Thanks a lot, first it didnt work, but after Updating amidiauto it works like a charm!
I just thought I have the newest amidiauto after installing Patchbox but wasnt like that.
anyway thanks a lot

1 Like
#11

If I only want to make connections between all plugged hardwares, am I simply add the lines in amidiauto.conf as

[allow]
hw <-> hw

What I need is to use Pisound as a MIDI host, for the connection with Digitakt and several controllers.

0 Likes
#12

At the moment you have to explicitly mention the names of the virtual MIDI ports if you want connections of ports in the same hardware category.

So something like:

[allow]
pisound <-> digitakt

and more lines like above. Use aconnect -l to see the port names, also the rules are case sensitive.

1 Like
#13

Thanks @Giedrius! It’s working!

I’m curious to know what the Midi Through MIDI device is.

Also, may I know is there a way I can run SuperCollider before amidiauto? Imagine I would like to do this:
scide MIDIClient.init MIDIIn.connectAll &

I’m not sure if I can do above on IDE, I want SC starts and initialize MIDIClient and connect all available ports, then let amidiauto recognize all the virtual ports from SC. I don’t need s.boot; as all I would like to do is use SC only as a MIDI dispatcher.

0 Likes
#14

I don’t think the order of startup is important, amidiauto does its work for all the ports it found on startup, as well as any ports appearing dynamically at runtime. Other software is free to make their own connections, amidiauto won’t disconnect them.

1 Like
#15

Thanks! It is wonderful!

0 Likes
#16

Hi Giedrius,
Ive just realized when I activate the ORAC 2.0 Module, that the Amidiauto Midi configs dont work anymore, but all the devices connects to Pure Data. When I deactivate the ORAC Module, everything works again. Any idea to solve this?
Here is the aconnect -l output with Orac activated:

client 0: 'System' [type=kernel]
0 'Timer           '
1 'Announce        '
    Connecting To: 128:0, 129:0

client 14: ‘Midi Through’ [type=kernel]
0 ‘Midi Through Port-0’
Connecting To: 129:0[real:0]
Connected From: 129:0
client 20: ‘pisound’ [type=kernel,card=1]
0 ‘pisound MIDI PS-0Z7FE7V’
Connecting To: 129:0[real:0], 130:0
Connected From: 129:0, 130:1
client 24: ‘OP-Z’ [type=kernel,card=2]
0 'OP-Z MIDI 1 ’
Connecting To: 129:0[real:0], 130:0
Connected From: 129:0, 130:1
client 28: ‘OP-1 Midi Device’ [type=kernel,card=3]
0 ‘OP-1 Midi Device MIDI 1’
Connecting To: 129:0[real:0], 130:0
Connected From: 129:0, 130:1
client 130: ‘Pure Data’ [type=user,pid=594]
0 ‘Pure Data Midi-In 1’
Connected From: 20:0, 24:0, 28:0, 129:0, 131:0[real:0], 133:0, 134:0
1 ‘Pure Data Midi-Out 1’
Connecting To: 20:0, 24:0, 28:0, 129:0[real:0], 132:0, 134:0
client 131: ‘MEC MIDI OUTPUT’ [type=user,pid=653]
0 'MIDI OUT ’
Connecting To: 130:0[real:0], 129:0[real:0]
client 132: ‘RtMidiIn Client’ [type=user,pid=794]
0 'TouchOSC Bridge ’
Connected From: 130:1, 129:0
client 133: ‘RtMidiOut Client’ [type=user,pid=794]
0 'TouchOSC Bridge ’
Connecting To: 130:0, 129:0[real:0]
client 134: ‘pisound-ctl’ [type=user,pid=807]
0 'pisound-ctl ’
Connecting To: 130:0, 129:0[real:0]
Connected From: 130:1, 129:0

0 Likes
Orac 2.0 for the Raspberry PI
#17

Yes, ORAC module has its own amidiauto.conf file, you can customize it here:

/usr/local/patchbox-modules/orac/amidiauto.conf

and re-activate ORAC.

0 Likes
#18

Hi, another questions here regarding Mac to Midi over Wifi.
I have Pi and Mac in the same network, and want to send Sync data from Mac to Pisound,
I have set it up as stated here: https://help.ableton.com/hc/en-us/articles/209071169-Sending-and-receiving-MIDI-messages-using-a-virtual-MIDI-network

Thats working, and Mac seems to send data to Pisound, but the devices connected to PIsound by USB dont receive the Sync data from Mac.
When I check on aconnect RtMidi Client is connected to everything, I also tried to connect RtMidiOut to OP-1 for example with amidiconf, using it with ORAC currently.
Any idea what could be missing? Thanks!

client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
        Connecting To: 128:0, 129:0
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
        Connecting To: 129:0[real:0]
        Connected From: 129:0
client 20: 'pisound' [type=kernel,card=1]
    0 'pisound MIDI PS-0Z7FE7V'
        Connecting To: 24:0, 129:0[real:0], 131:0, 28:0
        Connected From: 129:0, 131:1
client 24: 'OP-Z' [type=kernel,card=2]
    0 'OP-Z MIDI 1     '
        Connecting To: 129:0[real:0], 131:0, 28:0
        Connected From: 20:0, 129:0, 130:0, 131:1
client 28: 'OP-1 Midi Device' [type=kernel,card=3]
    0 'OP-1 Midi Device MIDI 1'
        Connecting To: 131:0, 129:0[real:0]
        Connected From: 131:1, 20:0, 24:0, 130:0, 134:0, 129:0
client 130: 'pisound-ctl' [type=user,pid=674]
    0 'pisound-ctl     '
        Connecting To: 24:0, 129:0[real:0], 131:0, 28:0
        Connected From: 129:0, 131:1
client 131: 'Pure Data' [type=user,pid=593]
    0 'Pure Data Midi-In 1'
        Connected From: 20:0, 24:0, 130:0, 129:0, 132:0, 132:0[real:0], 134:0, 28:0
    1 'Pure Data Midi-Out 1'
        Connecting To: 20:0, 24:0, 130:0, 129:0[real:0], 133:0, 28:0
client 132: 'MEC MIDI OUTPUT' [type=user,pid=677]
    0 'MIDI OUT        '
        Connecting To: 131:0, 131:0[real:0], 129:0[real:0]
client 133: 'RtMidiIn Client' [type=user,pid=773]
    0 'TouchOSC Bridge '
        Connected From: 131:1, 129:0
client 134: 'RtMidiOut Client' [type=user,pid=773]
    0 'TouchOSC Bridge '
        Connecting To: 131:0, 129:0[real:0], 28:0
0 Likes
#19

How did you check that the Raspberry Pi is actually receiving the messages from your Mac? You ought to have some process on RPi side able to receive the Mac MIDI messages, I don’t think I see such a process in the attached client list.

0 Likes
#20

Then I probably didnt see it. I was thinking that RtMidiIn and Out are connected to 28:0, which in that time is OP-1. What kind of information do you need to verify?
I can only say that I had added sucessfully PIsound / Rapsberry to the Virtual Midi Network.
Thanks, Im sorry If my information isnt accurate, trying to do my best.

0 Likes
#21

hi, i would like to send the midi in to midi out of the pisound card, but i don’t see those port whith aconnect -l command; can some one help me? thanks

0 Likes
#22

You should see Pisound’s MIDI ports listed in a way similar to this:

client 20: 'pisound' [type=kernel,card=1]
    0 'pisound MIDI PS-0Z7FE7V'
        Connecting To: 24:0, 129:0[real:0], 131:0, 28:0
        Connected From: 129:0, 131:1

In my experience, the most usual client number is 20:0, so you can try running aconnect 20:0 20:0 to forward incoming data directly to the output.

0 Likes
#23

In amidiauto.conf, i have to write 20<->0 ?

0 Likes
#24

I’m sorry, but still dont understand how the amidiauto.conf file as to be writen. I want to use the midi din5 output as a midi thru from the midi din5 input. Help!!

0 Likes
#25

I meant you can execute aconnect 20:0 20:0 to make the direct connection.

You can put this in /etc/amidiauto.conf:

[allow]
* <-> *
pisound <-> pisound

Afterwards, restart amidiauto server for the changes to take effect:

sudo systemctl restart amidiauto

Running aconnect -l will then produce:

...
client 20: 'pisound' [type=kernel,card=1]
    0 'pisound MIDI PS-2RZAMPG'
        Connecting To: 20:0
        Connected From: 20:0
...
0 Likes
#26

Thank you very much for the help, i will try it as soon as possible!

0 Likes
#27

Hi Gedrius,
I did your tips and it works like a charm! I realise now how easy was that, thank you for your patience!

1 Like
#28

Thanks a lot for that super handy deamon. Works like a charm!

1 Like