Exchange tips and tricks for the Akai MPC4000
User avatar
By thebeatmaka Tue May 21, 2013 5:58 am
Hey whats up y'all? So to get right to it; I have an MPC 4000, OS 1.71. I've had this bad boy for years and haven't ran into any problems that I could handle until this week. So I was making a few beats over a course of a week and obviously continuously saving my SEQs and MIDI files. I ultimately forgot to save my modified Program Files (.akp). So as I go to save the Programs it oddly begins to save slowly. The little gal is tapping her foot for a long time. I finally decide to hit the "Abort" key to re-instantiate the process over again. Same thing happens again. This time I let it run through it's course and everything seemed to save accordingly. So when I shut off my machine for the night, I returned the next day to load up. To great disappointment the Programs that I had saved are currently reading... BAD FILE FORMAT (405). My question is, how can I fix this? Is there a way to re-save or open the program somehow virtually and re-save with a different name? When I attempt to load through Aksys, it will allow me to save to my PC but when I import back into the machine I get the same actions. I'm hoping this makes sense and ready to provide you more detail if needed.
User avatar
By Mike Boogie Tue May 21, 2013 5:03 pm
Ah, the mysterious corrupted program rears its ugly head.

This process is gonna be extra tedious, but I believe one of your programs that is giving you the error has a bad or corrupted sample attached to it. Maybe the sample degraded due to a RAM glitch. I had this happen after a brownout in my home.

Sadly the only way to fix it is to recreate the program from scratch. Go through each sample and reassign them to a new program.
User avatar
By thebeatmaka Tue May 21, 2013 5:18 pm
Mike Boogie wrote:Ah, the mysterious corrupted program rears its ugly head.

This process is gonna be extra tedious, but I believe one of your programs that is giving you the error has a bad or corrupted sample attached to it. Maybe the sample degraded due to a RAM glitch. I had this happen after a brownout in my home.

Sadly the only way to fix it is to recreate the program from scratch. Go through each sample and reassign them to a new program.


How can I see what samples were assigned to the corrupted Program File? Is there a way to do this through Aksys?
User avatar
By Mike Boogie Tue May 21, 2013 7:00 pm
Not that I know of. I just recreated the program and started from scratch.

Best of luck to you.
User avatar
By thebeatmaka Thu May 23, 2013 1:57 am
Thanks homie for your insight. I will continue to experiment and research this mysterious issue!