Hello all!

I'm new to PureData so please bare with me, as I've almost certainly made some (many) rookie mistakes, but hopefully people here can help

Basically, I'm trying to use PureData as a MIDI click track controller for MainStage - so when I hit play in MainStage, it will count the bars and at set intervals, send a relevant patch change (which may then also trigger tempo changes) Personally I'm amazed it's not a feature built into MainStage, but ah well.

The first issue I seem to be having is when trying to send a second change after a first. My current setup (below) is to check if the bar is X, and if so send Y program change - however when the second check is confirmed, MainStage starts to rapidly flicker between the two patches, and the only way to stop it doing that is to stop my playback, play again for about 2 bars, then stop again.

So my two-fold question is how do I stop this flickering effect (IE, make sure it just sends the program change once and then stops sending it), and is there a better approach than my current layout? (I'm pretty sure there will be :P)

Current setup is based off of help I got on the Logic/MainStage forum suggesting this software, with tweaks to try and allow for multiple patch changes in one run

I've also tried using a single shared midiformat/midiout to no avail

Also for bonus points (for people familiar with MainStage) - is there a way for MainStage to tell PureData what the current patch is, so I can just write some clever stuff and have one script for all songs, instead of having to write a script per song and then load/close them manually?

@Flenix Hello, I am no midi expert, but you mentioned changing the tempo with the program change message. Does Program 0 set some crazy tempo (1000's bpm) and Program 1 not set a tempo at all? That would set the midi clock running fast enough for your patch to "flicker".
Your patch looks ok to me. You could replace [prepend 1] with [1(....... as the program change is just an integer, but that is all......
David.

The program changes are just program changes, nothing more - MainStage interprets those and changes to another patch, and the patch will change the tempo itself (which it also does if you just manually switch)

I think the problem I'm having is once it starts to send the program change it just keeps sending it over and over again.
How would I make it "stop" sending? I looked in the other recent thread to stop things, and they ended up just sending 0, but as 0 is a valid PC message I can't do that.

@Flenix Hello again. Try putting a [print] object connected to the outputs of [prepend 0] and [prepend 1] and look at what it prints to the terminal. I am not convinced. Your patch only sends a program change once, when the correct bar number arrives. And as you are counting beats the counted bar number cannot "come around" again until the midi clock is stopped and restarted, Maybe there is some kind of midi feedback loop in your system.
Connect the [print] object to other object outputs in your patch to see what could be going on....
and if you have a midi analyser app then try to see what messages Mainstage is sending and receiving....
David.