Behringer x-Touch Instructions for a perfect use - Page 3

bcab17 · 04-23-2021, 03:51 PM

Quote:

Originally Posted by Nos402

Oh weird! When I open it it's all still formatted and laid out exactly as I had it!

Attached as a PDF.

THANK YOU. This is great!

Nos402 · 04-24-2021, 01:12 PM

I decided to make a post detailing my entire journey of setting up my Xtouch with Reaper using CSI in case I ever needed it for reference or in case it could help anyone else.

https://heathallyn.com/setting-up-my...h-with-reaper/

bcab17 · 04-25-2021, 12:13 AM

Quote:

Originally Posted by Nos402

I decided to make a post detailing my entire journey of setting up my Xtouch with Reaper using CSI in case I ever needed it for reference or in case it could help anyone else.

https://heathallyn.com/setting-up-my...h-with-reaper/

What a cool idea. Thanks for stepping through your process. Everything is helping me understand CSI a little bit more. I think the the specific wording needed to customize the .zon file is still somewhat unclear to me. Things like "commenting out"...what is that, how is it done and why?

Even the first line in your PDF, //OnTrackSelection MapSelectedTrackSendsToWidgets.
I've seen "widgets" referred to in .mst files, but have no idea what they are or when they need to be noted like this in the .zon file. Even simple things like when to use // (forward slashes), where to leave spaces? I mean, much of it still looks like a foreign language to me.

Geoff Waddington · 04-25-2021, 05:47 AM

Quote:

Originally Posted by bcab17

What a cool idea. Thanks for stepping through your process. Everything is helping me understand CSI a little bit more. I think the the specific wording needed to customize the .zon file is still somewhat unclear to me. Things like "commenting out"...what is that, how is it done and why?

Even the first line in your PDF, //OnTrackSelection MapSelectedTrackSendsToWidgets.
I've seen "widgets" referred to in .mst files, but have no idea what they are or when they need to be noted like this in the .zon file. Even simple things like when to use // (forward slashes), where to leave spaces? I mean, much of it still looks like a foreign language to me.

Commenting out means that CSI won't scan the lines -- they are just there for you to read -- comments that you wish to add for clarity for yourself.

You can also comment out lines that would normally be scanned if you want to disable a piece of functionality, like this: //OnTrackSelection MapSelectedTrackSendsToWidgets

Widgets are just the faders, rotaries, buttons, displays, etc. that make up your surface.

Once you have defined a Widget and have given it a name in an .mst file you can then associate that Widget name with an Action in a .zon file to get something to happen in CSI/Reaper whenever you press/turn, etc. the Widget.

Nos402 · 04-25-2021, 01:17 PM

Looks like Geoff already covered it very well, but yeah "Commenting out" is just a general coding term for when you want to put something in there, usually for documentation purposes or as he said, disabling a piece of code. So any line starting with "//" will be ignored by the program. Every time I make a change I put a line in there starting with "//" so it's just a "comment" documenting what I did so that anyone reading my .zon file can easily see my comments about what I changed.

To take that first line you mentioned as an example, in the default .zon file, if you "select" a track, then it automatically goes to the "Sends" screen for that track, meaning that all the faders now show the sends for the track you just selected and if you again want to see all the tracks, their volumes and pans, you have to go back to the "Home" zone (there are a few ways to do that, one of which is pressing Global View). For my personal workflow, I wanted it to stay on the Home zone so that the faders ALWAYS show the tracks, volumes and pans even if I "Select" a track. If I want to see the "Sends" instead, I will manually press the "Sends" button to go to that zone.

So in browsing the default .zon file, I wasn't positive at first, but I *thought* that first line of code seemed to be what changed the screen when you selected a track, so I put "//" in front of it to "Comment it out" and basically make it non-existent to the program, and sure enough that accomplished what I wanted.

Hopefully that all makes sense.

Quote:

Originally Posted by bcab17

