Behringer X touch compact with DasLight5

Translation Projects
1

Hello, i’m new in the utilisation of bome for midi mapping and i need some help with the xtouch compact and dl5.

I already see a post about the xtouch full size but there’s too much option about it, and the motorized fader don’t work (i think its about the value but i dont find any website taling about this) so i put the file that i found and i just need someone to explain me how to do it or just convert the file because it’s kinda hard.

btw i only need the motorized fader to get 2 pages of fader, and the lights switchback, because there’s a lot of bugs with daslight about the buttons rgb switchback.

have a great day,

Maxime.

2

X-Touch dl5 test-switch faders pages–sjc.bmtp (38.7 KB)

here is the file

3

Hi and welcome to the Bome community!

Well I’m going to send you a new project that is simpified to just the faders.

I have my aliases set up as follows:

image
image628×443 10.7 KB

You can learn more about aliases from this tutorial.

I am select ports (devices) at the preset level except translator 1.2 which job it is to update the faders on the X-touch.

For more information about device selection, see this tutorial.

Preset 0 handles housekeeping project start.

Preset 0 translator 2 (0.2) initializes global variables used in this project.

Preset 1 handles all traffic coming from the X-touch and going to Daslight.

1.0 sends fader values to Daslight translating from Mackie MCU (pitch bend) to CC (70-78). I have stop processing set so other translators (that are not pitch bend) will not be activated later.

1.1 updates the faders with the preset is activated by triggering a timer.
1.2 is the timer that sends all fader message back to the X-Touch
1.3 and 1.4 suppresses the touch and release from the X-touch respectively.

Preset 2 handles all activity from Daslight back to X-touch.
2.0 converts CC70-78 to pitch bend and sends it back to the X-touch. If Daslight does not send feedback, it will not work.

I have a MIDI thru path set to allow for local feedback if Daslight doesn’t send feedback. It can be removed if Daslight is working correctly.

image
image611×347 23.4 KB

I also have a MIDI thru path set from My-Xtouch to Daslight for anything that does not go through a translator.

image
image633×270 15.8 KB

I only have 1 pages set at this time. You will need to add translators to switch pages (change presets) . I will leave it to you to figure out how to switch pages. I did this because the focus of your question was fader feedback and not page switching.

Good luck!

X-Touch-MCU-Daslight-Faders.bmtp (4.0 KB)

Steve Caldwell
Bome Customer Care

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

Hey thanks for your help,

I figured how to do the 2nd page, but now i need some tips about the led indicator, because when i click on buttons, they dont keep the rgb on, like on daslight if i affect an action on a button, the action is active on daslight but on the controller the button light is active for 0.1second and go to dark so idk how to do it, if you an show me how to do it for 1 and i’m gonna do it myself for the other,

And i’m also trying to figure how to switch this part when i’m changing my layers :

image
image879×698 115 KB

that could be really usefull if you can help me !

have a great day, maxime

5

test mcu.bmtp (6.5 KB) here’s my file if you want to ad on it some tips, thank you in advance !

6

Hi,

I made quite a few changes.

First all all notes from page 1 of Daslight use MIDI CH 1 while all notes on from page 2 of Daslight use MIDI CH 1.

I had to add logic to switch presets off and on base on the page that you are on. I used the right lower knob to do this (knob 16). If you turn it to the right it will move to page 2 and if you turn it to the left it will move to page 1.

Translator 0.4 initiates this.
Then translators 1.3 and 2.3 will then activate presets 2 and 4 respectively.

I created translators to convert notes coming back from Daslight and I use the global variables ge and gf to capture their on/off value in a bitmap. This caputures the bitmap for all bot the right buttons. This is done int translators 3.1 and 4.1. The values are capture and the LEDs are updated.

When switching banks, I added 2 translators upon activation to refresh the button bitmap. (1.2 and 2.2). They both call the timer translator I created in 0.5 to iterate and refresh all of the buttons I mentioned earlier.

The caveat is that Daslight needs to send note-on and note-off values that map to notes 0-31 on the desired page (MIDI CH 1 for page 1 and MIDI CH 2 for page 2).

The most complicated rules are those of translators 3.1 and 4.1 which perform the bitmapping exercise. Then translator 0.5 which extracts the value of the buttons for updating the LEDs.

I hope this works for you. This is generally deeper than we get for free support and is done through my private consulting practice.

At this level you might want to consider looking into that.

I’m not sure how you were handling the VPOTS as there is nothing in there to support that and similarily the buttons on the side.

MCU-Daslight-sjc-2025-11-09.bmtp (9.6 KB)

Steve Caldwell
Bome Customer Care

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

hey i’ve tried your file and nothing’s working, the knob is working but that’s not usefull because it randomly switch between page 3 and 4 and sometime it desactivate it. i wonder if its possible to put the layer a on note 54 and the layer b on 55 but idk to do this, and when i switch between page 1 and 2, and i comeback on the page 1, all faders are at 0 they dont keep the position, so if ou can help me that would be great. tysm in advance !

8

Hi,

The rules of translator 0.4 handles the page changes.

Change this:

// only notes 48 and 49
if pp<48 then exit rules, skip Outgoing Action
if pp>49 then exit rules, skip Outgoing Action
if pp==49 then gd=1
if pp==48 then gd=0
Log "Log gd=%gd%"

qq=gd+1

to this

// only notes 84 and 85
if pp<84 then exit rules, skip Outgoing Action
if pp>85 then exit rules, skip Outgoing Action
if pp==85 then gd=1
if pp==84 then gd=0
Log "Log gd=%gd%"

qq=gd+1

