New MPC 60 user // midi sync parameter not saved on reboot

Hello MPC 60 forum

I have just got myself a mint condition MPC 60 mk1 with OS 2.0.2

Mann,, that beast is big,, that beast is looking good and the timing and groove is so sweet compare to my MPC 1000 with JJOS XL.


I have 2 questions please:

1 : Why I am not able to retain the Sync Input Settings to midiclock when I reboot the MPC ( even if I save the parameters on floppy it will not kepp it assign )
Is this a bug because of OS 2.0.2 .? If so, do upgrading to 3.1.0 will solve this problem

2 : when I sample a new sound and go back to the main screen to playback the previously recorded sequence ( drums sequence with internal samples sound ), the sequence is delete or the track is gone,, nothing is there anymore ? I playback and it is erase.


Any MPC 60 Wizards out there dat can help me out!??

Cheers

Rqckmounted wrote:2 : when I sample a new sound and go back to the main screen to playback the previously recorded sequence ( drums sequence with internal samples sound ), the sequence is delete or the track is gone,, nothing is there anymore ? I playback and it is erase.

It's the limitation of 2.XX OS.

MPC60 Software version 2.0 Operator's manual, p. 126 wrote:The SAMPLE NEW SOUND screen:

To access the screen used for sampling new sounds, press the SOUNDS key, then press `f to select the SAMPLE NEW SOUND option. This will cause the following preliminary screen to appear...

...At this point, you must decide which drum you want to sample into, because once <proceed> is pressed, the drum you select and all sequence memory will be erased to provide maximum space for new sampling. If you have sequences or songs in memory which you do not want to lose, press the DISK key and then save them before proceeding.

Thank for the reply ZWUKOLOW


Anyone know how to reboot the MPC 60 without loosing the Midi sync input setting.??


I think I am gonna buy the OS 3.1.0

Rqckmounted wrote:Anyone know how to reboot the MPC 60 without loosing the Midi sync input setting.??

I think I am gonna buy the OS 3.1.0

Not sure that 3.10 will make any difference.

The OS 2.0 Operators Manual, page 161, indicates that the parameters in the PAR file should also be retained in the MPC automatically after power is removed, among those parameters are those in the Sync Screen...

Saving a Parameter file

The settings of most of the MPC60's data fields which are not normally
saved to disk are retained after power is removed, so that you don't have to
set them again every time you turn the power on. This function allows you
to save a special file called a "Parameter file" (file extension: "PAR") which
contains the current settings of these data fields.

The following is a list of the data fields which are retained after power
is removed, and which are saved within parameter files:

...snip...

(Sync screen)
• Sync input mode
• Shift sync early
• Midi input select
• 1/4 note click sync starts at current bar / bar 1
• Sync output mode FSK24/PULSE96
• Midi clock output 1/2/3/4/off

.../snip...

The service manual/schematics show a CL2020 lithium backup battery on the CPU board, I would guess that it needs to be replaced, so that the MPC retains those parameters automatically when power is removed, as it should.

Another possibility, though it might not work as it is not mentioned in the manual, might be to name the .PAR that you are saving to disk as SYSTEM.PAR, which works for .ALL files as SYSTEM.ALL to load that automatically when powered up, no idea if it would work for a .PAR file as well.

I'm sure it wouldn't hurt to get 3.10 or even 2.12 - it seems like most bugs like this happen on mad old versions

Well..here's an update

I am able to save parameter to disk and on rebooting the MPC and load it back from the disk and the Syncscreen Sync Input Settings is reload.

So I assume that this is normal since these are the procedures.

When I presse the HELP button in the (5) save parameter option, you can read this:

A 'PAR' file saves the settings of most data fields which are not saved in other file types. ( These settings are retained with power off.) Type the 16 caracter name for the 'PAR' file you are saving, ENTER , then (SAVE IT to disk) to save it

So the question is; Will it remain in memory if I upgrade to OS 3.10???

Rqckmounted wrote:So the question is; Will it remain in memory if I upgrade to OS 3.10???

It has nothing to do with the OS.

SimonInAustralia wrote:The service manual/schematics show a CL2020 lithium backup battery on the CPU board, I would guess that it needs to be replaced, so that the MPC retains those parameters automatically when power is removed, as it should.

Have you replaced the battery?

No I dit not replace the battery yet.


So do you think if I replace this battery it will also solve the problem of the sequence being deleted after recording/sampling a sound ?

Because if it solve that problem, I might NOT upgrade to OS 3.1.0

Rqckmounted wrote:So do you think if I replace this battery it will also solve the problem of the sequence being deleted after recording/sampling a sound ?

That is not a 'problem', it is a function of OS 2, that is the way it works, that is why it warns you before you record a new sample, changing the battery will not change the way that works.

Upgrading to OS 3.10 will stop that from happening.

the battery is dead so you lose the parameters when you power off... just save the params file and reload it every time. I'm not even sure if i'm glad after all these years my battery still works... it's only handy if you keep working on the same song all the time. I do suppose though that if you always have midi gear set up some special way it could save a few seconds... but when starting a new song it's annoying to have to go to other/defaults all the time cause volumes are all incorrect in the mixer and echo mixer, etc...


upgrade to 3.10 to prevent your sequence memory from getting erased when entering the new sample screen... until then save your sequence to disk before recording new samples and load them back up when you are done. It actually takes like 5 or 10 seconds extra... but it's manageable.

Rqckmounted wrote:
I have just got myself a mint condition MPC 60 mk1 with OS 2.0.2

The moral of this thread is try or ask the questions, before you commit to purchase. That way you know if you're getting good value for money for the price and whether any upgrades/maintenance is necessary.

Replacing the battery is cheap but tricky, the OS upgrade is an investment that many tight arses try to avoid making. A false economy in my opinion considering all the extra features it provides.

Mint condition is still great news though, lots of beat up 60's out there.

I'd take a beat up 60 with v3 over a mint v2 any day.

Thanks you all for your opinions/help

I have just perchase the OS 3.10 from MR LINN.

I am going step by step the see where it gonna lead me, after the OS upgrade I will look at upgrading the ram memory.

After all this, the question is : Should I keep my MPC 1000 with JJOS 2xl?

But that is another topic.

Cheers

You still should replace the battery as well.

Rqckmounted wrote:Thanks you all for your opinions/help

I have just perchase the OS 3.10 from MR LINN.

I am going step by step the see where it gonna lead me, after the OS upgrade I will look at upgrading the ram memory.

After all this, the question is : Should I keep my MPC 1000 with JJOS 2xl?

But that is another topic.

Cheers

Ok Peoples here is an update...

I have just installed 3.1.0 in my MPC 60

Now the sync parameter is saved ( loaded during booting)

I have also change the CR2032 battery.

But there is another problem....

here is the midi settings I want it to be loaded when I start / boot my MPC:

chn: 1A on trk : 01
chn: 2A on trk : 02

When I reboot why it does'nt memorise those parameters..!

How can this be achieve