MPC60 II Pads prob ?

OK, I thought about the problem a little more thoroughly and I would suspect the memory. The fact that offending sounds still trigger when they are deleted removes the possibility of a pad problem.

I no longer have the 60 in question in my possesion so I can't troubleshoot for you. I have a question though; do you notice it happening when you use more sampling time, ie the full 26 seconds? Could it be happening during "compacting memory"? It would seem the ghost sounds are indeed artifacts left in the memory somehow.

This one puzzled me to no end too. Sorry I can't be of more help!

^^that could be? I used to get this with my 60 and is one of the reasons why I went to the 3000...

I would often use most of the 60's memory, and did the sound compacting too

Cheers for the input people.
I've been converting sounds to stereo in every project this has happened. I have taken out the extra memory and it still does it, so it not the memory upgrade, it could be the 3.10 os stereo thing that's doing it ?
I'll see if I can duplicate the problem in project with no stereo samples

Thanks again
Toe

Nope, I NEVER use stereo sounds. Can't be just that. Using stereo sounds is a good way to use up more memory though.

A thought, although you removed the memory, you reloaded the problem sounds. Still wondering if the samples could be corrupted after compacting? It would seem to me that powering off the machine, thus dumping the memory, and reloading the samples would rule out a memory problem. Load the problem samples onto someone elses machine and see what happens. Email->mpc editor might be the move on this one.

Is this an OS problem??

If it were, I would assume that lots more people have had this problem.

I'm gonna keep thinking about this, if anybody has any additional info, please post it up, no matter how trivial.

I gave up on some fresh beats over this one, and I don't want that to happen to anybody else!

Ok so here's an update on this prob for anyone else thats looking round.

I called panic music here in the UK, I've used them before they seem v good. I explained the issue and he told me straight up it was almost 100% the dsp ? I think he said dsp, anyway he said its game over as the don't make that part any more.

I'm a bit gutted as I was planing on selling it on. You probably wouldn't notice the problem if you gave it a quick test, but I aint evil enuff to do that to someone on ebay.

Bit of a shitter, but hey, wat ya gonna do

FYI, There's a seller on eBay Germany that has a replacement board for sale. They say it's working and tested. Search under item number 330330774451.

That tech didn't necessarily know his MPC stuff. Yeah, they don't make all of the parts anymore, but most of this stuff can be fixed. That being said, I don't think that's the definitive answer on this problem.

From my experience, for the $0.02 that it is worth.

It is likely NOT the DSP ( LSI ) at fault where this problem is concerned.

More a sound memory allocation management or DSP ( LSI ) control bug/software oversight in the MPC60 3.XX OS.

The problem then manifests as an apparent DSP ( LSI ) fault.

Have seen this on a few machines. MK1's, MK2's.

Have confirmed it with other users on this list too.

So don't think your MPC60 is beyond help yet.

Can one of you folk with the suspect sounds send me an example of the faulting PGM/APS/SND files for analysis.

Loading them up here in my lab will be a good way to check things out in a way that is beyond most repair technicians.

An exact list of the steps that will guarantee failure each time will be of use in the analysis too.

Rohan.

mpc3000le wrote:From my experience, for the $0.02 that it is worth.

It is likely NOT the DSP ( LSI ) at fault where this problem is concerned.

More a sound memory allocation management or DSP ( LSI ) control bug/software oversight in the MPC60 3.XX OS.

The problem then manifests as an apparent DSP ( LSI ) fault.

Have seen this on a few machines. MK1's, MK2's.

Have confirmed it with other users on this list too.

So don't think your MPC60 is beyond help yet.

Can one of you folk with the suspect sounds send me an example of the faulting PGM/APS/SND files for analysis.

Loading them up here in my lab will be a good way to check things out in a way that is beyond most repair technicians.

An exact list of the steps that will guarantee failure each time will be of use in the analysis too.

Rohan.

Cheers

I've got the files on a CF card so I'll work out how to move them on to my laptop and I'll PM you about how to get them to you.

Thank you
Toe

ok, just to add to the data set (if any of you experts are still trying to figure this one out):

I have the same problem with my 60... specifically - very quiet samples (from the same program) triggering randomly, behind the sound I am intending to trigger. As someone else posted, it's most noticeable when playing a low sine wave or something similar.

I have noticed when I am playing a bass line with 16-levels (tuning), the ghost sounds are responding to the 16-levels at the same time. So listening back to the bass line, I hear other very samples in the background, which are being pitched up and down along with the bass note. The ghost sounds are random - different ones play each time the sequence is played back...

For the record, I have a 60 with:
- 3.1 software
- upgraded memory
- only a floppy drive

I don't use sound compression, mpc editor or stereo options... and just sample from wax.

Can anyone solve this??

@ rohan: from my experience, there doesn't seem to be a way to "guarantee failure" - sometimes it happens, sometimes it's gone when you reboot. I don't think it's specific to a program / sound file, as sometimes the MP misbehaves more than usual, no matter what you load up. 90% sure it has nothing to do with the files....

It sounds so much like the problem I had, sounds triggering itself out of nowhere, I just cleaned my pads and my problems where gone. Have you even tried this option yet?

quango wrote:@ rohan: from my experience, there doesn't seem to be a way to "guarantee failure" - sometimes it happens, sometimes it's gone when you reboot. I don't think it's specific to a program / sound file, as sometimes the MP misbehaves more than usual, no matter what you load up. 90% sure it has nothing to do with the files....

Ok ...

Some folk have had repeatable experiences with this fault...

Others ... random.

In particular, the fault where deleted sounds appeared to being still left some where in the machine memory as ghosts.

Seems a software fault to me.

A fault related to sound memory handling...

64hz wrote:It sounds so much like the problem I had, sounds triggering itself out of nowhere, I just cleaned my pads and my problems where gone. Have you even tried this option yet?

The problem you are referring to is a different one and for that ... your solution is completely valid.

This ghost in the memory issue though is a different problem.

I am still waiting on the files containing repeatable ghosts from another list member ( "Toe" ).

Taking "64hz" advice at face value though ... giving your machine a good overhaul including cleaning of the pad sensor assembly isn't such a bad thing.

Rohan.

mpc3000le wrote:I am still waiting on the files containing repeatable ghosts from another list member ( "Toe" ).

I can't work out how to move the files. My 60 has a CF card reader in it, but my laptop does not. Do you think I could put the CF card with the 60 data in my MPC500 and drag the files via usb mode on to my lap top ?

ok well I cleaned my pads with damp sponge, and sensors with tiny bit of alcohol

and vacuumed out all the dust bunnies, general cleanup...

result is an improvement actually (at least on this try, the ghost noises are not as frequent or obvious), but if I crank up that sine bass on solo, I can still make them out.

so I'll be following rohan's investigation with interest

honestly it's not really a major problem on my 60, you can barely make them out when the whole sequence is rolling, but it would still be sweet to figure it out.

cheers

Hopefully this problem is only heard out of the stereo outs and not the 8 outs... if this happens when you track then thats really a problem... I have noticed this and it really does not bother me too much.