Aaah Help! What does this crash screen mean? jjos3.06.....

Just spent 2 hours straight chopping snares/kicks/hats from 68 breaks that were just recorded into my 1000 (JJ 3.06)....and when I clicked 'do it' one time, to extract a sample, this screen rolled through!
I don't want to touch anything until I know that there is nothing I can do to save my work. Will the samples etc...be on the memory if I turn off/back on? I've only my blue box for 1 week so I have no idea what to do here.

Any help appreciated....I'm leaving it turned on until I get some answers. Thanks

Happened to me too with 4.xx, was a bug jj fixed real quick. I wrote down the code written in the error message and sent it as bug report. I never heard this happening with 3.06, maybe jj will fix the free version too? try it.

I dont think your work can be saved though...

I don't think you will be able to save what you have done! This looks like a typical death screen for a CPU.

What it does in its last few dying milliseconds is to dump out the current status onto the screen so a developer can see where it has crashed to figure out what has caused it so they can fix it.

PC is program counter and shows the address in memory where it is currently loading instructions into the CPU

SR is the status register of the CPU, a sort of scoreboard showing what state it is in, i.e. has a number got too big and overflowed, or has software tried to divide by zero or something stupid?

The other bits are various other bits of memory, I won't explain, look on wikipedia if you really care.

The bad news is this screen is called a debug screen. It shouldn't be encountered by users unless something bad has happenend. If it was an expected error, it would pop up with an error box akai/jj had coded into it, i.e. might pop up and say "cannot save, disk is full" or something similar.
What has happened with you is an error has occured but there is nothing in the software to pop up and say "hey you cant do this", so its just tried to do the impossible and the CPU has gagged on it.

I guess a power cycle (turn off then on again) will fix it but you will lose your unsaved work

The synclavier was a fantastic instrument in this respect, the CPU and sample memory was seperate, so you could turn CPU on/off if it crashed and leave the RAM turned on, so it retained all you samples.

hah! that last bit of info is cool.

i have gotten 4 of these screens in my life - 1 on os 1.07, 1 on 2.11, and 2 on various jjs.

Ok ****. I'll start over today with those breaks. aahhhh...at least I got my chop/extract speed up to about 1 sound per 20 seconds! should be quicker this time.
Only installed JJOS3.06 earlier that day, so I guess I had bad luck.
Thanks for the great info too.

PS Can' tbelieve how much better JJ is for chopping! I thought there was something I was missing when I was slooowwwly using the data wheel/numeric keys on the AK OS to set my chop points. What a waste of time, especially coming from ProTools, and recycle. Thanks JJ for JJ. I live in Japan, so maybe I should start randomly thanking everyone who walks by, that way sooner or later one of them will have to be JJ.

Just happened 2 more times today, lost heaps of work. ****. Might buy the new version...

whaaaaat

2 times today?
what were you doing? never heard of this.

ANTONYM----
same thing I was doing the first time it happened.

recorded parts of about 60 breaks into my mpc, as 60 separate samples.

Then proceeded to chop kicks and snares from the breaks, using edit mode, chop, extract.

After going through about 15-18 breaks, and chopping about 40 new samples (extracted kicks hats snares), I'll be doing the same routine as always, which is 'chop', set end point, set start point, edit/extract, 'do it' and as soon as I push 'do it'....BAM! There it is. I might add that I'm pushing the buttons very quickly, because when you are sitting there for so long doing the same thing, you get stupidly quick at it. Do you think the ram is shitting itself or something? I have no idea, just thinking that sometimes on a low ram PC if you do too much too quickly it can shit itself.

I'm going to buy jj4.57 or whatever the new one is, but still if you say you've never heard of this, then maybe I should be concerned about my MPC's internals

Smells like bad RAM to me. Do you have the original Akai RAM? Is it very hot where you work?

In any case, try reseating the RAM - open the MPC and take it out and carefully reinsert it.

parker - when i was on 3.0X my mpc did freeze while chopping, that was one of the times! since upgrading, i haven't had a chop freeze though...

i dunno. pain in the ass though. at least chopping is easier for you now and soon will get easier.

parkerlewis wrote:PS Can' tbelieve how much better JJ is for chopping! I thought there was something I was missing when I was slooowwwly using the data wheel/numeric keys on the AK OS to set my chop points. What a waste of time, especially coming from ProTools, and recycle. Thanks JJ for JJ. I live in Japan, so maybe I should start randomly thanking everyone who walks by, that way sooner or later one of them will have to be JJ.

main i'm waitin on my guy he gon d/l the os for me.. and i read the manaul, shoot i printed it out form the web site but it ain't really say much bout the choppin.. but yeah do go on bout this.. i'm still on the original os 1.0 and choppin takes FOREveR, SLOW AND tedious but i jus accecpted that as part of the "game".. but uh you shinin light on this for me..

go on wit that..

1. how is it better and more "usefull" then the orginal os..

thanks guy

be eaZy

Bizzla it's a different world. You can use the data wheel to speed across the waveform so quickly. The more you zoom in, the slower the data wheel will be so you get more accurate, but it's perfect. I was really really disappointed at the akai os chopping/edit mode, because I just couldn't believe how slow they set the data wheel!! At full 'zoom out' view, you can move from one end of a 4 bar loop to the other end in a couple of seconds, to give you an idea of how much faster the cursor moves. You can chop 16 pieces in 5 minutes, accurately in my experience over the last few days.

Also I find it's easy to first find the middle of a sample (say in a 2 bar sample, set just 2 chops, and then highlight each one and click 'divide', and then select each of these 4 chops and click 'divide'. This way you can quickly get rough chop points (if you want evenly spaced chops), and then just zoom in on each one, and they should be pretty close to a snare hit, or bass kick on the '1', etc....



****yes I have the AKAI brand ram, so it should be the goods. Hhmmm, I might try resetting the ram, but also grabbing the new OS by JJ. Once I saw how much better then 3.0X was, I'm sure 4.6X will be just as impressive.....

parkerlewis wrote:Bizzla it's a different world. You can use the data wheel to speed across the waveform so quickly. The more you zoom in, the slower the data wheel will be so you get more accurate, but it's perfect. I was really really disappointed at the akai os chopping/edit mode, because I just couldn't believe how slow they set the data wheel!! At full 'zoom out' view, you can move from one end of a 4 bar loop to the other end in a couple of seconds, to give you an idea of how much faster the cursor moves. You can chop 16 pieces in 5 minutes, accurately in my experience over the last few days.

Also I find it's easy to first find the middle of a sample (say in a 2 bar sample, set just 2 chops, and then highlight each one and click 'divide', and then select each of these 4 chops and click 'divide'. This way you can quickly get rough chop points (if you want evenly spaced chops), and then just zoom in on each one, and they should be pretty close to a snare hit, or bass kick on the '1', etc....



****yes I have the AKAI brand ram, so it should be the goods. Hhmmm, I might try resetting the ram, but also grabbing the new OS by JJ. Once I saw how much better then 3.0X was, I'm sure 4.6X will be just as impressive.....

Any way to remove a divide line? I've just been moving my start and end points to sort of cover up unneeded ones that I make by mistake..

hey guy...
I have seen that screen many many times while making beats. **** annoying! I sent it as a bug report, and it hasn't been fixed yet. I used to get the same error with the AKAI OS too... boo hoo.

At least now I know i'm not alone...!

klaze wrote:Any way to remove a divide line? I've just been moving my start and end points to sort of cover up unneeded ones that I make by mistake..

You can remove a divide line by using the combine function.