Hi. I’m trying to find a way to make Behringer X-touch with Studio One be programmed to have a few LED buttons of X-touch be hard assigned to SOLO of particular channels in Studio One, so that LEDs of these buttons properly reflect status: LED ON when solo selected, LED OFF when solo is off. For example: “INST” button assigned to Bus 1 solo, “Plug-In” button to Channel 32 solo, etc. And LEDs properly reflect the solo status. Is that possible with Bome products? Also, if I assign a fader in X-touch to a particular channel, will moving that channel by mouse in DAW make motorized faders of X-touch to follow accordingly? Thanks!

[image] stason99: I read through some of the forum posts and tried to mess around with Rules not knowing what I was doing. So I added this Rule: ga=ga^127 …and I set Outgoing Velocity to “ga”. and it seems working. Can you please check if that’s all that’s needed and whether this can cause issues in some circumstances that I’m not aware of? Can you suggest a more “robust” rule? Here’s the project: Hi, this will indeed work if you don’t use the global variable ga for anything else. [image] stason99: Could you please modify your last project to include a proper rule for LED toggle (my rule was probably cumbersome but it worked). Apparently X-touch requires a separate incoming MIDI command to lit a pressed button’s LED, and same command with vel 0 to the LED to dim it. Studio 1 should send the right command based on what the X-touch sends. For X-touch it will be a note on with the command note and velocity 127 for on and 0 for off. You may need to use raw MIDI data as output So for example if you want to light the LED with 90 00 7F, you would turn it off with 90 00 00. If you use a local variable (like qq), so you could do this Incoming 90 00 qq from Studio One You should not need to toggle it as the function on Studio One would already do that but if it. Outgoing 90 00 qq The value from studio 1 should be 7f and then 00 if it behaves like a normal solo. [image] stason99: Also, in your Presets number 1, for both translates outgoing messages you selected velocity qq. Why qq and what does it do? qq is a local variable placeholder which will contain the value coming from the input device or Studio One depending on the preset or translator defined ports. If coming from Studio One, it will normally toggle between 7F (127) and 0. [image] stason99: Also, I modified your Preset number 2 to block note C1 (90 00 7F) (REC button on Ch1) with any velocity. How can I instead set a range of notes from 90 00 xx to 90 07 xx to include all 8 channels’ REC buttons blocked in one translate? Yes it would look like this Incoming: 90 pp qq Rules: if pp>7 then exit rules, skip outgoing action Outgoing: None [image] stason99: And lastly, after we setup above mentioned functions, then I’d need to add one more: a rule to make so that only 1 of two (or three or four…) buttons gets engaged (and illuminated) at once such as with “Radio Solo” mode when only one channel can be soloed at the same time. For example: There are 2 solo buttons: F6, F7 and F8. I need pressing any of these to deactivate previously engaged one. I need this rule not only for solo but other functions as well. I’d appreciate if you add that to the sample project for me. Radio buttons are a bit trickier as you have to track their state with global variables. While free support does not include creating a complete solution for you, I can find an example where I helped another user with radio buttons here . You would need to examine it and learn how it…

[image] SteveC: Studio 1 should send the right command based on what the X-touch sends. For X-touch it will be a note on with the command note and velocity 127 for on and 0 for off. You may need to use raw MIDI data as output So for example if you want to light the LED with 90 00 7F, you would turn it off with 90 00 00. If you use a local variable (like qq), so you could do this Incoming 90 00 qq from Studio One You should not need to toggle it as the function on Studio One would already do that but if it. Outgoing 90 00 qq The value from studio 1 should be 7f and the Well, it does not lit up the LED and I don’t understand why. Are you saying that when X-touch button pressed, it sends the command to Studio One which should in turn send the LED ON message back to X-touch? For some reason it doesn’t work… The X-touch LEDs lit up when Solo is initiated from Studio One, but not from X-touch. Can you please assist me with a proper rule to set LED toggle from X-touch back to itself to control LED state? I don’t see any other workaround…

If Studio One is not sending back the right information and you need to control the LED state then you should be able to do it with MT Pro. However sending data from Studio One as well may cause the LED to get out of Sync. Say you want Solo Track 1 to toggle which should be note 8 Incoming: 90 08 7F from X-touch Rules: // toggle value ga=ga^127 Outgoing: 90 08 ga to X-touch Steve Caldwell Bome Customer Care Also available for paid consulting services: bome@sniz.biz

