Hi guys !
I just got a M-vave Chocolate midi footswitch controller and I would like to mute/unmute mixer channels with different neural dsp amps to play live.

I tried the link to controller button + pressing the footswitch & adding the correct port on the pop up window in FL but the 4 footswitch still just change if I'm going through : 808 kick - 808 Clap - 808 Hithat - 808 snare

If anyone could help me i'd be eternally grateful, thank you very much in advance !

(Using FL25)

 

Spoiler: Source: Grok KI

Hey there! Congrats on the M-Vave Chocolate—it's a solid, budget-friendly MIDI footswitch for live setups, especially with wireless Bluetooth convenience. I get the frustration; it sounds like your footswitches are accidentally mapped to MIDI notes that FL Studio is interpreting as triggers for drum samples (like in FPC or another drum plugin), instead of CC (Control Change) messages for muting/unmuting mixer channels or switching Neural DSP amp presets. This is a common hiccup with programmable controllers like the Chocolate, which defaults to note or preset modes unless you tweak it via the CubeSuite app.

I'll walk you through a step-by-step fix to reconfigure the Chocolate for CC toggles, connect it properly in FL Studio 2025 (FL25), and map it to mute/unmute mixer tracks with your Neural DSP plugins. This assumes you're using Bluetooth (most common for live wireless play), but I'll note USB alternatives. If you're on Windows/Mac, the process is similar—CubeSuite is available for both.

Step 1: Set Up the M-Vave Chocolate in CubeSuite App
The key is programming each footswitch (A/B/C/D) to send CC messages (not notes or program changes). CCs are perfect for toggling mutes (use CC values 0/127 for on/off) or switching Neural DSP amps (many support CC for preset banks or effect bypass).

1. Download and Install CubeSuite:
   • Search "CubeSuite" in the App Store (iOS), Google Play (Android), or download the desktop version from the M-Vave/Cuvave website (cuvave.com—look under support/downloads). It's free and required for custom mapping.
2. Connect the Chocolate:
   • Charge it fully (USB-C port on the side).
   • Power on the Chocolate—the Bluetooth LED will flash.
   • In CubeSuite, scan for devices and pair with "FootCtrl" or "M-Vave Chocolate." If using USB, plug it into your computer with a USB-A to USB-C cable (some users report needing a printer-style USB cable for stability, but standard works fine).
3. Program the Footswitches for CC:
   • In CubeSuite, select Advanced Custom Control mode (not basic or preset mode—this unlocks per-switch CC editing).
   • For each footswitch (A, B, C, D), go to the "Foot Switch Additional Options" section on the right.
   • Set Mode to "Single Step" or "Toggle" for simple on/off behavior.
   • Assign CC details:
     • MIDI Channel: Start with Channel 1 (you can change this later in FL if needed).
     • MIDI Type: Select "CC" (Control Change).
     • Data 1 (CC Number): Pick unique numbers for each switch, e.g.:
       • A: CC#20
       • B: CC#21
       • C: CC#22
       • D: CC#23
     • Data 2 (Value): For toggles like mute/unmute, set to 127 (full on) for press, and enable "Toggle" or "Momentary" mode so release sends 0 (off). For Neural DSP amp switching, use 0-127 values to select banks (e.g., 0 for Amp 1, 64 for Amp 2).
     • Optional: Enable "Long Press" for a secondary function (e.g., short press = mute, long press = tuner).
   • Banks: If you want more than 4 functions, set up Bank A/B switching (e.g., double-tap a switch to toggle banks, doubling your CC options).
   • Test in CubeSuite's MIDI monitor—it should show CC messages firing.
   • Save the preset and disconnect/reconnect to lock it in.

If the app feels clunky (some users complain about the UI), check this YouTube playlist for visual walkthroughs: "How to use the M-Vave Chocolate Midi Foot Controller" (it covers CC mapping around the 5-10 min mark).

Pro tip: Avoid note modes (like MIDI notes C1-G1, which trigger drums)—that's likely why you're hearing 808 samples. If it persists, reset the Chocolate to factory defaults in CubeSuite.

Step 2: Connect and Enable in FL Studio 2025

