# customizing MackieControl using MTP

**URL:** <https://forum.bome.com/t/customizing-mackiecontrol-using-mtp/1053>\
**Category:** Bome Products\
**Created:** [February 3, 2019, 11:25am UTC](https://forum.bome.com/t/customizing-mackiecontrol-using-mtp/1053 "2019-02-03T11:25:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kde1](https://forum.bome.com/letter_avatar_proxy/v4/letter/k/ce73a5/32.png) [@kde1](https://forum.bome.com/u/kde1)\
**Post date:** [February 3, 2019, 11:25am UTC](https://forum.bome.com/t/customizing-mackiecontrol-using-mtp/1053/1 "2019-02-03T11:25:10Z")

</div>

Hi,

I want to customize MackieControl output using MTP.

So far I can create a Midi Through in MTP, sending the original data from MCU to DAW, and change specific Midi messages in MTP. That does mean, that the changed midi data and the original midi data are both sent to my DAW. Is it possible to define if/then rules to only partially use Midi through?

Thanks, Klaus

---

<div class="post-metadata">

**Author:** ![SteveC](https://forum.bome.com/user_avatar/forum.bome.com/stevec/32/8250_2.png) [@SteveC](https://forum.bome.com/u/SteveC)\
**Post date:** [February 3, 2019, 4:26pm UTC](https://forum.bome.com/t/customizing-mackiecontrol-using-mtp/1053/2 "2019-02-03T16:26:34Z")

</div>

Hi Klaus,

If you have translator that has the check boxed marked “Swallow” then the MIDI trigger associate that specific translator will not be passed through the default route **if the outgoing action happens**. If for some reason you have a rule within the translator that says “exit rules, skip outgoing action”, the default MIDI will pass through. The point is that the translator **incoming trigger must be tru** e AND **the outgoing action must complete** for Swallow to work (unless the outgoing action is “None”).

A trick for blocking most MIDI output even if outgoing action is skipped is to put a translator at the end of the chain such as this.

———-

Incoming: oo pp qq

Outgoing : None

Options : Swallow

* * *

In the above case any 3 byte MIDI message will be blocked “swallowed” through the default paths. You could do something similar with 2 byte and 1 byte messages in which case only Sys ex will get through.

Of course, if you do not draw a line between the MIDI input and output in the routing section, then nothing gets through except for any translators that you create rules for. I generally do this if I don’t want any “MIDI THRU surprises”.

Let me know if you have any further questions:

Steve Caldwell  
Bome Q and A Moderator and  
Independent Bome Consultant/Specialist  
[bome@sniz.biz](mailto:bome@sniz.biz)

&nbsp;

---

<div class="post-metadata">

**Author:** ![kde1](https://forum.bome.com/letter_avatar_proxy/v4/letter/k/ce73a5/32.png) [@kde1](https://forum.bome.com/u/kde1)\
**Post date:** [February 3, 2019, 6:37pm UTC](https://forum.bome.com/t/customizing-mackiecontrol-using-mtp/1053/3 "2019-02-03T18:37:49Z")

</div>

hi Steve, thanks for the insight.

l ´ m gonna meditate about your answer and try to figure it out 😉

&nbsp;

all the best,

klaus