Technical questions for the MPC2000xl and the MPC2000
By 2Serious Fri Feb 25, 2005 5:29 am
Im buying an MPC2000xl and i know which sound modules I want, its about 4 of them I'm buying. I've already bought the mixer, I just have a question regarding them. How would I connect all of them to my mpc 2000xl so that I can play them when i choose which one I want to play? I mean, I saw the newbie tutorial vid and classic had one motif rack, and he had it going into the midi out of the mpc. but I have 5 modules, and it doesn't seem like enough outputs. Thanks to anyone who can help.

Btw I have a 16 channel mixer.

By 2Serious Fri Feb 25, 2005 10:48 pm
Bringin this up.
User avatar

By M.ic P.ro C.rusher Fri Feb 25, 2005 11:50 pm
I was always under the impression that you could only hook up two MIDI devices to the MPC2000xl seeing as there are only 2 MIDI outputs and 2 MIDI inputs.

Peace1
User avatar

By saintjoe Sat Feb 26, 2005 2:55 am
yo bro, you'll be fine if you get a midi out box/patchbay, has multiple ins/outs to run many midi devices

or you can do it ol skool and run the midi through from two or three of the modules to the other modules, then you'll have to go through the intricate midi channel assinging process so you don't trigger the wrong module, but hey it's possible and probably not too too hard :wink:

if you got the loot get a midi out box/patchpay

By nanoloop Sat Feb 26, 2005 4:15 am
the mpc only outputs 32 midi channels. You can use midi through to get all the module's hooked up. but you will still only be able to playback 32 parts. which is pushing it if all of those modules are 16part multitimbral. i guess you could get a midi interface for pc and slave a software sequencer to drive the remaining. modules. or get the oldschool midi patchbay like mentioned above. that way you can easily comfigure your midi for each different application.

By 2Serious Sat Feb 26, 2005 4:32 am
Thanks, is this what you guys are talking about by midi out box/patchbay?

http://www.musiciansfriend.com/srs7/g=h ... id/702514/

So basically, this is the one thing connected directly to my MPC, and all of the sound modules are directly connected to this?

By mpc3000 Sat Feb 26, 2005 8:44 pm
Getting a midi router/patcher for the outputs of an MPC is pretty much overkill and will end up being more complicated that chaining them together.

Per the midi spec you can chain 5 midi devices using the thru ports. So, in effect the person that asked the question could drive all modules off a single MPC output port. I have driven 14 devices without problem on the two outputs of the MPC.

"then you'll have to go through the intricate midi channel assinging process so you don't trigger the wrong module"

You would have to do the same for the midi router/patcher so I do not understand what is meant with this.

As far as many of the device being multi-timbral and potentially running out of the available 32 parts, a midi router/patcher still does not help with this. You are still going to be limited to 32 channels no matter.

There are very few instances in which there is a legitimate need for a midi router patchbay:
1) Some devices may only have a OMNI mode and would respond to every midi event no matter the channel so you need something that filters per port.
2) You actually have more than 10 midi devices and want to connect them all. Ten is a lot unless you are scoring an entire orchestra.
3) You are anal about timing. There is the possibility of introducing a slight delay for midi event as they pass through each relaying thru port. While this has been designed as part of themidi spec and should be inaudible, it is easily circumvented by placing higher priority modules closer to the MPC. Stuff that products pads, strings, and slower brass is relegated to the end of the chain. I really have never had a problem but some feel more comfortable working this way. The HUGE drawback in switching from chaining to a patcher/router is even though that every device will theoretically receive midi data at the same time, all would get it later than if they were directly connected to the MPC. In other words, now that the midi data has to go through a new device, it gets processed, filtered and routed which takes time. More time than if that device was connected directly to the MPC itself.

Again, there are legitmate uses for midi patchers, I am not convinced that the poster really *needs" one at this time.

By 2Serious Sat Feb 26, 2005 11:29 pm
^^^Cool thanks, so what do you recommend I do?

Because i have these 5 rack modules, and I want to run them from the MPC outs, but what do you use to control them while keeping it as simple as possible, if at all?
User avatar

By stryke Mon Feb 28, 2005 3:09 am
DAisy chain 'em bro.Out to in,out to in........into the mpc.

By 2Serious Mon Feb 28, 2005 6:34 am
But there are only two midi outs on the MPC...and I have 5 rackmounts, how do I hook them all up????

By mpc3000 Mon Feb 28, 2005 4:45 pm
" I have 5 rackmounts, how do I hook them all up"

Hmm, I would suspect out of 5 manuals at least one of them shows you.

The following from my previous post offers a really, really big hint:
"Per the midi spec you can chain 5 midi devices using the thru ports"
User avatar

By PhatCaprice Mon Feb 28, 2005 5:20 pm
I've been interested in this too. Assuming everything is hooked up correctly, how in the MPC would you tell it to trigger a certain patch from module #4?

ex:

I want track 1 on the MPC to play patch #1 on module #4. How would you tell the MPC to use module #4 utilizing the Thru ports? Because the MPC only has outs A(1-16) & B(1-16), controlling two devices directly. Do you have to configure module #1 to goto #4?? That's where it's confusing, for me anyway.

Daisy chaining the devices I understand, but how do you control them down the line from the MPC?

By 2Serious Mon Feb 28, 2005 10:57 pm
^^^Exactly what Im curious about.
User avatar

By stryke Mon Feb 28, 2005 11:58 pm
You go out of one mod into the other,out to in,out to in.....Into the mpc.As far as how to select which one to use has to be determined within the mod.I don't own any mods yet but i'm sure there's somethin' internally you can turn off so it won't detect/produce sound.