Post your views and questions about the Akai MPC2500

By zs941 Sun Nov 06, 2005 10:28 pm
FEATURE:

It would be really cool if RECORD mode would show you an actual decibel level (in numeric form) in addition to the rudimentary level bars.

Does anybody know what each block in the level corresponds to in dB?

By tse83 Mon Nov 07, 2005 12:13 am
Bug:

strange strange midi in port issues when using external midi controller: I've got an m-audio midi controller (keystation-61) which i know for a certain fact works perfectly fine but for some reason, when plugged into midi in 2, it goes apesh*t. :shock: :shock: it works fine when plugged into midi in 1. I know both midi ports are working (midi in 2 responded fine with midi clock for tracking into logic) and its definitely not the cables cuz i swapped it around a few times with spare midi cables.

probably an OS issue.


the earlier issue i had with the pads is probably something that is specific to my unit and is not really a 'bug' per se.
User avatar

By jahrome Mon Nov 07, 2005 12:36 am
tse83 wrote:

Bug:

strange strange midi in port issues when using external midi controller: I've got an m-audio midi controller (keystation-61) which i know for a certain fact works perfectly fine but for some reason, when plugged into midi in 2, it goes apesh*t. it works fine when plugged into midi in 1. I know both midi ports are working (midi in 2 responded fine with midi clock for tracking into logic) and its definitely not the cables cuz i swapped it around a few times with spare midi cables.

probably an OS issue.


the earlier issue i had with the pads is probably something that is specific to my unit and is not really a 'bug' per se.


You are not be very specific with your problem. 'apesh*t'???

I have a Roland A-90 keyboard controller. I have it connected to both MIDI INPUTs of the MPC 2500. SO far, no problems with the ports.

If you can be specific on the problem you are having, it can help fellow MPC 2500 users trouble shoot your problem. I also have the MPC sync with my computer (Nuendo) and it syncs fine. But when I stop Nuendo..the MPC 2500 will stop....then play for a second..and then stop again.

By zs941 Mon Nov 07, 2005 1:43 am
Like Jahrome I'm not quite sure what apesh*t means but I'll take a stab here:

Do you have soft-through turned on in any configuration?
User avatar

By jahrome Mon Nov 07, 2005 1:55 am
I do have to add that every once in awhile, the notes of my Fantom XR connected to the MPC get stuck. And of this OS, there is no ALL NOTE OFF function. I have to go to the Fantom XR and change programs which will stop the stuck note.

By tse83 Tue Nov 08, 2005 2:22 pm
my bad..i'll try to be more specific.

i had the minimoog voyager rack (my one and only sound module) hooked up to a midi out port (B) and i had the keystation (the midi keyboard) hooked up to midi in 2 (midi in 1 was working fine and i was using that to sync to logic 7 to track my beats).

the keystation however, would 'drop' notes every few presses...so say i was constantly playing the same key on the keystation over and over, every few notes, there would be a few dropped notes.


This never happened on my 1000 and the cable setup was the exact same (the midi setup is also identical in the >MIDI menu)
User avatar

By jahrome Wed Nov 09, 2005 12:41 am
tse83,

You can possibly have a bad MIDI port. I don't believe it is software related..especially since your MIDI 1 input is working fine.

By zs941 Wed Nov 09, 2005 4:41 am
you're using logic 7 so you must be using a mac. you should get a utility called MIDI Monitor. you should be able to find it at http://www.versiontracker.com. It's a free program and a total life saver when trying to diagnose MIDI problems. you'll need to chain it together like this to sniff the midi data coming from the mpc.

keyboard -> mpc midi in B
mpc midi out -> computer midi interface
computer midi interface -> moog (nice, btw!)

when you run MIDI Monitor you should see all of the MIDI Data sent over the wire as it happens. then you can see if the MPC is correctly passing the notes that are missing and will help you narrow it down. also, try a bunch of configurations (including cable swaps) to make sure you've really isolated the problem piece.