D::light and Behringer X-Touch via Bome

Hello,

 

I've managed to translate the HUI coming from the Behringer to a simple CC my lighting program understands thanks to previous posts and your advice to send the RAW midi message:

B0 00 pp B0 20 pp

So I'm able to control whatever midi assignments in the program with the Behringer. Thanks for that!

What I didn't manage properly yet is the way back: the program controlling the Behringer faders.

The way it kind of works is having a second translator for the returning signal from d::light which i sent through IAC 1 (to avoid midi loop). I captured the outgoing midi signal with the MIDI-monitor app and outputed again with RAW midi message B0 00 pp B0 20 pp to the x-touch.

This actually works, i can then control the Behringer faders out of d::light... BUT in this setup the other way around doesn't work anymore... the Behringer then sends incoherent midi to d::light. After deleting the second 'return-translator' it works fine again.

 

I guess I'm too ignorant for understanding the complexity of HUI or Bome...

Any idea how I could approach the problem?

Thanks a million

 

 


Attachments:
1576701069656_D-light-mit-returns.bmtp

Hi,

It appears you have all input ports going to all output ports in many cases. You know you can override the default ports and the preset level and at the translator level. Preset defaults override project defaults, translator defaults override everything.

I suggest you separate your translators into different presets by the input devices you want to control to override the project defaults. This is usually the preferred method as there will later be less presets to change if you make modification as there are less presets than translators.

So you set up a preset that you override defaults as From Behringer to Application. These will be the HUI to CC messages. Put all supporting translators for this path under that preset.

Then another preset to override defaults as From Application to Behringer. These will be the CC to HUI messages. Put all supporting translators for this path under that preset. That way, you target your messages by input and output device instead of receiving all messages from everything and sending all message so everything.

This tutorial should guide you further.

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

Brilliant! That’s it! Thanks for the quick reply!

Hello,

i have the same problem like you. Could you show me how you solve the problem with the way back to the behringer x-touch. This would be so great. I spend so much time in this topic. Thanks so far.

Hi,
Put the X-touch into MCU (not HUI) mode and then use the documentation in this post.

Steve Caldwell
Bome Customer Care


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

Steve could you send me a configuration for the behringer x touch with hui and motorfeedback like in the post with the gma2? I want to use it with the software Daslight.

Hi, this is beyond the scope of free support, however if you want to email me, I can give you an estimate for paid support. There are some examples on the forum that have partial solutions but not a full solution. We provide tips and tricks and general troublshooting here but do not buil full solutions. If there are other users that happen to have built the same solution, they are welcome to share though. You might find something close if you search on HUI.

Steve Caldwell
Bome Customer Care


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

Yes I know, but i will pay for my problem solver. One last question Steve. No it works with the feedback, but all faders and rotary control work as one in the software. Where is the problem here? How will i separate them? Thaks for all

Send me an email and I will provide you an estimate for the work as an independent contractor.

Each control will need a translator to convert from Mackie HUI or MCU to CC or other MIDI of your choice for the application.

Assuming that the application will feedback the same MIDI message that you send (that would be converted), we have to do reverse translation back to the controller with additional translators.

I really recommend you put your X-Touch in Mackie MCU instead of HUI mode as :

  1. MCU is easier to program ( Mackie HUI sends a minimum of 6 bytes per control where Mackie MCU sends 3)

  2. You will not loose the functionality of your master fader in MCU mode (which the HUI protocol does not support).

Steve Caldwell
Bome Customer Care


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