User Remote Scripts: Using Banks?
Posted: Tue Mar 08, 2011 1:56 am
I made a user remote script for my Novation X Station and it works great for controlling tracks 1-8.
But is it possible to utilize the "bank buttons" in the user remote script to access tracks 9-16 etc.?
I really only want to have my 8 faders and 8 buttons bank to the next 8 tracks, so they can control the "volume" and "track arm" of tracks 9-16 etc.
I've looked into programming a python remote script but this is way over my head. I don't need anything fancy, just access to volume and arm for tracks after 1-8, while keeping my 8 encoders locked into the 8 macro controls.
Any help would be so appreciated!
Here is my script for the X-Station:
# 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: ControllerName
OutputName: ControllerName
# 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]
# The Encoders will control the device parameters (you can also
# use knobs or sliders). Replace the -1's with the CCs sent by
# the respective controls on your controller. You can also set
# the channel for each controller if it differs from the global
# channel (if you leave the channel of an encoder at -1, Live
# will assume that the encoder uses the global channel).
Encoder1: 33
Encoder2: 34
Encoder3: 35
Encoder4: 36
Encoder5: 37
Encoder6: 38
Encoder7: 39
Encoder8: 40
EncoderChannel1: 15
EncoderChannel2: 15
EncoderChannel3: 15
EncoderChannel4: 15
EncoderChannel5: 15
EncoderChannel6: 15
EncoderChannel7: 15
EncoderChannel8: 15
# 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: -1
Bank2Button: -1
Bank3Button: -1
Bank4Button: -1
Bank5Button: -1
Bank6Button: -1
Bank7Button: -1
Bank8Button: -1
NextBankButton: -1
PrevBankButton: -1
LockButton: -1
[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: 49
VolumeSlider2: 50
VolumeSlider3: 51
VolumeSlider4: 52
VolumeSlider5: 53
VolumeSlider6: 54
VolumeSlider7: 55
VolumeSlider8: 56
Slider1Channel: 15
Slider2Channel: 15
Slider3Channel: 15
Slider4Channel: 15
Slider5Channel: 15
Slider6Channel: 15
Slider7Channel: 15
Slider8Channel: 15
MasterVolumeSlider: 47
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: 82
TrackArmButton2: 83
TrackArmButton3: 84
TrackArmButton4: 85
TrackArmButton5: 86
TrackArmButton6: 87
TrackArmButton7: 88
TrackArmButton8: 89
VolumeMapMode: Absolute
SendsMapMode: Absolute
[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: -1
PlayButton: -1
RecButton: -1
LoopButton: -1
RwdButton: -1
FfwdButton: -1
But is it possible to utilize the "bank buttons" in the user remote script to access tracks 9-16 etc.?
I really only want to have my 8 faders and 8 buttons bank to the next 8 tracks, so they can control the "volume" and "track arm" of tracks 9-16 etc.
I've looked into programming a python remote script but this is way over my head. I don't need anything fancy, just access to volume and arm for tracks after 1-8, while keeping my 8 encoders locked into the 8 macro controls.
Any help would be so appreciated!
Here is my script for the X-Station:
# 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: ControllerName
OutputName: ControllerName
# 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]
# The Encoders will control the device parameters (you can also
# use knobs or sliders). Replace the -1's with the CCs sent by
# the respective controls on your controller. You can also set
# the channel for each controller if it differs from the global
# channel (if you leave the channel of an encoder at -1, Live
# will assume that the encoder uses the global channel).
Encoder1: 33
Encoder2: 34
Encoder3: 35
Encoder4: 36
Encoder5: 37
Encoder6: 38
Encoder7: 39
Encoder8: 40
EncoderChannel1: 15
EncoderChannel2: 15
EncoderChannel3: 15
EncoderChannel4: 15
EncoderChannel5: 15
EncoderChannel6: 15
EncoderChannel7: 15
EncoderChannel8: 15
# 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: -1
Bank2Button: -1
Bank3Button: -1
Bank4Button: -1
Bank5Button: -1
Bank6Button: -1
Bank7Button: -1
Bank8Button: -1
NextBankButton: -1
PrevBankButton: -1
LockButton: -1
[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: 49
VolumeSlider2: 50
VolumeSlider3: 51
VolumeSlider4: 52
VolumeSlider5: 53
VolumeSlider6: 54
VolumeSlider7: 55
VolumeSlider8: 56
Slider1Channel: 15
Slider2Channel: 15
Slider3Channel: 15
Slider4Channel: 15
Slider5Channel: 15
Slider6Channel: 15
Slider7Channel: 15
Slider8Channel: 15
MasterVolumeSlider: 47
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: 82
TrackArmButton2: 83
TrackArmButton3: 84
TrackArmButton4: 85
TrackArmButton5: 86
TrackArmButton6: 87
TrackArmButton7: 88
TrackArmButton8: 89
VolumeMapMode: Absolute
SendsMapMode: Absolute
[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: -1
PlayButton: -1
RecButton: -1
LoopButton: -1
RwdButton: -1
FfwdButton: -1