Note that I’m using notes 84 and 85 which tranlate to hex 54 and 55 which are the layer buttons on your controller that I assume that you are using.

I also added translator 0.6 which updates the LED on the two buttons. It is called by a rule in 0.4.

I also set the led at startup in the rules of translator 0.3

Again, this is way beyond free support so if you need more help, it is probably best to drop me an email. This would likely require a conference call as I don’t have DasLight to test with and am not sure whether DasLight provides adequate MIDI feedback.

I tested the by communicating to and from MIDI Tools and my X-touch compact.

Either that or study the tutorials or examples I gave you.

MCU-Daslight-sjc-2025-11-10.bmtp (10.6 KB)

Steve Caldwell
Bome Customer Care

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

Hey, thanks for your file and all your work, everything is working, fader feedback between page 1 and 2, the lights feedback too, but all the knobs aren’t working, idk why i’m gonna try to figure this, and those buttons (under) aren’t sending informations, i’m gonna try to find where’s the problem and if i need help i’ll come back to you, thanks for evverything <3 !

image
image208×234 28.9 KB

10

OK, yes I didn’t program any of the knobs or the rest of the buttons on the side.

Steve Caldwell
Bome Customer Care

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

I’ve done this, everything’s working, but i’m lost about all the feedback things, i did no feedback because i didnt find how to do it, and for the 6 buttons led, i dont find anything to make them work, i always need to keep the button down, but i just want to keep it active only 1 time i press it, idk if you can show me how to do it but that would be really nice from you, have a great day!

modif xtouch compact 1411.bmtp (14.0 KB)

12

Presets 3 and 4 are for MIDI messages from Daslight back to the X-touch. If Daslight sends the correct note messages, then it should work. It really depends on what type of LED feedback Daslight sends.

You can press a button on your X-touch and in Bome MIDI Translator Pro open the log window and check MIDI IN and MIDI OUT to see what is happening. If Daslight doesn’t send any messages the would not be much we can do about it.

For the top encoders, side encoders and extra buttons on the side, we don’t provide full solutions here, just tips on how things get done. If you are looking for a complete solution for your use case, you can contact me for a quotation for paid services. Even with that, the success for what you are asking depends much on the Daslight capabilities for LED feedback.

In the current implementation of the existing buttons, we are toggling the LEDs using rules within Bome MIDI Translator Pro and just passing through MIDI information that Daslight sends back to the controller.

Steve Caldwell
Bome Customer Care

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

Hello,

I’ve worked alone and with chatgpt and gemini, and btw chatgpt suck for this tasks, gemini is better. i’ve figured how to get the vpot ledfeedback, how to make the buttons works etc, but i need some things.

1st, idk how to recall my previous page led value, when i’m turning my vpot on my page 1, and i put like 50%, 5/11 leds are active, and then i switch page and i put 100ù so 11/11 leds active, but when i comeback on my page 1, the 11 leds are still active and i need to turn it a litle bit and the led is coming to the previous led value. so if you can help me with that that would be great.

2nd, the vpots 15 and 16 are only note on, so i created my translator 5.4, but i dont know how to make the led active, i want like when i’m turning the left, the 6/11 left led are active but for only 1second, then release it and desactivate led, this option seems to be complicate but thats not a problem if it’s not working.

and 3st as you can see i have translator 5.0 and 5.1, its for the 6 buttons above the layers ab buttons, but their note message are 91 92 93 94 95 and the loop button is note 86 only, so idk if its possible to only have 1 rule to do the 6 buttons in 1.

have a great day!

Maxime.

version fonctionnelle 271125.bmtp (17.9 KB)

14

Yes, this is not easy.

I took care if issue 1.

I created global variables for VPOTS on both layers to keep track of their values. I no longer update either the fader or VPOT rings immediately. I always capture the data from both layers and only send infomation back to the currently active layer.

When switching layers, I have a timer that reads the global variable for that layer and updates the rings (similar to the faders)

I rely 100% on Daslight to provide MIDI feedback to update the values as if I updated directly back to the X-touch and also from Daslight the values would fight eachother.

All updates to the vpots are channeld through a perform action, 3.6 for layer 1 and 4.6 for layer 2.

Preset 6 is an ‘always on’ preset and always captures the Fader and VPOT feedback from Daslight for both layers, and the value of gd determine whether to send feedback or not depending on which layer we are on.

I disabled translators 3.4 and 4.4 since they have been replaced by my logic.

I didn’t do anything with your buttons.

New translators are 1.3, 2.3, 1.14, 2.14, 3.6, 4.6 an all translators in preset 6

I didn’t do anything with preset 5 because I didn’t address anything there.

I also added rules to translator 1.2 to document the new global variables I’m using.

version fonctionnelle 271125-sjc.bmtp (23.1 KB)

Steve Caldwell
Bome Customer Care

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

hey thaks for your file, everything is working thank you very much, but is it possible to disable the 1st led, because when my value=0 on daslight, 1 led is still active so idk if its possible to let the led inactive when i’m at 0?

16

and on my file i’ve created the presset 5.3 to get the vpots 1 to 6 note message and the led was working, but now with your file my led ring is missing so idk what changed but i’m gonna try to find why and also for my led buttons, idk why too but before the changement the leds were working and now nothing

17

Yes, the strategy for updating LED’s changed.

I added a new bitmap for the side buttons and timers to update the LEDs. Also the page 1 LED will light at startup.

Also, I noticed your presets weren’t in a known state at startup so I added translators for that.

This really should have been a paid engagement.

version fonctionnelle 281125-sjc.bmtp (26.1 KB)

Steve Caldwell
Bome Customer Care

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