All times are UTC

 
 



Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: X-TOUCH MINI - Lock and Control 2 Devices - Tutorial
PostPosted: Tue Nov 06, 2018 9:56 pm 

Joined: Tue Nov 06, 2018 9:21 pm
Posts: 4
dear friends,

today i received my x-touch mini.

Great Device, MC Mode is cool.
But that preset was not what I was looking for.
(and maybe you feel like this, too)

My problem was that you could only control the device which is in focus and there is no "lock to control surface" option.
Also I wanted to use the x-touch layers to control 2 seperate devices.
...and further, I wanted to use more then on x-touch mini in my setup.


some troubles with configuring at first, but now all is very easy and i am very happy :)
now its time to share.

Here is the (really easy) setup for you:

1. download the behringer editor app for x-touch mini.
2. set to "standard" mode, not "mc"
3. edit the fader/encoder/buttons
- Global Ch: 1
- put fader and buttons and encoder-push buttons on channel "global"
- put all the "turn" encoders on channel 11 and map cc1 - cc8 on them
- map cc11-18 on the "push" encoder
- map cc21-cc28 on the Buttons 1-8
- map cc31-cc38 on the buttons 9-16
- map cc9 to the Fader

4. Click "Dump A" to Save Layer 1 to the x-touch hardware

5. Edit the Fader/Encoder again:
- Global Ch: 2
- put all the "turn" encoders on channel 12.
- leave all the other cc mapping as we set in step 3.

6. Click "Dump B" to Save Layer 2 one to the x-touch hardware

--- finished x-touch setup.

now, make a user control surface in ableton.
to do so, read here : https://help.ableton.com/hc/en-us/artic ... ace-script

after reading the link I above, create two folders in the "User Remote Scripts" Folder.
first folder: X-TOUCH MINI L1
second folder: X-TOUCH MINI L2

then copy and paste my two UserConfiguration.txt files in the directories above. (L1 and L2)

--- finished ableton user control surface creation

now, open up ableton and go to settings.
Set Control Surface 1 to : "X-TOUCH MINI L1"
Set Control Surface 2 to : "X-TOUCH MINI L2"
Set both "in" and "out" to "X-TOUCH MINI"

no need to set track/sync/remote options to on. (only if you want to midimap the other buttons)

---- finished ableton setup

now the following is possible:

1. Click "Layer A" on x-touch.
1. go to your liveset and select a device with mouse.
2. click "encoder 8" on your x-touch and the x-touch layer-A will lock to that device.

3. click "Layer B" on x-touch
1. go to your liveset and select another device with mouse.
2. click "encoder 8" on your x-touch and the x-touch layer-B will lock to that device.

----------------------------

You can do that with multiple X-touch mini controllers.

-----------------------------

the preset has the following ableton mapping:

encoder 1 to 8 rotation: Parameter 1-8
encoder 1 to 5 Push: Select Parameter Page(Bank) 1 to 5
encoder 6 Push: select next parameter page
encoder 7 Push: select previous parameter page
encoder 8 Push: lock ableton device to current x-touch layer

fader: master volume

Lower 8 buttons:
1: back to arrangement
2: set locator
3: jump to previous locator
4: jump to next locator
5: loop
6: stop
7: play
8: rec

---------------------------------------------------------------------------------------------

Copy this Text and insert it in the UserConfiguration.txt in the folder "X-TOUCH MINI L1":

Code:
# Config File for User-defined Instant Mappings

# We assume that the controls on your MIDI controller
# send CCs (except for pads). All controls that do not have
# an explicit channel setting are expected to use the
# global channel. CCs & Notes are counted from 0-127
# and channels from 0-15.

