MOD POD Setup Guide
MOD POD can be used in several different ways depending on your workflow. Choose the setup that best matches how you make music.
Power
MOD POD requires power at all times.
When connected directly to a computer, power is supplied directly via USB. For setups that do not involve a computer connection, MOD POD will need an external USB power source.
Compatible Power Sources
- Power bank
- Phone or tablet
- Wall adapter
- Any compatible USB power source
Low Power Use
Because MOD POD has very low power consumption, most portable power banks can power it for extended sessions.
MOD POD → Computer / Laptop
This is the most portable setup. Simply connect MOD POD directly to your computer or laptop via USB.
With most DAWs, MOD POD works as a standard MIDI controller.
- Pitch Bend
- Modulation
- Manual Sustain
- Aftertouch
- Macro Controls
Important Note
Some features require MIDI loopback. This includes velocity control and advanced sustain modes (Latch, Smart, and Tight modes).
At this time, when connecting directly to a computer or laptop, full functionality is supported only in Ableton Live.
We are currently developing software that will create an invisible MIDI bridge between MOD POD and all major DAWs to allow for full functionality across all DAWs.
Ableton Setup
To unlock full MOD POD functionality in Ableton Live:
Step 1: Connect MOD POD
Connect MOD POD to your computer via USB.
Step 2: Open MIDI Settings
Inside Ableton, go to Preferences → MIDI.
For both Input and Output MIDI Ports, find "MOD POD" and enable:
- Track
- Sync
- Remote
Step 3: Create MIDI Track 1
Create a MIDI track.
Set MIDI From to Computer Keyboard.
Set MIDI To to MOD POD.
Arm this track.
Step 4: Create MIDI Track 2
Create a second MIDI track.
Set MIDI From to MOD POD.
Load your VST or instrument on this track.
Arm this track as well.
To arm multiple tracks in Ableton simultaneously, hold Command (Mac) or Ctrl (PC) and click the Arm/Record button on each track.
MOD POD → MIDI Controller → Computer
To connect MOD POD to another MIDI device, use the MIDI In and MIDI Out ports located on the back of the controller. Connect your MIDI controller's MIDI OUT to MOD POD's MIDI IN, then connect MOD POD's MIDI OUT back to your controller's MIDI IN.
MIDI OUT always connects to MIDI IN.
Depending on what type of MIDI ports your external device uses, you’ll need either 3.5 mm TRS MIDI cables or 5-pin DIN MIDI cables using 3.5 mm TRS adapter cables.
If needed, you can purchase compatible MIDI cables here.
Full Feature Access
This setup allows access to MOD POD’s full range of features, including velocity control and advanced sustain modes, regardless of which DAW you use.
MOD POD → Standalone MIDI Hardware
This setup uses the same cable requirements described in the previous setup.
In most cases, your MIDI device will need to be set to Local Control: OFF. This routes MIDI information out of the device, through MOD POD, and back into the device. Please check your MIDI hardware's manual for more information on how to change the Local Control setting.
Customizing MOD POD
When MOD POD is connected directly to your computer or laptop via USB, the CONFIG tool on the website will automatically detect your controller.
The CONFIG tool allows you to customize how MOD POD communicates with your DAW or other MIDI devices by changing Control Change (CC) values assigned to each control. Refer to your MIDI device manual and find the MIDI Implementation Chart for a complete list of CC values for that particular hardware.
Open Config ToolDefault Control Assignments
- M1 → Velocity
- M2 → No default assignment
- Pitch → Pitch Bend
- Mod → Modulation
- Aftertouch → Aftertouch
Important Note
The MIDI Channel assigned to your MOD POD needs to match the MIDI Channel assigned to your external MIDI device for proper communication. If your MIDI device is not generating audio, please check the MIDI Channel assigned to your device.
Understanding Plugin Behavior
When using MOD POD with a DAW, certain controls may behave differently depending on the specific virtual instrument you are using.
For example, M1 defaults to velocity control. If you turn the knob and do not hear any change in velocity, this does not necessarily mean MOD POD is malfunctioning.
Velocity May Require Internal Routing
Some VSTs are designed so that incoming velocity data does not directly affect audible volume or expression by default.
In some cases, velocity may need to be manually assigned inside the VST to parameters such as volume, filter cutoff, envelope modulation, or other internal parameters.