Editing midi remote scripts

[hurlingdervish]

is there any guidance on this subject?

trigger finger auto maps to drum racks (yay! you know this...) but puts the sliders to global pitch and volume (nay! how worthless!)

what am I looking for?

[8O]

You don't mean Automap as in Novation's Automap, right? You mean Live's Remote Surface Instant Mapping, right?

[hurlingdervish]

You don't mean Automap as in Novation's Automap, right? You mean Live's Remote Surface Instant Mapping, right?

midi remote scripts

[8O]

Ok, so three threads that I know of:
http://forum.ableton.com/viewtopic.php?f=1&t=126205
http://forum.ableton.com/viewtopic.php?f=1&t=125245
http://forum.ableton.com/viewtopic.php?f=1&t=84590
But in general there isn't a whole lot of info on it as the basic script seems to be quite limited.

[hurlingdervish]

what bugs me is that they put a global pitch parameter that doesn't even exist in the main program...

????

why bother?

so theoretically (ill test it so dont say test it if i deleted a line of code that had pitch blah blah blah , it would all work fine right?

[hurlingdervish]

iÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿ( iÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿiÿÿÿÿ(! t constst GENERIC_STOPt GENERIC_PLAYt GENERIC_RECt GENERIC_LOOPt GENERIC_RWDt GENERIC_FFWDt TRANSPORT_CONTROLSt GENERIC_ENC1t GENERIC_ENC2t GENERIC_ENC3t GENERIC_ENC4t GENERIC_ENC5t GENERIC_ENC6t GENERIC_ENC7t GENERIC_ENC8t DEVICE_CONTROLSt GENERIC_SLIDERSt VOLUME_CONTROLSt GENERIC_BUT1t GENERIC_BUT2t GENERIC_BUT3t GENERIC_BUT4t GENERIC_BUT5t GENERIC_BUT6t GENERIC_BUT7t GENERIC_BUT8t TRACKARM_CONTROLSt GENERIC_BUT9t
BANK_CONTROLSR t CONTROLLER_DESCRIPTIONSt
MIXER_OPTIONS( ( ( sY H:\Dev\8.0.4-Final\Projects\AppLive\Resources\MIDI Remote Scripts\TriggerFinger\config.pys <module> s2

i couldnt find anything on pitch though

maybe that (amazing) dude who did the nanoKontrol knows??

[8O]

Yeah, I also don't recall any pitch setting in that script, so it must be something extra, not belonging to those script models, like the extra functionality you get from Mackie emulation, for example.

I think if you create a new remote script and assign your Trigger Finger to that, you should lose all the old Trigger Finger mappings (including the undocumented ones). Not sure as I can't test it, but it would make sense as one of the ideas of creating new scripts is to support controllers that aren't in the standard list.

[hurlingdervish]

hmmm

FUCK!

i dont think ill be able to do that...very disappointing considering that the pitch was probably a half baked add on like "everything else does something so why not this slider?"

ive tried the enigma m-audio software several times, but its not happenin

and of course....m-audio has nothing to say about it except "don't use the automap functions"

[fishmonkey]

you can also try using the script for another device... of course you will need to find out what right MIDI messages are so you can program your Trigger Finger to send the same things...

also, have you tried making your own custom instant mapping using the blank user config template?

[hurlingdervish]

you can also try using the script for another device... of course you will need to find out what right MIDI messages are so you can program your Trigger Finger to send the same things...

also, have you tried making your own custom instant mapping using the blank user config template?

i have no idea where to even start...

all i need is the drum rack to pads mapping

any idea what that looks like?

[fishmonkey]

editing your own User Remote Script would be the best idea then...

have to run now, but can help more later if no one else chimes in in the meantime...

are you on Mac or Windows?

the pre-defined scripts and the blank user-defined script with some instructions are in your Live preferences folder...

on a Mac the folder is:

~/Library/Preferences/Ableton/Live 8.0.5/User Remote Scripts

[hurlingdervish]

cool i think i can handle this

one question though

where do i paste the code i need? into a copy of the init file renamed to something?

[8O]

Just put it exactly where it says in the instructions:

1. Create a directory in 'User Remote Scripts'.
The name of the directory will show up in the
list of Control Surfaces in Live.
Naming: The name of the directory should not
start with '_' or '.'.

2. Copy the the file 'UserConfiguration.txt' into
your directory. The name of the file needs to
remain unchanged.

3. Edit the copy to adapt it to your needs. The
comments in the file will tell you what to do.

In my case, I created a custom mapping for my UC-33e, so I created a "UC-33e Custom" folder, and the file goes here:

<user>/Library/Preferences/Ableton/Live 8.0.5/User Remote Scripts/UC-33e Custom/UserConfiguration.txt

[8O]

Here's some snippits of my custom mapping, I don't have any drum rack controls mapped, but maybe the global parameters, etc, can help you a bit...

The bits I added are in bold...

[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: UC-33 USB MIDI Controller
OutputName: UC-33 USB MIDI Controller

...

[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: 108
Encoder2: 109
Encoder3: 110
Encoder4: 111
Encoder5: 112
Encoder6: 113
Encoder7: 114
Encoder8: 115
EncoderChannel1: -1
EncoderChannel2: -1
EncoderChannel3: -1
EncoderChannel4: -1
EncoderChannel5: -1
EncoderChannel6: -1
EncoderChannel7: -1
EncoderChannel8: -1

I got each encoder value by entering midi-learn mode in Live and noting which number each controller was when moved. I got the input name and output name by noting exactly what was written in Live's midi preferences tab with the UC-33e connected up in the normal way. I wasted half an hour trying to get it to work only to realise that I'd copied the file into the wrong folder - it must be in the one I mentioned above, nowhere else, otherwise it won't work. Good luck!

[fishmonkey]

another thing to watch out for is getting the global channel right...

the Ableton script numbers the MIDI channels from 0-15... some controllers number the channels from 1-16 instead, if so you will need to subtract one to get the right global channel number to put in the script...