(step-by-step tutorial) cheap 40$ Midi Bluetooth TRS footswitch for Fractal (M-Vave Chocolate)

Jiffo said:
I don't see why it shouldn't work, if the connections are straight through, as in tip to tip, ring to ring, sleeve to sleeve. There will be a slight resistance between the connections, but too small to make any difference.

Give it a try and see, the adapters are cheap and if you're anything like me, you'll probably have a few of these lying about for headphones.
Click to expand...

Thanks for your insight

overture1922 said:
Yes, I use this way, there is no problem.
Click to expand...

Standard 3.5mm jack to 1/4" Adapter that you would use with headphones, nothing special?
 
overture1922 said:
UPDATE: how to use it with TRS to midi cable.

You will need a MIDI-TRS type A cable.

View attachment 145673


View attachment 145679

If you have previously configured the Mvave Chocolate with Bluetooth, all the parameters will remain the same both on the the Mvave and the Fractal. Be sure to select ´´TRS-MIDI´´ on the Cubesuit.

View attachment 145672
Click to expand...

I can't seem to figure out how to get to the screen you are showing to select "TRS MIDI". How do I navigate there? I don't see any kind of settings wheel or link to get me to a global configuration. I am using CubeSuite on an iPad with the M-Vave Chocolate.
 
Last edited:
overture1922 said:
View attachment 154227
Click to expand...

Thank you! That was just what I needed for the TRS MIDI configuration option.

Still can't seem to get things working. I currently am using a TRS to MIDI hardwired connection from the Chocolate to the FM9. I set up the four switches under "Custom Control" mode in CubeSuite per your instructions earlier in the topic to use CC's 20-23.

I figured a quick and dirty test would be to use the learn mode under the 'Bypass' tab under Setttings --> 'MIDI Remote' to make sure I was getting MIDI to the FM9 but the 'Learn' function just sits waiting and never seems to see anything transmitted. Wondering if the pin configuration for my TRS to MIDI cable is correct. Doesn't seem to be. Do you know of anywhere on the FM9 to change the pin configuration for MIDI? The cable is molded so it would be difficult to change there.
 
overture1922 said:
As far as I know, there's no way to configure the pin connection on the Fractal. I am sure that the issue is the cable type.
Click to expand...

Agree! Pretty sure that the cable is the problem. Just looked at the TRS to MIDI pin configuration illustration on the CubeSuite and then tested the cable with a multimeter and that is definitely not how the cable is wired. Wonder what the MIDI pin to tip-ring-sleeve mapping should be from the Chocolate to the MIDI connector on the FM9?

Update: Saw your screenshot earlier in the topic for the required wiring from TRS to MIDI. Thank you for all the valuable info you have posted here!!
https://forum.fractalaudio.com/thre...-fractal-m-vave-chocolate.186861/post-2599122
 
Last edited:
I created my own TRS-MIDI cable using the wiring I found in this topic. Seems to be working properly but I encountered another issue. I have the Chocolate (not the Plus version). I used the recommended 'Custom Control' setting and set up each switch with its own CC#. The problem is that switch A is acting like a latching switch and switch D is acting like a momentary switch.

I am using the iPad version of CubeSuite and I don't see anywhere in the CubeSuite app to set a switch to latching or momentary. Would like all four switches to act as latching for now, but would like to be able to configure them separately in the future. Can anyone shed some more light on this. Thanks!

I would also like to be able to set up the switches to tap and hold. Need to resolve the momentary/latching issue first though.

Update - Latching/Momentary issue solved: Figured out what controls momentary or latching behavior on the Chocolate using the CubeSuite app. Under the 'Custom Control' mode. When you click on the 'Undefined' configuration for any of the footswitches there is a software/virtual switch labeled 'Visual Behavior'. If it is on the footswitch is latching, if it is off the footswitch is momentary. Not very intuitively named.

Note: I was able to set all four footswitches to latching with the iPad CubeSuite app, but the Windows version had a bug, at least for me that only allowed the 'Visual Behavior' switch to be set for footswitches A & B. Although I could set them on for C & D, every time I exited that configuration screen or the Windows app and came back in, they were off.

I am using the Chocolate, at least initially, just to toggle the bypass state on four different blocks. Using the FM9's 'Bypass' tab under 'Settings' --> 'MIDI/Remote' to configure it on the FM9 side. The 'Learn' function makes it a breeze to map the correct CC# to the Chocolate footswitches. First follow the instructions earlier in this thread to assign CC#'s to the Chocolate's footswitches under the CubeSuite's 'Custom Control' tab. Make sure you turn on the 'Visual Behavior' switch in CubeSuite for each switch that you want to act as latching (each tap changes bypass state).
 
Last edited:
overture1922 said:
Try this:

Advanced Custom mode 1 → Footswitch A → Mode

There you can select the working modes of each foot (right now I´m using the Single Step option)
Click to expand...

Yup, found that. My next efforts will be to test with mode 4 in CubeSuite. The tap & hold mode.

A shame that there is no visual feedback as to what a footswitch has activated and what state it is in (active or bypassed). You at least get that momentary message, I assume, if you set up the footswitch to leverage a layout footswitch. Not so much a Fractal issue as one that speaks more to the current paradigm and protocol for MIDI switching and the lack of more robust communication and a proper 'ack' between devices and MIDI switchers. That is where proprietary foot switchers like the FC-6 or FC-12 still have the edge, but I hope it doesn't stay this way forever.
 
I checked the controller and did everything according to the instructions. Now it works. Everything is fine. Button 1 works as Tap tempo, buttons 2 and 3 switch scenes up and down, button 4 is a tuner. I encountered a problem with the correct pinout of the cable. I had to open it and re-solder it according to the instructions. Now the question is how to make all four buttons assigned to scenes 4, 5, 6 and 7??
 
Maxxxiz said:
Now the question is how to make all four buttons assigned to scenes 4, 5, 6 and 7??
Click to expand...
If I understood you correctly, the footswitch assignment should work on every scene. I don't know what happened. For instance, my Chocolate is set up to use the loop and tuner. They work on every scene and preset.
 
I just want to switch scenes with buttons. Three scenes on the processor and four scenes on the controller. How to do this? that is, I press button A, scene 4 is turned on, button B, scene 5, and so on
 
Maxxxiz said:
I just want to switch scenes with buttons. Three scenes on the processor and four scenes on the controller. How to do this? that is, I press button A, scene 4 is turned on, button B, scene 5, and so on
Click to expand...

On Fractal do this:
1750023514162.png

On Chocolate, go to Advanced Custom Mode 1, then:
1750023608044.png
CC 34 0 for scene 1
CC 34 1 for scene 2
CC 34 2 for scene 3
CC 34 3 for scene 4
CC 34 4 for scene 5
CC 34 5 for scene 6
CC 34 6 for scene 7
CC 34 7 for scene 8
 
Last edited:
Maxxxiz said:
Thanks. If the first three scenes are included from the processor, then which midi command should I start programming with?
Click to expand...
Chocolate button A put CC 34 3 for scene 4
Chocolate button B put CC 34 4 for scene 5
Chocolate button C put CC 34 5 for scene 6
Chocolate button D put CC 34 6 for scene 7
 
You must log in or register to reply here.
Back
Top Bottom