Share your knowledge on these two classic MPCs
User avatar
By marrelarre Fri Sep 28, 2012 8:52 pm
Ok heres the problem, i just copped a MPC60 mk1, hella nice condition.

But i turns out that some pads are triggering the one next to em.

For example: if i hit pad 2, aka note 36, it triggers, besides 36 of course - 45, 42 and sometimes 46. not all at the same time but always something else.

This is on ALL the pads, are the sensors busted? Cus he said, and i can tell, that the guy before him changed all the pads and buttons, theyre mint.

Should I open it up and see if he messed up putting in the new sensorso r get some new ones?
User avatar
By ArKyve-31 Fri Sep 28, 2012 10:28 pm
yeah check the sensors sheet, maybe gently wipe it off, make sure the wire harness is properly attached,also initialize the parameters just to be sure the same midi note numbers aren't assigned to several pads
User avatar
By marrelarre Fri Sep 28, 2012 10:36 pm
I opened her up and it seems legit, i mean it wasnt a new set of sensors or anything, and it was kinda messy around them but the sensors themselves were clean (cleaned em some more).

Double-checked all the wires, seems ok.

Still having the problem tho.

dont think parameters is the problem, if i go to program and hit pad 2 it says note 36A02, and switches to saying 42A03, so it seems like the sensors must be busted right?
User avatar
By marrelarre Fri Sep 28, 2012 11:59 pm
That really sucks.. and its not like i wanna return it (traded it for a 2kxl + cash), i wanna keep it!
Im hella broke so ill guess ill have to wait for 25th of october and use it as is at the moment, try to figure out what buttons dont go together ;)

Thanks for imput!
By fooddude Sat Sep 29, 2012 2:57 pm
Isn't this a common problem with the 60? ...not dirty sensors..but "ghosting"?

Also, a nice little easy and quick secret fix to vintage synths and mpcs is a simple "reseating" of all the plugs- simply unplugging and replugging them in, maybe even 2 or 3 times... doing this scrapes/cleans off a bit of 30 year old corrosion/gunk on the pins/plugs/connections and results in a nicer more solid connection. It usually fixes most problems and will run healthier. It worked on 3 of my synths and also my otari r2r and either fixed them or made them run much better.
By Clint Sat Sep 29, 2012 3:10 pm
In my experience 'ghosting' or unintentional double triggers will sometimes occur on a perfectly good MPC60. Quirks of the machines software/ hardware IMHO. Possibly a bug.
User avatar
By ArKyve-31 Sat Sep 29, 2012 3:46 pm
clint246clint wrote:In my experience 'ghosting' or unintentional double triggers will sometimes occur on a perfectly good MPC60. Quirks of the machines software/ hardware IMHO. Possibly a bug.



I'm a fortunate soul, never had any issue like that thankfully.
By fobedafied Sun Sep 30, 2012 7:38 am
my pads on my second hand 60II have always been hella unresponsive... :x

someone in a thread on here said something about the problem may be with what velocity is controlling or something like that... i cant really remember, but i think it was a parameter setting where velocity could control other things besides amplitude... its been a while and im hella rusty on that OS...


been meaning to check that out on my 60, and open her up and check out the sensors if that doesnt help...

soon... :nod:
User avatar
By mr_debauch Sun Sep 30, 2012 9:57 am
I co-sign re-seating all cables and connectors.

ALSO, I do suggest resetting all params ... the 60 sometimes can store data on battery (unlike the 2000xl) that remains when powered off and back on again.

Last but not least... when you assign a unique sound to every possible pad (including the medium highhat, and open highhat... and a sound on everything in bank 2) does it trigger the same neighbouring pads when in bank 2? if it's a sensor problem then it will also do it the same way in bank 2. if not, then it could be a bug or error... or it could be a short on the midi board or something... who knows.
User avatar
By vinyl_junkie_1620 Sun Sep 30, 2012 11:20 am
mr_debauch wrote:I
ALSO, I do suggest resetting all params ... the 60 sometimes can store data on battery (unlike the 2000xl) that remains when powered off and back on again.


That always used to annoy the hell out of me! Turn it off and when you turn it back on all settings are the same down to the last quantization setting and how many bars you had used on your prev sequence.

The Akai VX-600 was the strangest, it had NO patch memory because it remembered everything!
So if you tweaked a patch it would stay like that.. Want to go back to how it was? Tough luck! lol

The ghosting thing on the MPC also to me sounds like a totally different thing, I had it on the mk1 60 I borrowed.
It would sometimes do it, not all the time.
Can't remember exactly what it did, but it was like a very quiet distorted digital sounding echo of other sounds when you pressed another pad.
By fooddude Sun Sep 30, 2012 4:49 pm
Ghosting just makes the mpc sound more "analog".. hehe ;)

As for the params, I know what ya mean.. easy fix is to just never change nor replace the 30yo battery, or just unsolder it off and leave it empty/battery-less. I leave mine battery-less, mostly because I am lazy or too cheap to get a new one; but now that people mention that the saved params being annoying and wanting to reset, I will just leave it battery-less for good..it's nice to always have the 60 freshly reset at every start up. Battery-less = a cleaner running mpc60.

When ya think about it, a battery is pointless anyways- since it only stores params (which you'd have set-up differently per project anyways; and also can save to disk per project too) and also midi-channel names (which isn't a problem anyways to just leave blank, since you'd be most likely to have memorized which of your instruments are on what channel/midi-out)

I remember even forat told me the above regarding the battery, for those same reasons too.
User avatar
By marrelarre Sun Sep 30, 2012 7:59 pm
To my understanding ghost in the machine just triggers sounds untentionally and very damp and low in background, hence the name.
My machine THINKS i press pad 2 AND 5 6 7 (just an example), even says so if i go to program, it says first A02 then A03 instantly afterwards, so i dont think its the ghost-bug. Its also the same if i go to bank B,C or D, and the same buttons.
So I think sensors is the way to go, right?
And if that doesnt work ima call the buyer up and tell him i want my shit back, haha.

Ive resetted all the parameters.
and the plug part ima try when i get my new sensors, considering im gonna be inside it anyways.
User avatar
By mr_debauch Mon Oct 01, 2012 12:27 am
marrelarre wrote:To my understanding ghost in the machine just triggers sounds untentionally and very damp and low in background, hence the name.
My machine THINKS i press pad 2 AND 5 6 7 (just an example), even says so if i go to program, it says first A02 then A03 instantly afterwards, so i dont think its the ghost-bug. Its also the same if i go to bank B,C or D, and the same buttons.
So I think sensors is the way to go, right?
And if that doesnt work ima call the buyer up and tell him i want my shit back, haha.

Ive resetted all the parameters.
and the plug part ima try when i get my new sensors, considering im gonna be inside it anyways.


yes so it might be the sensor sheet... it might be badly connected, the connection could be dirty... etc. I would try taking it off and cleaning the connectors and reseating them before trying to buy a new expensive piece of kit... I still have original mpc60 sensors that work great!