Technical questions for the MPC2000xl and the MPC2000
User avatar
By MalaKai Mon Jun 22, 2015 2:33 am
Has anyone ever had this issue when doing Zone -> Edit -> Slice Sound?

It doesn't happen all the time but when it does it's frustrating. I wait 20 minutes (longer than it should reasonably take) then I'm forced to restart the machine and lose everything. It seems completely random too. Sometimes I can zone edit four 2 bar samples and then it will happen on the 5th, other times it will happen with the second sample I slice.

I hope it's not related to the recent water accident I had. (viewtopic.php?f=1&t=177497). I think it probably is though since this didn't happen before. When I first got the machine I had one or two random lockups in different situations but this new condition seems to be a constant.

Maybe I need to replace the memory? Or worse..
User avatar
By MalaKai Mon Jul 13, 2015 6:44 am
Hella weird, this problem seems to have solved itself. Been using the 2KXL heavily in the past week and it hasn't happened once. Side note: I reformatted the card because a couple of project folders got garbly. No clue if this is related since the sample should be in memory already but knock on wood.
User avatar
By Wal Martian Mon Jul 13, 2015 5:00 pm
If you have sampled a really long sound, some functions can take what seems like a lifetime. I often clear the unused sounds from my 2K before saving, and if there are long samples it can take quite some time. I would assume it's not frozen and it's just taking forever to process.
By mQueue Mon Jul 13, 2015 10:14 pm
Switch out your memory. In my experience the problems will be intermittent and show up in different places of the OS but will continue to bog you down.
User avatar
By distortedtekno Mon Jul 13, 2015 11:11 pm
My 2k freezes up if I'm using all the RAM and I try deleteing samples. Looks like the XL suffers from the same thing. Eventually, it'll process. But it ends up taking close to an hour, from what I recall. That'll kill any creativity you got. Better off rebooting and deleting samples as soon as you know you won't need them. Luckily, I was only testing the two machines I have in order to discover that. So I can confirm that with two machines and three pairs of RAM modules that it's not a RAM issue. Just a slow processor. The 'Test Mode' will confirm the RAM has no issue.