Need a hint on TouchOSC with MODEP

Patchbox OS MODEP
1

TouchOsc installed on Samsung Android Tablet.

Bridge is set to patchbox.local.
I am using this address to connect with my Mac.
Possibly Android doesn’t resolve Bonjour addresses so let me try the IP address.
That doesn’t seem to help.
MIDI Send and receive port are <Bridge 1> (which was populated into the “Browse” dropdown). I think this doesn’t prove there’s a connection, simply that I defined a bridge.
Button MIDI params
Trigger x any
touch
Type Control Change
Channel 1
Controller 3
Value 2

sudo tcpdump | grep -i udp

shows stuff arriving on port 12101.

01:43:43.862855 IP 10.0.0.78.12102 > 10.0.0.23.12101: UDP, length 16
01:43:43.862931 IP 10.0.0.23 > 10.0.0.78: ICMP 10.0.0.23 udp port 12101 unreachable, length 52
01:43:44.038897 IP 10.0.0.78.12102 > 10.0.0.23.12101: UDP, length 16
01:43:44.038940 IP 10.0.0.23 > 10.0.0.78: ICMP 10.0.0.23 udp port 12101 unreachable, length 52
01:43:44.454042 IP 10.0.0.78.12102 > 10.0.0.23.12101: UDP, length 16
01:43:44.454088 IP 10.0.0.23 > 10.0.0.78: ICMP 10.0.0.23 udp port 12101 unreachable, length 52
01:43:44.588968 IP 10.0.0.78.12102 > 10.0.0.23.12101: UDP, length 16
01:43:44.589022 IP 10.0.0.23 > 10.0.0.78: ICMP 10.0.0.23 udp port 12101 unreachable, length 52
01:43:45.037222 IP 10.0.0.78.12102 > 10.0.0.23.12101: UDP, length 16
01:43:45.037304 IP 10.0.0.23 > 10.0.0.78: ICMP 10.0.0.23 udp port 12101 unreachable, length 52
01:43:45.172179 IP 10.0.0.78.12102 > 10.0.0.23.12101: UDP, length 16

In MODEP, separated mode, TouchOSC selected.

No indication on the setup panel in MODEP that anything happened. The UI does not tell you to expect anything, but in any case it still does not work.

thanks,

DL

2

I added the MIDI display and connected “Hardware TouchOSC MIDI” to it. Nothing is shown when I press the button in TouchOSC on the tablet.

Maybe I need to change the UDP port on the sending side? Listener is on 59133.

patch@patchbox:/var/modep/pedalboards/S_H_Filter.pedalboard $ sudo netstat -lpn | grep osc2midi
udp        0      0 0.0.0.0:59133           0.0.0.0:*                           1300/osc2midi       
patch@patchbox:/var/modep/pedalboards/S_H_Filter.pedalboard $
3

Maybe this post can help you. https://community.blokas.io/t/is-patchbox-os-modep-now-supported-on-raspberry-pi-5/5422/14

1 Like
4

Thanks, let’s see what I discover.

patch@patchbox:~ $ sudo su
root@patchbox:/home/patch# service modep-touchosc2midi status
× modep-touchosc2midi.service - TouchOsc2Midi service
     Loaded: loaded (/lib/systemd/system/modep-touchosc2midi.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2025-03-16 20:34:00 GMT; 1h 2min ago
   Duration: 1.051s
    Process: 1094 ExecStart=/bin/bash /usr/modep/scripts/start_touchosc2midi.sh (code=exited, status=1/FAIL>
   Main PID: 1094 (code=exited, status=1/FAILURE)
        CPU: 992ms

Mar 16 20:34:00 patchbox systemd[1]: modep-touchosc2midi.service: Scheduled restart job, restart counter is>
Mar 16 20:34:00 patchbox systemd[1]: Stopped modep-touchosc2midi.service - TouchOsc2Midi service.
Mar 16 20:34:00 patchbox systemd[1]: modep-touchosc2midi.service: Start request repeated too quickly.
Mar 16 20:34:00 patchbox systemd[1]: modep-touchosc2midi.service: Failed with result 'exit-code'.
Mar 16 20:34:00 patchbox systemd[1]: Failed to start modep-touchosc2midi.service - TouchOsc2Midi service.

OK service is clearly not running. Let’s see if I can start it manually.

root@patchbox:/home/patch# service modep-touchosc2midi restart
root@patchbox:/home/patch# service modep-touchosc2midi status
● modep-touchosc2midi.service - TouchOsc2Midi service
     Loaded: loaded (/lib/systemd/system/modep-touchosc2midi.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Sun 2025-03-16 21:38:04 GMT; 1s ago
    Process: 1201 ExecStart=/bin/bash /usr/modep/scripts/start_touchosc2midi.sh (code=exited, status=1/FAIL>
   Main PID: 1201 (code=exited, status=1/FAILURE)
        CPU: 980ms

Looks not. Let’s try the command.

Had to install python-pip first.

root@patchbox:/home/patch# python3 -m pip install zeroconf==0.24.4 --break-system-packages
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting zeroconf==0.24.4
  Downloading https://www.piwheels.org/simple/zeroconf/zeroconf-0.24.4-py3-none-any.whl (56 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 56.2/56.2 kB 300.1 kB/s eta 0:00:00
Requirement already satisfied: ifaddr in /usr/lib/python3/dist-packages (from zeroconf==0.24.4) (0.1.7)
Installing collected packages: zeroconf
  Attempting uninstall: zeroconf
    Found existing installation: zeroconf 0.47.3
    Not uninstalling zeroconf at /usr/lib/python3/dist-packages, outside environment /usr
    Can't uninstall 'zeroconf'. No files were found to uninstall.
Successfully installed zeroconf-0.24.4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
root@patchbox:/home/patch#

Next:

root@patchbox:/home/patch# service modep-touchosc2midi restart
root@patchbox:/home/patch# service modep-touchosc2midi status
● modep-touchosc2midi.service - TouchOsc2Midi service
     Loaded: loaded (/lib/systemd/system/modep-touchosc2midi.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-03-16 21:41:42 GMT; 4s ago
   Main PID: 2444 (touchosc2midi)
      Tasks: 4 (limit: 3910)
        CPU: 729ms
     CGroup: /system.slice/modep-touchosc2midi.service
             └─2444 /usr/bin/python3 /usr/bin/touchosc2midi --midi-in=2 --midi-out=2

Mar 16 21:41:42 patchbox systemd[1]: Started modep-touchosc2midi.service - TouchOsc2Midi service.
Mar 16 21:41:43 patchbox bash[2444]: Failed to create secure directory (/nonexistent/.config/pulse): No suc>
Mar 16 21:41:44 patchbox bash[2444]: Waiting for first package from touchOSC in order to setup target addre>
lines 1-12/12 (END)

Looks promising. Thanks!!!

Will report back.

DL

1 Like
5

@Pilal it works now! Thanks. I wasn’t focused on that solution even though I’d seen it as I am using the Pi 4, not 5. But I am using the aarch64 version of the PatchboxOS image, which is probably the dependency.

DL

6

I had the same issue after moving from patchbox 32 bits to the bookworm 64 bits version. Hope this will be fixed in a future release.

1 Like