5000 locking up....

Getting really tired of this **** locking up. I'll spend an hour creating a pattern and it'll lock up and I'll lose everything. Get a stable OS for **** sake

ya'll shoulda listened to us 4000 users instead of clowning..looks like the new akai is still the same old akai. Good luck with that..

FRESHFOR'88 wrote:ya'll shoulda listened to us 4000 users instead of clowning..looks like the new akai is still the same old akai. Good luck with that..

Don't get me wrong I love the 5000. I had a 4000 and IMO the 5k is a lot better I believe it's most def the best MPC out there. They are just having issues with their OS just like the rest of them had when they came out. It does get frustrating but do I regret trading my 4k in on the 5k?? HELLLL NAWWWW!! 5k is a BEAST!

The MPC 4000 did the exact same thing and worst when it was released. The best bet is to always wait for a few OS updates with music production workstations because there is always issues with the first OS. This is not just an Akai/Numark problem...Roland, Yamaha, and Korg released products with a crappy OS that were later upgraded.

Exactly, I dont why everyone was exspecting the 5000 to be perfect on OS Version 1! everyone of your computer OS, MPC OS, and everything elses OS started out like that.

I haven't had a lock up or crash so far. I had my mpc5k since july the 2nd. I never had any problem with my mpc4k or any other equipment I own. I guess I am electronically lucky that way.

You know it really isn`t a 4k or 5k thing if you don`t save your sequence and multi constantly like on a DAW or document, you would always lose your work. It is the users not taking steps to preserve their work.

Lesson learn is that machines crash so one should save constantly thier is no history or redo button on a mpc.

It's wise to save your work every so often while you create...but with the MPC 5000, it can freeze up within a few minutes depending on what you are doing. Then you start focusing too much on saving every other minute instead of composing music.

Askia Shaheed wrote:It's wise to save your work every so often while you create...but with the MPC 5000, it can freeze up within a few minutes depending on what you are doing. Then you start focusing too much on saving every other minute instead of composing music.

You know if any mpc I ever owned from the 2xl, 1k, 3k, or my 4k ever did that, I would take it back to the maker and exchange it.

And sometimes when I did have a problem I would go backtrack and check where I might have fuked up if I had any hiccups in my style of workflow something as simple as assigning two programs to the same midi channel would **** up my simple layout and overload my sequence in my budding mpc days.

Man, the MPC 5000 would even freeze up while trying to get to the saving folder of where you are trying to get too...

I feel ya UBANKRECORDS... It took me 2 days to finish a track for an artist(probably actually only 4 hours, if i wasnt in between other sessions)... Trying to save and load samples, and the load and save screens start moving slow.... It can be hell.... but once they get it together, the MPC 5000 can possbily be the beast it was meant to be.

Blue Haze wrote:

Askia Shaheed wrote:It's wise to save your work every so often while you create...but with the MPC 5000, it can freeze up within a few minutes depending on what you are doing. Then you start focusing too much on saving every other minute instead of composing music.

You know if any mpc I ever owned from the 2xl, 1k, 3k, or my 4k ever did that, I would take it back to the maker and exchange it.

And sometimes when I did have a problem I would go backtrack and check where I might have fuked up if I had any hiccups in my style of workflow something as simple as assigning two programs to the same midi channel would **** up my simple layout and overload my sequence in my budding mpc days.

Assigning two programs to the same MIDI channel? Which MPC are you talking about?

I owned some of those sample models and they did freeze/crash (especially the MPC 4000) but I didn't take them back I just waited for an OS update. But like I have said many times...I wouldn't expect too much from any new product with a new operating system.

They say that from the point of inspiration it only last 15 minutes, after that your trying to hard...

Thats why when i get my 5000 ima spend the first few days just gettin my workflow down not really tryin to create any monsters...

Teknokeyz wrote:Thats why when i get my 5000 ima spend the first few days just gettin my workflow down not really tryin to create any monsters...

You mean the next couple of days, weeks, months? I'm pretty sure this isn't an isolated problem this thing is having at this point.

I'd wait it out for a minute until at least the next os update. But that's not even guaranteed to cure all the ills either...something to think about.

Askia Shaheed wrote:

Blue Haze wrote:

Askia Shaheed wrote:It's wise to save your work every so often while you create...but with the MPC 5000, it can freeze up within a few minutes depending on what you are doing. Then you start focusing too much on saving every other minute instead of composing music.

You know if any mpc I ever owned from the 2xl, 1k, 3k, or my 4k ever did that, I would take it back to the maker and exchange it.

And sometimes when I did have a problem I would go backtrack and check where I might have fuked up if I had any hiccups in my style of workflow something as simple as assigning two programs to the same midi channel would **** up my simple layout and overload my sequence in my budding mpc days.

Assigning two programs to the same MIDI channel? Which MPC are you talking about?

I owned some of those sample models and they did freeze/crash (especially the MPC 4000) but I didn't take them back I just waited for an OS update. But like I have said many times...I wouldn't expect too much from any new product with a new operating system.

I was talking about making rookie mistakes in the heat of the moment starting out, then scratching my head wondering what is wrong or why my mpc crashed, then I discovered wtf I done fuk up moving too fast making simple mistakes like that.

But it was and will always be a learning experience. As I learn my way around my various mpcs I make less mistakes resulting into less crashes. If i just got any new mpc, I wouldn`t fool myself into thinking I knew what the hell I was doing and its all machine bugs.

I`m guessing realistically some of it mind you could be user error. I would expect that basic functions like saving to do just that save or take it back, record a basic midi track to do just that record, or take it back and etc.

But if SCD or more experience 5k user use the 5k with none of these simple hiccups then it could be user error and then I would take my 5k to a experience users or go watch them and their workflow or just simple sit-down push every button, with the guide nearby until I got it right.

Each mpc is basically the same structure but each has an its own workflow one has to adapt to each machine, not the other way around the machine to you.

I predict months from now you will have less problems not just because of an so called O.S. update, but you have a more comprehensive workflow with the mpc at hand. User error vs O.S. bugs goes hand and hand.

I'm sorry but I got a new MPC and I know exactly what I am doing. Only boredom has me even writing in tis thread. I already reported in another thread that this new MPC will freeze doing very simple things. This is not user error. If SCD hasn't encountered this problem, than he is not using OS 1.01 or he isn't being forthcoming.

For the record, this MPC is pretty much like all the newer MPCs. If you can use an MPC 1000 or 2500, you really do not need to read the manual. The newer features you can figure out just by playing with it a few hours.