More MIDI control

I couldn’t see if anyone mentioned this, (sorry if I missed throughout 41posts):

There is no distinction between 0 or 127 value for the footswitch CC numbers. So for either value sent from any midi source switches are toggling. Therefore we cannot synchronize the toggle states of any external midi controller with QC’s switch bypass state.

For ex. Using Fcb1010, normally I can map Stomp default behavior of any given scene (I have UNO chip by the way) giving dedicated values, however QC is ignorant with them. So there may be times where my stomp led is on, but QC’s switch is off.

Solution is too simple, I guess. Just separating on off values of switches’ Cc numbers 35-42. 0-63 bypassed, 64-127 engaged.

Hope to see some progress in Midi implementation soon.

Yep, sounds SO simple doesn’t it…but alas, it seems too complicated for the programmers at Neural!

This is one of the most upvoted feature requests and I really don’t think this is a hardware limitation, so they will have to get around to this at some point. I’ll just keep posting ideas to this thread to keep the activity high.

I just want to be able to use midi through and midi clock out at the same time

Adding my two cents to this. As a new OC user, the lackluster MIDI functionality is one of the only gripes I have with the unit. I came from an HX Stomp XL, where you can assign arbitrary CC numbers to any parameters you want. I also want to be able to set a footswitch to send a MIDI command, but not also be tied to a scene or stomp. This is another thing that HX/Helix does easily. It’s concerning that we’re this far into the QC’s life and this still hasn’t been improved. Robust MIDI capabilities should be standard stuff at this point, especially with so many bands using MIDI automated setups.

Yes, it is puzzling why expanding MIDI has taken so long. It’s been highly requested, virtually all of the competition has more advanced MIDI and, (I’m not a programmer but) it seems like it would be one of the easier features to expand.

There are a few hacks that folks have come up with, for instance, I found one (posted on the forum) that allows me to use MIDI pedals to turn up to 8 FX blocks off and on while in Preset mode. The forum can be a great resource.

As you’ve probably figured out, your QC has lots of big attributes and has plenty of amazing sounds available. The last update added lots of cool features, lets hope that expanded MIDI will be in the next one.

Welcome to the QC universe and the forum!

Hey Pete, can you steer me to some of those midi hacks?

Well, there’s only one that I use and it goes like this…say I’m in Preset mode, so the QS’s onboard foot switches select the 8 presets in a particular bank, but I also want to turn different FX blocks off and on. I have two Hotone MIDI controllers giving me a total of 8 more footswitches. In Stomp mode, I assign the 8 onboard FSs (foot switches) to turn different blocks off and on. I set up each of the Hotone FSs to send three commands, a command to put the QC in Stomp mode, then send a command to trigger a specific FS on the QC, then third command to return the QC to Preset mode. When I press a Hotone FS, the 3 commands are all sent very quickly (less than 300ms?) so I don’t even notice any delay. If you want to access a different feature, for instance, change Scenes from Stomp mode, you only need to change the first and third commands from your MIDI controller. You can even have different banks on your controller for different functions. I hope this all makes sense.

I wish I could take credit for this hack but I stumbled onto it in a forum post a couple of years back. Concerning other MIDI hacks, figure out what you want to accomplish and search the forum or post a question about that specific task.

Ah! Yes, thanks….I’m currently using that hack but just switching back and forth between scenes and stomps.

I’ve been thinking about a different hack but haven’t seen it here in the forum. It would involve the 8 switches in stomp mode but instead of using them for individual FX, setting each switch up to turn on a group of FX…kind of like setting up a scene BUT doing it in stomp mode. The rub is you need to have an empty scene (or maybe 2) that you can switch to, setup with ALL the FX OFF because using this method in stomp mode won’t set the FX that are ON to OFF when you switch between theses “stomp scenes”. ULTIMATELY that would give you 14 “scenes”. I’ve toyed around with this but haven’t implemented it…I’m kinda thinking that it might be too slow for a real-time performance.

Anyway, just an idea to mess with since it seems Neural is still dragging their feet on implementing realistic, internal midi control.

Hmmm, correct me if I’m wrong but, I believe you can assign more than one thing to a foot switch. Say you have a delay block set for a slapback and another set for a long delay with repeats. If you assign their active/inactive buttons to footswitch A, then store the preset with the slapback block active and the long echo inactive, when you go to Stomp mode and press footswitch A, it should toggle back and forth between them. Is that what you had in mind? I can’t access my QC right now to verify that it’s possible.

