mpc program change problem on the new OS

Hi,

I use the MPC1000 primarily as a live sequencer in conjunction with other synths in a fairly big rig. The MPC has been working as the brains for the whole operation, doing drum patterns and sequences on external synths.

The whole operation has worked fairly well on previous OSs, but after updating to the new OS2.10, the program change - messages have stopped to transmit!

Has anyone had the same problem/found a solution to this problem?

I have the latest os and haven't got any problems with the program change messages , at least not if i send from mpc to my virus c synth.
Entering Program changes in step-edit and just using the "No." program both work .

I´ve got a mpc1000 and a virus c too.
And i have the same problem with program change messages. A put the N.in the step time but the mpc1000 dont change the program...

I tried it again and i'm sorry to say that everything works fine.
I have the Keyboard version of the virus C and have the latest os v6.5.

When i set a track to send midi to the virus , i can use the "NO.1" program to change the patches on the synth by just selecting the 1 in "NO.1" and changing the number.
And in step-edit , when i press insert and the select "Program Change" and then change the number it changes patches when i press play.
Are you sure you aren't using "Controll change" instead of "Program Change" ?

yeah i have.
at least when working with material made before the os update, then after the update, my sequences wouldnt send program changes!!

it turns out that the way the program changes are handled has all been altered slightly in os2.10.

i used to put the relevant program change number in each midi track of each seq in os 1.07........it worked well until i updated, and then my old sequences wouldnt change my external synth patches all of a sudden.

if i remember it right.....i think you need to get the seq that has prog changes in, make a note of the prog number in there, then set the 'inst:prg' for that track - to be the prg that's 2nd from the end when scrolling up through the prg's.......then there's one that relates to program changes only, set this to the required progchange number. then edit its 'send prog changes in this track' field to 'yes'.

should work, worked well for me since then.....but its a lot of retro-fitting previous work. search all my posts, and u will eventually spot the prog change problem stuff. good luck.