Share your knowledge on these two classic MPCs
User avatar
By DOVESKI Thu Feb 03, 2005 5:17 pm
At first I thought I was tripping out, or maybe I made the mistake, I would do a tight sequence, load it up the next morning, and one sample would be different, I thought maybe I was just drunk/high the night before, or since I had headphones on at the time I wasnt hearing it right, but now I'm sure my MPC is buggin.

When saving programs, it has the tendency to replace a new sound (not from my kit - usually just labeled SOUND502, or the if chopped - 1OUND2, 2OUND2) with either a sound from the kit or a different version of the chopped sound, usually a deleted part (using DEL ZONE FUNCTION) and of course this fucs up the whole beat -

anyone else have/or had this problem.

By elmacaco Thu Feb 03, 2005 7:25 pm
It might be naming the sounds that confuses it, two saounds with the same name etc.

make sure your midi assignments don't have the same midi note for two pads in Master or Program layouts.

By djimpak Thu Feb 03, 2005 10:30 pm
i woudlnt mind takin it off ya hands
User avatar

By DOVESKI Fri Feb 04, 2005 12:44 am
elmacaco wrote:It might be naming the sounds that confuses it, two saounds with the same name etc.


No sir.
By mpc3000le Fri Feb 04, 2005 1:01 am
DOVESKI wrote:When saving programs, it has the tendency to replace a new sound (not from my kit - usually just labeled SOUND502, or the if chopped - 1OUND2, 2OUND2) with either a sound from the kit or a different version of the chopped sound, usually a deleted part (using DEL ZONE FUNCTION) and of course this fucs up the whole beat -

anyone else have/or had this problem.


First, go over this process again:

___________________________________________
========= Save a Program (PGM) =========
Program:19-Program name Size: 0K
Disk:SCSI DISK PART A Free: 793K
Save:PROGRAM+SOUNDS (NORMAL)
Replace same sounds on disk:NO (FASTER)
==================================
<Do it> <Select disk>
____________________________________________


The "Save" field:

Program files contain no sound data so when saving a program, the sounds used by the program are normally also saved at the same time. This choice field permits the option of saving the program file by itself without the accompanying sound files.

The two options are:

PROGRAM+SOUNDS (NORMAL):
This is the normal setting, saving first the program file then each
sound file used within the program.

PROGRAM ONLY (NO SOUNDS):
This option allows only the program file to be saved without any
sounds.

The Replace same sounds on disk field:

This field appears only if PROGRAM+SOUNDS (NORMAL) is selected in
the field above. It has two options:

NO (FASTER):

When saving a program (and its sounds), if a sound file exists on disk
with the same name as one of the sounds to be saved, the file is not
overwritten by the sound in memory. If when saving a program you
know that the sounds have not changed, this option will permit a
faster save.

YES:

When saving a program (and its sounds), if a sound file exists on disk
with the same name as one of the sounds to be saved, the disk file is
overwritten by the sound in memory. If when saving a program you
know that the sounds have changed, you should select this option.

Ok, now the next part...

How much RAM is in your MPC3000 and how close to all of it is being used ?

More as I think of it.

Cheers,

Rohan.
User avatar

By DOVESKI Fri Feb 04, 2005 3:58 am
Rohan thanks for the rundown, but I do all of the above formetioned, now I noticed some more of my MPC fucin up, Ill be in a program that is/was fine, i will be tweaking the filters for one sound/pad, the filter will be applied to another during play and out of play....

And Ro, I am 3.11 (loaded from disc - chip is 3.08 will fully expaded memory) thanks.

Also whats weird is i noticed on one program is the sound that rpelaced what i wanted was the portion of the sample i dleted, on another it is just a snare from my standard kit. I think either i need new OS chips or the memory is faulty.

By elmacaco Fri Feb 04, 2005 4:33 am
Maybe the OS on the floppy is a little worn? Did you try a fresh disk with a fresh copy of the OS?

Other than that I'd check the Power supply's 5 Volt line just to be sure.

Sorry about all the easy Questions Dove, we know you know what you are doing, but we have to rule out the easy stuff first.
User avatar

By DOVESKI Fri Feb 04, 2005 4:43 am
Nah its all good, no ego trippin with us man. Im just worried about this shit. Also, the power supply is stock and i actually had the power supply replaced by Forat about three months after i got this particular unit.

By elmacaco Fri Feb 04, 2005 4:49 am
Who knows, I would check the % volt line as weird power can cause weird glitches, but this sounds like the OS issue, did you try a new disk? I'd try that first.

Does it happen when you don't boot the OS from floppy? With 3.08?

By mpc3000le Fri Feb 04, 2005 7:43 am
DOVESKI wrote:Rohan thanks for the rundown, but I do all of the above formetioned, now I noticed some more of my MPC fucin up, Ill be in a program that is/was fine, i will be tweaking the filters for one sound/pad, the filter will be applied to another during play and out of play....


Hmmm... sounds like some bad RAM access stuff is going on.

DOVESKI wrote:And Ro, I am 3.11 (loaded from disc - chip is 3.08 will fully expaded memory) thanks.


Oh... a lot changes from 3.08 to 3.11.
The boot code for the SYS loader and the init stage are still 3.08 in your machine prior to launching 3.11 from floppy.
Booting from floppy = reduced sequencer memory and a whole bunch of other issues beyond the scope of this response.

Best to have a newer version in ROM.

PM me for more info on this newer version in ROM thing.

DOVESKI wrote:Also whats weird is i noticed on one program is the sound that rpelaced what i wanted was the portion of the sample i dleted, on another it is just a snare from my standard kit. I think either i need new OS chips or the memory is faulty.


Possibly a combination of both.
If you're running 32 meg in your machine then it would be best to run a newer operating system build in ROM.

Try pulling the RAM out, cleaning the contacts and swapping it around.

You could also prior to performing any sound editing; goto the create new sound menu. At this point on entering the create new sound menu, the MPC3000 will compact and re-organise the sound allocation tables in memory. Returning to the sound edit screen after it has completed the sound memory re-arranging routine may yeild some better edit results.

Try it out.

Rohan.

By elmacaco Fri Feb 04, 2005 7:52 am
Do you mean the sample new sound?

I'm not sure the 60 has create new sound.

By mpc3000le Fri Feb 04, 2005 8:10 am
elmacaco wrote:Do you mean the sample new sound?

I'm not sure the 60 has create new sound.


ahhhmmm ... yeah. But we're talking about MPC3000's anyway :-)

Rohan.

By elmacaco Fri Feb 04, 2005 8:35 am
I know, I just like to keep track of the 3000 and 3.10 60 differences.

By mpc3000le Fri Feb 04, 2005 9:14 am
elmacaco wrote:I know, I just like to keep track of the 3000 and 3.10 60 differences.


MPC3000 = "Create New Sample" option 5 in the PGM/SOUNDS screen.

Elmacaco, you going to get an MPC3000 one day ? :-)

Rohan.

By mpc3000le Fri Feb 04, 2005 9:19 am
Dunno what is wrong with me tonight ... grrrr. :-(

What I meant to type is:

Option 5, "Sample New Sound" in the PGM/SOUNDS screen.

Confusion... sorry.

Rohan