Can someone please point me in the right direction, I’m having trouble finding any decent info.
Here’s what I need to do:
In Ableton 6, I need to get Midi Feedback when I press a button that’s midi mapped. This is so I can turn LEDs on and off.
If I use something like the Mackie Control script it’s definately possible to do everything I need to, but there is way too much other midi data flying about to make any sense of to do a direct hack. The files for the Mackie control etc are not human readable - any clues how they make 'em?
I need to know how to build a custom Midi Remote Script myself, I don’t think the “User Defined” using UserConfiguration.txt one is gonna do it (or will it?), because I need to get to stuff like buttons in VST plug ins (all do-able, but how?)
Live does this “just by itself” for mapped controls since version 5, for version 4 you had to write a special command into a text file, here is the history with robert henkes own reply:
just started reading those threads carefully - wow, some really cool info I missed!
Thanks again
and BTW: re automapped midifeed back, i haven’t checked everything, but I’m working with things like the cue and that defo doesn’t work with out a script active…
this is strange, as robert henke himself wrote the following:
“…The MIDI feeback option is not necessary anymore, since Live 5 this is enabled anyway. The options.txt stuff is a bit tricky. Things might change here from verision to version… so you can never be sure it does what you think it will do…”
I also know that the MONOME lights works without any script with MIDI FEEDBACK from the active clips, mhh.
But you are right that PHYTON is the key to the “real” control surface mapping. 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. So one has to assign e.g. MIDI Note ON´s to every clip/control which should spit out MIDI feedback. 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. This is where Phyton comes in.
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..
i am very interested about the “midi feedback” feature of Live, does anybody have links to concrete and very deep coding about it ? I planned to develop a controler based on this.
well my Live!5 does it by default, no need to hack anything.. (or is it that i dont understant what you are talking about?.. midi feedback=the host says to the MB, or any other controller if a mapped button is on or off, so for example if you push a mapped button with the mouse the correspondent button will light up as well in your box)
wow - it’s weird yours was on already - lucky you! took me ages to track down a solution…
you on Mac or PC?
but also - the main point is of course, before you do lots of work on using the midifeedback stuff, you might wanna upgrade and go into the remote scripting - could save a duplication of work in the long run…
