Ableton Forum

have you got livecontrol or griid running? this is the default behaviour of these apps in order to keep them synced with the current clip.

As he says in the video, the clips are just sending program / bank change messages. Make a new midi track, add some blank clips, then under "Notes" set the bank to the desired value. Should trigger a bank change on launch. You need to direct the midi track to the right midi interface for t...

Not 100% sure how it works in max, in python you get a tuple. In max does get_selected_notes give you a list? If so you need to do some zl magic to remove the rows you dont want, then call replace_selected_notes with your updated list.

You need to select all the notes in the clip, get the list of notes, remove the row you dont want, then use replace_selected_notes.

what are you currently using to control touchosc? midi or osc? if using osc you should look at bundling your osc messages together, this makes touchosc significantly faster when sending a lot of data.

This is only the case in order to keep the clip editors in sync. If you dont sequence midi with cliip/livecontrol i can give you a fix to disable the clip polling.

deselect all your midi remote scripts in midi preference and see if the behaviour is the same. griid / livecontrol both deselect all notes after a change (well its actually a select all then deselect all) in order to keep in sync with the clip.

Totally doable, theres no limitations in the remote scripts for 8 parameters, its just thats the way its currently designed and most of the framework is built. If you are going to build a custom device, you'd probably want a customised remote script for it anyway. Drop us an email, maybe we can help...

current track is: live_set view selected_track current clip is more complictated, you need the selected scene: live_set view selected_scene then combine with selected_track to get to the clip. you'll need to look up the path of the current track + scene first, then create a path in the form of: live...

You want the Kapture TriggerTrack section, which ultimately calls playing_slot_changed

You've raised an error somewhere before the script disconnects, leaving listeners connected to objects that no longer exist. Check the log file for the last place you raised an error.

Only way to get rid of it is to close / restart live

Hoffman2K, How is the level of each of your knobs shown visually? Is it just by the position of the knob? A suggestion could be to change the brightness of the LED in the knob according to the level it's set at. This would make it easier to "shift" when parameters are updated on DAW, inst...

Just a quick update, we are now shipping these. See here for more info: http://post.monome.org/comments.php?Dis ... 657&page=2

Dont think there is a mixer_device on clips is there? Think this is one of those few parameters that isnt exposed to the liveapi

The slow down is generally the speed of the api in m4l, however with 14 tracks i would have thought it'd be ok. Will have to check into that.