Mic Live red light on Midas M32 using Yellowtec hush

Bome Products
1

Hi, i know very little about MIDI & i’d like to know if the following is possible using a Bome product.
Basically, i’d like to interface the Midas M32 mixer so that when any fader is open it triggers a red ‘mic live’ light outside the studio. The M32 has the following MIDI details:

MIDI Channel 1 is fader information, 0-127
MIDI Channel 2 is mute/unmute a channel
MIDI Channel 3 is pan, 0 hard Left, 127 hard right
MIDI CC for the faders is 0 for channel 1 & 31 for channel 32

The interface i was thinking of using is the Yellowtec Hush, this is a red light triggering unit that accepts a wide range of inputs to switch the light, including MIDI. i’ve spoken to Yellowtec support & they say it will work however the Hush can accept only one message per switching operation, so it could be set to switch when only one fader opens but as each fader sends different MIDI info some sort of global command (ie any fader open) needs to be sent to the Hush. Is this possible with MIDI translator? thank you.

2

Hi and welcome to the Bome community!

The following should be close to what you want but I only set it up for 8 channels for testing.

First, I set my aliases up as follows.

image
image368×275 5.5 KB

You may need to set them up for your actual devices.

You can learn more about aliases from this tutorial.

I use the global variable ga as a bitmap for determining fader values. If a given fader is more then 0 then the bit will be set to 1, otherwise it will be set to 0. Fader 1 is bit 0 , fader 2 bit 1 and so on.

If all fader value are zero the global variable ga=zero an we turn the light green.

For mute I use a similar method where mute status is controlled by global variable gb. Mute 1 = bit 0, mute 2 is bit 1 and so on.

If all channels (8 of them) are all muted, we turn the green light on no matter the state of the faders.

For 8 channels we mask the global variable at 255 (8 bits).

We determine the current state by my manipulating global variable gc. where it will be a value of either 127 (for red) or 0 (for green)

Translator 1.0 sets the mute state of gb. Translator 1.1 sets the fader state of ga. Translator 1.2 is just for my testing to turn all mute states on or off.

Both translators 1.0 and 1.2 call translator 1.3 which does all of the evaluation and determines whether to set a note on state or note-off state to the YellowTec. The output may need to be modified for the MIDI messages you want to send. I send note 60 on MIDI CH 1 value 127 for green an value 0 for red. If the state doesn’t change, I don’t send anything because I don’t want to flood the device with MIDI messages unless the state changes.

I tried to comment the rules as much as possible. If your logic is different, feel free to modify and use. If you want a custom solution, I’m available as a independent consultant for a fee.

The rules of translator 1.0 assume Note 0-7 on MIDI channel 2 for mute state.

The rules of translator 1.2 assume CC 0-7 on MIDI channel 1 for fader state.

Translator 0.2 sets the global variable used and 0.3 calls 1.3 to send the intial state to the YellowTec.

Good luck!

YellowTec-2025-05-06.bmtp (5.0 KB)

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz
3

Thanks for the detailed answer Steve, its fantastic! I’ve been doing some more research & i dont really need to use the Hush for my application (its very expensive!) as i only need to send a switching signal to the light controller. I think the MIDI solutions relay will do the job at less than half the price of the hush. For info, the MIDI solutions relay only needs to send either a contact closure or a low voltage (5-30VDC) to trigger an opto-isolated mains switcher which will turn the red light on.

4

Thanks for letting me know! The project file methodology would be much the same but maybe just a different MIDI message.

In my example, mute turns on green light only if all tracks are muted or if a track sliders are set to zero.

You might want to change that so it turns on the green (or off) by default and then turns on red light only if a given a given track is muted and the volume slider is not zero on that same given track. There are lots of different scenarios/logic that you might want to use and that is the trickiest part of setting it up.

With using bitmap logic and rules, most anything is possible.

You can even set it up to turn on when a given application is focused or not.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz