just lost a beat

worked for a good hour or so on something

went to listen to it before going to bed and

CPU address error when loading the sequence

the program and samples are fine, but loading the sequence causes the error

dangit

oh well

maybe it wasn't meant to be

tap the samples out again - it may just come back to ya

resample and save as wav b4 you turn it off and then at least you can hear what you did and copy it if you lose summit.

sorry to hear your loss..
...i had major major **** like that on my BR1600 CD and ended up dropping it off a 25 storey tower block - needless to say I felt better.

Not that that is my advice, though, MPC's get vertigo.

Pc!

If it happened once it'll happen again.
Curious, do you have 128MB RAM?

naw

rebuilt the beat

everything's cool

kind of weird that it did that

whatever though i still have all the source material stacked on my other turntable

but yeah it's kind of a bummer that it did that, never happened when i had a 2000xl and 1000

I get this error all the time. F-u-c-k-i-n-g machine!

eimer wrote:I get this error all the time. F-u-c-k-i-n-g machine!

yeah me too. succs big time. when i load projects i get the SYSTEM ERROR, pgms work. is there any solution?

ThaSuperSoaker wrote:

eimer wrote:I get this error all the time. F-u-c-k-i-n-g machine!

yeah me too. succs big time. when i load projects i get the SYSTEM ERROR, pgms work. is there any solution?

There is some conflicts in the software when you load samples, creates sequences and then loads more samples. It can be fixed with an update (like that's gonna happen), so no there is no solution.

There are probably over 10 other posts about this. We've already called Akai, emailed test cases, and they do nothing. I thought maybe my 128MB RAM was the problem so I took it out, but I haven't bothered to test it. The MPC500 is a great tool in theory, in my real world it sucks. I don't save anymore and use it more as a live instrument than longterm workstation. There are still bugs if you don't save though, like hitting a pad and getting multiple samples triggering after, and programs not working until you go back into the track settings then going back to the track.

There are lots of weird little quirks that should be fixed through OS updates, but have not, and somehow get ignored despite lots of people all saying they share them. Akai must have some internal policy where everyone agrees to pretend it is the first time they heard of the bug every time someone reports it, then ignore them. Most people will give up and move on, some will get upset so Akai says they'll replace the hardware. After that long process most probably figure it's not worth the hassle. This saving/loading bug is huge. But only Akai can fix it, and they don't.

Could you tell, your MPC was on batteries when you were saving stuff? I was once transferring files via USB from my laptop to MPC when MPC reported "battery low", then when I tried to load a sequence that I just copied to MPC's CF card, it reported an error and stalled. When I replaced the batteries and re-copied the sequence file, then it worked fine. Maybe, when the voltage is low when it's on batteries, it saves a corrupt file and this causes the problem. Now I use a power adapter and/or replace batteries regularly when there's no power outlet nearby and everything is ok.

brazeca wrote:Could you tell, your MPC was on batteries when you were saving stuff? I was once transferring files via USB from my laptop to MPC when MPC reported "battery low", then when I tried to load a sequence that I just copied to MPC's CF card, it reported an error and stalled. When I replaced the batteries and re-copied the sequence file, then it worked fine. Maybe, when the voltage is low when it's on batteries, it saves a corrupt file and this causes the problem. Now I use a power adapter and/or replace batteries regularly when there's no power outlet nearby and everything is ok.

Mine is on the main suply all the time, but i still get this ugly messages. Now i save all my sequences in another folder for backup. It's only the sequence part that gets corrupt on my machine.

so how you are savin? cause i stopped savin cause the error ish makes me cry. so if i end up with some ideas, which i probably like to redo, edit or finish the next day for example i just dont save anything. cause the int. memory thing seems to flowers up everytime. but not savin can't be the solution..., all the savin on the 500 makes me sick...