[Globals]
# The channel that the controller should send on
GlobalChannel: 0
# If your controller is connected via USB, replace ControllerName
# with the name of the respective port. Live will then try to
# recognize the ports for you when you select your Instant-Mappings
InputName: X-TOUCH MINI
OutputName: X-TOUCH MINI
# If your controller has pads that send notes, you can use them to
# play the visible pads in your DrumRacks. Just replace the -1 for
# the note (and channel) of the respective pad. The arrangement of
# the pads in the DrumRacks is as follows:
#   1     2     3     4
#   5     6     7     8
#   9    10    11    12
#  13    14    15    16
# (If you leave the channel of a pad at -1, Live will assume that
#  the pad uses the global channel)
Pad1Note: -1
Pad2Note: -1
Pad3Note: -1
Pad4Note: -1
Pad5Note: -1
Pad6Note: -1
Pad7Note: -1
Pad8Note: -1
Pad9Note: -1
Pad10Note: -1
Pad11Note: -1
Pad12Note: -1
Pad13Note: -1
Pad14Note: -1
Pad15Note: -1
Pad16Note: -1
Pad1Channel: -1
Pad2Channel: -1
Pad3Channel: -1
Pad4Channel: -1
Pad5Channel: -1
Pad6Channel: -1
Pad7Channel: -1
Pad8Channel: -1
Pad9Channel: -1
Pad10Channel: -1
Pad11Channel: -1
Pad12Channel: -1
Pad13Channel: -1
Pad14Channel: -1
Pad15Channel: -1
Pad16Channel: -1

[DeviceControls]
Encoder1: 1
Encoder2: 2
Encoder3: 3
Encoder4: 4
Encoder5: 5
Encoder6: 6
Encoder7: 7
Encoder8: 8
EncoderChannel1: 10
EncoderChannel2: 10
EncoderChannel3: 10
EncoderChannel4: 10
EncoderChannel5: 10
EncoderChannel6: 10
EncoderChannel7: 10
EncoderChannel8: 10
# Enter the respective map mode for the encoders here. The following
# map modes are available:
# - Absolute
# - Absolute14Bit
# - LinearSignedBit
# - LinearSignedBit2
# - LinearTwoCompliment
# - LinearBinaryOffset
# - AccelSignedBit
# - AccelSignedBit2
# - AccelTwoCompliment
# - AccelBinaryOffset
# Consult the controller's documentation to find out which mode to use.
EncoderMapMode: Absolute
# Buttons used here are expected to not be toggles (i.e., sending
# value 0 every second time you press it).
Bank1Button: 11
Bank2Button: 12
Bank3Button: 13
Bank4Button: 14
Bank5Button: 15
Bank6Button: -1
Bank7Button: -1
Bank8Button: -1
NextBankButton: 16
PrevBankButton: 17
LockButton: 18

[MixerControls]

VolumeSlider1: -1
VolumeSlider2: -1
VolumeSlider3: -1
VolumeSlider4: -1
VolumeSlider5: -1
VolumeSlider6: -1
VolumeSlider7: -1
VolumeSlider8: -1
Slider1Channel: -1
Slider2Channel: -1
Slider3Channel: -1
Slider4Channel: -1
Slider5Channel: -1
Slider6Channel: -1
Slider7Channel: -1
Slider8Channel: -1
MasterVolumeSlider: 9
MasterSliderChannel: -1
Send1Knob1: -1
Send1Knob2: -1
Send1Knob3: -1
Send1Knob4: -1
Send1Knob5: -1
Send1Knob6: -1
Send1Knob7: -1
Send1Knob8: -1
Send2Knob1: -1
Send2Knob2: -1
Send2Knob3: -1
Send2Knob4: -1
Send2Knob5: -1
Send2Knob6: -1
Send2Knob7: -1
Send2Knob8: -1
TrackArmButton1: -1
TrackArmButton2: -1
TrackArmButton3: -1
TrackArmButton4: -1
TrackArmButton5: -1
TrackArmButton6: -1
TrackArmButton7: -1
TrackArmButton8: -1
VolumeMapMode: Absolute
SendsMapMode: Absolute

