Question about 3.5 and program changes

Hello, friends.

When they went to ver 3, I ended up rolling back to two, due to the inability to put program changes that actually worked on a track.

What's the status of program changes with 3.5? Are they easy or complicated? I know that I heard something about using list view, but even then, that had problems. I saw in the manual, but it seems like it just addresses the initial program change. I need to be able to change programs/banks a few times over the course of the sequence.

The prog change issue is the only thing keeping me from upgrading at this point, so I'm trying to find out what it's currently like, as well as how easy/difficult it is. Thanks in advance.

I've sent in feedback to Akai about hoping for program changes per sequence (and also per track in each sequence). The current single program change per track is not cutting it for me.

I've also sent a request for being able to pass through true program change messages coming in via midi. This way I could bypass the limitations regarding MPC 3 and handle the program changes from elsewhere...

Wow, so I guess I won't be upgrading until this is addressed. I simply can't use this for my performances if this is how it is. I can't believe they haven't addressed this, it's such a basic and important function of a sequencer. Thanks.

On MPC 3, you can easily record program changes by using List View > Insert > MIDI Automation > Program Change.

Is it working as it's supposed to, now? When I originally tried it,bit wasn't working properly... Something about the values not going in correctly and it not making the change. Also couldn't do bank changes, if I remember correctly. Have you been able to change the program on a track more than once and can you change banks?

MSB is assigned using CC#0, and LSB is assigned using CC#32.
In versions prior to MPC 3.5, program change values were displayed as 0–100%, but this has been correctly updated to show 0–127 in the current version.

Elijah wrote:MSB is assigned using CC#0, and LSB is assigned using CC#32.
In versions prior to MPC 3.5, program change values were displayed as 0–100%, but this has been correctly updated to show 0–127 in the current version.

Ah, thanks for pointing that out, I'll update the MPC Bible to reflect that bug fix.

Elijah wrote:MSB is assigned using CC#0, and LSB is assigned using CC#32.
In versions prior to MPC 3.5, program change values were displayed as 0–100%, but this has been correctly updated to show 0–127 in the current version.

Good to know....

So before I make the shift, let me make sure I'm understanding this correctly. I'd go into list view for the track, where I'd insert a program change, and if necessary, an MSB and/or LSB? Do they come up in the menu as those things or do I just need to know it's 0 and 32?

Thanks again.

MPC-Tutor wrote:

Elijah wrote:MSB is assigned using CC#0, and LSB is assigned using CC#32.
In versions prior to MPC 3.5, program change values were displayed as 0–100%, but this has been correctly updated to show 0–127 in the current version.

Ah, thanks for pointing that out, I'll update the MPC Bible to reflect that bug fix.

I've been holding off on the 3.5 guide (still have the 2.0). Do you explain this process in the new version? Thanks.

lordradish wrote:

Elijah wrote:MSB is assigned using CC#0, and LSB is assigned using CC#32.
In versions prior to MPC 3.5, program change values were displayed as 0–100%, but this has been correctly updated to show 0–127 in the current version.

Good to know....

So before I make the shift, let me make sure I'm understanding this correctly. I'd go into list view for the track, where I'd insert a program change, and if necessary, an MSB and/or LSB? Do they come up in the menu as those things or do I just need to know it's 0 and 32?

Thanks again.

That's correct. When inserting them in the list, MSB and LSB will appear as “Bank Sel MSB” and “Bank Sel LSB.”

lordradish wrote:[). Do you explain this process in the new version? Thanks.

Yes, it’s not complicated though, it’s just INSERT > MIDI automation in list edit

lordradish wrote:

Elijah wrote:MSB is assigned using CC#0, and LSB is assigned using CC#32.
In versions prior to MPC 3.5, program change values were displayed as 0–100%, but this has been correctly updated to show 0–127 in the current version.

Good to know....

So before I make the shift, let me make sure I'm understanding this correctly. I'd go into list view for the track, where I'd insert a program change, and if necessary, an MSB and/or LSB? Do they come up in the menu as those things or do I just need to know it's 0 and 32?

Thanks again.

No one seems to mention that you cannot add a single program change in the list view. For some reason AKAI decided to always add a second program change for you in the beginning of your list. This cannot be deleted. Yes, you read that correctly...

Please someone tell me that this is not true. It surely cannot be true..!? I'm so confused why on earth this "feature" should ever exists.

I just tested it with one of my synths and get wonderful glitches in the audio because even though setting the undeletable program change to the same number as the one I actually insert where I want it. The patch is reloaded every singel cycle.

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

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.

Program change aside, this has long annoyed me. Could anyone here please explain why MPC does that ? Sure, initial values can be useful - but then I can insert them... Or at least let me delete them !

I had so much issues trying to cope with the RAM !

Is it possible to change the preset of a plugin of the MPC, at the beginning of a pattern ?

For exemple, i load a MiniD bass in plugin 1 and a FABRIC in plugin 2, and i set the preset at the beginning of each song, to be able to have differents sounds for each song (=Pattern)

It would be a solution for me, to use less plugin, and change the preset at the beginning of songs.