start point modulation + note repeat = DIV. Error at 3000:00

Yup, this will undoubtedly cause a DIV error screen after a minute or two, especially if you run your sequencer at double speed(like you should! ). I'm so glad I found the issue at least, I lost a ton of work the past month to DIV ERROR but now I'm back in the flow.

Im reporting this for the 2k classic, if anyone can really say this is not the case with 2kxl I might have to make the upgrade finally.

i go apeshit with noterepeat and start offset - via both pad pressure and 16 levels. never had a problem.

i dont run my seq at twice the bpm but ive always found 1/32 notes just fine. i do however occasionally bring the bpm up to 300 and never noticed this.

tapedeck wrote:i go **** with noterepeat and start offset - via both pad pressure and 16 levels. never had a problem.

i dont run my seq at twice the bpm but ive always found 1/32 notes just fine. i do however occasionally bring the bpm up to 300 and never noticed this.

goddamnit! Please tell me this is the XL! I just tested it again and velocitystart/noterepeat is 100% guaranteed a nearly instant crash on my 2k classic. It's such a killer effect, I will go XL today for this and this alone

i am on xl yes
it is probably the coolest deep effect you can get out of the mpc

It is really such an incredible effect. At least for the few minutes at a time that I could pull this off, it was surprisingly expressive and usable. I guess it really depends on the sample.

It's settled, XL purchase is on the way. Either that or a 1000 they seem to be about the same price used these days.

Harmoncj wrote:It's settled, XL purchase is on the way. Either that or a 1000 they seem to be about the same price used these days.

if my xl died i'd have a hard time not considering a jj 1k or 2.5k - hell i do think about it already

Sold my 2k classic, but I can recall doing lots of start point velocity modulation with note repeat and had no issue ever. For the record I was at regular bpm using 1/16th and 1/32nd Q value.

After all this I get another DIV error late yesterday. My machine must be pretty messed up because velocity assignments at all just end up killing the internal sampler. It's too much, if this was common to all mpc2000's, I think I would have heard about it by now.


On the other hand it's never failed me for using as MIDI/sequencer. Sometimes the sequencer/MIDI data will even work after the DIV error. I really just wanted to make things as simple as possible but at least I can count on the 2k as a sequencer.

Have you tried pulling the RAM and testing if it happens with onboard RAM only, or tried different RAM modules?

Maybe the particular RAM you are using can't keep up with the amount and speed of reads this process is creating, maybe a different make/model of RAM module will handle it better?

im with simon - at first i thought ram was bad, then i thought, maybe not, but it could be your ram.

simple, easy to check. just take it out and try to reproduce the problem.

SimonInAustralia wrote:Have you tried pulling the RAM and testing if it happens with onboard RAM only, or tried different RAM modules?

Maybe the particular RAM you are using can't keep up with the amount and speed of reads this process is creating, maybe a different make/model of RAM module will handle it better?

Thats a really good point, for about a week I went back with the stock 2MB internal. It seemed to do a lot better but eventually DIV error was just as frequent as before.

What's nice is this stuff is so cheap I'll keep an eye an out for different types of RAM to test out.

The other thing I tested was if I might get the machine to run better on one of the previous OS versions. It didn't help the situation but I found a little bonus about OS 1.0 and 1.31: the pad parameter edit screens will stick on the pad you've selected in the 16 levels screen. This should make it a lot easier to fine tune.

Harmoncj wrote:The other thing I tested was if I might get the machine to run better on one of the previous OS versions. It didn't help the situation but I found a little bonus about OS 1.0 and 1.31: the pad parameter edit screens will stick on the pad you've selected in the 16 levels screen. This should make it a lot easier to fine tune.

cool find

Great find! That always annoyed the crap out of me

Damn.... That's a killer idea! I haven't thought to try note repeat+velocity mod....

What types of samples are you guys using with this trick? I will absolutely experiment, but I'd love to hear from others as to a nice place to start! I can see a simple drum loop turning into mad glitch heaven with this little gem!