What a cool idea. Thanks for stepping through your process. Everything is helping me understand CSI a little bit more. I think the the specific wording needed to customize the .zon file is still somewhat unclear to me. Things like "commenting out"...what is that, how is it done and why?

Even the first line in your PDF, //OnTrackSelection MapSelectedTrackSendsToWidgets.
I've seen "widgets" referred to in .mst files, but have no idea what they are or when they need to be noted like this in the .zon file. Even simple things like when to use // (forward slashes), where to leave spaces? I mean, much of it still looks like a foreign language to me.

bcab17 · 05-12-2021, 09:41 PM

Quote:

Originally Posted by Sofia

Hi, I bought an x-touch yesterday and I configured it so now it works great with Reaper. Also the Plug-ins works good. I tested it on Windows 7 and 10 with the latest Reaper and Sws update.

I hope this post will be useful!

Sorry in advance for my English. I'm from Italy.

Enjoy!

STEP 1: Upgrade the Firmware

Connect X-Touch, press "Display" while turning it on and check the firmware version.
Download FIRMAWARE
Download MIDIOX
Open MidiOx
- Options --> Midi Devices --> select x-touch in Midi Inputs and Midi Outputs
- Options --> check the last "Pass SysEx"
- View --> SysEx.. --> Command Window --> Load File... (Load the Firmware file)
- Still in SysEx window: File --> Send SysEx File
Re-check the Firmware now!

STEP 2: Configure Mackie Control Klinke
MC Klinke in necessary to have control on plug-ins in addition to track and transport control.
Download MACKIE CONTROL KLINKE
Copy the ZIP file in "Plugins" folder of Reaper installation folder and unpack it here
On X-Touch, press "Select" on first channel while turning it on, select Mode MC and Ifc USB
Open Reaper --> Options --> Preferences... -->
- Control/OSC/web --> Add --> Mackie Control (Klinke) and then, if the device is connected via usb, change the value of "control surface display update frequency" to 30 (This is in Control/OSC/web menu)
- MIDI Devices -->
  right click on X-Touch voice in Midi inputs to set "Enable input" and "Enable Input for control messages"
  right click on X-Touch voice in Midi outputs to set "Enable output"
  make sure to choose "MIDIIN2 (X-Touch)" and MIDIOUTN2 (X-Touch) to use it with another MIDI device.

STEP 3: Close Reaper, Restart the PC

STEP 4: TIPS:

