AHEE

I made a max patch that routes "pgm chgs" from an iPad to Ableton to switch the presets on a synth.

But the behavior I'm seeing is perplexing.

In max, I am seeing the correct data come in and then out, but then in ableton it always recieves the previous pgm change.

I hit "preset 1" -nothing happens in ableton

I hit "preset 2" -ableton recieves "preset 1"

I hit "preset 3" -ableton recieves "preset 2"

I hit "preset 1" again -ableton recieves "preset 3"

Any ideas on how this could be happening?

I am using the "pgmin" & "pgmout" objects.

P.S. Due to complicated reasons I cannot send the messages directly from the iPad to Ableton. Also the patch is doing many other routes with Midi notes and Ctrl messages that are working perfectly in Ableton.

Hello y'all!
Really love the community support here!

I made a max patch that routes "pgm chgs" from an iPad to Ableton to switch the presets on a synth.
Simple enough.

But the behavior I'm seeing is perplexing.
In max, I am seeing the correct data come in and then out, but then in ableton it always recieves the previous pgm change.

I hit "preset 1" -nothing happens in ableton
I hit "preset 2" -ableton recieves "preset 1"
I hit "preset 3" -ableton recieves "preset 2"
I hit "preset 1" again -ableton recieves "preset 3"

program-change-to-ableton-error

definitely sounds like you've got some sequence of triggering wrong.

either post the patch (easy!) or attentively read the following chapter (enduring!) of the max tutorial, as it's the basis for everything going on within this software.

https://cycling74.com/docs/max5/tutorials/max-tut/basicchapter05.html

definitely sounds like you've got some sequence of triggering wrong.
either post the patch (easy!) or attentively read the following chapter (enduring!) of the max tutorial, as it's the basis for everything going on within this software.

https://cycling74.com/docs/max5/tutorials/max-tut/basicchapter05.html


Here is a simplified version of the patch, still behaves the same.

The Ctrl and Notes work just fine, but the pgm changes still behave like I said above.

Here is a simplified version of the patch, still behaves the same.
The Ctrl and Notes work just fine, but the pgm changes still behave like I said above.

Your patch works fine here for program change messages to Live. I'd recommend though to use trigger object for security reasons in your subpatches as the order of execution is crucial.

Have you tested it with a simple dummy M4L device using a pgmin to check what arrives ?

Hey y'all I have an update on the situation! Sorry it took so long, got busy with other gigs. OK so...

I tried rearranging the triggers as you Suggested Benny, but it seamed to act the same way either way I ordered it. Then I tried adding in a Max4Live object and it received Midi from the same BUS and Channel as my Synth and I watched as the CORRECT Midi info came into ableton.

SO my situation is I am sending PGM changes from TOUCH OSC into MAX/MSP then from MAX/MSP into ABLETON to switch PGM changes on two Sylenths, one Kontakt, and one Ableton Sampler.

I send "PgmChg 1" and I see it trigger correctly in MAX, then I set up a dummy M4L device in ABLETON and see "PgmChg 1" arrive while at the exact same time nothing is triggered in the Sylenth.

I send "PgmChg 2" and I see it trigger correctly in MAX, then I set up a dummy M4L device in ABLETON and see "PgmChg 2" arrive while at the exact same time I see "PgmChg 1" suddenly trigger in the Sylenth.

I send "PgmChg 3" and I see it trigger correctly in MAX, then I set up a dummy M4L device in ABLETON and see "PgmChg 3" arrive while at the exact same time I see "PgmChg 2" suddenly trigger in the Sylenth.

I wish y'all could see this happening, it's so surreal.

Any ideas? Suggestions? Thanks for the help so far.

Hey y'all I have an update on the situation!  Sorry it took so long, got busy with other gigs.  OK so...
I tried rearranging the triggers as you Suggested Benny, but it seamed to act the same way either way I ordered it.  Then I tried adding in a Max4Live object and it received Midi from the same BUS and Channel as my Synth and I watched as the CORRECT Midi info came into ableton.  

Any ideas? Suggestions?  Thanks for the help so far.

BTW, when I use this old outdated Windows Only program running under Crossover called "MidiOX", this delay goes away and works perfectly as I want it too. The whole point of this MAX Patch is so I don't have to use "MidiOX" as it's windows only and has no more support from the company that made it, so I can't share it with my friends. Thanks again.

BTW, when I use this old outdated Windows Only program running under Crossover called "MidiOX", this delay goes away and works perfectly as I want it too.  The whole point of this MAX Patch is so I don't have to use "MidiOX" as it's windows only and has no more support from the company that made it, so I can't share it with my friends.  Thanks again.
-AHEE


The displacement by 1 may be due to different PGM numbering of devices/synths (starting at 0 vs. starting at 1).

Program Change to Ableton Error!