Is this correct as I describe it? To be honest I never tried it myself, I am just also very interest in this topic and scanned all the forums like mad to gain some information. This should work without any script (according to the Ableton forums).Ģ) Generic control surfaces: those commands should work in EVERY Live set where one is working, without having to assign controls with MIDI mapping. It has some basic parameters you can assign and I. MIDI Note ONÂ´s to every clip/control which should spit out MIDI feedback. Ableton has a User Script in the Midi Remote Scripts folder for writing your own custom control surfaces. I think we have to differentiate between two different topics for this discussion:ġ) MIDI Feedback from assigned controls/clips: this only works for the actual Live set one configures manually. I also know that the MONOME lights works without any script with MIDI FEEDBACK from the active clips, mhh.īut you are right that PHYTON is the key to the 'real' control surface mapping. Program Data folder is not visible by default, you might need to enable 'Show hidden folders' as shown here). Remotify.io is a revolutionary new web app that gives you the ability to create your own dynamic MIDI remote scripts within Ableton, for your MIDI controllers. WINDOWS - Located in C:ProgramDataAbletonLive 10 SuiteResourcesMIDI Remote Scripts. so you can never be sure it does what you think it will do.' Copy the contents of the Script folder (MonoFramework, Tools and Twister) to your Ableton Lives MIDI Remote Scripts folder.

Things might change here from verision to version. '.The MIDI feeback option is not necessary anymore, since Live 5 this is enabled anyway. This is strange, as robert henke himself wrote the following:

How to write midi remote scripts