Work around for program changes 3.4.1

Hi team,
Question about the program changes that are lost in 3.4.1 and if one has found a workaround for it , I hope, or is it what it is (unfortunately)

So to keep the example short,
Create sequence 1 with a drum program say tr707 sounds,
Copy the sequence to sequence 2 and replace the drum program with tr909 sounds

In the mpc2500 this works and the drums would change when changing the sequence,, this works with the 2.15 software as well,
But was really hoping to use the arranger mode in the 3.0 software for more overview of the sequence and having the luxury of even looping pieces of the sequence, and then eventually switch to sequence 2.

Thinking I am running into the limitation of the 3.0 software, but perhaps one has found a solution, or am I overseeing something?

Basically when building a set like this, all the mpc’s or their software have some kind of limitations, it’s never a 100% right of course.

Working on the mpc-one

Thnx in advance
Danny

One possible solution:

Create track 1 with 707 drumkit
Create track 2 with 909 drumkit
Switch between 1 et 2 by mute/unmute

A problem with that is crowding the sequence with tracks. A possible alleviation of that is to organize the tracks by bank (A, B, C, D), so that, at any point in the set, the relevant tracks are all on a single pad bank. Not perfect for the track swapping case though, because it would require mute -> swap bank -> unmute.

Hi Jean, thnx for your answer, but it isn’t quite the solution I was looking for. I would like to write an entire track , or most of the track in 1 sequence. And think that doing it like this would take up allot of space and error sensitive in live performance

A pair of Glasses wrote:Hi Jean, thnx for your answer, but it isn’t quite the solution I was looking for. I would like to write an entire track , or most of the track in 1 sequence. And think that doing it like this would take up allot of space and error sensitive in live performance

Having two tracks with the same part will not take up a significant amount of additional space. Midi data is compact by design. Even better, if you want to control one track from the other, that is send midi from one track to the other, then you save even that. Of course you can't mute the first track, you have to set its volume to zero (I think, that's what you'd have to do in 2.x but I know that mutes are different in 3.4).