How to work on plug-ins? Add FX to tracks, push "PLUG-IN" on the top right of the X-Touch and then push "SELECT" on the first channel of the X-Touch. Now, when you choose a plug-in on the PC, it's assigned on the X-Touch. Press "PAN/SORROUND" to go back to track control.
Some buttons on the right are assignable (like the buttons next to GLOBAL VIEW. Check "Special Key" in the Action Window to assign a MIDI button on the X-Touch to an action. OPEN THE IMAGE
A few explanations on the buttons assigned to Reaper:

PAN/SORROUND: Track control

PLUG-IN: plug-ins control

SEND: Sends control. It works only if a track with send is selected. SELECT button exchange send and receive channels adjustments.

FLIP: Swap Volume and Pan potentiometers for fine adjustments.

F1, F2, F3... refer to markers.
CONTROL + Fn create a marker
SHIFT + Fn create a selection
MARKER button with the led on: press rew or fwd to switch between markers

Try MODIFY buttons in combination with other functions:
- CONTROL + SELECTn add a selected track
- ALT + SELECTn select from 1st to n track
- SHIFT + SELECTn select from n to 1st track
- CONTROL + AUTOMATION buttons sets the behavior on all tracks.
  The same with REC, SOLO, MUTE buttons
- CONTROL + rew or fwd go to beginning or end of project.

Enjoy!

Just got the x-touch, and followed the firmware update process using midi-ox:
Open MidiOx
Options --> Midi Devices --> select x-touch in Midi Inputs and Midi Outputs
Options --> check the last "Pass SysEx"
View --> SysEx.. --> Command Window --> Load File... (Load the Firmware file)
Still in SysEx window: File --> Send SysEx File

Upon clicking "Send SysEx File", a screen pops up with:
INetCache > IE > 7JSZX6Q9 is in the address window
The X-Touch Sysex update file listed in the main window
And it's asking me to type in a file name, and click "Open"

SO I'M LOST. What is that weird address, and what file name am I supposed to type in to "open"?

bcab17 · 05-12-2021, 09:48 PM

Quote:

Originally Posted by DeBased

It arrived today (X-Touch full version) and I love it. I find judging track volumes with it is way better, somehow focusing on a screen and pixel-adjusting automation gets in the way of being in the moment. Didn't realise how much!

So I've just tried the built-in MC support, to see the limitations. Ready to try CLI now, would be great if the scribble colours could be made to work.

BTW I had the AMD Ryzen Code 10 USB bug, but found the recent 1.21 firmware fixed that. I wonder if they added the colour SysEx to MC mode. Will have a play ...

I just got the x-touch, and am stuck in the firmware update process. My "Reaper PC" is a Ryzen system, so the x-touch was not recognized, so I used my Surface Pro, downloaded Midi-Ox and the firmware update.
This is the process:
Open MidiOx
Options --> Midi Devices --> select x-touch in Midi Inputs and Midi Outputs
Options --> check the last "Pass SysEx"
View --> SysEx.. --> Command Window --> Load File... (Load the Firmware file)
Still in SysEx window: File --> Send SysEx File

Upon clicking "Send SysEx File", a screen pops up with:
INetCache > IE > 7JSZX6Q9 is in the address window
The X-Touch Sysex update file listed in the main window
And it's asking me to type in a file name, and click "Open"

SO I'M LOST. What is that weird address? Do I need to change it? And what file name am I supposed to type in to "open"?

Nos402 · 05-12-2021, 10:08 PM

Are you powering up the Xtouch in "Update Mode" (Hold the "Display" button while powering on)?

Quote:

Originally Posted by bcab17

I just got the x-touch, and am stuck in the firmware update process. My "Reaper PC" is a Ryzen system, so the x-touch was not recognized, so I used my Surface Pro, downloaded Midi-Ox and the firmware update.
This is the process:
Open MidiOx
Options --> Midi Devices --> select x-touch in Midi Inputs and Midi Outputs
Options --> check the last "Pass SysEx"
View --> SysEx.. --> Command Window --> Load File... (Load the Firmware file)
Still in SysEx window: File --> Send SysEx File

Upon clicking "Send SysEx File", a screen pops up with:
INetCache > IE > 7JSZX6Q9 is in the address window
The X-Touch Sysex update file listed in the main window
And it's asking me to type in a file name, and click "Open"

SO I'M LOST. What is that weird address? Do I need to change it? And what file name am I supposed to type in to "open"?

bcab17 · 05-12-2021, 10:17 PM

Quote:

Originally Posted by Nos402

Are you powering up the Xtouch in "Update Mode" (Hold the "Display" button while powering on)?

Thanks for the quick reply, man. You have really been a help to me on this topic.

Anyway, I saw that the Surface Pro had a Windows update loaded and ready for install, so I quite Midi-Ox, did the update and restarted the Surface.

I went through the same fireware update process, and this time I copied the firnware update sysex file into the the file name window, clicked "open", and the x-touch updated to firmware 1.21 (I think that was it).

It's getting late here on NY, so I'll probably setup the x-touch in Reaper tomorrow. I'm going to try the Klinke extension first...then at some point, when I have a good amount of time set aside for it, I will venture into the world of CSI.

Thanks again!

bcab17 · 05-12-2021, 10:41 PM

Quote:

Originally Posted by Sofia

Hi, I bought an x-touch yesterday and I configured it so now it works great with Reaper. Also the Plug-ins works good. I tested it on Windows 7 and 10 with the latest Reaper and Sws update.

I hope this post will be useful!

Sorry in advance for my English. I'm from Italy.

Enjoy!

STEP 1: Upgrade the Firmware

Connect X-Touch, press "Display" while turning it on and check the firmware version.
Download FIRMAWARE
Download MIDIOX
Open MidiOx
- Options --> Midi Devices --> select x-touch in Midi Inputs and Midi Outputs
- Options --> check the last "Pass SysEx"
- View --> SysEx.. --> Command Window --> Load File... (Load the Firmware file)
- Still in SysEx window: File --> Send SysEx File
Re-check the Firmware now!

STEP 2: Configure Mackie Control Klinke
MC Klinke in necessary to have control on plug-ins in addition to track and transport control.
Download MACKIE CONTROL KLINKE
Copy the ZIP file in "Plugins" folder of Reaper installation folder and unpack it here
On X-Touch, press "Select" on first channel while turning it on, select Mode MC and Ifc USB
Open Reaper --> Options --> Preferences... -->
- Control/OSC/web --> Add --> Mackie Control (Klinke) and then, if the device is connected via usb, change the value of "control surface display update frequency" to 30 (This is in Control/OSC/web menu)
- MIDI Devices -->
  right click on X-Touch voice in Midi inputs to set "Enable input" and "Enable Input for control messages"
  right click on X-Touch voice in Midi outputs to set "Enable output"
  make sure to choose "MIDIIN2 (X-Touch)" and MIDIOUTN2 (X-Touch) to use it with another MIDI device.

STEP 3: Close Reaper, Restart the PC

STEP 4: TIPS:

How to work on plug-ins? Add FX to tracks, push "PLUG-IN" on the top right of the X-Touch and then push "SELECT" on the first channel of the X-Touch. Now, when you choose a plug-in on the PC, it's assigned on the X-Touch. Press "PAN/SORROUND" to go back to track control.
Some buttons on the right are assignable (like the buttons next to GLOBAL VIEW. Check "Special Key" in the Action Window to assign a MIDI button on the X-Touch to an action. OPEN THE IMAGE
A few explanations on the buttons assigned to Reaper:

PAN/SORROUND: Track control

PLUG-IN: plug-ins control

SEND: Sends control. It works only if a track with send is selected. SELECT button exchange send and receive channels adjustments.

FLIP: Swap Volume and Pan potentiometers for fine adjustments.

F1, F2, F3... refer to markers.
CONTROL + Fn create a marker
SHIFT + Fn create a selection
MARKER button with the led on: press rew or fwd to switch between markers

Try MODIFY buttons in combination with other functions:
- CONTROL + SELECTn add a selected track
- ALT + SELECTn select from 1st to n track
- SHIFT + SELECTn select from n to 1st track
- CONTROL + AUTOMATION buttons sets the behavior on all tracks.
  The same with REC, SOLO, MUTE buttons
- CONTROL + rew or fwd go to beginning or end of project.

Enjoy!

Sofia, I finally got the x-touch firmware update to work (your step by step instructions were a HUGE help...thank you), and I just downloaded the latest Klinke extension. Your directions say to copy the zip file in the Reaper "Plugins" folder and unpack it there. However, the Klinke manual that I also downloaded says to copy the zip file into the "User Plugins" folder.

Can you you let me know which is the correct folder?

bcab17 · 05-12-2021, 11:49 PM

Quote:

Originally Posted by Nos402

Are you powering up the Xtouch in "Update Mode" (Hold the "Display" button while powering on)?

Well, I just tried setting up both standard Mackie Universal Control and the Klinke version in Reaper (Preferences/Control Surfaces), then changed the "Control Surface Update Frequency" to 30 Hz.

Still in preferences, under "Audio", I went to "Midi Devices, and enabled the x-touch for midi input and midi output.

Then I closed Reaper and restarted the pc. When Reaper finished loading a project, the faders on the x-touched jumped up to -10dB...and that's all! No buttons, pan knobs or faders do anything. The x-touch is powered on, connected via USB...I must be missing something.

Back in Reaper preferences, in the Control Surface page, I selected the Mackie Protocol option, and tried selecting the x-touch for Midi in and out, and an error message popped up "Error opening Midi inputs and outputs." I don't think I was supposed to do that in the Control Surfaces page anyway.

I'm completely stumped. The Klinke manual install directions stop after selecting Klinke in the Preferences/Control Surfaces...no mention about Midi in and out settings.

Klinke · 05-13-2021, 02:07 AM

Don't activate the MIDI-In and MIDI-Out of the X-Touch in the Options --> Midi Devices dialog, they must be disabled here. Instead select them in the "Control Surface page". You are right, this is missing in the manual, I will add it in the next release.

bcab17 · 05-13-2021, 07:36 AM

Quote:

Originally Posted by Klinke

Don't activate the MIDI-In and MIDI-Out of the X-Touch in the Options --> Midi Devices dialog, they must be disabled here. Instead select them in the "Control Surface page". You are right, this is missing in the manual, I will add it in the next release.

As always, thanks for this. I was referring to the Sofia post as my install/setup "bible"...the step by step thing was great for me:

Open Reaper --> Options --> Preferences... -->
MIDI Devices -->
right click on X-Touch voice in Midi inputs to set "Enable input" and "Enable Input for control messages"
right click on X-Touch voice in Midi outputs to set "Enable output"
make sure to choose "MIDIIN2 (X-Touch)" and MIDIOUTN2 (X-Touch) to use it with another MIDI device.

However, either the comment about enabling midi input and output in "MIDI Devices" is wrong or I am misinterpreting the instructions somehow.

So, to make sure I've got it right:

1) Your extension zip file can be copied and unpacked in EITHER the Reaper "Plugins" or the "User Plugins" folders...and there is no difference/advantage to either option?

2) The x-touch must only be selected/enabled for MIDI input and output in the "Preferences > Control Surface/OSC/Web Control" page, and it should be disabled in the "Preferences > Audio > MIDI Device" page?

