Exchange tips and tricks for the Akai MPC4000
User avatar
By DJ A-Sharp Thu Mar 04, 2010 8:14 pm
Can someone in the most simple terms explain what multis are? I've read the 4000 Reference Manual and user guide and don't quite get it. Is it just different saved effect settings for a particular program?

And what would be the use of the multis? Would it be like, ok you can use the same sounds of a program but you save different multis so that you can use them on different song genres for example?

Please break it down for a new 4000 user.

BTW.....THE MPC 4000 is the greatest MPC EVER. PERIOD!!!!!
Last edited by DJ A-Sharp on Sun Oct 09, 2011 1:23 pm, edited 1 time in total.
User avatar
By gertie Thu Mar 04, 2010 8:32 pm
as clint wrote before....

Put very simply, a MULTI is a group of programs which may be used in a particular project and loaded as a whole for immediate use.

A kick drum program
A snare program
A Hi-hat program
A bass program
A keyboard program
A sample program

If these six programs were loaded and used to create a song, you'd want to save them in a multi otherwise you may have issues later on when you come back to put in more work.

theres more info in this topic..

viewtopic.php?f=2&t=107733
User avatar
By DJ A-Sharp Thu Mar 04, 2010 10:04 pm
Thanks. Again....LOL
User avatar
By dabmeister Thu Mar 04, 2010 11:08 pm
Yeah, the 4k is def an amazing musical tool. There's so much that can be done with this joint. Congrads on your new ownership and maybe RT. 210 will be sounding off with them hot beats later this spring/summer. :)
User avatar
By DJ A-Sharp Fri Mar 05, 2010 12:11 am
Imma try
By Jay Quentin Tue Mar 16, 2010 1:10 am
Feel free to reach out to me and I'll show you the MPC Advantage... especially on the MPC 4000.

Professional Workflow, Production that breathes, advance real-time control, data management and polished sound before Pro Tools.

Or we can just talk shop.

Jay Quentin
917 442 5757

MPC Master Classes_Producer Development
1000 • 2000• 2000 XL• 2500• 3000 • 4000

Free Audition Kit [email protected]
User avatar
By rokuez Wed Mar 17, 2010 12:38 am
gertie wrote:as clint wrote before....

Put very simply, a MULTI is a group of programs which may be used in a particular project and loaded as a whole for immediate use.

A kick drum program
A snare program
A Hi-hat program
A bass program
A keyboard program
A sample program

If these six programs were loaded and used to create a song, you'd want to save them in a multi otherwise you may have issues later on when you come back to put in more work.

theres more info in this topic..

viewtopic.php?f=2&t=107733


thankyou thankyou
User avatar
By feline1 Thu Mar 18, 2010 5:17 pm
You can't "not" use multis -
even if you are only using one program, it still has to be inside a multi.

There's only one multi active and in use at a time (but you can have several loaded up in memory, waiting to be selected).

The Multi contains all the settings and routings for which Effects are applied, which audio outputs you are senind to, and which MIDI channels you are receiving on.

One way to think of a Multi is as the equivalent of a hardware mixer/patchbay,
and indeed that's basically what it looks like in Ak.Sys.
By digiman Wed Jun 29, 2011 8:39 am
gertie wrote:as clint wrote before....

Put very simply, a MULTI is a group of programs which may be used in a particular project and loaded as a whole for immediate use.

A kick drum program
A snare program
A Hi-hat program
A bass program
A keyboard program
A sample program

If these six programs were loaded and used to create a song, you'd want to save them in a multi otherwise you may have issues later on when you come back to put in more work.

theres more info in this topic..

viewtopic.php?f=2&t=107733


