MPC LIKE PROGRAM CHANGES IN ABLETON


    Jul 11 2018 | 12:23 pm
    Hello ! I 'd like to be able to send Program Changes just by highlighting a Scene Name. (without triggering any clip). Ex: I select the scene 1. Scene 1 sends PC 3 (channel 4) to an external synth and PC 5 (channel 10) to another one. My synths are monitoring the good preset. Then I hit play on Ableton. It works well on MPC, and it's very useful to send those kind of messages without starting any clock.....
    I've tried many ways to achieve this (ClyphX, midi macros) but I failed everytime, and obviously the best way is to program a patch in Max. (or maybe a User Action in python code!) :/ The big problem is : I'm new to this software and I don't understand anything !!!! If someone can help me ... ! Thanks !!!!!!
    Best
    Raphael

    • Jul 11 2018 | 10:06 pm
      It can be done with M4L (midi effect device). Here is a basic patch that gives you the name of the selected scene.
    • Jul 12 2018 | 5:54 pm
      Thanks BROC !!
      I've tried to paste from clipboard into a new Max project but how can I integrate it to Live? The shortcut to export it as a Max4Live device is not available ... :/
    • Jul 12 2018 | 6:17 pm
      In Live open an empty Max MIDI effect and paste the patch.
    • Jul 18 2018 | 3:47 pm
      Hello Broc, I've tried to paste it in a max midi effect but nothing happens.... :S I saw the patch "fire selected clip" in the Live abstractions menu and it gave me an idea : why not triggering only a few dummy clips to send the PC just by highlighting them: but there's another problem... Is there a script "select=bang" or "highlight=play" or that kind of message ? I really want to avoid the manual trigger...
      Thanks ! btw, I keep practicing on Max :S
      Raphael
    • Jul 18 2018 | 7:06 pm
      Well, my patch was only the main part of a solution. But here is an example of the completed patch.
    • Jul 20 2018 | 3:32 pm
      DAMN YOU JUST SAVED MY LIFE
      thank you very much Broc !!!!!!!!!
      (by the way good tutorial to understand how it works)
    • Jul 24 2018 | 1:08 pm
      I tried to make a blend of the abstraction "fire selected clip" and your patch in order to get the clip name (depending of the scene) and convert it into a program change message but I cannot manage to make it work :/
      so sorry to bother you...
    • Jul 24 2018 | 2:36 pm
      I think you need to remove 'view' from the path message.
    • Jul 24 2018 | 2:43 pm
      Thx! Works ! I already tried without the "view" in the past but I actually figured out that it needs a button to trigger the patch (i guess to get access to the lists). Is there a function to automatically get the access?
    • Jul 24 2018 | 2:49 pm
      I mean just by selecting my scene trigger the patch ? (it works well if I assign two buttons : one with the same mapping than my shortcut "next scene" and the second with the "previous scene" mapping but it's quite messy).
    • Jul 24 2018 | 3:57 pm
      Look at my previous patch. It triggers just by selecting the scene. You could do something similar for selecting the track and use both in combination.
      What exactly is the ideal intended usage and behaviour?
    • Jul 25 2018 | 8:30 pm
      I know it's very messy (ahah) but I finally made this patch and it works perfectly (the way I wish) except when there's a folded group track on the left of each track there's this device put it on. (even when I patch "live.path" in "follows path" and not "follows bject") I don't understand why (maybe an ID problem) but I can't find a solution. When I unfold the group track it works then...
    • Jul 25 2018 | 10:40 pm
      I'm glad it basically works for you. The group track problem may happen because the visible_tracks index changes if a group on the left is folded or unfolded. Not sure how to solve except replacing visible_tracks by tracks.