Ableton Live's "Random Midi Effect" as MaxMSP patch


    Jan 20 2021 | 7:49 pm
    Hey there! I am fairly new to Max, and I am currently trying to build a Sequencer with generative possibilities. I want to be able to add the functionality of Ableton Live's "Random Midi Effect" to each step of this sequencer. Ideally, I would like to have four "Random Midi Effect" per step. Does anybody has a patch of this Ableton Midi Effect? I attach a pic to refresh your memory. In my case, I will substitute both the "Choices" and "Scale" parameters for a simple Semitone/Pitch Control Parameter and I won't need the "Mode" section neither, so is fairly simple I guess.
    I've been spending some good hours on making this myself but due to my level I think I am overcomplicating everything. I am ending up with huge patches only to recreate the Random Effect function.

    • Jan 21 2021 | 4:53 am
      according to this: https://www.ableton.com/en/manual/live-midi-effect-reference/ 👇works a bit like this maybe?
    • Jan 21 2021 | 3:02 pm
      Hey thank you so much for the answer! Did you just make this? This is just perfect, although there is some type of problem with the probability knob, for some reason when placed at 100% it doesn't behave with 100% chance. Any idea on how to fix this?
    • Jan 21 2021 | 7:47 pm
      Did you just make this? This is just perfect, although there is some type of problem with the probability knob
      i thought i knew what you mean and posted some other fix, but now i realize i'm not sure... let me know what you hear(i no longer have Ableton on my comp, just going by text here 😅), and i can take a better look... i made it pretty quickly for you to start with, but now realize it could probably use more commenting... this is the basis of the whole patch(you could use [random 101] -> [<= ] to be more accurate in your patch but i doubt that's what you were running into):
      (it might be that you want the 100% to never allow the original to pass, in which case it would need to incorporate the offset later in the original patch better somehow...)
    • Jan 24 2021 | 4:18 pm
      thanks a lot again! yeah, this is exactly what I meant "(it might be that you want the 100% to never allow the original to pass, in which case it would need to incorporate the offset later in the original patch better somehow...)". I will try to fix it :)