No pirates in my house! It’s a hazard symbol !
The maximum general audio level is set at -4dB, but if absolutely necessary this pedal can be increased from -4dB to +6dB… 
1 Like
So you went all digital? Can you list the software you chose and the hardware it works on?
Thanks
Just curious.
Windows 11 Pro 22H2
MSI computer i7-12650H, 32 GB RAM
As I’m working with a writer-poet who reads his texts in public, I accompany him alone by playing my musical and sound atmospheres creations.
4 hours of programmes, totally different atmospheres each requiring a huge number of instruments and effects.
For creation, edition, mixing, recording (sending to Reaper) and live performances: Gig Performer, that’s it, it’s all in there.
Thanks to the controllers, I can play without ever taking my hands off the guitar.
MG is at the very beginning of all chains in Gig Performer, but only for MIDI conversion and the use of some Midi Machines.
In GP I use a wide range of other plugins (amps, fx, instruments, loopers, players, scriptlets, mixers, etc.).
The list is long, longer than you can buy hardware for!
More info here: https://youtu.be/LnHB-79LM70
BUT: for jamming or playing with simpler configurations in short performances: MG, that’s it, it’s all in there too 
1 Like
Thanks a lot - love the video.
However what was most amazing for me is your 4h gig!
Great stuff and using Windows 11 means you solved the latency problems that people talk about.
Impressive!
A lot of things I still need to practice then. 
4 hours, but not all at once! That’s our entire repertoire, but public readings generally last between 45 and 90 minutes.
There’s no secret about it: a PC that comes out of the factory will never be able to work properly in real time with a latency lower than that of a DAW. It needs to be dedicated solely to audio and optimised as much as possible.
Guide to Optimize your Windows PC for the Stage
1 Like
Wow, you guys are blowing me out of the water. Thanks so much for all the ideas and gear advice. I can see how my whole living room will be taken over by it- I’m halfway there already.
Back on MIDI Controller topic I might have hit something in my Meloaudio. I was trying to create an ad-hoc configuration by using Custom Mode. When used in Custom Mode the press of momentary foot-switches are not caught by MG3. When using the factory (toggle - latch) mode it works.
Did you experience the same problem with other controllers? I am operating MIDI Commander via an USB HUB (Powered). I think I read somewhere (or was answered on this forum) that ‘momentary’ data depends on controllers and might vary. MIDI Monitor reports each footswitch press correctly but when I use MG3 it does not work. By default MIDI commander latest firmware before end of life send cc # and 127 (Press) not 64. I might need another controller but before spending money on MIDI Captain (I like the form factor) I might need a confirmation. Thanks.
MIDI footswitches send 0 or 127, that is all, 64 is not possible unless modifying a curve in the controller’s application if existing…
Momentary send 127 when pressing, 0 when releasing.
Latch send 127 when pressing and stay to 127 until pressing again to go back to 0.
Usually, you define the mode in the application provided with the controller.
In your case, if factory mode works, keep it and, then in MG, assign to the virtual controllers the CC numbers corresponding to those of factory mode.
To change the type of footswich action, click in the small window under the controller number and select latch, invert or - (the last 2 are momentary but 0-127 or 127-0).
Next, you’ll need to determine why Custom Mode isn’t working, so you’ll certainly need to read the manual carefully. 
1 Like
Hi Harold thanks for reply.
I played with what you posted in the image… to no satisfaction. It does not work.
With program ALL CC (Factory Firmware with ALL CC + Toggle) it works as shown in the Video:
Unfortunately with Custom Mode (toggle off) it does not work as shown (after a successful learning it does not switches off even if I change to LATCH). LATCH is not shown I forgot to capture it but it did not work in the test:
I think I recall somewhere (in another thread) that momentary switches messages should have a duration. If you exceed that duration the message is misinterpreted maybe.
Stranger enough in Ableton Live I can manage the Live Looper with the same configuration (Custom) that it does not work with MG3. Midi Commander was abandoned Mid Air and a lot of firmwares were issued to correct various things, including the ‘hang’ on some units. That’s why I updated the Firmware with a no hang version. That also changed the Power On + A program ALL CC moving it from ‘momentary’ to toggle = ON. Hence I had to go Custom with Ableton Live Looper (at least now with no hangs it seems) while I can use ALL CC program that’s all CC with Toggle ON. Who knows which unsolved bugs this firmware has… but it’s an interesting discovery…
That’s Ableton Definition :
Toggle and Momentary MIDI functions
- Live Versions: All
- Operating System: All
MIDI control buttons are usually capable of sending either Toggle or Momentary messages.
A Toggle MIDI message means the pedal or button sends out a value of 127 when pressed once. This does not constitute a complete message for certain parameters until it is pressed a second time and a value of 0 is sent. Most footswitches usually send Toggle by default.
A Momentary MIDI message, sends a value of 127 when pressed, and 0 when released.
And here’s the old thread topic :
It’s difficult to analyse your videos as I’m having trouble seeing the controller numbers and the operating mode chosen in MG (under the controller number: - invert or latch).
Also, you should indicate the corresponding controller number assigned in the Meloaudio application in factory and custom mode.
Finally, you should only match one controller in MG as the cables of the 2 controllers displayed are mixed up, I can’t see where one goes and where the other goes.
Sorry, I don’t have a good view.
1 Like
Hi Herold,
I’ll shoot the videos once more tomorrow and reload. Thanks for the suggestion. I’ll follow it.
MG3 was always in - mode.
In factory mode I use CC 1, CC 2 in Toggle ON.
In Custom CC81 in Toggle OFF.
But it’s better for everybody’s understanding to shoot again the videos and make a better work in explanation! Thanks for pointing this out.
Ciao
Pasha
PS : Don’t be sorry… my eyesight needs big Lens just to read Whataspp messages …
I was reading your post with interest! My MIDI Commander worked well in custom toggle mode (after initial set up I did) on all 8 switches. Since 2 days it doesn’t work at all anymore. Now reading in your post that this seems to be a “known” issue I took the piece out of the garbage bin again.
Do you have a source for that firmware update you did?
1 Like
Sure!
Here’s the onedrive link to download : MeloAudioArchive1.zip
Let me know if download works. 
Instructions :
I have been successful in replacing the firmware using a Windows 11 Machine.
Steps :
Download the package provided
Expand the package (unzip)
Find file : en.stsw-stm32080.zip and expand it
Install the software by clicking on DfuSe_Demo_V3.0.6_Setup.exe
Now comes the tricky part (I had to find out my self and took me some time):
After installation find here C:\Program files (X86)\STMicroelectronics\DfuSe\bin\ the Driver ‘folder’ and install from there the driver according to your architecture (there are two files : dpinst_amd64.exe or dpinst_x86.exe)
After this go back to the main directory where you expanded the main package and look into the zip files (read the readme.txt file for each of them) and once you have selected the proper FW for your needs then follow the instructions (each zip file has a PDF file with instructions).
I was able to install a new firmware although I run Windows 11. Do not use a USB Hub, connect MELOAUDIO directly to PC.
Keep in mind that originally foot switches sent cc. with a value of 64!
Then it came the ALL CC firmware (with hungs) where all 8 footswitches where toggle OFF (and 127 was sent)
Then it came a release with ALL CC,Toggle OFF and no hungs (or so they claim) (127)
Then it came a release with ALL CC,Toggle ON and no hungs (127)
The program is always the Power ON + A.
Hope it helps, to me the hardware is not 100% reliable even after the new FW. What they try to cure with a new FW was an initial production batch that becomes unresponsive after some time (you have LEDs on and off but no CC is sent). After the ‘cure’ it works better and hungs are less frequent but here and there they still happen. I have it connected to an USB 2.0 Powered Hub which is pretty crowded (6 devices out of Seven) so it might be my configuration. YMMV.
Enjoy!
1 Like
@pasha Wow, thanks a lot for your help. I’ll check it out and let you know whether the unresponsive controller will work again after the FW update.
PS: it worked fine on my Win11 laptop. When I moved it to my Mac (10 port USB hub), it first worked fine too but after about 2 weeks it started to hang.
Download worked!
1 Like
Great! Good luck! Looking fwd to know if it works for you.
I would like to connect an expression pedal and a breath controller via USB to my Mac.
Which one of the two works best?
for expression you probably want the breath controller.
for control (volumes, efx levels, blends) the exp pedal is the way to go.
the breath controller allows a much finer level of control (especially if you are already a singer, harmonica or wind player). it’s easier to do the mark knopfler volume swell with a breath controller than an exp pedal.
Ok, but which MIDI interface should I get ?
It is difficult to give advices. If you really just want one expression pedal you could buy one that outputs MIDI already. They are a bit more expensive but you don’t need a dedicated MIDI interface since they are connected directly to your computer via USB.
If you like to expand your setup in the future it’s better to go for the MIDI interface solution.
For the breath controller I’d recommend the TEC BBC2 model.
Thank you Dutti67, will get a MIDI pedal, the breath controller already works via USB Midi.