Two other things...

1) Sofia mentions enabling "MIDIIN2 (X-TOUCH)" and "MIDIOUT2 (X-TOUCH)" if you have another midi device. I must assume that this is NOT correct, since you have said to disable MIDI input and output in the "MIDI Device" page of Preferences.
So, what do I do when I want to use another MIDI device with Reaper (and presumably with the X-Touch)?
My SSL 2+ interface has MIDI I/O (but they're not connected to anything yet).
I also have an external digital multitracker that I may eventually want to use MIDI Clock to sync with Reaper and the sequencer in my synth/workstation.
And at some point, I will be getting a MIDI keyboard/controller.
What happens when I want to start using these devices with Reaper?

2) Another forum member posted this:
"Go into preferences>Track Control Panels and change the "Volume Fader Range" from +12 to +10. This will make the fader numbers match almost perfectly when adjusting faders." Do you have any experience with this?

Thank you!!!

Klinke · 05-13-2021, 07:58 AM

Quote:

Originally Posted by bcab17

As always, thanks for this. I was referring to the Sofia post as my install/setup "bible"...the step by step thing was great for me:

Open Reaper --> Options --> Preferences... -->
MIDI Devices -->
right click on X-Touch voice in Midi inputs to set "Enable input" and "Enable Input for control messages"
right click on X-Touch voice in Midi outputs to set "Enable output"
make sure to choose "MIDIIN2 (X-Touch)" and MIDIOUTN2 (X-Touch) to use it with another MIDI device.

