Frame, Pads, Views, and the Frame Editor
An in-depth practical guide to using your frame: pad types, connections, views, and editing workflows.
If you want to get comfortable with Framepad IO quickly, think in three building blocks: your frame, pads, and views.
A frame is your workspace for one setup or use case. Inside that frame, you add pads that either trigger actions or send MIDI messages. Views then let you present the same frame in different ways, depending on whether you are configuring or performing.
Start with a Frame
Your frame is your main control workspace. Keep it focused on your most important setup so it stays fast to navigate and reliable in real use.
When creating a frame, you can start blank or choose a template. Blank is ideal when you want full control from scratch. Templates are useful when you want a working starting point that you can refine.
What Is a Pad?
A pad is a control block inside your frame. Every pad has a purpose, such as triggering something once, holding a state, or sending a MIDI message.
Pads are grouped into three categories:
| Category | Pad types | Best use |
|---|---|---|
| MIDI | Program Change, Control Change | Sending concrete MIDI messages to your device (preset and parameter control). |
| Trigger | Button Trigger, Keyboard Shortcut | Initiating actions quickly from taps or keyboard input during testing and desktop workflows. |
| Controls | Round Knob, Toggle | Building an interactive control surface for dial-style and on/off behavior. |
Connecting Pads
Connections define how pads work together. In practice, many setups use a trigger or control pad connected to a MIDI pad.
A practical pattern is to keep interaction on one side and MIDI output on the other. This keeps your frame easier to read and debug:
Trigger or Control Pad -> MIDI Pad -> External Device
This separation also helps when you want to reuse your interaction layout but change device targeting later.
Frame Views: Why They Matter
Views let the same frame serve different moments in your workflow. Framepad IO supports Flow and Grid views.
| View | Best for | Why |
|---|---|---|
| Flow | Routing and structure | Makes connection logic easier to understand visually as your setup gets more complex. |
| Grid | Performance-oriented layouts | Gives you a clearer pad matrix for fast interaction during live use. |
A common pattern is to design routing in Flow view and keep a clean, play-ready layout in Grid view.
Using the Frame Editor Effectively
The Frame Editor is where you shape layout and routing. Changes are saved automatically, so you can iterate quickly.
In Flow view, you have access to the full editing toolset:
| Tool | What it does | Best use |
|---|---|---|
| Edit | Select and adjust existing pads and settings. | Fine-tuning behavior and configuration. |
| Create Pad | Click the canvas to place a new pad. | Building out your frame quickly from an idea. |
| Move Pads | Reposition pads in your layout. | Grouping related controls for readability. |
| Resize Pads | Change pad size on the canvas. | Emphasizing primary controls and reducing visual noise. |
| Connect Pads | Create routing between pads. | Building predictable interaction-to-MIDI signal paths. |
| Toggle Visibility | Show or hide pads in a view. | Simplifying what is visible without rebuilding the frame. |
In Grid view, editing focuses on layout actions such as moving and resizing, which is ideal for final performance preparation.
A Simple Workflow That Scales
If you are not sure where to begin, this workflow works well:
1) Start with a small goal (for example: switch two presets and one bypass). 2) Create only the pads you need. 3) Connect interaction pads to MIDI pads. 4) Test each path with your device before adding more. 5) Create a second view for performance polish.
By repeating this loop, you can grow from a tiny frame to a full rig controller while staying organized.
Final Tips
Name pads clearly. Keep related controls close. Use views intentionally instead of trying to do everything in one layout.
Most importantly, build around your real playing workflow. A frame that feels obvious under pressure is the frame that performs best.