Question about 3.5 and program changes

.

Elijah wrote:In MPC, setting automation always inserts an initial value at 1:1:0. This can be a bit annoying when using Program Change.

So what does this mean? Change that first one to whatever program I want to initially start with?

lordradish wrote:

Elijah wrote:In MPC, setting automation always inserts an initial value at 1:1:0. This can be a bit annoying when using Program Change.

So what does this mean? Change that first one to whatever program I want to initially start with?

You pray to the God of your choice that your synths or drum machines do not belong to the majority of gear actually reloading their patches every time they get a program change message.

If your gear belong to the majority of gear. You will most likely experience audio glitches when the patches reload. And if your patches utilize reverb and delay you will get abrupt resetting of these every program change.

I want to chime in here, because I have found with the new 3.XX firmware versions, the PrgCh function in trackview has changed for the worse.
With 2.XX you could set a channel and programnumber in the track and this change (midievent) was just sent one time in the beginning of the sequence. When it looped, it was not sent again. PERFECT!
This avoids those glitches of external gear (the internal can not change anyway) but enables you as well to do live performances with manual pattern changes, to move though a performance. Ever new Sequence/Patten could sent a program change ONE TIME, no matter how often it was looped then. Fatastic.
I can perform live music while deciding on the fly how long a seqence/pattern will run, until I move forward to the next.
Now, with 3.XX, when you set a programnumber, it is GLOBAL. Means when you change it in one sequence, it is changed as well in any sequence before and after. What?!? WHY?
This breaks my way to perform with the MPC as a sequencer for synth.
Like stated above in earlier comments, inserting a PrgCh as midi event in the grid/pianoroll would repeat with every loop of the sequence, which as well would break the seamless function of external synth. with every loop a hickup.
Excuse me, this is crap.
Yes, I could always go back to 2.15.1. I did. But now I can not use my recently aquired PluginFX, that sound so nice.
Result: I am not pleased and will not buy any new plugin stuff any more.
I will receive a Digitakt soon, let´s see ow this will work out for me instead. It´s more compact anyway.

EDIT: I can´t edit my post above... well I did not see the first page of this thread, where this has been talked about.
However, as far as I can see no one has mentioned that the PrgCh that you set for the current track (pre 3.xx versions) in view was just sent one time at the beginning of the sequence, and not repeated when the sequence loops.
This has been a very important feature.
And more than that, you could easily change that program while you might reprogram the synth and want to point to another program. Now you´d have to open the editor repeatedly and change the midievent in the grid.
Cumbersome. Makes no sense.