Technical questions for the MPC2000xl and the MPC2000
User avatar
By nymphfoe Tue Oct 21, 2003 6:40 pm
I was putting my song's seguences in order in the normal track view screen and I hit overdub (to add some more hit-hats) and this popped up on my screen (DIV. Error at 3000:OOF4). None of the buttons worked so I left it on for a couple minutes and nothing...so I left it on for an hour and nothing...I shut it down and restarted it and reloaded the song and now the same screen pops up and nothing will play at all.. I feel I've lost this track to the MATRIX so I'm just wondering if anyone knows what I did and why this happened so It'll never happen again(hopefully). I'm using just the MPC2000 and the files were .snd off one floppy so I know I had enough memory cuz minez is maxed ouT(32MB). I don't know what else to tell you guys to help analyze this but just ask please..Thanx Oh I'm using the 1.72 OS too....

By macman Tue Oct 21, 2003 7:50 pm
My XL did that about 4 time in 2 days.


I've now sold the piece of shi!!

My 3000 will be arriving in the next day or so.
User avatar

By nymphfoe Wed Oct 22, 2003 2:40 am
Man that's too joe but I ain't ready to give up yet...what were you doing when it happened to you. I've had it since 95 and this is the first time so I'm give it a chance since I've loaded other songs and they're fine so hopefully it's just an isolated incident. Is the MPC 3000 working out...Peaceout!
User avatar

By Lampdog Wed Oct 22, 2003 3:59 pm
Try downloading a fresh copy of the OS and re-installing it.
User avatar

By nymphfoe Thu Oct 23, 2003 6:03 pm
well itried the new OS and nothing will play on that particular sequence, and I can't copy and redo the sequence cuz I did some wierd things to it I can not replicate( i know everyone's done that before)...well at least I have some of the song back...Another track Neo is flying to in the lost MATRIX of the MPC world...Peaceout ya'll
User avatar

By Lampdog Thu Oct 23, 2003 9:46 pm
I've lost many seq's when I first started. I don't exactly what you did but sounds like a lost cause. Maybe you didn't save often and actually started back with half of the seq u saved cause when it locked up you lost whatever it was that wasn't saved. Stuff that was saved on the disk already can be reloaded.
User avatar

By Lampdog Thu Oct 23, 2003 9:46 pm
Everytime I make like 3 different changes I will save my stuff.
User avatar
By Lampdog Fri Jun 17, 2016 12:19 am
hok-2 wrote:I keep getting the same thing on my Mpc2000
DIV. Error at 3000:OOF4
The machine freezes then makes a load of trippy noises.
It keeps doing it after a while whenever I load up that particular Program and sequence.
Anyone got any idea what could be making it do this?

aif it keeps happening with a particular program then don't load that program.
Re-created it from scratch and delete the old corrupt program. OR, it may be a file, sample, seq, something associated that loads along with that program.
User avatar
By hok-2 Fri Jun 17, 2016 12:52 pm
Problem Resolved.
I deleted some sounds in the program
I had 3 quite long keyboard samples (11 secs) that I'd been working on prior to making this program for a guy who wanted one the sounds on my synth and I'd been sampling each C-note.
These were still in the memory.
So I cleaned up the program and deleted those, although I wasn't using them in that sequence.
And it's working fine now.

I'm thinking perhaps one of them was in the sequence but, muted and was causing it to crash?
I supose that if a 11 second sample was being retriggered at the start of each bar it would eventauly reach a point where it overlapse so many times the mpc exceeds maximum polyphony...¿

The truth is I have no idea why it was crashing but, I'l be keeping my programs tidier and be saving more often in the future.
The beat is loaded up and working today.
Blessed be the Mpc Gods.
User avatar
By Lampdog Fri Jun 17, 2016 4:54 pm
I had a feeling it was a file causing this when you said only a "particular" program.
I've had that happen before. I opened the corrupt wav file in sound forge, resaved as 44/16, same name, and placed it right back into the same program as before and it worked perfectly after that.

For a corrupt PGM or APS or ALL the road is harder, lol.
User avatar
By hok-2 Sun Jun 19, 2016 5:29 pm
Update:
Nope it's screwed.
It worked for a bit but then it kept crashing again.
So I decided to delete it all and start again.
I didnt realy want to have anything stored on my hard drive that might mess up future work.
Somthing, some where in the sounds, program or song is curupted.