FritzBox router turned MIDI looper box

Oct 27, 2026 Last reply: 16 hours ago 4 Replies
Jump to replies (4)

When everything is running, this setup turns a scrap FritzBox router into a small MIDI brain: Orca-C plays as a text sequencer in a terminal grid right on the box, while a custom eight-track Python looper handles looping, with networked MIDI traffic available across the whole setup. The looper clocks itself off an incoming KeyStep clock once a sequence is recorded into the first track, and it drives a small rig of synths and sequencers patched through USB and audio cables.



How it came together is the part I find impressive. Robin Sutcliffe - Audio Visual Art cross-compiled both Midish and Orca-C for the Lantiq MIPS 24C chip inside these boxes, since Midish has no package for the platform. Everything installs through the OpenWRT APK installer over SSH or the web GUI, config lines were edited in GNU nano, and terminal event logs captured the incoming Clock, Note On and Note Off streams during testing. Apparently the Mac cross-compile was fiddly enough that a Linux machine is on the wishlist for next time.



The looper interface itself looks thoughtfully laid out: eight tracks, each showing status, event counts, plus mute, solo and arm flags. And the router keeps its day job, since these boxes can still work as networked MIDI pass-through devices, with one acting as server and the rest as clients in a small network.



The honest sticking point is notes that drop or hang. Midish runs but loses and holds notes often enough to matter, and even the Python looper, which the maker finds very playable, still throws the occasional stuck note during dense playing. The cause is unclear, and trying a different FritzBox model is the planned next step to see if the hardware is to blame.



Project by Robin Sutcliffe - Audio Visual Art . Watch it on their YouTube channel:

formatting link


Curious about the install path here. Once the binaries were built for the Lantiq chip, did they go onto the box through the APK installer over SSH, or was the web GUI route used for any of it? And did aseqdump behave normally for checking what the router could see of the connected gear?

Building a looper out of discarded routers seems like a genuinely clever call. The hardware costs nothing, the boxes still work as networked MIDI pass-through, and one can serve while others act as clients. The trade-off is obvious though: a MIPS router was never meant for real-time MIDI work, and the stuck notes look like the price of that choice. I still think it is worth it for what the platform gives back.

One idea worth trying: spread the load across more than one box. The setup already supports a small network with one router as server and the others as clients, so the sequencer and the looper could live on separate units. If background services or low-level router behaviour are causing the hung notes, isolating the MIDI duties onto different machines might reduce the collisions and keep the glitchy character while calming the worst of it.

The maker has laid out the path pretty clearly. OpenWRT images get onto these Fritz routers without much trouble, though not always straightforwardly. Midish and Orca-C come as compiled APK files that transfer over and install directly, and Python3 with the Linux ALSA MIDI tools go in via the APK installer through SSH or the web GUI. The compiled files are offered on request, so getting hold of them should not be a barrier.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required