GUIDE Audio interfaces
Connecting an external USB audio interface to your MPC
Every current standalone MPC can hand its audio engine off to an outboard USB interface instead of using its own internal sound device, which is how you get past whatever inputs and outputs shipped built in. That is one feature, documented on Akai's own Preferences > Audio Device screen. A separate feature lives on the exact same screen and gets confused with it constantly: MPC One G2 and MPC Key 37 G2 have their own USB Audio Channel Out toggle, 8 In/8 Out versus 24 In/24 Out, for how the MPC itself behaves when a computer or phone is the one doing the hosting. Same screen, same manual page, two different jobs. Every field, every quote, checked page by page against Akai's own manual, including a wording inconsistency inside the manual itself worth flagging plainly.
The short version
Akai's own Standalone OS manual documents this under one heading, Audio Device, and the opening line states the whole point plainly: the screen exists to "set up an external USB and Linux class-compliant audio interface for use with your MPC hardware." Flip the Audio Device field from Internal to the connected interface, and the MPC routes its own audio engine through that outboard hardware instead of its own built-in sound device. That is the feature this article is mostly about: your MPC acting as the host, an interface plugged into it acting as the guest.
The feature that gets confused with it lives a few lines down the same page, and it does the opposite job. MPC One G2 and MPC Key 37 G2 have a USB Audio Channel Out setting, 8 In/8 Out or 24 In/24 Out, and Akai's own note under it names the exact scenario it is built for: compatibility "with certain USB audio hosts, including Android devices." A phone can only be "hosting" USB audio if the MPC itself is the thing being hosted, meaning the MPC is the audio device in that pairing, not the host. That is the second feature: the MPC acting as the audio interface for whatever computer or device it's plugged into, not hosting a separate box at all. This article covers both, keeps them clearly labeled the whole way through, and flags a wording inconsistency inside Akai's own manual that makes the mixup an easy one to make.
Why hook up an external interface at all
Standalone MPCs ship with a fixed set of physical ins and outs built into the unit itself, whatever that specific model's chassis has room for. An outboard class-compliant interface is how you get past that ceiling without opening a computer or leaving Standalone Mode at all: more simultaneous mic or line inputs for tracking a full band or a multi-mic drum kit straight into the sequencer, extra outputs for a bigger monitoring or DI setup, or simply a preamp and converter you already trust more than whatever's built in. None of that requires Controller Mode or a DAW running on a laptop, it's a Standalone Mode preference, set once and left alone until you unplug the interface.
SAM'S NOTE: This is the setting I point people to first when they've outgrown a machine's built-in inputs but don't want to give up standalone workflow to get more of them. You don't need to touch a computer for this. Plug the interface in, flip one field in Preferences, and the pads are recording through it instead of the internal converters, same session, same screen, no Controller Mode detour.
Preferences > Audio Device: hosting an interface
Akai's own field-by-field description of the Audio Device screen is short. Quoted in full:
"The settings on this screen allow you to set up an external USB and Linux class-compliant audio interface for use with your MPC hardware. Audio devices must also be set to 44.1 kHz sample rate and 128 sample buffer size. Note: If you are unsure of your audio interface's compatibility, check with the original equipment manufacturer for more information. Audio Device: This determines whether you are using the Internal sound device, or a selected class-compliant audio interface connected to your MPC hardware."
Two words in that opening paragraph carry real weight: "class-compliant." Akai isn't shipping or certifying a list of supported interfaces here, it's naming a USB standard. A class-compliant interface is one that works with a generic driver built into the operating system rather than requiring the manufacturer's own installed driver, which matters a great deal on an MPC, since there's no way to install a third-party Windows or macOS style driver on standalone hardware. If an interface needs a proprietary driver to function on a computer, that's a real signal it may not work plugged straight into an MPC, and Akai's own note punts that exact judgment call back to the interface's manufacturer rather than publishing a compatibility list of its own.
The 44.1kHz / 128-sample requirement
The same opening paragraph states a hard requirement, not a recommendation: "Audio devices must also be set to 44.1 kHz sample rate and 128 sample buffer size." That's two settings you configure on the interface's own side, not on the MPC. Most class-compliant interfaces expose a sample rate and buffer size either through physical controls on the unit itself or a small control panel app the manufacturer provides for the computer, and Akai's own wording puts the responsibility for getting that combination right squarely on you before you connect, not on the MPC to detect and correct a mismatch automatically. The manual doesn't describe what happens if the interface is left at a different rate or buffer size when connected, so this article isn't going to guess at a specific failure mode the source itself doesn't spell out. Treat "must" as literal: set 44.1kHz and 128 samples on the interface first, then connect it and select it in Audio Device.
The 32 Inputs/Outputs checkbox
One field down from Audio Device sits a checkbox for expanding the channel count available through the connected interface:
"32 Inputs/Outputs: Check this box to enable use of up to 32 simultaneous inputs and outputs. Note: Increasing the number of simultaneous inputs and outputs will also increase CPU overhead."
The wording is a ceiling, not a guarantee. "Up to 32 simultaneous inputs and outputs" describes the maximum the field unlocks, actual available channel count still depends entirely on what the connected interface itself physically has. A 2-in/2-out interface doesn't gain 32 channels by checking this box, the box just raises the MPC's own internal cap so it doesn't artificially bottleneck a bigger interface that does have more channels to offer. Akai's own note is worth taking at face value rather than skipping past: leaving this checked when your interface doesn't need that many channels burns CPU overhead for headroom you're not using, so the honest default is to leave it unchecked unless you're actually running a multi-mic session that needs it.
Setting it up on the hardware
The full procedure Akai documents for this screen is short and doesn't go beyond the field descriptions above, so here's what that translates to on the hardware, stated plainly rather than padded out with steps the manual doesn't actually give: set your interface's own sample rate and buffer size to 44.1kHz and 128 samples first, connect it to your MPC's USB port, open Menu, go to Preferences, select Audio Device, and change the Audio Device field from Internal to the connected interface. Check 32 Inputs/Outputs only if the session genuinely needs more than the interface's default channel allotment. That's the entire workflow this section of the manual documents, no separate procedural mode, no additional confirmation screen described.
MPC One G2 / Key 37 G2's separate channel toggle
This is the feature that shares a screen and a general subject with everything above, and is not the same thing. Quoted in full:
"USB Audio Channel Out (MPC One G2 and MPC Key 37 G2 only): This determines the number of available USB audio channels: 8 In, 8 Out or 24 In, 24 Out. Reducing the channel count can improve compatibility with certain USB audio hosts, including Android devices."
That single word, "hosts," is the tell. A host is the device that manages the USB connection and enumerates the peripherals plugged into it, the same role the MPC itself plays in the "Preferences > Audio Device" feature covered above. Here the roles flip: an Android phone or tablet can only be the host if the MPC is the thing being hosted, meaning the MPC's own USB-C port is presenting itself as a multi-channel audio device to whatever computer or phone it's plugged into. Reducing the channel count from 24 to 8 is offered specifically as a compatibility fix for hosts, phones especially, that choke on a higher channel count. Akai's own "Updates in v3.9" summary of MPC One G2 and MPC Key 37 G2's new features backs up that reading directly, describing this as expanded "multi-channel recording and routing capabilities when using class-compliant devices," delivered specifically alongside new "USB-C host and device support in standalone mode, enabling direct connection to USB audio interfaces, MIDI controllers, and storage devices without a computer." Host mode is the outbound-interface feature this article opened with. Device mode is what this toggle governs: the MPC being recorded from by something else, a computer running a DAW, or an Android phone, over that same USB-C port, exposing either 8 or 24 channels depending on the setting.
Two features, not one
| Hosting an external interface | USB Audio Channel Out toggle | |
|---|---|---|
| Who is the USB host | Your MPC | The connected computer or Android device |
| What plugs into what | An outboard interface plugs into the MPC | The MPC plugs into a computer or phone |
| Fields involved | Audio Device (Internal/external), 32 Inputs/Outputs | USB Audio Channel Out (8/24) |
| Hardware scope, per the manual | Not model-restricted in the text | "MPC One G2 and MPC Key 37 G2 only" |
| Requirement | 44.1kHz sample rate, 128 sample buffer, class-compliant device | None stated beyond the channel count itself |
Every field in that table lives on the same Preferences > Audio Device screen, described across the same handful of sentences in Akai's own manual, which is exactly why it's easy to read the whole page as one feature. It isn't. One direction is your MPC hosting outboard hardware. The other is your MPC being hosted by something else. Same screen, opposite roles.
A note on manual versions
Every claim above is checked directly against Akai's Standalone OS User Guide, Manual Version 3.9, page 62 for the full Audio Device screen and page 8 for the "Updates in v3.9" feature summary, both confirmed against the printed footer number on the extracted page itself. Manual Version 3.7's equivalent Audio Device section sits on page 58 and is word-for-word identical for the intro paragraph, the Audio Device field, and the 32 Inputs/Outputs checkbox. What's missing from v3.7 entirely is the USB Audio Channel Out bullet, because MPC One G2 and MPC Key 37 G2 didn't exist yet at that manual version, a genuine feature addition rather than a rewording. The table of contents in the v3.7 file confirms the same boundary from the other direction: its Technical Specifications section lists MPC X, MPC Live, MPC Live II, MPC One/One+, MPC Key 61, and MPC Key 37, with no G2 models anywhere in that list.
One more inconsistency worth stating directly rather than smoothing over, per this site's standing rule that conflicts get disclosed, not silently resolved: within the v3.9 manual itself, the same setting is given two different field names. The full field description on page 62 labels it "USB Audio Channel Out." The "Updates in v3.9" feature summary on page 8, describing the same toggle in the same 8/24 terms, calls it the "USB Audio Channel Count setting." Both sentences describe the identical control, in the identical manual, and neither page cross-references the other's exact label. If you're hunting for this setting by name and only find one of the two labels in a search, that's the manual's own inconsistency, not a sign you're in the wrong menu.
A third data point complicates the model-scoping question further rather than resolving it. Akai's separate MPC Live III / MPC XL User Guide, internally labeled Manual Version 3.7 in its own header despite being a different document from the general Standalone OS Guide of the same version number, includes this exact USB Audio Channel Out bullet, word for word, including the Android host compatibility note, but without the "(MPC One G2 and MPC Key 37 G2 only)" qualifier attached to it in the general guide. That could mean the restriction genuinely doesn't apply to MPC Live III or MPC XL and the general guide's parenthetical is specific to that document's context, or it could mean the qualifier was simply dropped in the MPC XL guide's version of the same boilerplate text. Akai's own MPC Live III-specific User Guide, a separate document labeled Manual Version 3.6, doesn't include the USB Audio Channel Out bullet at all, only the 32 Inputs/Outputs checkbox, which points toward the toggle being a genuinely newer addition rather than something MPC Live III has simply always had unlisted. This article isn't going to guess which reading is correct. If you own an MPC Live III or MPC XL and want to know whether your specific unit has an 8/24 USB Audio Channel Out toggle, checking the Preferences > Audio Device screen on your own hardware directly settles it faster than any manual comparison can.
See also: Enable Disk Streaming
The section immediately following Audio Device in Akai's manual, on the same page, is Audio/Export, and its first field is relevant to anyone tracking multiple simultaneous inputs through a new interface: Enable Disk Streaming, which lets samples stream from a drive instead of loading fully into memory, recommended against an SSD connected to your MPC's internal SATA port where available. If you're about to start tracking a full band through a multi-input interface and expect long simultaneous takes across many tracks at once, that's worth a look before you hit record, though it's a separate setting from anything on the Audio Device screen itself and this article's core subject stays the interface connection, not disk streaming.
Common mistakes
Mistake: connecting the interface before setting its own sample rate and buffer size. Akai's manual states 44.1kHz and 128 samples as a requirement on the interface's own side, set before it's selected in Audio Device, not something the MPC negotiates for you.
Mistake: leaving 32 Inputs/Outputs checked by default. It's a ceiling for interfaces that need it, not a setting to leave on for headroom, and Akai's own note ties it directly to added CPU overhead.
Mistake: hunting for "USB Audio Channel Count" only in Preferences and giving up. The field itself is labeled "USB Audio Channel Out" on the actual Audio Device screen. "USB Audio Channel Count" is the name Akai's own v3.9 feature summary uses for the identical setting.
Mistake: assuming the 8/24 toggle changes how many channels an external interface offers. It doesn't. That's the 32 Inputs/Outputs checkbox and the interface's own hardware. The USB Audio Channel Out toggle governs the MPC's own channel count when a computer or Android device is hosting the MPC, the reverse relationship.
Verdict
VERDICT
Adding more inputs and outputs than your MPC has built in: that's Preferences > Audio Device, Internal switched to your connected class-compliant interface, set to 44.1kHz and 128 samples on the interface's own side first, with 32 Inputs/Outputs checked only if the session actually needs that many channels. Your MPC One G2 or Key 37 G2 not showing up cleanly, or at all, on an Android phone or a picky computer over USB: that's the separate USB Audio Channel Out toggle, dropping from 24 In/24 Out to 8 In/8 Out, on the same Preferences screen but governing the opposite direction of the connection. Same page of the manual, two different jobs, and confusing them is the single easiest way to spend an hour troubleshooting a setting that was never going to fix the actual problem.
Run into a class-compliant interface that didn't play nice, or a channel-count fix that saved a session? Tell us what happened.