[image] SteveC: [image] stason99: I read through some of the forum posts and tried to mess around with Rules not knowing what I was doing. So I added this Rule: ga=ga^127 …and I set Outgoing Velocity to “ga”. and it seems working. Can you please check if that’s all that’s needed and whether this can cause issues in some circumstances that I’m not aware of? Can you suggest a more “robust” rule? Here’s the project: Hi, this will indeed work if you don’t use the global variable ga for anything else. Can I use any other non-global (local) variable in this rule? Is it better to use a local variable? My understanding is that local variables are: pp qq rr ss tt uu vv ww xx.

[image] stason99: Can I use any other non-global (local) variable in this rule? Is it better to use a local variable? No, local variables are non persistent. Their value is unknown unless set by the rule or incoming trigger and the value disappears when the translator is finished. In contrast, a global variable starts out with a value of 0 when the project starts and stays persistent until it is changed. So you need to use a global variable and in the case of toggling, you will need a different one for every value you want to persist. Steve Caldwell Bome Customer Care Also available for paid consulting services: bome@sniz.biz

[image] SteveC: If Studio One is not sending back the right information and you need to control the LED state then you should be able to do it with MT Pro. However sending data from Studio One as well may cause the LED to get out of Sync. Say you want Solo Track 1 to toggle which should be note 8 Incoming: 90 08 7F from X-touch Rules: // toggle value ga=ga^127 Outgoing: 90 08 ga to X-touch So should there be ga for each toggle button, or should I use different global variables for each button? Sorry, I still don’t understand variables well enough. Also, I really appreciate your help, but could you please open Studio One one more time with X-touch and try to figure out why Studio One is not sending MIDI back to X-touch for LED signaling? Maybe there’s a setting I’m missing?.. Should all MIDI devices pass incoming MIDI to output by default? I asked om a Studio One group and forum but got no reply.

[image] stason99: So should there be ga for each toggle button, or should I use different global variables for each button? Sorry, I still don’t understand variables well enough. For MT Pro toggle control, each button will require a different global variable. [image] stason99: Also, I really appreciate your help, but could you please open Studio One one more time with X-touch and try to figure out why Studio One is not sending MIDI back to X-touch for LED signaling? Maybe there’s a setting I’m missing?.. Should all MIDI devices pass incoming MIDI to output by default? I asked om a Studio One group and forum but got no reply This is how I mapped Solo in Studio One for the generic controller. When pressing solo in Studio One the Solo light is toggling correctly. However it may be because the Mackie Command is also being sent to BMT 1. It appears that Studio One is only sending CC value of 0. [image] [image] [image] Video This is the project file I used. Test-2 Rule-sjc-2022-08-08.bmtp (3.5 KB) Steve Caldwell Bome Customer Care Also available for paid consulting services: bome@sniz.biz

Since custom mode in Studio One doesn’t seem to be able to have better feedback control, you may want to just use the Mackie feedback commands to handle the LED feedback states . You could set up translators for those commands or perhaps just let MIDI through routing do it’s thing.

[image] SteveC: This is how I mapped Solo in Studio One for the generic controller. When pressing solo in Studio One the Solo light is toggling correctly. However it may be because the Mackie Command is also being sent to BMT 1. It works in my case, too: clicking solo in Studio One makes X-touch button light toggle correctly. But when I press the button on X-touch - then LED on the button pressed in X-touch does not lit up. Also, please try with non-solo X-touch button since those are controlled by Mackie protocol. Please assign a non-solo button of X-touch to a solo in Studio One and see of light on X-touch goes on when that button is pressed.

[image] SteveC: Since custom mode in Studio One doesn’t seem to be able to have better feedback control, you may want to just use the Mackie feedback commands to handle the LED feedback states . I have no idea how to program Mackie xml… I’m assigning non-solo buttons in X-touch to trigger solo of channels that are not part of the faders of X-touch. For example: F6, F7, F8 to control solo of busses 20, 21, 22 while faders/channel buttons of those busses are not controlled by x-touch. So it’s pretty much impossible to reprogram that xml to do so, at least not for me. I’d have to intercept Mackie solo commands of busses 20, 21, 22 and translate them to F6, F7, F8 of X-touch…

Bome Forum

Can Bome assign solo to particular channels with LED toggle working?

Bome Products

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled