Clip operations - How to just select rather than fire

    Dec 18 2009 | 11:01 am
    Hi - New To Max and just starting to grasp the basics - I have figured how to get the "current playing slot" index and then be able to manipluate any clip property.
    What I want to do is get Ableton to physically select the currently playing clip in the highlighted track - rather than actually trigger it. So I can then see whatever I am doing to manipulate the clip.
    Any help on how to approach this gratefully accepted.

    • Dec 19 2009 | 5:04 pm
      Would be interesting for me also. What I recognized is that even if you call the method "fire", the clip is not properly selected. I have turned on the property "select fired clip" (or similar) but it doesn't work.
      AND: I cannot set the property "highlighted_clip_slot" of the object "live_set view". (However it's possible to set the "selected_track" and "selected_scene")
      Sorry for I connot help you :)
    • Dec 19 2009 | 9:25 pm
      Looking at the LOM:
      available_main_views Returns: view names [list of symbols]. This is a constant list of view names to be used for the other functions: Browser Arranger Session Detail Detail/Clip Detail/DeviceChain.
      focus_view Parameter: view_name Shows named view and focuses on it
      Looks like this might do what you are needing - changing the view of the app.
    • Dec 23 2009 | 8:57 pm
      I though about your suggestion. I think these functions replicate what you can do in Abelton to change a view.
      In which case this doesn't help as none of those commands will not navigate to a clip or a scene.
      Also you can't navigate using max to a particular scene as it the scene function can only be observed or got - not set.
      Any further ideas on this gratefully accepted. I am trying to build a mouse less environment and this is a stumbling block.
      Its all very well being able to change Clip attributes via max - particular the clip start and length + loop points - But you really need some visual feedback when your doing this.
      It does seem in general one of the shortcomings of M4L API so far is that it can't address any function which you can't address in Ableton via key commands or MIDI - which is a shame.
    • Jul 09 2016 | 7:53 pm
      I know this is an old thread, but in case you are still looking,
      i believe the answer lies in here! :)