Behringer X-Touch One support - most DAWs but not Reaper

[jesus4c]

Behringer have recently released the X-Touch One single fader control surface and it seems perfect for Reaper users on a tight budget, BUT it's had issues with the fact that a mouse-click on a track in a DAW didn't automatically select that track on the X-Touch One. A definite deal-breaker for most users.

So, Behringer have updated the firmware, and it now works as expected on most DAWs except:

Unfortunately Reaper, in regards to Track Selection and their implementation of it under the MC protocol is really just geared up for an 8 channel controller not single channel. It is to do with the way their Track Select works. Unfort nothing we can do about this from our side with regards to Mc Control.

If Reaper update this in future then we will be happy to re-visit for a future firmware release.

Is this something that can be implemented in a future Reaper release?

[mschnell]

In these forums, there are multiple threads on Surface device Reaper extensions (including "DrivenByMoss4Reaper", "Klinke" and "CSI") these might help with integrating the XTouch One (and hundreds of other Control Surfaces) and to define a workflow for same the meets the actual user's workflow desires (which is heavily depending on the dedicated task they want to accomplish).

-Michael

[Masi]

Originally Posted by mschnell

In these forums, there are multiple threads on Surface device Reaper extensions (including "DrivenByMoss4Reaper", "Klinke" and "CSI") these might help with integrating the XTouch One (and hundreds of other Control Surfaces) and to define a workflow for same the meets the actual user's workflow desires (which is heavily depending on the dedicated task they want to accomplish).

If I understand the request the workflow is simple enough: select a single track in Reaper, the single track surface controller will select the same track.

From what I have gathered using control surfaces in Reaper is a PITA. While I have the impression that (some) hardware vendors sometimes don't make it easy for DAW developers, but also that Cockos has controls surfaces not very high on its priority list.

I thought about buying a XTouch One, but its odd that this very basic feature doesn't work. It's so basic that I didn't even expect it could not be working out of the box.

I'm fine with spending time to create a very personal worklflow, but I'm disappointed if any given software/hardware combination doesn't offer at least a useful out-of-the-box experience.

But it strikes me odd that there are issues as Beheringer ships the XTouch One even with Reaper UI overlay.

Masi

[mschnell]

Originally Posted by Masi

If I understand the request the workflow is simple enough

I suppose on the long run this will suite only a small minority of the users. If I spent money for a hardware controller I will want to use it for many more tasks.

Originally Posted by Masi

Cockos has controls surfaces not very high on its priority list.

This obviously is correct, and a good decision.
The complexity of decently supporting a control surface is a task that can be much better done in a 3rd party plugin such as "DrivenByMoss4Reaper", "Klinke" and "CSI".

I do know that "CSI" is very promising but right now in pre-Alpha state. I don't know much about "DrivenByMoss4Reaper" and "Klinke", as to me CSI seems to feature the most viable ideas and I am not in a hurry.

in fact "Moss" is interesting in that it supports multiple DAWs.

-Michael

[Masi]

Originally Posted by mschnell

If I spent money for a hardware controller I will want to use it for many more tasks.

That's true. But all those posting make me fear that if I buy a controller I either spent days to configure it just to figure out that I cannt use all the features of the controller in Reaper.

Originally Posted by mschnell

The complexity of decently supporting a control surface is a task that can be much better done in a 3rd party plugin such as "DrivenByMoss4Reaper", "Klinke" and "CSI".

Maybe I'm underestimating the complexity, but I wonder where it comes from? Is it the lack of an *industry* standard? All the proctols that are usually talked of seem to be proprietary with more or less buggy clones.

Anyway, thanks for the pointers. I'll check out those plugins.

Masi

[mschnell]

Originally Posted by Masi

That's true. But all those posting make me fear that if I buy a controller I either spent days to configure it just to figure out that I cannt use all the features of the controller in Reaper....Maybe I'm underestimating the complexity

That is why I hope for CSI to be "official released". Here the idea is that anybody can create configuration files (not scripts !) supporting possible protocols of a wide range of devices (including but not limited to more or less MCU compatible ones, as well Midi as OSC based, and other files defining the preferred workflows a user might imagine.

Now the extension software in place, the community can create and provide these configuration files.

-Michael

[Masi]

Originally Posted by mschnell

"DrivenByMoss4Reaper", "Klinke" and "CSI".

DrivenByMoss4Reaper is active. It may or may not be possible to overcome the reported issue by using the generic MCU controller:

http://www.mossgrabers.de/Software/Reaper/Reaper.html

CSurf Klinke seems to be dead (or at least sleeping):

https://bitbucket.org/Klinkenstecker/csurf_klinke_mcu

CSI may be up to it. To get it flying testers are needed:

https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

Masi

PS: Still not convinced that Reaper couldn't have full support for MCU and HUI. But I have to admint that I have no clue what a DAW is supposed to (or may send to) a controller when a track is selected. And how to cope with the fact that a user may select more than one track, eg use the last selected one or the one with the lowest number.

[ivansc]

Originally Posted by jesus4c

Behringer have recently released the X-Touch One single fader control surface and it seems perfect for Reaper users on a tight budget, BUT it's had issues with the fact that a mouse-click on a track in a DAW didn't automatically select that track on the X-Touch One. A definite deal-breaker for most users.

So, Behringer have updated the firmware, and it now works as expected on most DAWs except:



Is this something that can be implemented in a future Reaper release?

Hey - looks like you have been bashing the piggy bank after all! Which Audio-MIDI interface did you go with in the end? Sorry about the OT post.

[DaveKeehl]

I'm really interested in the X-Touch 1, can anyone tell me what works and what doesn't with Reaper?

[mschnell]

Obviously, the correct location to ask this id the "Control Surfaces" subforum.

-Michael

[deeb]

Does anyone have x-touch mini working in reaper?

[mschnell]

Obviously, the correct location to ask this id the "Control Surfaces" subforum.

-Michael