However, either the comment about enabling midi input and output in "MIDI Devices" is wrong or I am misinterpreting the instructions somehow.

I was not aware that the X-Touch come also with physical MIDI-Ports. The 2nd post in this thread should help to elimenate the confusion. There are two pairs of inputs and outputs, the first one which is likely called only X-Touch is used for the communication with the X-Touch itself, the second pair, which is called MIDIIN/OUT2 (X-Touch) is for communication with the hardware that you connect to the physical MIDI-Ports of the X-Touch. The extensions needs the first one, so you must disable these ports in Preferences Audio / MIDI Devices and select them in Preferences / Control/OSC/web / Mackie Control Protocol. The second (with MIDIIN/OUT2 in the names) can be enabled in Preferecnes / MIDI Device, if you want to use the X-Touch also as an additional MIDI-Interface.

Regarding the fader range I can not help you, as I don't own a X-Touch. Just try it out and check what fits to your tastes.

bcab17 · 06-10-2021, 07:14 PM

I'm using the X-Touch and really enjoying the Klinke extension.

Is there a way to assign a single action to a spin/turn of a V-Pot, so that the spin acts like a single button push?

I want to assign actions to a V-Pot so that a press "glues all items on a track", a left turn "freezes track to mono", and a right turn "freezes track to stereo".

