LiveAPI observer for scene selection?


    Jul 22 2020 | 3:29 pm
    For a project, I am attempting to synchronize something outside of Ableton Live with specific scenes in the set. To do this, I have been digging into the Live Object Model and the implementation of the LiveAPI in Javascript.
    I found an answer from Andrew Pask about coding a basic observer for volume, but when I tried to adapt it for observing the scene using
    var liveObject = new LiveAPI("live_set scenes");
    it fails to update with my selections in Ableton Live. It seems to report the correct id of the scene at the time it first runs, but then it never updates.
    Has anyone tried something like this before? Any suggestions about how to code an observer for the current scene in Ableton Live?
    -Nathan

    • Jul 24 2020 | 9:39 am
      why java and not simple live.path -> live.observer object ? I am not using Live at all, but helping someone out took only few minutes to get live.observer report current selected scene either by id, number or name
    • Jul 30 2020 | 8:18 pm
      Javascript makes it easier for me to track changes using version control, since the live.path & live.observer object only work inside M4L.
      On your advice, I tried the following collection of objects. It does not seem to report the current scene inside my Max for Live device.
      Any ideas?
    • Jul 30 2020 | 8:53 pm
      Doing some more digging and found this M4L device from 2012 that fires scenes. Using their method, I can get the selected scene. It's not clear how I could make this an observer unless I do some sort of polling.
      Even then, it is a selected scene and not one that has been fired. A fired scene will be selected, but a selected scene is not necessarily fired. Unless I am missing something?
    • Jul 30 2020 | 10:07 pm
      OK, this solution works as a temporary measure. But I would still prefer to know when the scene has been fired, not just selected.
    • Jul 31 2020 | 6:30 am
      I used this in one project. Am not Live user at all, maybe this can be done more effective...
      sending info out can be easily done, midi, OSC I also could not find any way to get info on which scene is fired- did read up and down the LOM documentation, nothing. All that could be issued is if scene is triggered (blinking) in idle time to fire in case firing is quantised and not immediate.
    • Aug 10 2020 | 3:04 pm
      Thanks for this example. Seems to match what people were telling me over in the Facebook group. You can get the currently selected scene, but you cannot observe when a scene is triggered. Seems like a gap in the LOM implementation.
      My thanks to Source Audio and everyone that offered input.
    • Aug 10 2020 | 3:06 pm
      For archival purposes, here is the solution I created for getting the currently selected scene:
    • Feb 01 2021 | 1:04 pm
      thank you Source Audio for your detector !