Bugs in 4.25/4.26

Has anyone had their mpc skip one beat towards the ends of a sequence? This happens once or twice every 5 minutes or so...really bad bug, as it puts the mpc out of sync.

Also, there is still the occasional truncation bug, IE: The sample only plays to one half of it's full length if it's as long as the sequence and the sequence contains more than 3 tracks playing samples.

Maybe my MPC is cursed?
I practically needed an exorcist when it would combust into static. Thank god I haven't had that problem lately...but any error affecting time syncronization cannot be good for people who use their MPC with a computer or external sequencer....

Damn, that sounds messed up. It might be your mpc.....

i am having problems with copy and paste in the step-editor

also the move function has the problem

like this

001.01.00 (37)
001.02.00 (37)
001.03.00 (37)
001.04.00 (37)
001.04.48 (37)

copy the note on 001.04.48
paste it on 001.02.48

what happens is

001.01.00 (37)
001.04.48 (37)
001.02.00 (37)
001.03.00 (37)
001.04.00 (37)
001.04.48 (37)

all sound stops but the counter keeps on running. so i suppose its still running.

Greetings.

nope mines is all good beats alllday with no problems

Does anyone think this could be a result of my third party RAM? I have a stick of SHIKA RAM 256 SO DIMM...should work alright. I can't figure out what else could be causing these errors, as this is the second MPC i've got....replaced once already. Do hardware errors occur often with the 1000's? I know AKAI is a less than praised company...but I thought the MPC was supposed to be as stable as technics...

-ED

Has anyone had their mpc skip one beat towards the ends of a sequence? This happens once or twice every 5 minutes or so...really bad bug, as it puts the mpc out of sync.

mine just stuttered.. but i noticed the song length on my korg ran out... so it wasnt an mpc problem at least..

I have original akai mem in mine

its so wierd.. i've never had ANY of the problems people post about in here.. maybe cause i have a newer 1k? i dunno

hmm, nope, mine is about two months old.
I wonder if this batch is defective though, the last one I got had another problem...

i get a weird bug when i record on one track, leave record on, and then switch to another track. the stuff in the first track continues to get recorded over...it's strange, but i do'nt know a lot about it yet.

dood too bad jj only speaks japanese

too bad we don't speak japanese

As far as missing the odd beat towards the end of a bar; I've had a very short stuttering affect as well. Now to something that really miffed me the other night , after spending time chopping up a nice sax run I went into edit mode and timestretch, now manual tempo detect is working quite well, then i hit auto, and got the unknown function errors and illegal this and that, so i lost my work as the i was locked out. To check i turned on loaded a beat hit tempo auto detect, and same thing fellows. Don't use AUTO.

FLOOD wrote:also the move function has the problem

like this

001.01.00 (37)
001.02.00 (37)
001.03.00 (37)
001.04.00 (37)
001.04.48 (37)

copy the note on 001.04.48
paste it on 001.02.48

what happens is

001.01.00 (37)
001.04.48 (37)
001.02.00 (37)
001.03.00 (37)
001.04.00 (37)
001.04.48 (37)

all sound stops but the counter keeps on running. so i suppose its still running.

Greetings.

confirmed.
and it can mess up the other tracks in the seq. and undo does not fix the problem.
i also suspect midi grid edit to sometimes mess up the sequence. not 100% sure though.

an other bug is that while a seq is playing, the pads won't produce sound if the selected track is muted.

volo -> i am positive that what you described are not hardware issues. they are either software bugs or user error. (for problem one, are you sure all your samples are trimmed properly: no long silence at the end ?)

truvc wrote:

FLOOD wrote:also the move function has the problem

like this

001.01.00 (37)
001.02.00 (37)
001.03.00 (37)
001.04.00 (37)
001.04.48 (37)

copy the note on 001.04.48
paste it on 001.02.48

what happens is

001.01.00 (37)
001.04.48 (37)
001.02.00 (37)
001.03.00 (37)
001.04.00 (37)
001.04.48 (37)

all sound stops but the counter keeps on running. so i suppose its still running.

Greetings.

confirmed.
and it can mess up the other tracks in the seq. and undo does not fix the problem.
i also suspect midi grid edit to sometimes mess up the sequence. not 100% sure though.

an other bug is that while a seq is playing, the pads won't produce sound if the selected track is muted.

volo -> i am positive that what you described are not hardware issues. they are either software bugs or user error. (for problem one, are you sure all your samples are trimmed properly: no long silence at the end ?)

Does this happen all the time? i havent loaded up 4.25 or 4.26 yet, but i wanna finish a beat and i do use step edit alot. Ima try it out later but feel free to respond