The press of the V-Pot works fine, but when I turn it left, the track freezes and refreezes again and again (as if each increment of the V-Pot turn runs the freeze action).

I'm using the "special key" option to assign the actions, and I noticed that the MICI CC options window (to select absolute or relative) is always greyed out. I thought I would try those options.

I'm obviously doing something wrong. Can anyone help me with this?

DJ Graco · 03-05-2022, 05:04 AM

Hi.
I have another problem. It is not very bothersome, but ... I noticed that when I close the Reaper project or the entire program, the X-Touch sliders do not slide down but remain in the position they were in before and only turning the device on and off causes that the sliders go down. Do you also have such a problem?
I tested it with a few other DAWs and when I turned off the project, the sliders always went down.
I am currently using Klinke.

DJ Graco · 03-19-2022, 11:42 AM

Hi, I went home, connected the X-Touch and set it up. Everything works except one thing. How do I control the volume sliders directly on the controller, everything works, but if in the program itself I change the volume of the track, the sliders do not move and touching any of them returns to the original value? What am I doing wrong? In control surface I have selected for midi input and midi output X-Touch for Mackie Control Protocol Klinke. Tried turning on the X-Touch control from the preferences / midi devices but it behaves the same. I apologize in advance for such stupid questions, I am a beginner.

Klinke · 03-19-2022, 01:06 PM

Quote:

Originally Posted by DJ Graco

How do I control the volume sliders directly on the controller, everything works, but if in the program itself I change the volume of the track, the sliders do not move and touching any of them returns to the original value?

This behavior indicates that the extension is not receiving messages from x-touch for some reason. Does the x-touch works with any other software?

Quote:

Originally Posted by DJ Graco

Hi.
I noticed that when I close the Reaper project or the entire program, the X-Touch sliders do not slide down but remain in the position they were in before and only turning the device on and off causes that the sliders go down. Do you also have such a problem?
I tested it with a few other DAWs and when I turned off the project, the sliders always went down.
I am currently using Klinke.

Yes, this is normal, but it's a good idea to improve this, I have added this to my TODO list.

DJ Graco · 03-20-2022, 06:16 AM

@Klinke thank you very much for the answer.
The case is that I am blind and under windows a very well working screenreader is Reaper with the plugin of Osara. Unfortunately, I currently don't have access to a Mac, where Logic is, I tested it on another X-Touch, which is in my school, and everything seems to work fine when I connect it to my computer. I also tried updating the firmware in my personal X-Touch but that didn't fix the bugs.

DJ Graco · 03-22-2022, 05:20 AM

Hey, yesterday I tested the controller with samplitude and everything worked fine with the faders in the Mackie Control.

Stoneglow · 12-06-2023, 12:03 AM

