4.50 MPC freezing in CHOP

Hi,

yesterday night I was chopping my way through a bunch of samples, at somepoint, i asked the mpc to convert the chops into samples (with create new programme: yes) and the MPC froze on me. Never happened before, but it was the firts time i had used the feature where you change the samples root name.


I wonder if I had reached the max number of samples in the unit (with all the chops etc, I had probably more than 200 samples in RAM eventually).

I had to reboot the unit.

It is the first time i ever saw the mpc100 hang since I have installed the JJ OS...

it happened AGAIN yesterday, I was chopping a sample in 24 slices and when I hit F2 to edit it into a new programme/slices the MPC displays WAIT... I've waited 22 minutes (I clocked them) b4 I decided I could only reboot.

Anybody can reproduce this? I had 154 samples and 7 programmes loaded in RAM when this happened...

this is on 4.5? or the latest?
the only problem i've ever had with chop is the "SLICE TOO SMALL" dialog

I'm still with 4.50. I will try and upgrade to the latest OS, but it never hapened before to me.

os 4.55 i chopped a sample in 32 and it works but before that i got a can't execute message i don't remember how it came.

OK, I think I'm narrowing it down and I thought I would share the conclusions.
Yesterday I upgraded to 4.55, loaded a heavy environment (15 programmes, 192 samples) and proceeded to chopping a long sample in 24 slices. When I hit DO IT the MPC froze again with the message WAIT... on screen. I waited 15 minutes then decided it was enough and rebooted. I reloaded only the sample in question and proceeded to chop it, the MPC handled that fine. So I guess it is a problem with RAM required to perform the chop functions. In my case I had 35-40% of RAM free with all my programmes and samples loaded, so I guess that wasn't enough to process the chopping.
I will report that as a bug, because I don't find it appropriate that the MPC freezes when it lacks RAM to perform any job, I would rather have a warning and be given the ability to save and move to something else.

PS: I've embarked on a serious new concept here, and I'm afraid I might run into RAM management issues. The project I'm working on will use samples in excess of 500 eventually, I hope the MPC will be able to handle that... I will keep you posted.

maybe it would be cool trying to reproduce this bug onto backwards versions... including 2.10... maybe it's a physical matter.

yea from what ive noticed this can happen on akai 2.10 so this is an issue not resolved yet i would too like a function that warns you that you cant do this action for low memory ect..someone should get on to akai about that so jj can mod an add to his new os too hehe