Ableton Forum

Get it here - http://www.omnision.co.uk/UserConfiguration.txt

Put it here C:\Documents and Settings\(username)\Application Data\Ableton\Live 7.0.14\Preferences\User Remote Scripts\(create folder here - I've called mine Nanokontrol so that its easier to identify in midi preferences)

I've no idea how file management works on a mac - sorry.

eight rotaries map to the 8 macro controls
8 faders map to tracks 1 - 8 . Fader 9 maps to master volume.
8 top row buttons map to record arm for tracks 1 -8.
I think these work better if the buttons are switched from momentary to toggle mode.

buttons 8 and 9 on bottom row map to bank down/ bank up. I'm at the wtf stage with banks in Live, can't figure out if I don't understand the concept or if I don't notice the profound change that occurs when I shift up a bank.

transport buttons do what they should.

its worth reading the #comments that the abletonpeople have strewn thru the textfile since it made it easy for me to understand what to do, there's still 8 buttons that could do with assigning but I ran out of patience and decided to make some music instead...
I think that I designed the script using using the default settings on the nanokontrol - if not check that the midi cc numbers in the text file match up with ccs on in the Kontrol editor.

Big up the budget massive!

anybody knows where to put this on a mac?

Thanx,

Heiko

got it,

Library - preferences - ableton - 6.05 - user remote scripts - 'copy the txt file here'

but I didn't get Live to see it in 'control surfaces'

hmmmmmmmm

you need to put a folder into the "user remote scripts folder". Name the folder "NanoKONTROL" and it will show up as such in preferences in the list of surfaces, at the bottom of the list.

Does the arm track actually work in toggle mode? Or do you still have to press the button twice?

Cheers Pepe

doesn't work....it shows it in preferences, but doesn't do anything differnt

hi all. i want to customize your user script but i would like to map the two buttons to mute and solo, and the eight knobs to work out as pan pots. i've been reading your script but i don't know how to define mute, solo, and pan so that then i can write which CC will control each one. is there a place that has this info? thanks!

Hello. Ableton's current implementation of instant mapping doesn't cater for pan and mute commands - so there is no way of achieving it using this script. If you do a google quest for mackie control emulation you'll discover what cc's and midi notes are used to achieve mutes and pans within the mackie system. I've tried using scene 1 on the nanokontrol as instant mapping and scene 2 with some of the mackie commands - then set up the nanokontrol as both a remote control (using the nanokontrol script) and a fake mackie controller - using the mackie preset. It worked OKish (some latency on clip navigation) but I never bothered with mapping out mutes and pans.
It might be easier to create a template set with these controls premapped.

thanks a lot for your custom made script.

thanks for the script
this will make my next live set so much more pleasurable

Could somebody please repost the configuration file from the first post? It is offline.

here's the user configuration script


# 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: nanoKONTROL 1 SLIDER/KNOB
OutputName: nanoKONTROL 1CTRL
# 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: 14
Encoder2: 15
Encoder3: 16
Encoder4: 17
Encoder5: 18
Encoder6: 19
Encoder7: 20
Encoder8: 21
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
Bank7Button: -1
Bank8Button: -1
NextBankButton: 40
PrevBankButton: 41
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: 2
VolumeSlider2: 3
VolumeSlider3: 4
VolumeSlider4: 5
VolumeSlider5: 6
VolumeSlider6: 8
VolumeSlider7: 9
VolumeSlider8: 12
Slider1Channel: -1
Slider2Channel: -1
Slider3Channel: -1
Slider4Channel: -1
Slider5Channel: -1
Slider6Channel: -1
Slider7Channel: -1
Slider8Channel: -1
MasterVolumeSlider: 13
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: 23
TrackArmButton2: 24
TrackArmButton3: 25
TrackArmButton4: 26
TrackArmButton5: 27
TrackArmButton6: 28
TrackArmButton7: 29
TrackArmButton8: 30
VolumeMapMode: Absolute
SendsMapMode: Absolute

[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: 46
PlayButton: 45
RecButton: 44
LoopButton: 49
RwdButton: 47
FfwdButton: 48

Works OK thank you !

I'll try to program encoders to control PAN and low button as SOLO

I'll keep you posted