We make a MIDI Clock Injector that can replace your polytec and merges Control and Program Change messages received with the MIDI Clock it generates: Also, running status should never 'saw off' the controller value, only the message type/channel which is the first byte of the 3 that make up a control change message. However, running status has nothing to do with MIDI Clock, as clock data ALWAYS takes priority over any other type of MIDI message. Running Status is actually a great feature of MIDI, as MIDI bandwidth is relatively limited (by today's standards). Glad to see you understand the advantages of MIDI-controlled gear! This is due to the fact the FX1 doesn't have MIDI thru capability Without going into War & Peace, I've had to use a MIDI merger to mix the main footcontroller (Axess FX1), MIDI clock (polytec 34One), and a MIDI Solutions Dual Footswitch Controller. This might be all fine and dandy for a keyboard player, but for a guitar player using multiple MIDI messages of the same type (especially control changes/CC's), it can cause all sorts of dramas like MIDI lockups and lockouts.įor those interested,I have a pretty complex MIDI controlled rack rig. And it does this by sawing off like status bytes in MIDI messages, that being the MIDI message type and MIDI channel. I've tried mergers from M-Audio, MIDI Solutions (the best of them) and a Kenton (hopeless), they all implement a degree of running status.įor the uninitiated (just my understanding, hope it's correct), MIDI running status is used to streamline data in MIDI. I'm hoping for some ideas for a MIDI merger that doesn't implement running status. Long time since I posted here, but here I go (hope it's the right place).

Midi solutions merger