Tryin to get rtpmidid on PI4

Patchbox OS
1

I am trying to connect a PI4 (Patchbox OS Bookworm) to connect to a PI zero 2 (Debian Trixie). Status of rtpmidid on PI4 gets me:

rtpmidid.service - rtpmidid
Loaded: loaded (/lib/systemd/system/rtpmidid.service; enabled; preset: enabled)
Active: failed (Result: signal) since Sat 2026-08-08 11:32:10 BST; 6min ago
Duration: 15ms
Process: 782 ExecStart=/usr/bin/rtpmidid --ini=/etc/rtpmidid/default.ini (code=killed, signal=ABRT)
Main PID: 782 (code=killed, signal=ABRT)
CPU: 11ms

Aug 08 11:32:10 patchbox systemd[1]: rtpmidid.service: Scheduled restart job, restart counter is at 5.
Aug 08 11:32:10 patchbox systemd[1]: Stopped rtpmidid.service - rtpmidid.
Aug 08 11:32:10 patchbox systemd[1]: rtpmidid.service: Start request repeated too quickly.
Aug 08 11:32:10 patchbox systemd[1]: rtpmidid.service: Failed with result ā€˜signalā€™.
Aug 08 11:32:10 patchbox systemd[1]: Failed to start rtpmidid.service - rtpmidid.

2

Try getting it to run manually first by executing:

/usr/bin/rtpmidid --ini=/etc/rtpmidid/default.ini

and check what output do you get. It seems to be crashing.

You may also try to run it through strace in case of no useful output, so you can get a sense of what it was trying to do just before crashing:

strace /usr/bin/rtpmidid --ini=/etc/rtpmidid/default.ini
4

Thx for your help here are the logs

/usr/bin/rtpmidid --ini=/etc/rtpmidid/default.ini
/usr/bin/rtpmidid: line 9: syntax error near unexpected token newline' /usr/bin/rtpmidid: line 9: ā€™

strace /usr/bin/rtpmidid --ini=/etc/rtpmidid/default.ini
execve(ā€œ/usr/bin/rtpmididā€, [ā€œ/usr/bin/rtpmididā€, ā€œā€“ini=/etc/rtpmidid/default.iniā€], 0x7ff9e57c88 /* 42 vars */) = -1 ENOEXEC (Exec format error)
strace: exec: Exec format error
+++ exited with 1 +++

seems to be wrong version for RPi zero 64bit, but I canĀ“t get the right one with apt-get

5

Where did you get rtpmidid installed from?

6

I have tried:

sudo apt install rtpmidid -y
Error: Unable to locate package rtpmidid

7

hence I could not make rtpmidi work on the zero (on the pi4 (patchbox os) which I want to connect it seems to be enabled but has errors)
So I started experiments with py scripts for sender and receiver (not to mention a turn over socat, most promising because direct hardware, but no succes)
Now I have a ping connection, a RPizero sending start/stop/clock but RPi 4 receives only start/stop and no clock can be seen on aseqdump.

All this with the help of copypaste A.I. and really no progress in linux wisdom :wink:

8

Yeah, it looks like it is not currently being packaged and hosted by Debian, but there was a user request for that, but no action on that yet.

The best way to go about it I think would be to clone the git repo:

and try to build it locally. It does not come with ready to go instructions, but the AI should be able to figure out how to go about it.

Looking at the Makefile targets, Iā€™d try commands like make help and make run. I would skip all the Docker stuff on RPi Zero (and other Piā€™s too, if possible)

You may get some missing dependencies errors, those should be fixed by figuring out which Deb packages to install. For example sudo apt install libasound2-dev

If you get stuck, please share the commands you run and what outputs you get.ā€™

The repo README.md lists some alternative RTP MIDI implementations that you could give a try.

9

solved with the mentioned .py scripts (heavily modified :slight_smile:

10

So in the end you had AI implement it for you? :smiley: Or did it fix some open source scripts for you?

11

yes it was a long journey with try&error on AI and finally it worked. Unfortunatly there is really no progress in learning Linux or Phyton only in asking AI the right questions.
Hope I will find a way to make AI really teach me these things, so I know why this all works and I can help myself and others in the future