feelin cheated TONITE !!!

i love this 2500 that i've now had for the last 5 years, BUT this thing been playin with me mind a little this last
couple months. I'am not of man of much complaining but, WHY ? is that since i've updated to 1.46OSXL,
This Faaaaackin Machine decides it just wanna stop with sum kind of fuuuckery right in thee middle of a deep
session & just FREEZE up ?
is it just me or is any of you'all havin the same problem ?
cuz this no cool, just lost 4hrs of work tonite bout 15 mins ago........... ( just a little upset with the 1.46 update )

I feel for ya man

Yep, I feel you! It's bad shit having a machine freeze up on ya! My first MPC2000 used to freeze up mid session, it eventually got worse and worse until it eventually croaked.

Hahahaha, I actually think that my first few posts here went on about it dying!

Back on topic, you'll never get them 4 hours of work back but perhaps you can recreate what you had in those 4 hours in less than half the time?

did you try holding down the ERASE key as you start up? it's a good idea to do that if you're having problems.

just make sure before you do that you make a note of your pad sensitivity settings/etc because it wipes out all of your preferences & resets them to the default setting.

man I hate it when that kind of thing happens... it happened a couple of times to me on the computer because of user error... I did stuff I knew I shouldn't have done like adding a resource intensive pluggin while a complex large song was running and it crashed. Since then I have become a compulsive saver.. haha



and sooty, is that a guinea pig?

mr_debauch wrote:and sooty, is that a guinea pig?

the most famous guinea pig of all. click my sig for the full story!

Sooty_G wrote:

mr_debauch wrote:and sooty, is that a guinea pig?

the most famous guinea pig of all. click my sig for the full story!

hahahahhahaha...... hahahahahahahahhahahaah

that is crazy!

to avoid a crash in jjos2xl 1.45 (1000) and 1.46 (2500),
avoid doing this:

1- creating a midi track, then
2- setting qlink REALTIME TUNE, then
3- recording a performance, then
4- entering STEP EDIT and finally
5- changing a value (velocity, for example).

this causes a crash.

crothers wrote:to avoid a crash in jjos2xl 1.45 (1000) and 1.46 (2500),
avoid doing this:

1- creating a midi track, then
2- setting qlink REALTIME TUNE, then
3- recording a performance, then
4- entering STEP EDIT and finally
5- changing a value (velocity, for example).

this causes a crash.

nice........... & thanks... some good little notes there...
Welcome aboard Crothers !!

mr.pleasant wrote:

crothers wrote:to avoid a crash in jjos2xl 1.45 (1000) and 1.46 (2500),
avoid doing this:

1- creating a midi track, then
2- setting qlink REALTIME TUNE, then
3- recording a performance, then
4- entering STEP EDIT and finally
5- changing a value (velocity, for example).

this causes a crash.

nice........... & thanks... some good little notes there...
Welcome aboard Crothers !!

yup,

experienced same shit. looks like jjos just posted a fix. hopefully it will indeed fix these issues. nothing like crashing while working on a dope aszz beet!

IllRhythm wrote:Yep, I feel you! It's bad **** having a machine freeze up on ya! My first MPC2000 used to freeze up mid session, it eventually got worse and worse until it eventually croaked.

Hahahaha, I actually think that my first few posts here went on about it dying!

Back on topic, you'll never get them 4 hours of work back but perhaps you can recreate what you had in those 4 hours in less than half the time?

you should make sure you save more often, i usually save after every major change i make to a beat. say, every 20 minutes?