Be notified the Live Set is closing, before MIDI out is unavailable?

    Max For Live

    Adam Murray's icon
    Adam Murray's icon
    Adam Murray
    Oct 20 2011 | 8:57 am
    I am trying to reset the state on some external MIDI hardware I am controlling via a Max for Live patch.
    I have the "reset" process working properly when triggered from a button in my patch. And if I hook it up to a [closebang] or [freebang], then it works when I delete the device. But it does not work when I simply close the Live Set or Live itself, which is what I was mostly concerned with...
    I am guessing there is a timing issue here, where Live's MIDI out to external hardware deactivates just before my "reset" process is triggered, and all MIDI out messages from my patch are ignored.
    Has anyone run into an issue like this? Is there another strategy I can use to talk to my external hardware from a patch at the time when the Live Set is closing?

    • amounra's icon
      amounra's icon
      Oct 20 2011 | 9:18 am
      G'Luck w/that. I've been round and round with it. I've tried the normal avenues (live.this_device, freebang, closebang), triggering things from Python through observers in either js or with raw Max observers. No dice. I might be missing something obvious, but I've been pretty exhaustive about it. [live.this_device] should be the answer, but it won't do what I need it to. Perhaps you'll have better luck with it. (In my case, this problem has the most pertinence when moving between edit and live modes with patches, but I know what you're referring to).
      Seriously, if anyone has a solution, I'd love to hear it. If not, it would be a great new feature ;) I know, however, this is in the Abe's court.
    • broc's icon
      broc's icon
      Oct 20 2011 | 10:33 am
      I suspect that Live simply doesn't communicate the 'closing set' operation to the M4L devices such that they could send a closebang as required. Strictly speaking this would be a bug.
    • Adam Murray's icon
      Adam Murray's icon
      Adam Murray
      Oct 21 2011 | 2:46 am
      Thanks for the replies. Maybe I will ask on the Ableton forums in the hopes that an Ableton dev will notice, because yeah it just sounds like a major limitation / bug in Max for Live right now. Oh well. It's annoying but not the end of the world.