Hey Pete, yes…you’re right. That’s basically what I’m saying about having “stomp” mode be a quasi-version of scene mode, i.e. setting each button up to perform like a scene with various FX on or off. The issue then is when you go between the different switches in stomp mode there is no memory of what effect is on so you’d end up with FX that are on when you want them off. The FIX for that would be to use midi to switch to an empty scene (i.e. losing a scene), which would turn OFF every effect not needed, then back to whichever stomp button setting you wanted.

Now, you’ve got me thinking about program mode and I’m wondering if having a basic, empty program to call would keep the amount of scenes at 8.

I have time today to test this….maybe 2 days hahaha. I’ll let you know how it goes.

So….between the Holidays I had the time to try my idea of using “stomp” mode as a quasi-scene mode, i.e. setting several devices on or off per switch. To control the state of the devices I figured I could make an EMPTY scene where ALL the devices were set to off (or bypass) and switch to that via midi in-between stomp scenes. Ultimately, NO DICE! The issue is that Neural has defeated that ability (via Mode Control) when using an external midi controller. It works fine IF you use the switches on the QC itself BUT my thought was to have a controller that had a bigger footprint with more switches. Needless to say…I’m frustrated after spending several days trying to figure out this work-around only to find that Neural has purposefully defeated that capability.

Now, before someone responds with “but the QC CAN be controlled with an external controller!!” I want to say that I am NOT talking about just controlling the QC’s switches via an external controller. I’m trying to hack the system a bit by using “stomp” & “scene” mode to create flexible, quasi-scenes where a group of devices are ON PER SWITCH in stomp mode.

I just wanted to post this for anyone else in the forum who might be trying the same thing. Please, if you’re out there….let me know!

Have you tried hybrid mode? Hard to say exactly, but kinda seems like scene mode would be what you’re actually after, especially with wanting to control multiple blocks with a footswitch…. Maybe I’m confused as to why you’d need something more specific beyond that, since scene mode does exactly what you’re describing

I think he’s looking to use more switches in addition to what’s on the QC, which is the hangup- bcz every midi function is essentially tied to footswitches on the QC instead of individual fx or blocks, etc, so we basically can’t configure more than 8 scenes or stomps. Even just being able to split up Hybrid Modes into customizable switches would help, but we can’t do that either.

Correct xush! I want to put the QC in a rack and control it with an external midi switcher but I’m hemmed in by Neurals lack of direct midi on/off control of the individual devices.

Over 3 years now I’ve been requesting better Midi control, even contacting customer support but NO answer or explanation. Frustrating!

Ahh yeah I see what you mean. Honestly it’s a bummer Neural haven’t made the midi up to date with what any other similar modeler can do

The only workaround I could imagine is to use different presets with the same blocks. Then you would have 8 scenes and 8 stomps per preset. And send multiple cc messages to change preset and activate the stomps or scenes you like.

But then you would introduce gaps when switching, so probably no real alternative.

As a new QC owner, it’s disheartening to see this thread from three years ago with virtually no solution since. I love the unit and everything it can do, but the lack of useful MIDI control is stopping me from replacing my whole live rig with the QC.

I play in a jam band and keeping live improv fresh is the goal. Therefore, it’s helpful for me to have a bunch of effects I can turn on and off individually (say, sixteen) to get new sounds as “prompts” for jams (mixing and matching sixteen is a lot of combinations!). I made a Preset with the FX I wanted, sounded great. Figured I’d just buy an external MIDI controller with eight more buttons and have completely replaced my pedalboard. Guess that’s not possible.

I’m currently using hacky workarounds like using Scenes as “pseudo-stomps”, but it’s not the same since on/off states are not maintained across Scenes. And since the goal is to have the songs sound new and different each time, coming up with a load of Presets or Scenes or “default sounds” via Stomp combinations doesn’t really cut it.

Has there been any response at all from the devs about whether they plan to address the issue? It’s so disappointing to know such an expensive unit lacks such basic functionality.

Hey Space…the short answer is “NO”, NADA, NOTHING. I’m not sure who started this thread 3+ years ago (maybe me :face_with_spiral_eyes:) but there’s been nothing from NDSP about adding more midi control. I’ve even gone back and forth with tech support about it and have gotten nowhere. At this point I’ve given up hope.

I still like my QC and continue using it despite its midi control short comings. I’m waiting to see if the Helix is a viable alternative…if it’s even CLOSE to the QC feel-wise I’ll jump ship and won’t look back. Until then it seems ALL we (the user base) can do is cross our fingers, wait and hope.

Just wanted to tell you that this method is a game changer for me and even though it’s a workaround, it works well! Thank you and thank whoever originally posted that workaround.