Ableton Forum

mclive wrote: For example, say i start a new set, load an operator instrument into the midi track, the only parameter that maps is knob5 on the oxygen to Time (in the time, tone, volume shell area). That's it. The other buttons do nothing.

longjohns wrote:My (limited) take on automap is that it would be most useful to put devices into racks, so that you can control which parameters are where, by the macro assignments which you make.

mclive wrote:

longjohns wrote:My (limited) take on automap is that it would be most useful to put devices into racks, so that you can control which parameters are where, by the macro assignments which you make.

i'm sure this is helpful, but i'm afraid i've no idea what you've just said - this is quite new to me...does anyone know where these templates are stored? it would help to know what the instant map THINKS the default midi settings are for these devices.

thanks

longjohns wrote:The research you're doing will certainly help you. I must admit I have not played with the custom mapping file myself...

But the important part of what I was trying to say is this:

Let's assume you have the 8 pots on your Oxy8 working nicely and mapping automatically to devices. What's to say that they're going to map to the controls you actually want to use? An extreme example might be Operator. How many parameters are available in Operator? Lots. So which ones are going to map to your 8 pots - probably not the most useful combination of controls.

That's why I'd try putting the device inside a Rack. Then you can map the controls which you'd most like to use out to the 8 macros up front. Then you can save that as a rack preset. Now you can define what controls you want to be automapped for every device, all you've got to do is go through once and make the mappings to the macros.

longjohns wrote:The research you're doing will certainly help you. I must admit I have not played with the custom mapping file myself...

longjohns wrote: That's why I'd try putting the device inside a Rack. Then you can map the controls which you'd most like to use out to the 8 macros up front. Then you can save that as a rack preset. Now you can define what controls you want to be automapped for every device, all you've got to do is go through once and make the mappings to the macros.

longjohns wrote:I just did a little experiment and made a config file for the oxy8, just to go through the process.

My guess as to some of your problems is that you may have other midi mappings in the set to those controllers, which will override the automapping.

Also check to make sure that your pots on the controller have not been changed to some other CC#'s or MIDI channels.

# Config File for User-defined Instant Mappings

# We assume that the controls on your MIDI controller
# send CCs. All controls, except the sliders for volume
# and the encoders for device parameters, are expected
# to use the global channel. CCs 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: In USB Keystation
OutputName: Out USB Keystation

[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: 10
Encoder2: 11
Encoder3: 12
Encoder4: 13
Encoder5: 14
Encoder6: 15
Encoder7: 16
Encoder8: 17
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: -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: -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: -1
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: -1
PlayButton: -1
RecButton: -1
LoopButton: -1
RwdButton: -1
FfwdButton: -1