Sébastien

How can I get a bang when Push 2 is turned on in M4L? I tried sysexin. It works while patching but not when nested in Live. Is it possible with live.observer?

how-to-get-a-bang-when-push-2-is-turned-on

https://cycling74.com/forums/cross-platform-max-for-live-sysex-and-unrestricted-midi-inout-externals/

Well actually it works only when the Push 2 is loaded before you drop a device in a track.

I periodically poll the control_surfaces object for changes and this works very well. This object will do that on a bang, or if you set the @auto part it will do it on a timer. It will output the id of Push or 0 if it doesn't exist. That way you get connect and disconnect:

And here is a javascript version of the same concept. You can pass callback functions in as options when you create the object like onPushConnected and onPushDisconnected:

The polling with metro method sends out the control_surfaces $1 path id to quickly after a bang to grab_control $1 when turning on the Push 2. Which results in errors. That's why I was looking into the sysexin message to match 240 0 33 29 1 1 10 0 247.

But in conjunction with the polling what finally works for me is to live.observe the implicit_arm property (use only by Push for now) of a selected_track and gate the Push 2 path id and thus the call grab_control $1 until the value of the implicit_arm turns to 1. That way I can grab_contol $1 automatically after Push 2 is turn on and loaded.

Ah, I'm familiar with that type of problem. The python midi remote scripts don't create all of the objects in the hierarchy when th device is created (I.e. Connected) and it waits for a particular event to initialize them. At least this was true for push 1, probably for performance reasons. For example the SessionController wasn't created until you actually entered session mode on push. Quite annoying for programmers. So you have to find and wait for a particular event to create the object, as you have done.

How to get a bang when Push 2 is turned on?