Making a scene launch trigger

    Mar 12 2019 | 5:56 pm
    Hello all again, I'm trying to create a patch that automatically goes to next scene when I press my MIDI Key (The controller can't be directly mapped to it for some reason). I can't quite figure out the patching for this. I'm less than a week into learning max, so it's been quite overwhelming. I have the button setup: Midi in and then sel 15 (the button sends the value 15), and then I have a call fire set up through a trigger, but I'm not sure how to figure out to get max to detect what scene I'm currently on. Thanks for any help with this.

    • Mar 13 2019 | 2:08 am
      If you're using pads, you should probably use [stripnote] to avoid double triggering. Then, about your question, it depends what you call a scene and what system you use to deal with your scenes. Is a scene a [pattr] preset?
    • Mar 13 2019 | 7:59 am
      I'm realizing I didn't fully describe it, sorry. I want this patch to work to launch actual scenes in Ableton Live. I tried making a call fire and a message containing goto_ next scene $1, and receive a bang from the desired note on the controller, but it didn't have any effect.
    • Mar 13 2019 | 2:17 pm
      hey, you can easily increment between scenes with something like this
      then I guess you could make it better by getting the number of scenes and mapping your controler to a live.numbox (I don't think there is a live version of the incdec Max object)
    • Mar 14 2019 | 2:45 pm
      Thanks Florent, this did the trick! One last question, is there a way to take this further? I want to be able to click on the necessary scene in Ableton without making it send the call fire to trigger? For example: I have it on scene 15. I then have the track trigger mapped in the session until it reaches a looping section, but that scene is scene 19. If I use the controller, it's going to trigger scene 16 next. How can this to find the scene I'm on to know when to go to the next appropriate scene? Here's what I added to the suggested scene to make the MIDI controller (which is sending signal 15 from the button I can test it just by clicking the bang though of course.):
    • Mar 14 2019 | 4:32 pm
      I'm not sure I understand what you're trying to do, but if you want to observe which scene is currently playing, there is a property "is_triggered" that you can get and observe with the live API
    • Mar 14 2019 | 4:37 pm
      I'm trying to launch clips in Ableton, and since I'm a saxophonist I can't use hand controllers. The controller I have needs a way to read what scene is currently playing, or have a way for me to give it a scene without launching, so that the function you gave me can launch the scene after that when pressed. Just music playback.
    • Mar 14 2019 | 10:30 pm
      Try this to select any scene:
    • Mar 14 2019 | 10:38 pm
      Evan, this selects the scene, but is there a way to sort of do the opposite? Making it so that whatever scene I highlight shows up in the index? Then by pressing my controller, it activates the scene that it's sitting on?
    • Mar 14 2019 | 10:50 pm
      Not entirely sure what you mean by "shows up in the index". You can fire the selected scene by midi mapping to the selected scene fire button that gets exposed on the master track when in MIDI mapping mode. Or use this:
    • Mar 14 2019 | 11:18 pm
      The problem with that is my MIDI controller maps to that button, but the type of signal it's sending won't trigger it for some reason. Each button on the controller is registered by ableton as "Pitchbend," so mapping it does nothing to button based mappings like that.
    • Mar 14 2019 | 11:59 pm
      Might be sending Program Change messages. You don't need to MIDI map though, you can take MIDI into the device directly and manipulate it that way.
    • Mar 15 2019 | 12:38 am
      I'm not sure I understand what you mean by that? Can you explain a little more? (I understand the program change part). Directly into which device, and how would you suggest manipulating it? I think I can edit the couple of patches I've been given to make it work, but curious to see what you mean if it's an easier solution.
    • Mar 16 2019 | 3:25 am
      Make sure the device is a max MIDI device, and input MIDI directly into the track > device from your controller, as if you were playing a software instrument. Using midiparse, you can get any type of MIDI data coming into the device and do whatever you want with it after that. Bypassing any quirks of Live's MIDI mapping implementation.