Quote:

Originally Posted by Sofia

Hi, I bought an x-touch yesterday and I configured it so now it works great with Reaper. Also the Plug-ins works good. I tested it on Windows 7 and 10 with the latest Reaper and Sws update.

I hope this post will be useful!

Sorry in advance for my English. I'm from Italy.

Enjoy!

STEP 1: Upgrade the Firmware

Connect X-Touch, press "Display" while turning it on and check the firmware version.
Download FIRMAWARE
Download MIDIOX
Open MidiOx
- Options --> Midi Devices --> select x-touch in Midi Inputs and Midi Outputs
- Options --> check the last "Pass SysEx"
- View --> SysEx.. --> Command Window --> Load File... (Load the Firmware file)
- Still in SysEx window: File --> Send SysEx File
Re-check the Firmware now!

STEP 2: Configure Mackie Control Klinke
MC Klinke in necessary to have control on plug-ins in addition to track and transport control.
Download MACKIE CONTROL KLINKE
Copy the ZIP file in "Plugins" folder of Reaper installation folder and unpack it here
On X-Touch, press "Select" on first channel while turning it on, select Mode MC and Ifc USB
Open Reaper --> Options --> Preferences... -->
- Control/OSC/web --> Add --> Mackie Control (Klinke) and then, if the device is connected via usb, change the value of "control surface display update frequency" to 30 (This is in Control/OSC/web menu)
- MIDI Devices -->
  right click on X-Touch voice in Midi inputs to set "Enable input" and "Enable Input for control messages"
  right click on X-Touch voice in Midi outputs to set "Enable output"
  make sure to choose "MIDIIN2 (X-Touch)" and MIDIOUTN2 (X-Touch) to use it with another MIDI device.

STEP 3: Close Reaper, Restart the PC

STEP 4: TIPS:

