KEYGROUPS & MIDI CONTROLLERS MPC LIVE2 (3.4.0.92 beta)

THX FOR THE EXPERT ADVICE!!!
NEWBIE HERE...

So I have been toying around with this MPC Live 2 for a few hours. I can't figure out how the key groups are set up in the new MPC 3 beta. When I add a key group track and then try to assign a sample/sound from the pool I can't drag a sound to a pad.

How do I assign a sound to the key group if I can't add it to a pad? The screen only shows empty pads with MIdi #'s and notes like (C-2, C#-2, D-2, Eb-2 etc.) I cannot assign any sounds in the sample pool to a key group.

My end goal is to assign bass sounds from the sample pool to a key group so that I can play them across the pads or a MIDI keyboard chromatically. Let me know if you need photos or more info.

I DON'T GET IT... PLEASE HELP!!! Thanks guys.

No different to mpc2. So you just LOAD TO POOL from the browser then assign via TRACK EDIT

The Sample Assign tab in the browser cannot be used for keygroups. You can assign samples from the Samples tab in the keygroup edit screen.

Having to load a WAV to project pool first feels like Akai don't WANT you to use keygroups.

Thanks for the speedy response. Keygroup edit screen? How would I navigate to that? I am not familiar.

HouseWithoutMouse wrote:Having to load a WAV to project pool first feels like Akai don't WANT you to use keygroups.

Very true statement.

beatmenace101 wrote:Thanks for the speedy response. Keygroup edit screen? How would I navigate to that? I am not familiar.

MENU > Track Edit

After loading the sample into the keygroup, double-tapping the waveform on the main screen opens the track edit screen.

By the way, it's not very user-friendly that pressing the Browse button on an empty keygroup in the main screen and selecting a sample doesn't load it into the keygroup.

Wow. Yes, thats insanely silly of Akai. So the only way to add a sound to the key group is through the sample sample edit screen.

Why do they allow you to create one from the track menu when theres absolutely nothing you can do with it?Thats crazy!!!!

I mean, Akai's current workflow is full of these weird ass dead-ends, so I guess it shouldn't be *too* surprising that it carries over to MPC3. I guess I'm just used to seeing them hang around at this point. My advice: don't get too hung up on it. It's annoying, but there's not much anyone can do.