MPC 3 -- Let's GO!!

dustyslices wrote:FxPansion is still part of inmusic so I don't get why they can't use that technology

I'm pretty certain FXPansion is no longer. BFD seems to be the only thing they kept. Cypher 2 and Strobe got bought by Roli, Angus the main guy from FXpansion is working with Image Line etc.

Yeah my bad, In music acquired BFD only, for some reason it stuck in the back of my head that Akai has acquired fxpansion as a whole but obviously its just a glitch in my bubble

Anyone else feel more comfortable doing mixing stuff in the box with the new UI and convenience features?

- Vertical faders
- Easily accessible sends with returns preloaded with Reverb and Delay
- Channel Strip as an default effect
- Easily turn automation on/off for a specific item

From my understanding the whole 1-track-1-program situation kind of interrupts how some did mixing on the MPC prior to the beta but as someone who didn't really go deep into mixing stuff prior to this, I'm liking things right now.

I'm getting increasingly less interested in the whole MPC+ Mixer workflow outside of the few inputs I use. Not going to be hasty but I'm seriously considering downsizing and just getting a small mixer for the I/O.

did the midi note map change one day?
Im using this list:
https://soundprogramming.net/file-forma ... equencies/

But the MPC v3 has completely different note numbers.

ontherun wrote:did the midi note map change one day?
Im using this list:
https://soundprogramming.net/file-forma ... equencies/

But the MPC v3 has completely different note numbers.

I think so. When I used the C1 custom mapping in MPC2 on my MIDI tracks routed to my other tracks with Program kit, it mapped exactly as the Program track itself from Pad A1-H16. Now in MPC3, the same custom C1 mapping routed to a Drum track (vs Programs) is way off, out of order from Pad A1-H16. I’m not sure if it’s a bug but if so i reported this to Akai’s bug reporting page.

Lex Luthor71 wrote:

ontherun wrote:did the midi note map change one day?
Im using this list:
https://soundprogramming.net/file-forma ... equencies/

But the MPC v3 has completely different note numbers.

I think so. When I used the C1 custom mapping in MPC2 on my MIDI tracks routed to my other tracks with Program kit, it mapped exactly as the Program track itself from Pad A1-H16. Now in MPC3, the same custom C1 mapping routed to a Drum track (vs Programs) is way off, out of order from Pad A1-H16. I’m not sure if it’s a bug but if so i reported this to Akai’s bug reporting page.

thanks, i always look for the error on my side.
When I go into the step sequencer, the notes are also different than on the main screen.

Can someone check if you use the stepequencer that the notes are on different pads than on the main screen?
I trigger a drum machine over midi and its baiscaly unusable.

ontherun wrote:did the midi note map change one day?
Im using this list:
https://soundprogramming.net/file-forma ... equencies/

But the MPC v3 has completely different note numbers.

The note mapping has not changed in the recent MPC2 and MPC3. (In an earlier version of MPC2, the classic MPC mapping starting from C#1 was changed to start from C1.) The MIDI note number for C1 can vary between manufacturers; in MPC, C1 corresponds to note number 36.

Even with MPC3, if you load a program created with a much older version, the mapping will start with C#1. This can be easily remapped.

Elijah wrote:

ontherun wrote:did the midi note map change one day?
Im using this list:
https://soundprogramming.net/file-forma ... equencies/

But the MPC v3 has completely different note numbers.

The note mapping has not changed in the recent MPC2 and MPC3. (In an earlier version of MPC2, the classic MPC mapping starting from C#1 was changed to start from C1.) The MIDI note number for C1 can vary between manufacturers; in MPC, C1 corresponds to note number 36.

Even with MPC3, if you load a program created with a much older version, the mapping will start with C#1. This can be easily remapped.

when I set a Pad to C1, that go to the midi monitor and press that pad it says C4 and the midi device receives a completely different Note number.
And why to blink other pads when I press C1?

When I assign a Note to PAd A1, than Pad A5 and finaly A9 the Pad A1 has no more note assigned.

Detailed, step by step recreation would help immensely, starting from the very beginning of the entire process. Video etc.

ontherun wrote:when I set a Pad to C1, that go to the midi monitor and press that pad it says C4 and the midi device receives a completely different Note number.
And why to blink other pads when I press C1?

ontherun wrote:when I set a Pad to C1, that go to the midi monitor and press that pad it says C4 and the midi device receives a completely different Note number.
And why to blink other pads when I press C1?

When using the CUSTOM feature in Pad Perform on the MPC3, the same issue occurred.

So these issues are relating to using a MIDI track with pad perform set to CUSTOM? So the custom mapping set is not behaving as configured?

Again, please try presenting this is a detailed, step-by-step way as it's really hard to decipher exactly what is going on.

MPC-Tutor wrote:Detailed, step by step recreation would help immensely, starting from the very beginning of the entire process. Video etc.

ontherun wrote:when I set a Pad to C1, that go to the midi monitor and press that pad it says C4 and the midi device receives a completely different Note number.
And why to blink other pads when I press C1?

hope that helps:
https://www.youtube.com/watch?v=O6gnNgNGKJc

You know where the midi notes are displayed.
I always press the same pad, only once when the r8m is shown i press A2, to show it receives something.

The CUSTOM mode in Pad Perform seems to be broken. Try creating a dummy drum track and MIDI track, editing the note map of the drum track, and setting its Send-To to the MIDI track.

Blue Haze wrote:

herbie wrote:If I’m in arrange view and looking in grid mode and have the view zoomed in and want to overdub some new parts on a plugin track, as soon as I press overdub the view zooms out so all the events are tiny - this is frustrating as often I’m zoomed in so I can see events clearly as cues before I add my overdub.
Anyone else found this and is there a fix?
Is there a link to send reports to Akai as this didn’t happen prior to this 3 beta.
Thanks

I always loop the area I want to overdub in arranger setting up the regions that way the zoom stays the same. I hope it helps. Loop area first expand the zoom, and then overdub.

Just seen this - thanks! I’ll give it a try now