By daanvanharen
Sun May 31, 2026 3:41 pm
Hey all,
I've got my Chocolate plus working with my MPC live 2 via the Cubesuite app. I found two sources of information somewhere (can't remember but thanks to those people!) listed below.
For me the trick was to make sure a line SYSex line in Cube Suite starts with 'F0' and ends with 'F7' in 'advanced custom mode'. I'm still trying things out but I got, start, stop and record working. See below for the mmc codes etc
--------------
How to control an MPC ONE PLUS WITH A MIDI FOOTSWITCH. Many folks have had problems making this work (including me!))
The key here is for the MPC ONE TO RESET TO START!
<br/>INSTRUCTIONS FOR M-VAVE CHOCOLATE + MIDI CONTROLLER FOOTSWITCH. :
Connect MPC ONE to M-Vave Chocolate + via Bluetooth (or MIDI cable):
• Turn on Bluetooth in MPC One: Menu>Preferences>Bluetooth
• Flip the Chocolate UOH Switch to H (Host) and it should connect
<br/>**Chocolate+Settings:**
<br/>Advanced Custom Mode Footswitch A: SYSEX Mode: Press Down Release (2 commands)
<br/>Bank A (Resets MPC Transport to 0): F0 7F 7F 06 44 06 01 00 00 00 00 00 F7
Bank B: (Play Start) Mode: Single Step F0 7F 7F 06 02 F7
Footswitch B (Stop): SYSEX Mode: Single Step F0 7F 7F 06 01 F7
Footswitch C (Continue Play): Mode Single Step SYSEX F0 7F 7F 06 02 F7
--------
<br/>**ADDITIONAL MIDI SYSEX INFO (MMC) for other commands:**
<br/>Core MMC Message Structure
• F0: Start of SysEx.
• 7F: Universal SysEx Manufacturer ID (for MMC).
• <DeviceID>: Target device ID (00-7F, where 7F is all devices).
• 06: Sub-ID #1 (indicates an MMC Command).
• <Command>: The specific action (e.g., 01 for Stop, 02 for Play).
• F7: End of SysEx.
<br/>**Common MMC Commands (Hexadecimal)**
• 01: Stop
• 02: Play
• 04: Fast Forward
• 05: Rewind
• 06: Record Strobe (Punch In)
• 07: Record Exit (Punch Out)
• 08: Record Ready (Arm Tracks)
• 09: Pause • 0A: Eject
<br/>**Locate/Goto Message (for Cueing)**
• This message uses a specific format to cue to a precise timecode (hours, minutes, seconds, frames, subframes).
• F0 7F <DeviceID> 06 44 06 01 <hr> <mn> <sc> <fr> <ff> F7. Response Messages
• MMC also uses Sub-ID #1 07 for responses, indicating status changes (e.g., device busy/ready). In essence, MMC provides universal transport controls, acting like a remote control for recording gear via MIDI, with specific codes for each function.
--------
**Update**: I bought the <ins>M-Vave Chocolate Bluetooth controller from Aliexpress</ins> because it was very cheap and I didn’t want to risk something more expensive not working. I’ve been able to get several commands working using SysEx messages and the rough but functional CubeSuite app.
- stop: 7F 7F 06 01
- play: 7F 7F 06 02
- record: 7F 7F 06 06
- reset: 7F 00 06 44 06 01 00 00 00 00 00
I've got my Chocolate plus working with my MPC live 2 via the Cubesuite app. I found two sources of information somewhere (can't remember but thanks to those people!) listed below.
For me the trick was to make sure a line SYSex line in Cube Suite starts with 'F0' and ends with 'F7' in 'advanced custom mode'. I'm still trying things out but I got, start, stop and record working. See below for the mmc codes etc
--------------
How to control an MPC ONE PLUS WITH A MIDI FOOTSWITCH. Many folks have had problems making this work (including me!))
The key here is for the MPC ONE TO RESET TO START!
<br/>INSTRUCTIONS FOR M-VAVE CHOCOLATE + MIDI CONTROLLER FOOTSWITCH. :
Connect MPC ONE to M-Vave Chocolate + via Bluetooth (or MIDI cable):
• Turn on Bluetooth in MPC One: Menu>Preferences>Bluetooth
• Flip the Chocolate UOH Switch to H (Host) and it should connect
<br/>**Chocolate+Settings:**
<br/>Advanced Custom Mode Footswitch A: SYSEX Mode: Press Down Release (2 commands)
<br/>Bank A (Resets MPC Transport to 0): F0 7F 7F 06 44 06 01 00 00 00 00 00 F7
Bank B: (Play Start) Mode: Single Step F0 7F 7F 06 02 F7
Footswitch B (Stop): SYSEX Mode: Single Step F0 7F 7F 06 01 F7
Footswitch C (Continue Play): Mode Single Step SYSEX F0 7F 7F 06 02 F7
--------
<br/>**ADDITIONAL MIDI SYSEX INFO (MMC) for other commands:**
<br/>Core MMC Message Structure
• F0: Start of SysEx.
• 7F: Universal SysEx Manufacturer ID (for MMC).
• <DeviceID>: Target device ID (00-7F, where 7F is all devices).
• 06: Sub-ID #1 (indicates an MMC Command).
• <Command>: The specific action (e.g., 01 for Stop, 02 for Play).
• F7: End of SysEx.
<br/>**Common MMC Commands (Hexadecimal)**
• 01: Stop
• 02: Play
• 04: Fast Forward
• 05: Rewind
• 06: Record Strobe (Punch In)
• 07: Record Exit (Punch Out)
• 08: Record Ready (Arm Tracks)
• 09: Pause • 0A: Eject
<br/>**Locate/Goto Message (for Cueing)**
• This message uses a specific format to cue to a precise timecode (hours, minutes, seconds, frames, subframes).
• F0 7F <DeviceID> 06 44 06 01 <hr> <mn> <sc> <fr> <ff> F7. Response Messages
• MMC also uses Sub-ID #1 07 for responses, indicating status changes (e.g., device busy/ready). In essence, MMC provides universal transport controls, acting like a remote control for recording gear via MIDI, with specific codes for each function.
--------
**Update**: I bought the <ins>M-Vave Chocolate Bluetooth controller from Aliexpress</ins> because it was very cheap and I didn’t want to risk something more expensive not working. I’ve been able to get several commands working using SysEx messages and the rough but functional CubeSuite app.
- stop: 7F 7F 06 01
- play: 7F 7F 06 02
- record: 7F 7F 06 06
- reset: 7F 00 06 44 06 01 00 00 00 00 00