How to work on plug-ins? Add FX to tracks, push "PLUG-IN" on the top right of the X-Touch and then push "SELECT" on the first channel of the X-Touch. Now, when you choose a plug-in on the PC, it's assigned on the X-Touch. Press "PAN/SORROUND" to go back to track control.
Some buttons on the right are assignable (like the buttons next to GLOBAL VIEW. Check "Special Key" in the Action Window to assign a MIDI button on the X-Touch to an action. OPEN THE IMAGE
A few explanations on the buttons assigned to Reaper:

PAN/SORROUND: Track control

PLUG-IN: plug-ins control

SEND: Sends control. It works only if a track with send is selected. SELECT button exchange send and receive channels adjustments.

FLIP: Swap Volume and Pan potentiometers for fine adjustments.

F1, F2, F3... refer to markers.
CONTROL + Fn create a marker
SHIFT + Fn create a selection
MARKER button with the led on: press rew or fwd to switch between markers

Try MODIFY buttons in combination with other functions:
- CONTROL + SELECTn add a selected track
- ALT + SELECTn select from 1st to n track
- SHIFT + SELECTn select from n to 1st track
- CONTROL + AUTOMATION buttons sets the behavior on all tracks.
  The same with REC, SOLO, MUTE buttons
- CONTROL + rew or fwd go to beginning or end of project.

Enjoy!

Thank you for this Sofia.

I'm unable to connect via Mackie Control Universal (the X-Touch is not recognized) so I am hoping on this Klinke approach.

I've followed your steps and have unzipped the Klinke zip folder in Reaper's plugins folder.

Then I've gone to Preferences > Control/OSC/web > Add

But Mackie Control (Klinke) is not there as an option. Reaper is not seeing it.

1 - Is there somewhere other than the reaper plugins folder that might serve as another option for Reaper to see it?

2 - Is it possible my version of Reaper is just corrupted and that's why it can't see Klinke dlls in it's plugins folder?

3 - Is it possible that some kind of Read Only permission is causing Reaper to not be able to see the Klinke dlls?

Thanks,

Stoneglow · 12-06-2023, 12:15 AM

Quote:

Originally Posted by Klinke

This behavior indicates that the extension is not receiving messages from x-touch for some reason. Does the x-touch works with any other software?

Yes, this is normal, but it's a good idea to improve this, I have added this to my TODO list.

Hi Klinke,

I have the same issuer OP was experiencing - my X-Touch just sits there with the MCU connection and nothing happens. And my Reaper does not seem to be able to recognize the Klinke dlls when they are unpacked into the plugins directory - Klinke does not appear as an option when I got to add a new control surface in preferences.

How can I test if the X-Touch works with any other software? The only software I have that I would expect it to work with is Reaper... can you suggest a software that I can easily install and learn how to test the X-Touch fairly quickly with?

Or, better yet, overall - do you have any idea what my best option for next steps might be?

My goal is simple - to be able to use my X-Touch with Reaper in any capacity whatsoever and, ideally, using your Klinke settings. Any clue what I should be testing?

Lastly, is there any setting in Reaper, either in preferences or else chosen during installation, that would prevent Reaper from seeing your Klinke dlls? I can't understand how they can just not be seen.... Is Reaper stuck behind some kind of permissions wall?? Any ideas?

This has been driving me mad for the week since I bought this X-Touch and I can't figure out how to do anything at all with it. I would love to experience what I'm reading other posters experiencing.

Thanks,

Stoneglow

Klinke · 12-06-2023, 03:58 AM

Quote:

Originally Posted by Stoneglow

Hi Klinke,

I have the same issuer OP was experiencing - my X-Touch just sits there with the MCU connection and nothing happens. And my Reaper does not seem to be able to recognize the Klinke dlls when they are unpacked into the plugins directory - Klinke does not appear as an option when I got to add a new control surface in preferences.

How can I test if the X-Touch works with any other software? The only software I have that I would expect it to work with is Reaper... can you suggest a software that I can easily install and learn how to test the X-Touch fairly quickly with?

Or, better yet, overall - do you have any idea what my best option for next steps might be?

My goal is simple - to be able to use my X-Touch with Reaper in any capacity whatsoever and, ideally, using your Klinke settings. Any clue what I should be testing?

Lastly, is there any setting in Reaper, either in preferences or else chosen during installation, that would prevent Reaper from seeing your Klinke dlls? I can't understand how they can just not be seen.... Is Reaper stuck behind some kind of permissions wall?? Any ideas?

This has been driving me mad for the week since I bought this X-Touch and I can't figure out how to do anything at all with it. I would love to experience what I'm reading other posters experiencing.

Thanks,

Stoneglow

My first guess is that you moved the files into the wrong plugin folder, e.g. for VSTPlugins. You find the correct folder when you select in the Reaper-Menu "Options/Show REAPER resource path in explorer/finder...", and then copy the .dll files into the folder UserPlugins. I have attached a screenshot of this.

And I hope you are running windows, as my extension is windows only.

In the case that the extension still does not show up in the Control Surface Preferences, you could try to install DrivenByMoss or CSI.

Stoneglow · 12-07-2023, 08:27 PM

Quote:

Originally Posted by Klinke

My first guess is that you moved the files into the wrong plugin folder, e.g. for VSTPlugins. You find the correct folder when you select in the Reaper-Menu "Options/Show REAPER resource path in explorer/finder...", and then copy the .dll files into the folder UserPlugins. I have attached a screenshot of this.

And I hope you are running windows, as my extension is windows only.

In the case that the extension still does not show up in the Control Surface Preferences, you could try to install DrivenByMoss or CSI.

Thanks Klinke,

As it turns out, I did have a defective unit and simply going to the store and exchanging it was all the problem solving needed. I wish I did this a week ago instead of spending hours and dollars on a solution.

This second one works easily and, presumably, perfectly. Now all I have to do is learn this thing. Thanks for the help.