I'm thinking about trying a autoload setup like this. What i'd like to do is create different programs for each drum parts (snare, kiks, hihat, percussion, etc) just like mentioned above. Then, what I'd like to be able to do is then create a new program where I would assign sounds from each the the different programs to create a full drumkit. I could take a snare from the snare program and assign it to one of the pads in the new program and then take a kick from one of the other programs in memory and assign it a different pad in that same new kit. So, I could build kits from the different programs that are in memory. I guess the question i have is when you change the sound on a pad by scrolling through other sounds, are you limited to just the sounds in the existing program or can you somehow scroll through sounds from any program you have in memory when you assign sounds to pads. If you can do this, that would make my life a whole lot easier than i ever could have imagined with the 4000.
By mQueue Wed Jun 29, 2011 10:55 am
digiman wrote: I guess the question i have is when you change the sound on a pad by scrolling through other sounds, are you limited to just the sounds in the existing program or can you somehow scroll through sounds from any program you have in memory when you assign sounds to pads. If you can do this, that would make my life a whole lot easier than i ever could have imagined with the 4000.


When you scroll through samples in the Program screen where you're assigning samples to pads, any sample loaded into memory can be selected.
By digiman Wed Jun 29, 2011 2:27 pm
mQueue wrote:
digiman wrote: I guess the question i have is when you change the sound on a pad by scrolling through other sounds, are you limited to just the sounds in the existing program or can you somehow scroll through sounds from any program you have in memory when you assign sounds to pads. If you can do this, that would make my life a whole lot easier than i ever could have imagined with the 4000.


When you scroll through samples in the Program screen where you're assigning samples to pads, any sample loaded into memory can be selected.


Even if you want to assign a sound to the new program from a different program in memory than the one you're currently on?
By mQueue Wed Jun 29, 2011 7:18 pm
digiman wrote:Even if you want to assign a sound to the new program from a different program in memory than the one you're currently on?


yep...give it a shot
By digiman Tue Jul 05, 2011 5:48 pm
mQueue wrote:
digiman wrote:Even if you want to assign a sound to the new program from a different program in memory than the one you're currently on?


yep...give it a shot


Well dang, it sure does work! The only thing I regretted about getting rid of Maschine and picking up the 4000 was the ability to easy maneuver through sounds in my library and build kits very quickly. Initially, I didn't think the 4000 was capable of doing this. Now this REALLY changes the game. The 4000 was the best purchase I have ever made for my studio -PERIOD. I guess you can tell I'm hella amped about this, huh? :D

Thanks
User avatar
By DJ A-Sharp Sun Jul 17, 2011 2:10 am
@ Digiman...

So the Mashine is not like all the industry people make it out to be? Since you are coming from that direction to an MPC 4000 what is your thoughts? just curious....
By digiman Sun Oct 09, 2011 3:01 am
DJ A-Sharp wrote:@ Digiman...

So the Mashine is not like all the industry people make it out to be? Since you are coming from that direction to an MPC 4000 what is your thoughts? just curious....


FWIW, Maschine was "cool" for me. The workflow was amazing. Especially being able to drag and drop midi from Maschine directly to your DAW without having to track everything out. That was a HUGE plus. The downfall for me was basically in the sequencer. At first I thought it came very close to the feel of the MPC in terms of timing. However, after more than a few instances where even with the swing on I felt like I had to still going and nudge a hihat here or move a kick there to get the feel right. The straw that broke the camel's back was on one track I was working on I was trying to use the note repeat to create a 16th note hi hat track and the feel of the note repeat just couldn't capture the groove. To make a long story short, I ended up spending almost 4 hours just trying to get the swing and feel of the drums happening. After that happened, I just thought I'd experiement with the MPC again just for giggles, since I was over it at that point and had moved on to Maschine. We'll lo and behold, when I tried to re-sequence the same track I had spent 4 hours nudging kicks, snares, and hi hats around with on the Maschine, I got the PERFECT track in terms of timing/feel in about 60 secs on the MPC with just the standard 16th note quantization with a 50% swing. At that point I put maschine on the market and then picked up a 4000. After getting the 4000, I haven't looked back since. Getting used to the workflow in the MPC has been a challenge for me, coming from being able to do things like drag and drop and being able to do everything graphically . What I realized at the end of the day after really digging deep in the manual is that the MPC can do so much more in terms of functionality and creatively that even some of the most advanced DAW's ever could even dream of creatively.