Reviews and questions about the entry-level MPC500
User avatar
By rydan Thu Jan 04, 2007 6:13 pm
Well, I was saving a program, choose save, and then create new folder, named the folder and hit doit. The display stayed at "creating folder" forever, without any way to get out of it other than rebooting the MPC. Later, the browsing of folders was very vierd. I could step down in one folder, and then back up, and be somwhere else completely. So, i connected to the computer, and the folder it tried to create when it crashed was there, but it wasn't possible to delete it, either from the MPC or from windows, so I have had to copy everyting else from the card to the pc, reformat the card, and then put everything back.

Anybody else had this? I have the latest OS (1.11)
User avatar

By Antonym Thu Jan 04, 2007 7:26 pm
DING DING DING DING DING

jesus akai, figure it out, this is the 3rd machine in which the SAME BUG has cropped up

mpc1000 - os 2.1
mpc2500 - os 1.22
mpc500 - os ....

this is the "new folder" bug
create your folder before you start your project, otherwise you will lose your work.
User avatar

By Upright Thu Jan 04, 2007 9:30 pm
This is a weird bug. If it is the same bug that the other mpc's have(more than likely it is) then it's the kind of thing that comes and goes. I use to experience this in my early days of the 2500 about two or three times at the most....I don't ever make a folder to save to before I make my tracks and I haven't had the problem in about 5 months. Like I said only experienced this two or three times total.

weird bug :D
Last edited by Upright on Fri Jan 05, 2007 4:16 am, edited 1 time in total.
User avatar

By Antonym Thu Jan 04, 2007 9:38 pm
This is a weird bug. If it is the same bug that the other mpc's have(more than likely it is) then it's the kind of thing that comes and goes.


yeah, i don't know how to reproduce it...

in my experience it always cropped up when i'd spend hours on something i love, then poof, gone

i think the whole pride/love thing is what triggers this bug, never happens when you don't give a sht about the beat you were working on :roll:
User avatar

By Antonym Thu Jan 04, 2007 9:39 pm
they really did just throw in the same code into all these machines
User avatar

By Upright Fri Jan 05, 2007 4:14 am
Antonym wrote:

in my experience it always cropped up when i'd spend hours on something i love, then poof, gone

i think the whole pride/love thing is what triggers this bug, never happens when you don't give a sht about the beat you were working on :roll:


ROTF ....hahahahahahahaha!!1 :D
User avatar

By rydan Mon Jun 04, 2007 2:25 pm
Actually, that sounds just like it!

Just happened to me again yesterday. Was on a train, had browsed like 1000 beatbox samples to create a "favourite" kit. All done. Save, make new folder. Hang.

Hasn't happened since my last post in this thread. Of course it had to happen after like 3 hours of unsaved work...

ByErgg Mon Jun 04, 2007 4:50 pm
Antonym wrote:i think the whole pride/love thing is what triggers this bug, never happens when you don't give a sht about the beat you were working on :roll:


I know exactly what you mean! I created this kit to save in the internal flashrom, when saving it only said "0%" and the MPC500 froze on me.

I think we should email Akai anyway to let them know, every time we have problems. If they don't know we have them, they won't bother fixing them.

I don't expect them to read this forums (but they should...).

Snerg
User avatar

By madbeets Tue Jun 05, 2007 7:31 pm
I have never had this happen.
I go to save:program
DO IT
cursor up select
NEW FOLDER:locate where I want the new folder to be
name the new folder
DO IT
SAVE with samples
DO IT

and it works every time.

I do this with projects, sequences, programs, samples.
Never had a problem. There has to be something else somewhere that people are doing to get this. A bug doesn't just happen sometimes and not others without a value getting set that corrupts the data.

It seems Akai is working on the MPC code right now as they have released new OS updates for all the machines. If we can figure out what corrupts this every time they might get it fixed before they move on to something else.

I want to see them have the last sample that was mapped to a pad remembered.
It's the only real pain I have with the MPC500 and 2500, going through long lists of samples every time I assign a pad.

ByErgg Tue Jun 05, 2007 8:50 pm
I hate that the MPC500 goes back to the first sample in the folder after loading one. It should go back to the last sample you loaded, so you don't need to scroll through the whole list again.

Snerg
User avatar

By lovesign Tue Jun 05, 2007 10:12 pm
If someone can document an exact process that outputs this error every time, I will report it directly. Without a way to replicate this consistently, it becomes difficult to identify and fix.
User avatar

By rydan Wed Jun 06, 2007 10:06 am
madbeets wrote:I have never had this happen.
I go to save:program
DO IT
cursor up select
NEW FOLDER:locate where I want the new folder to be
name the new folder
DO IT
SAVE with samples
DO IT

and it works every time.


That's exactly what I do too. Works ALMOST every time. I'm actually considering returning my 500 for a check up on the CF card reader, I have had more problems with corrupt files lately.
User avatar

By rydan Wed Jun 06, 2007 10:07 am
madbeets wrote:It's the only real pain I have with the MPC500 and 2500, going through long lists of samples every time I assign a pad.
''

Ditto. If EVERYBODY would email akai about this, maybe it would get fixed as well...
User avatar

By rydan Wed Jun 06, 2007 9:47 pm
I might be on to something here...

Reformat:ed my card from FAT32 to FAT. All of a sudden, I have still not been able to corrupt files by overwriting (replacing) them. I could do that in like 5 saves with fat32. Perhaps a bit early to say, but it seems more stable...

What file system are you running on the CF card? Fat16 or Fat32?
User avatar

By lovesign Wed Jun 06, 2007 10:10 pm
Antonym wrote:they really did just throw in the same code into all these machines


That's really just a silly comment, especially if you knew who wrote the original 1K & 2.5K code ! :roll: