Intro & AI-use disclaimer
I wanted to run ORAC on my Pi running standard Trixie OS, not Patchbox. But ORAC, as available on in Technobear’s Github repo for ORAC, can’t be used on Trixie OS because the externals are 32-bit, not 64-bit. So, on 2026-10-13, I (Brian Hagerty) used Claude to help me build ORAC on my Pi. I iterated with Claude until I got instructions that worked without errors; this post documents the working instructions. Note that there is some material at the bottom of this document that I have not tested; it is clearly labeled.
Also, note that ORAC is abandonware. The project is inactive, and the maintainer is not accepting pull requests.
Building ORAC from source on the Pi (Raspberry Pi OS, 64-bit)
Orac is a set of Pd patches. It loads compiled Pd “externals” from orac/externals/. The PI/ folder in the Orac repo already includes these externals, but they are 32-bit (armhf) builds from 2020. Pd on 64-bit Raspberry Pi OS can’t load them, so you have to build them yourself.
| Part | Where it comes from | What it provides |
|---|---|---|
| MEC | build from source | KontrolRack, KontrolModule (the Orac engine) and mec-app (OSC/Push 2 bridge) |
| Mi4Pd | build from source | brds~ clds~ clds_reverb~ grids lmnts~ rngs~ rngs_chorus~ rngs_ensemble~ rngs_reverb~ wrps~ |
| abl_link~ | build from source (libpd/abl_link) | Ableton Link (used by the clock module) |
| routeOSC, freeverb~, moog~, tanh~ | apt packages | needed by main.pd, reverb, analogstyle/analogmono, and dtanh |
Per Claude: These steps were checked on 2026-10-13 by cross-compiling everything for arm64 with GCC 14 (the compiler in Trixie), with and without Push 2 support. The assembled Orac was then run headless in an arm64 build of Pd 0.55-2 under emulation: it loads its modules and presets with no crash.
Per me (Brian Hagerty): I followed these instructions and successfully built and ran ORAC on my Raspberry Pi 4 running Raspberry Pi OS Trixie, with PiSound software installed.
1. Install build tools and Pd externals
sudo apt update
sudo apt install git cmake build-essential pkg-config \
libusb-1.0-0-dev libasound2-dev libcairo2-dev puredata-dev \
pd-osc pd-freeverb pd-ggee pd-cyclone
puredata-dev provides m_pd.h and matches the apt Pd (0.55.2). libcairo2-dev is only needed for Push 2 support.
2. Get the sources
mkdir -p ~/src && cd ~/src
git clone --recursive https://github.com/TheTechnobear/MEC
git clone --recursive https://github.com/TheTechnobear/Mi4Pd
git clone --recursive https://github.com/TheTechnobear/Orac
git clone --recursive https://github.com/libpd/abl_link
Use --recursive, because MEC and abl_link depend on git submodules.
3. Build MEC
First, fix a 64-bit bug in MEC’s bundled copy of oscpack (the OSC library). Without this fix, Orac crashes with Segmentation fault right after client connected pd.osc:127.0.0.1:6000:
cd ~/src/MEC
sed -i 's/defined(__x86_64__) || defined(_M_X64)/defined(__x86_64__) || defined(_M_X64) || defined(__LP64__)/' \
external/oscpack/osc/OscTypes.h \
external/oscpack/osc/OscOutboundPacketStream.h \
external/oscpack/osc/OscReceivedElements.h
git diff --stat # expect 3 files changed, 4 insertions(+), 4 deletions(-)
This old oscpack only treats x86-64 as a 64-bit platform. On 64-bit ARM it makes its “32-bit” integer type an unsigned long, which is 64 bits there. Every OSC message is then written with 8-byte fields where 4-byte fields are expected, which corrupts memory. The fix applies the 32-bit types to every 64-bit Linux platform (__LP64__). It changes nothing on x86-64 or on 32-bit Pi OS.
Then configure and build:
cd ~/src/MEC && mkdir -p build && cd build
CXXFLAGS="-include cstdint -include cstdio -include ostream -include stdexcept" \
cmake .. -DCMAKE_BUILD_TYPE=Release \
-DCMAKE_POSITION_INDEPENDENT_CODE=ON \
-DDISABLE_EIGENHARP=1 \
-DCMAKE_POLICY_VERSION_MINIMUM=3.5 \
-DPUSH2=ON
make -j3 mec-app KontrolRack KontrolModule
Why each workaround is needed:
CXXFLAGS=-include …: the code is from 2019–2024 and is missing#includelines that GCC 14 needs (it fails with errors like'uint16_t' does not name a typeand'ostream' is not a member of 'std'). These flags add the missing headers without editing the source.CMAKE_POSITION_INDEPENDENT_CODE=ON: without it, the link fails withrecompile with -fPIC.DISABLE_EIGENHARP=1and building only the three targets: the Eigenharp driver (EigenLite) doesn’t support 64-bit ARM (#error "unsupported platform"). A plainmakewould still try to build it and fail. Leaving it out only removes Eigenharp support.CMAKE_POLICY_VERSION_MINIMUM=3.5: only CMake 4.x uses this. With the CMake 3.x in Raspberry Pi OS it does nothing, and CMake says so (see below). It’s there so the same command keeps working if CMake is ever upgraded to 4.x, which refuses to configure these old projects without it.PUSH2=ON(optional): builds Ableton Push 2 support (libmec-push2.so). Leave it out if you don’t have a Push 2.
Changing options later: to add or remove an option such as -DPUSH2=ON, rerun the same cmake command in the same build folder with the option changed, then run make again. You don’t need to delete anything first, because CMake updates its saved settings and regenerates the makefiles. To start completely fresh, use rm -rf ~/src/MEC/build and begin step 3 again.
Expected warnings from cmake (safe to ignore):
CMake Deprecation Warning … Compatibility with CMake < 3.10 will be removed …: the project’sCMakeLists.txtdeclares a very old minimum CMake version. It’s only a notice.Manually-specified variables were not used by the project: CMAKE_POLICY_VERSION_MINIMUM: CMake 3.x ignores this setting (see above).- With
PUSH2=ON, possibly someCMake Warning (dev)policy messages about the Push 2 library. These are notices for the project’s developers.
A good configure ends with -- Build files have been written to: …/MEC/build.
Output goes to build/release/bin/mec-app and build/release/lib/ (the .pd_linux and .so files, including libmec-push2.so with Push 2 on).
4. Build Mi4Pd
cd ~/src/Mi4Pd && mkdir -p build && cd build
cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_POSITION_INDEPENDENT_CODE=ON -DCMAKE_POLICY_VERSION_MINIMUM=3.5
make -j3
This produces 10 externals in build/release/lib/. You’ll get the same two harmless cmake warnings as in step 3.
5. Build abl_link~
cd ~/src/abl_link/external
make
Expect pages of asio warnings. The build has worked if it ends with target all in lib abl_link~ completed.
6. Assemble the Orac package
The repo’s create_pi.sh script merges Core/ and PI/ into pkg/pi. NOPACK=1 stops it before it builds the (armhf) .deb packages. Afterwards, replace the old 32-bit binaries with your new builds:
cd ~/src/Orac
NOPACK=1 sh scripts/create_pi.sh
cd pkg/pi
# remove the old 32-bit binaries
rm -f orac/externals/*.pd_linux orac/externals/*.so MEC/*.pd_linux MEC/*.so MEC/mec-app
# Orac externals
cp ~/src/MEC/build/release/lib/* orac/externals/
cp ~/src/Mi4Pd/build/release/lib/* orac/externals/
cp ~/src/abl_link/external/abl_link~.pd_linux orac/externals/
cp /usr/lib/pd/extra/osc/{packOSC,routeOSC,unpackOSC}.pd_linux \
/usr/lib/pd/extra/freeverb~/freeverb~.pd_linux \
/usr/lib/pd/extra/ggee/moog~.pd_linux \
/usr/lib/pd/extra/cyclone/tanh~.pd_linux orac/externals/
# MEC app and its libraries
cp ~/src/MEC/build/release/bin/mec-app ~/src/MEC/build/release/lib/*.so MEC/
Copying the apt externals into orac/externals means Orac finds them no matter which Pd is running it (0.55.2 from apt or 0.56.5 built from source).
7. Change the user from pi to USERNAME
Out of the box, ORAC has the username “pi” in environment variables. Change that to whatever username you are using to run it.
sed -i 's#/home/pi#/home/USERNAME#g; s#=pi$#=USERNAME#; s#EnvironmentFile=/etc#EnvironmentFile=-/etc#' \
orac/orac.service orac/orac.json MEC/mec.service
grep -n 'USERNAME\|Environment' orac/orac.service orac/orac.json MEC/mec.service # check the result
8. Install
sudo cp -R MEC orac /usr/local/
mkdir -p ~/media/orac/usermodules
cp -nr /usr/local/orac/media ~
cp -nr /usr/local/orac/data ~
9. First run (by hand)
Pd opens the Pisound directly through ALSA, so JACK must not be running. If you were running something that used JACK (such as SuperDirt), close it first, then check:
pgrep -a jackd(no output means JACK isn’t running).
Find the Pisound’s device number in Pd:
pd -nogui -alsa -listdev -send "pd quit"
The Pisound appears twice, once as pisound (hardware) and once as pisound (plug-in). Use the number for pisound (hardware) (for example, 6. pisound (hardware) → N = 6). Both entries go to the same input and output jacks on the Pisound:
- hardware opens the card directly, with no conversion layer and the lowest latency.
- plug-in opens the same card through ALSA’s conversion layer, which adapts sample rates and formats the card doesn’t support natively. Orac runs at 48 kHz, which the Pisound supports, so that layer isn’t needed. Use the plug-in number only if Pd reports an error opening the hardware device.
Device numbers can shift. Plugging in a USB audio device or changing HDMI audio settings can renumber the list. Rerun -listdev before putting the number into orac.service (step 10), and again whenever the hardware changes.
Then start Orac, replacing N with that number:
cd /usr/local/orac
pd -nogui -alsa -rt -alsamidi -audiodev N -r 48000 -audiobuf 4 mother.pd main.pd
You should see KontrolRack::module found: … lines and no … couldn't create errors. Stop it with Ctrl-C.
To use the remote OSC display, run MEC in a second SSH session:
cd /usr/local/MEC && ./mec-app osckontrol.json
For a Push 2, use ./mec-app pushkontrol.json instead (see “Using an Ableton Push 2” below).
10. Run as services (optional)
First rerun pd -nogui -alsa -listdev -send "pd quit" to confirm the pisound (hardware) number hasn’t changed (see step 9). Then, in /usr/local/orac/orac.service, change ExecStart to the command that worked above (where N is the pisound device number):
ExecStart=/usr/bin/pd -nogui -alsa -rt -alsamidi -audiodev N -r 48000 -audiobuf 4 mother.pd main.pd
For Pd 0.56.5 built from source, use /usr/local/bin/pd instead (check with which -a pd). Then install the services:
sudo cp /usr/local/orac/orac.service /usr/local/MEC/mec.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl start orac; sleep 7; sudo systemctl start mec
journalctl -u orac -f # watch the log
- To start Orac at boot:
sudo systemctl enable orac mec. Leave this off if you also use SuperCollider/JACK, because both can’t open the Pisound at the same time. - Before starting SuperDirt:
sudo systemctl stop mec orac. - If you hear dropouts, raise
-audiobuf(try 8 or 10). The value 4 comes from Patchbox OS, which uses a real-time kernel.
Controlling Orac on a headless Pi
- Pd OSC client on a laptop:
- First, in PD, you will need to add the
oscexternal (Tools → Find externals → osc). - Next, you need the file
main.pdfrom the folderOrac/OscClients/pd/in Technobear’s Orac files. You do not need (or want) theexternalsin those files; they are 32-bit only, and you likely have a 64-bit OS. - Open the
main.pdfile in PureData on your laptop, and edit the host message box, chaningorganelletoYOURPI.local(or whatever; this should be a name at which your Pi is reachable on your network). - PureData on the laptop should now be talking to
mec-appon the Pi on port 6100 and receiving data back on port 6101. Make sure that your laptop can listen for UDP traffic on 6101. Firewall rules, or TailScale’s ShieldsUp setting, could block traffic from the Pi.
- First, in PD, you will need to add the
I have tested nothing from here down. BCH
- Lemur (iPad/iPhone): I have not tested this, but there are layouts at Technobear’s GitHub repo in
OscClients/lemur. The OSC target should be set toYOURPI.local:6100(again, use whatever name resolves to your Pi). - MIDI controller:
KontrolRackruns inmididevice mode, so should be able to use MIDI learn. I have not tested this. - Ableton Push 2: see below.
Using an Ableton Push 2
-
Build MEC with
-DPUSH2=ON(step 3). -
Allow non-root access to the Push 2’s USB display:
sudo cp ~/src/Orac/Core/MEC/79-push2.rules /etc/udev/rules.d/ sudo udevadm control --reload-rulesThen unplug the Push 2 and plug it back in.
-
Run MEC with the Push config:
./mec-app pushkontrol.json. For the service, edit/etc/systemd/system/mec.serviceand swap whichExecStartline is commented out (osckontrol.json↔pushkontrol.json). Then runsudo systemctl daemon-reload && sudo systemctl restart mec.
Pd 0.55.2 vs 0.56.5
Pd externals don’t normally need a rebuild for a newer Pd version, so the same orac/externals folder should work under both. The only thing to change is the pd path in orac.service. If an object fails to create under 0.56.5, rebuild steps 3–5 against 0.56.5’s m_pd.h. For CMake builds, the m_pd.h bundled in each repo is used, so this would only matter for abl_link: run make PDINCLUDEDIR=/usr/local/include/pd.