[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: 36
PlayButton: 37
RecButton: 38
LoopButton: 35
RwdButton: 33
FfwdButton: 34







Copy this Text and insert it in the UserConfiguration.txt in the folder "X-TOUCH MINI L2":

Code:
# Config File for User-defined Instant Mappings

# We assume that the controls on your MIDI controller
# send CCs (except for pads). All controls that do not have
# an explicit channel setting are expected to use the
# global channel. CCs & Notes are counted from 0-127
# and channels from 0-15.

[Globals]
# The channel that the controller should send on
GlobalChannel: 1
# If your controller is connected via USB, replace ControllerName
# with the name of the respective port. Live will then try to
# recognize the ports for you when you select your Instant-Mappings
InputName: X-TOUCH MINI
OutputName: X-TOUCH MINI
# If your controller has pads that send notes, you can use them to
# play the visible pads in your DrumRacks. Just replace the -1 for
# the note (and channel) of the respective pad. The arrangement of
# the pads in the DrumRacks is as follows:
#   1     2     3     4
#   5     6     7     8
#   9    10    11    12
#  13    14    15    16
# (If you leave the channel of a pad at -1, Live will assume that
#  the pad uses the global channel)
Pad1Note: -1
Pad2Note: -1
Pad3Note: -1
Pad4Note: -1
Pad5Note: -1
Pad6Note: -1
Pad7Note: -1
Pad8Note: -1
Pad9Note: -1
Pad10Note: -1
Pad11Note: -1
Pad12Note: -1
Pad13Note: -1
Pad14Note: -1
Pad15Note: -1
Pad16Note: -1
Pad1Channel: -1
Pad2Channel: -1
Pad3Channel: -1
Pad4Channel: -1
Pad5Channel: -1
Pad6Channel: -1
Pad7Channel: -1
Pad8Channel: -1
Pad9Channel: -1
Pad10Channel: -1
Pad11Channel: -1
Pad12Channel: -1
Pad13Channel: -1
Pad14Channel: -1
Pad15Channel: -1
Pad16Channel: -1

[DeviceControls]
Encoder1: 1
Encoder2: 2
Encoder3: 3
Encoder4: 4
Encoder5: 5
Encoder6: 6
Encoder7: 7
Encoder8: 8
EncoderChannel1: 11
EncoderChannel2: 11
EncoderChannel3: 11
EncoderChannel4: 11
EncoderChannel5: 11
EncoderChannel6: 11
EncoderChannel7: 11
EncoderChannel8: 11
# Enter the respective map mode for the encoders here. The following
# map modes are available:
# - Absolute
# - Absolute14Bit
# - LinearSignedBit
# - LinearSignedBit2
# - LinearTwoCompliment
# - LinearBinaryOffset
# - AccelSignedBit
# - AccelSignedBit2
# - AccelTwoCompliment
# - AccelBinaryOffset
# Consult the controller's documentation to find out which mode to use.
EncoderMapMode: Absolute
# Buttons used here are expected to not be toggles (i.e., sending
# value 0 every second time you press it).
Bank1Button: 11
Bank2Button: 12
Bank3Button: 13
Bank4Button: 14
Bank5Button: 15
Bank6Button: -1
Bank7Button: -1
Bank8Button: -1
NextBankButton: 16
PrevBankButton: 17
LockButton: 18

[MixerControls]
# Again enter the appropriate CCs for the respective controls.
# If all sliders use the global channel to send their data,
# you can leave the channels at -1. You can, of course, use
# encoders or knobs instead of sliders.
VolumeSlider1: -1
VolumeSlider2: -1
VolumeSlider3: -1
VolumeSlider4: -1
VolumeSlider5: -1
VolumeSlider6: -1
VolumeSlider7: -1
VolumeSlider8: -1
Slider1Channel: -1
Slider2Channel: -1
Slider3Channel: -1
Slider4Channel: -1
Slider5Channel: -1
Slider6Channel: -1
Slider7Channel: -1
Slider8Channel: -1
MasterVolumeSlider: 9
MasterSliderChannel: -1
Send1Knob1: -1
Send1Knob2: -1
Send1Knob3: -1
Send1Knob4: -1
Send1Knob5: -1
Send1Knob6: -1
Send1Knob7: -1
Send1Knob8: -1
Send2Knob1: -1
Send2Knob2: -1
Send2Knob3: -1
Send2Knob4: -1
Send2Knob5: -1
Send2Knob6: -1
Send2Knob7: -1
Send2Knob8: -1
TrackArmButton1: -1
TrackArmButton2: -1
TrackArmButton3: -1
TrackArmButton4: -1
TrackArmButton5: -1
TrackArmButton6: -1
TrackArmButton7: -1
TrackArmButton8: -1
VolumeMapMode: Absolute
SendsMapMode: Absolute

[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: 36
PlayButton: 37
RecButton: 38
LoopButton: 35
RwdButton: 33
FfwdButton: 34


btw: watch out, that the midi channel numbers used inside your userscript.txt are from 0-15.
but in the x-touch editor they are from 1-16.



----------------------
hope this hepls anyone :)
----------------------
fabi


Last edited by schwarzlichtfabrik on Tue Nov 06, 2018 11:56 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: X-TOUCH MINI for ableton - Lock and Controll 2 Devices
PostPosted: Tue Nov 06, 2018 10:23 pm 

Joined: Mon Apr 26, 2010 6:38 am
Posts: 2920
Any reason you didn't just set it to MCU mode and then set it up as a Control Surface device in Live? That should allow it to work at a higher integration level than using a user script and is very easy to set up in a few seconds.

https://www.youtube.com/watch?v=T_EC-zSwAgs

_________________
Freelance SoundLabs
Soundcloud


Top
 Profile  
 
 Post subject: Re: X-TOUCH MINI for ableton - Lock and Controll 2 Devices
PostPosted: Tue Nov 06, 2018 11:35 pm 

Joined: Tue Nov 06, 2018 9:21 pm
Posts: 4
hi jester,

sorry for the confusion.
I forgot to point out my reasons:

1. when in mcu mode, i was not able to set "lock to control surface" in the right-click menue of a ableton device.
this option appears for surfaces like apc40 or kontorl49 and many others, but not when I selected "mastercontrol" or "mackiecontrol".

2. the mcu preset confused me too much because of the multi function encoder as device-control, pan input and send. I only need it for device controlling.

3. I liked to use the two layers of the xtouch to control 2 seperate devices (what also needs "lock")

4. I wanted to use more then one x-touch mini in the setup.

maybe i did something wrong, but with live 9 and live 10, i just never got this "lock" option when using xtouch as mcu with mastercontrol or mackiecontrol.


Last edited by schwarzlichtfabrik on Tue Nov 06, 2018 11:58 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: X-TOUCH MINI for ableton - Lock and Controll 2 Devices
PostPosted: Tue Nov 06, 2018 11:53 pm 

Joined: Mon Apr 26, 2010 6:38 am
Posts: 2920
Yeah I think the way the MCU mode works it is assumed it will follow what you do and not lock to a device, the functionality within the script reacts to the selected track.

All good, if there is an actual reason for it then that's what needs to be done. Just pointing out the MCU method for someone that googles this in 5 years time for a solution.

_________________
Freelance SoundLabs
Soundcloud


Top
 Profile  
 
 Post subject: Re: X-TOUCH MINI for ableton - Lock and Controll 2 Devices
PostPosted: Wed Nov 07, 2018 12:04 am 

Joined: Tue Nov 06, 2018 9:21 pm
Posts: 4
jestermgee wrote:
Just pointing out the MCU method for someone that googles this in 5 years time for a solution.


funny, that you think about this!
because while I was researching about the stuff above, I got trapped many times in forum-threads about special mappings like this here, but with no one posing a clarification, that there is an easy-peasy basic-solution.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC

 
 

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group