It looks like you're new here. If you want to get involved, click one of these buttons!
@milkthistle: I provided a way to change the colors in the user mapping pages because it was possible, but unfortunately once we hand off the controls to another channel, it's impossible for the script to affect what colors are set by Ableton. This is a shortcoming of their MIDI Mapping system, and there isn't anyway around it through scripting. As soon as Ableton turns on/off a control that is mapped via UserMapping, it will either send a 0 or a 127 (or 64? I can't remember) to the control that is mapped, which is why you always see only one color as feedback on those buttons.
The problem with the colors is specific to user-mapping, yes. The controller determines what color a button is painted depending on the velocity it receives. Ableton does not offer any sort of customization for this value when you User-Map a control. Consequently, if you user-map a button, when Ableton turns it on, it will always send a value that is greater than 63 (which means the on-value for every button is always going to be the same, by default I think it's green).
That is exactly what I found out myself as well, so it basically means that using specific colors for a user page is not useful, because the mapping will override it, due to the way that Ableton handles the mapping as described by Amounra.
The new version looks great. Don't know how I missed that this came out!Going through the wiki page / docs (http://wiki.lividinstruments.com/wiki/CNTRLR_Ableton_Live_Remote_Script_v2), a few requests - In the first image (http://wiki.lividinstruments.com/images/2/2c/CNTRLR_full.jpg)- Add "@ssign" and "lock" text to the bottom right in the 4x4 areaWhere is says use the "Session or Note" button, shouldn't it say "Sequence or Session" button?
Hello, thanks a lot for this update!! its just amazing how fast I can work now, I'm so happy and very excited to start using it... I just have a question how to change all my previous saved projects with this devices to frozen one? Currently I cannot activate them as it is working with new devices but I have a lot of saved projects with saved old DrumStepr and Synthstepr what to do now? and also currently when you are entering MFL mode all top encoders remain with the same functionality as in script mode so I cannot tweak last encoders in my MFL devices as groove, Repeat etc. thanks for the answer
A possible bug: the sixth button on the top row of 16 isn't responding to user input.Usability issue/request:In Accent, you have to hold Shift and turn the middle left encoder for access to the Repeat Len knob, but the button is activated from a different encoder. If m4l shift used the bottom row of encoders for the bottom row in Accent, it would make more sense: the Repeat Len knob and activator button would be on the same encoder. Feature requests:The Audio Clip loop time control is nifty, the same feature for Midi clips would be great, too. Is it possible?Setting velocities in the native (not max) sequencer would be amazing. Maybe holding down the step button and using an encoder to set the velocity? Or maybe color controls and hitting the button more than once to incrementally go through three pre-defined (in the script) velocities for the step + off? Also, thanks for making the user mode knobs/buttons/faders configurable in the script!Awesome script, thanks guys.
Thanks for the answer, problem which I'm talking about its not loading itself, but once I opening project where old stepprs were used I cannot control them with new script. So I would like to do is control with new script my saved M4L devices or at least update them somehow, is there any way?
Hey Amounra buddy,
@Mike: No, of course it doesn't work. My bad. Forget what I told you in the last post, instead add these lines to the stock script at around line 269 (anywhere within the CntrlrSessionComponent, actually). I just tested it, it's working for me.
@Tartari and @Amounra,
Sorry my bad, just found out that you have to press the shift for that.
Sorry Mike, I just can't reproduce it here.....if you figure out any new info, let me know, I'm definitely interested in fixing it if I can get something to grasp, but right now I can't make heads or tails of it.
Not to worry, I'm aware of this. I'll have an update available soon.
I've made some changes to the github repository, these should fix beta 9.21b problems with our scripts. I haven't tested extensively, so please let me know if you find more issues besides the ones I've fixed. Have the flu here, but I'll try to check in a little later to see what's going on....