nanoKey user remote script

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
lenzcom
Posts: 1
Joined: Sat Jul 09, 2011 9:51 pm

nanoKey user remote script

Post by lenzcom » Sat Jul 09, 2011 10:16 pm

Hello there,

because this is my first post in this forum I want to say HELLO to the community. I'm Daniel, 28y living in Essen, Germany.

I was currently searching for a User Remote Script for the nanoKEY (v1). I was now wondering what to do with the control names and numbers.

Do I have to change "Pad" to "Key" and how to name "Bank"-Buttons? "Octave-1-Down/UP", "Pitch UP" etc?

Control numbers compared to the controls showing up in "Korg Kontrol Editor" are CC1, CC14-CC31, CC81,CC83,CC86,CC87 (see Screenshot below my current user script code)

Thanks for your help in advance.

Here is what I have so far:

Code: Select all

# 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: nanoKEY 1 KEYBOARD
OutputName: nanoKEY 1 CTRL
# 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: 36
Pad2Note: 37
Pad3Note: 38
Pad4Note: 39
Pad5Note: 32
Pad6Note: 33
Pad7Note: 34
Pad8Note: 35
Pad9Note: 28
Pad10Note: 29
Pad11Note: 30
Pad12Note: 31
Pad13Note: 24
Pad14Note: 25
Pad15Note: 26
Pad16Note: 27
Pad1Channel: 36
Pad2Channel: 37
Pad3Channel: 38
Pad4Channel: 39
Pad5Channel: 32
Pad6Channel: 33
Pad7Channel: 34
Pad8Channel: 35
Pad9Channel: 28
Pad10Channel: 29
Pad11Channel: 30
Pad12Channel: 31
Pad13Channel: 24
Pad14Channel: 25
Pad15Channel: 26
Pad16Channel: 27

[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: 0
Encoder2: 1
Encoder3: 2
Encoder4: 3
Encoder5: 4
Encoder6: 5
Encoder7: 6
Encoder8: 7
EncoderChannel1: -1
EncoderChannel2: -1
EncoderChannel3: -1
EncoderChannel4: -1
EncoderChannel5: -1
EncoderChannel6: -1
EncoderChannel7: -1
EncoderChannel8: -1
# 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
Image

Locked