Ableton Forum

well, there's nobody who could tell better than you, after TRYING IT OUT!

I see you send an 8 to your object for backspace/delete, what numbers should we send your object to get ctrl shift m? Cheers!

Have a look at that list:

http://java.sun.com/j2se/1.5.0/docs/api ... vent.VK_F1

You can send a list to the keyPress-object in order to press multiple keys at one time.

could be nice to implement this function directly in the apc40 or the LP (not sure control surface scripts support keyboard msg)
for ex : if you press metronome butt(hold) + the desired clip slot (matrix) => delete
for the focus problem (live not selected) is there something in max to list the available opened windows
and to select the one named or containing "Live 8" (name in title bar)
what do you think?

I think, this is not a matter of ableton but java. The keystroke always has effect on the window that is in front / highlighted.

If you don't want to have ableton in front but still want to use the given delete-object, you might go that way: use java to bring ableton to front, delete the clip and then again put the other program in front.

But I guess this will be quiet buggy...

ring wrote:Have a look at that list:

http://java.sun.com/j2se/1.5.0/docs/api ... vent.VK_F1

You can send a list to the keyPress-object in order to press multiple keys at one time.

Ring it does work great!! I through a list at it and it was able to do ctrl shift m. Though I had only tested your patch by it self, once I incorporated it into a bigger patch I had some serious cpu hits or something because my audio would start dropping out after the patch was banged. I used tomatoe_joe's version and it worked a charm. His only change is the delay object is replaced by defer so maybe this could have caused some cpu problems. From what I read defer has something to do with cpu priority and the overdrive in max, anyway thanks again to ring and tomatoe_joe!!!!

Why this has to be so complicated?

I think this should be as easy as sending 'call delete' to the corresponding ClipSlot ID. Then all the window-focus problems would disappear.

I hope Ableton/Cycling74 will map all the standard menu actions in the maxforlive API soon.

yannxou wrote:Why this has to be so complicated?

I think this should be as easy as sending 'call delete' to the corresponding ClipSlot ID. Then all the window-focus problems would disappear.

I hope Ableton/Cycling74 will map all the standard menu actions in the maxforlive API soon.

Good question!!! Try working with M4L and a control surface, pure torture!! even the "Official" ableton controllers are not even documented in the LOM, not sure if this is a ableton or c74 problem but people are even starting to blame Akai.