RackSanity MPC Companion · Setup
From installation
to your first sound.
Set up the Mac host and MPC plugin separately, then pair them using RackSanity’s guided connection screen.
This guide describes the tested preview on MPC Live III, OS 3.10.0. Keep your current working projects and rack files saved. The customer download is not open yet.
What you’ll need
- A Mac with your supported AU/VST3 instruments, effects, samples and authorizations installed locally.
- An MPC Live III running OS 3.10.0—the model and OS used in the owner’s tests.
- The Mac and MPC on the same trusted local network for Companion control.
- Your configured USB connection for MIDI and audio between the MPC and Mac.
- A prepared installer USB drive and the community Plugin Manager for the MPC plugin step.
The Companion does not carry audio or MIDI notes over its network connection. Do not expose its control port to the public internet.
Install RackSanity on the Mac
- Save your rack and quit any running RackSanity app.
- Open the RackSanity + MPC Companion
.pkgand follow the installer screens. - Open
/Applications/RackSanity Companion/RackSanity.app. Use this exact app if you also have an older public or debug build installed. - Scan the Mac’s installed plugins and choose its audio and MIDI devices. Start with one instrument to verify sound.
The installer includes the separate MPC ZIP at /Library/Application Support/RTW Audio/RackSanity Companion/Packages and an MPC Setup.html guide beside the app. It does not automatically install onto the MPC.
Use Power → Rack Check to review the active audio device, slot routes and unavailable instrument/FX warnings. Rack Check does not inspect sample libraries inside a plugin.
Prepare the MPC side
If the community Plugin Manager already opens on your MPC, keep that working setup and skip the first-use helper steps.
- Prepare a USB using the reviewed Plugin Manager v1.3.0 bundle. Copy its contents to the USB root, including hidden
.mpc-manager-id, rather than copying the enclosing folder. Preserve existing files when updating. - Copy the included
RackSanity-Companion-0.0.8-mpc-aarch64.zip, still zipped, into the USB’slocal-pluginsfolder. - Save your MPC project and insert the USB. On first use with OS 3.10, select
Plugin Manager helper.xpain the MPC Browser. Choose Load, select internal MPC Documents as the extraction destination, then Save. Allow extraction to finish. - Shut the MPC down normally and turn it back on to activate that helper. With the prepared USB inserted, hold Shift + Menu for two seconds to open the manager.
- Choose Browse plugins → Local and select RackSanity Companion 0.0.8. Verify its version and destination before installing.
- The owner’s tested destination is
/nvme/Synths. If needed, use Setup → Plugin location to select it. Anoexec, read-only or unavailable destination must be corrected by choosing a supported location; do not bypass mount restrictions. - Install/update the Companion and preserve existing user data, including its private pairing configuration. Choose Return to MPC and wait for MPC to finish reopening.
Opening Plugin Manager stops the MPC application. Returning can take 30 seconds or longer; let it finish. The upstream manager guide covers its installation and recovery behavior.
Connect the rack
- On the Mac, open Power → MPC Companion Connection.
- Choose the Mac address on the same network as your MPC, then click Enable on this Mac. If multiple adapters are listed, use the one connected to that network.
- Save the MPC project, connect it to this Mac by USB, and enter Controller Mode so its storage mounts on the Mac.
- In the same RackSanity dialog, choose Save pairing to MPC…. Select the installed RTW Audio - VST - RackSanity Companion folder—on the owner’s setup, under MPC User → Synths.
- Eject all mounted MPC volumes in Finder. Return the MPC to Standalone and open one Companion instance on a plugin track.
- Press Connect. Confirm your rack is visible and Live Edit is off. Arm Live Edit only when you want controls or confirmed loading actions to change the Mac rack.
After enabling it once, open the Mac app normally next time; Terminal is not required. If the Mac’s address changes, repeat the pairing export. Pairing is private: do not share your companion.conf or its token.
Keep instrument tracks independent
- Load Hive or another supported instrument in RackSanity slot 1. Assign its MIDI input and receive channel, for example channel 1.
- Use a native MPC MIDI track assigned to that channel and the Mac USB MIDI port. For another instrument, use another slot and channel, for example channel 2.
- Select either rack in the Companion. That changes the control target; it does not change the native MIDI track assignments.
- For audio capture, configure the Mac’s output to the MPC USB audio return and record it onto an MPC audio track. Stop recording, mute the instrument MIDI tracks, and play the recorded audio to verify the capture.
Save the Mac rack and MPC project separately. Load the saved Mac rack before connecting. Automatic Mac rack recall from an MPC project is not included.
For effects, choose FX → Add FX, select a scanned effect, arm Live Edit and press Add Selected FX. Existing rack limits and supported-effect policies still apply. Your plugin editor opens on the Mac.
Check these first
“Host unavailable”
Open the exact installed Companion-enabled RackSanity app. Check Power → MPC Companion Connection is enabled, confirm both devices share the intended network, and re-export pairing if the Mac address changed. Allow the app’s requested incoming connection through the Mac firewall; don’t disable the firewall.
The panel colors or Add FX list are missing
Check that an older RackSanity app is not running instead of the matching Companion host. The ordinary public beta app does not provide every Companion feature. If the FX list says no cached effects, scan your effects in the Mac app.
The knobs do nothing
Connect, select the intended rack, and arm Live Edit. The eight mapped controls require valid parameter assignments in RackSanity. An unavailable/unmapped control is inactive.
Connected, but no audio
Check the native MPC MIDI track’s destination/channel and RackSanity’s slot input/channel/output. Then check the Mac audio device, output level and mute state. Companion connection alone does not establish audio routing.
The app launches without Companion next time
Open Power → MPC Companion Connection and enable it on this Mac. Use the same installed app on relaunch. Disable stops the bridge and removes the startup opt-in while preserving its private configuration.