1. Open MIDI Settings:
   • In FL, go to Options > MIDI Settings (or hit F10).
   • Under Input, find your Chocolate (it might show as "FootCtrl," "M-Vave," or "MIDIIN2"). Enable it and set Controller Type to "Generic Controller" (not something drum-specific like "Drum").
   • If using Bluetooth, ensure Windows/Mac Bluetooth MIDI drivers are installed (search "Bluetooth MIDI driver" for your OS if it's not auto-detected).
   • Under Output, enable it too for two-way comms (useful for Neural DSP feedback).
2. Test MIDI Input:
   • Arm a mixer track for input (click the record arm button).
   • Step on a footswitch—watch the MIDI indicator light up in FL's toolbar. If you see notes instead of CCs, go back to CubeSuite and switch to CC mode.
   • If it's still triggering drums, check your project: Look for an FPC or drum plugin loaded on a channel with low notes mapped (e.g., C1= kick). Right-click the plugin > Replace > something non-drum, or remap its pads to higher notes.

Step 3: Map to Mute/Unmute Mixer Channels in FL
For live muting/unmuting tracks (e.g., to solo an Neural DSP amp channel):

1. Select the Mixer Track:
   • Open the Mixer (F9).
   • Pick the track with your Neural DSP plugin (e.g., Archetype: Plini on Track 1).
2. Link to Controller:
   • Right-click the Mute button on the mixer track.
   • Choose Link to controller.
   • In the popup, click Start (or the auto-detect icon)—then step on your footswitch (e.g., A for CC#20).
   • FL will detect the CC. Set Link to "Last tweak" or manual, and enable Toggle mode for on/off behavior.
   • Adjust sensitivity if needed (e.g., CC value >64 = mute).
   • Repeat for other tracks: B for Track 2 unmute, etc.
3. For Multiple Neural DSP Amps:
   • Load separate Neural DSP instances on different mixer tracks (e.g., Track 1: Clean Amp, Track 2: Lead Amp).
   • Mute all but one by default.
   • Map footswitches to unmute/switch: Right-click the track's Volume fader or Mute, link to your CC as above.
   • Pro move: Use automation clips. Right-click Mute > Create automation clip, then draw toggle points and link the clip to your CC for smoother live changes.

Step 4: Bonus - Direct Control for Neural DSP Plugins
Neural DSP plugins (like Archetype series) have built-in MIDI learn for footswitches—great for live amp switching without mixer mutes.

1. Load your Neural DSP plugin on a mixer track.
2. In the plugin GUI, right-click an amp model or effect bypass button (e.g., "Amp 1 On/Off").
3. Select Enable MIDI Learn.
4. Step on the footswitch— it auto-maps the CC to toggle it.
5. For preset switching: Right-click the preset browser, enable MIDI Learn, and assign CCs to bank up/down.
6. In plugin settings (gear icon), ensure MIDI input is enabled and set to your Chocolate's channel.

Test in standalone mode first (open the plugin outside FL) to confirm CCs register.

Troubleshooting Common Issues

• Still Hearing 808 Drums? Your project has a drum rack (FPC/Slicex) responding to low MIDI notes. Delete or remap it: In the plugin, right-click pads > MIDI settings > Change note triggers to high keys (e.g., C3+).
• No Detection in FL? Restart FL, toggle Bluetooth off/on, or try USB mode. In MIDI Settings, set "Enable" and increase buffer size if latency spikes.
• Latency Live? Use wired USB for zero-delay; Bluetooth adds ~10-20ms, fine for most but test your setup.
• FL25 Specifics: If you're on the latest beta, update to stable—some MIDI routing bugs were fixed in mid-2025 patches.

This should get you toggling between those Neural amps seamlessly for live jams. If it doesn't click (e.g., share your CubeSuite screenshot or exact error), hit me with details. Rock on!

 

Massive thanks =)
I got it setup ! Now I've found that having two amps at the same time is worth getting thrown out of the stage so the fix is to have the amps that are following each other during the track being pressed both at the same time, one being turned off and one turned on

Is there any way to make sure only one of the 4 amps is turned on and that when clicking on the next amps in the track it would automatically turn off the previous one ?
Thank you again !

 

Last edited: Oct 13, 2025