Merge MIDI IN messages with QC Preset MIDI OUT when MIDI THRU is enabled

As the QC does not send MIDI clock, I have a MIDI controller that connects to the QC’s MIDI IN port. I enabled MIDI THRU on my QC to sync my other pedals’ clocks. But I also have Preset MIDI OUT on many of my presets to change some of my pedals’ parameters when scene changing on the QC. The problem is that when MIDI THRU is enabled on the QC, Preset MIDI OUT will not work. This behavior is not documented anywhere, and I can still set Preset MIDI OUT messages.

We need the QC to merge its own Preset MIDI OUT messages with incoming MIDI messages when MIDI THRU is enabled.

From my understanding, MIDI THRU is by definition meant to send the incoming MIDI unaltered to the next device. Adding data to the incoming MIDI and then sending it to another device isn’t MIDI THRU anymore, is it?

Normally MIDI THRU is used when multiple devices are chained together and addressed via individual MIDI channels. Many MIDI devices have 3 MIDI ports. IN, OUT and THRU. As far as I know, THRU is used on purpose to avoid any additional MIDI data from receiving devices.

On the Eventide H9 it is possible to set “MIDI clock receive” and “MIDI clock send” independently. If “receive” is set to OFF and “send” to ON, the H9 will ignore incoming clock but send a clock signal with its own tempo. If “receive” is set to ON and “send” to ON, then it will adjust its own tempo to the incoming clock signal and send a clock signal with the same tempo to the next device. This has nothing to do with MIDI THRU though.

I guess, the QC needs a proper MIDI clock functionality in the first place and then it should provide a similar option as on the H9 for example.

3 Likes

I’m fairly new to MIDI, and I recall reading about the MIDI clock send and receive feature on some devices. The biggest part of my problem is exactly that: the QC does not send midi clock so I have to rely on another source up the chain. I just got a MIDI controller pedal which opens a lot of possibilities, but still, I’d love for the QC to be able to ‘thru’ the MIDI clock and messages from upstream, with the addition of being able to add my Preset MIDI OUT from the QC down the chain

1 Like

Most MIDI controllers are able to merge with MIDI Thru. The FCB1010 for example.

3 Likes

Voted! Ran into this problem today and didn’t realize it was a thing. Definitely would love a MIDI MERGE option like the BigSky has.

2 Likes

Had the same issue. Was told by support that they are working on it being a fully midi capable controller.

They said they’re not going to release it until it works flawlessly. I’m sure it will be coming soon enough.

In the meantime, I’ve gotten around using the QC footswitches almost entirely with a Morningstar MC6. But I’m sure anything with multiple midi outs will work fine.

I put the QC in Scene mode and switch presets, scenes and send program number changes to an external pedal.

The clock info is per preset, so I just use that for internal effects. I think you would need a clock like a Disaster Area to go into your multiple out controller or midi hub.

1 Like

Hey @ninety7 ,

I agree, its a problem. I hope they fix this question.

Thanks!

2 Likes

Up !

So important to fix this problem, it’s the basic of midi utilisation.

thanks :wink:

2 Likes

Agree. Minimum requirement is to document this limitation while it exists. It is very non-standard in Midi control land. And I wasted 2 hours today trying to figure out why it wasn’t behaving as expected.

but much better to actually fix it. Other devices have a “out/Merge Thru/Thu Only” choice which would allow for the current behavior.

I don’t know of any pedals that combine merge with through. It would require the ability to filter messages and send on multiple channels, or else it could potentially create feedback loops. I solved this problem with a cheap device from CME called the U6MIDIPro. It can merge, route and filter MIDI signals with 3 in and 3 out. I was able to link my RC600 and my H90 with the QC for patch selection, expression pedal and clock synch (with RC600 as master).

Latecomer to this feature request with a few comments:

Actually, the current MIDI thru behavior is as specified in the MIDI standard. Thru is thru, and not merge. Typically, thru is realized on an electronic signal level, so the signal isn’t even read and then sent. Not sure if this is how the QC implements Thru, though…

Fully agree - the description of the Thru function in the QC manual is pitiful “…enables the MIDI thru function” - especially NOT warning less experienced MIDI users that enabling MIDI thru will disable MIDI out…

I would strongly advise AGAINST using MIDI mergers with MIDI timing messages. Merging requires reading the MIDI signal, buffering it, sequencing the two streams so that messages don’t conflict and then outputting the result. This can significantly affect the timing of the signals, so using this e.g. for MIDI clock is not a great idea - you may get significant clock jitter as a result. Using “electronic” MIDI thru has far less of a risk of that happening - essentially, you’re getting (pretty much) the “original” MIDI signal, not a “processed” one.

With the new OS version, we’re now getting clock output, so part of the OP’s problem should be solved now.

But still, having the OPTION of choosing “Out”, “Thru”, or “Merged” for the output port would be a great addition, as long as you know what you are doing…

Certainly has my support - and my vote!

Regardless of the Midi spec definition, nearly every effects device with Midi ability that I’ve ever owned, which could also generate their own midi messages had a Midi Out port which could be set to Midi Thu or Midi Merge. Occasionally one might also offer “Out” only choice.
Including mid-90s Alesis rack effects, most guitar multi-fx pedals, and more.
This is what I mean be “non-standard”…

Nothing untill now… its so crazy.

we are waitting to use basic midi functions.

Thanks!

the fact that you can’t send midi out when midi thru is enabled, is whack. This think cost me over $3000 AUD and it’s a pretty basic function.

Nuts this still not been fixed or even planned to do so within next firmware (at time of writting thatd be 3.0). Its tbh one factor which stops me ever recommending the qc to anyone. its such a dumb choice of theyres to have implemented in the 1st place

1 Like

It’s not a “dumb choice”. Merging midi signals is a far more complex and involved bit of programming.
It’s not like audio where you just add two signals together, you have to get the separate messages and commands separated and lined up. That requires buffering messages, allocating memory etc…

It’ll come at some point, but as with any company, they don’t have infinite resources, so tasks get prioritised.

There’s plenty of things I would like the QC to do, or do differently, but I can’t change it myself, so just have to find work arounds.
You can get a midi merge box for ~£40 if it’s such a crucial thing.

Only just encountering this issue now as I dig deeper in to what the QC can do (and cannot do)

Anyone know of the midi improvements in the next update will address the issue of not being able to merge?

1 Like

they’ve made no specific mention of ‘merge’
Only adding more commands per switch and XP. I hope it’s not another half-baked ‘solution.’

2 Likes

This is still not possible? its been months… this is a breaking feature for my live setup…