I CONTACTED AKAI ABOUT NOTE MOVE BUG

note move bug or move event whatever.. i cant find anywhere on this forum of that exact bug i got with the splash screen error... or the mpc1000 mutes a sequence or part of it when using move event. i saw a post where i replied back on the subject but no luck here finding this. i wanna show akai its not jsut me with this error on move event. some of u guys knows how it sucks to loose a track due to an os glitch.. i lost many just tryn to find a fix when it does glitch all in all i always end up saving the glitch with the track. it sucks. so help me better my bug report to akai we can start here in this thread telling them the bug of this move event..that way i can just link them to this thread.. no swearing or talking smack if they read this..akai are people to u know. so treat our geust with respect please

haha bug reporting to akai? that's a good one, i've got more:

write a letter to santa claus
email the president
send telepathic messages to Audrey Tautou
pray to a god
visit a retirement home
ask yourself an important question and then take a whole lot of pills
fill your ears with plaster and attempt to communicate with a blind man

yeah, i've had this bug and i just don't use move ever. i guess it's fixed in JJ, but i'm back in 1.07.

copy > paste > delete works for me.

EDIT: and yeah, i've emailed akai about this like 3 times. once a long time ago they asked for a sequence that had been corrupted like this, which i sent. still, i think those people got fired, no responses lately.

i haven't had this problem yet - which OS are you using?

is it only when moving notes? or all events - midi stuff and q link automation included?

despite antonym's infectious optimism he's right.
akai care more about profit margins than sticking
to the 'professional' label they so haphazardly
stencil onto their equipment.

but i managed to get through to audrey with my superior
psychic hook-up and she wanted me to ask y'all to stop calling.

ya it happens when using move event any event really and ull get this bug make sure u have a sequence made so u can tell that u lost a track lol.

ascdi wrote:i guess it's fixed in JJ, but i'm back in 1.07.

why would anyone do this?! even 2.10 is better than 1.07, not to mention jjs free v3...

Antonym wrote:haha bug reporting to akai? that's a good one, i've got more:

write a letter to santa claus
email the president
send telepathic messages to Audrey Tautou
pray to a god
visit a retirement home
ask yourself an important question and then take a whole lot of pills
fill your ears with plaster and attempt to communicate with a blind man

Yeah, I'm really happy with 3.06 (free). The new functions when chopping is worth it alone.

heres a off topic question... does the 3.06 have all the current 2.01 bugs fixed?

i quit 2.10 because of the save bug, the move bug (this thread) and the fact that you could not step forward or back in step edit. seriously, shift-left and right do nothing. it's kinda hard to step edit when you can't step. before they went silent akai told me that was probably because the 2.10 was mainly the 2500 OS and it has dedicated step buttons. i was pretty surprised at that they would FORGET to make a feature work, but little did i know that i was spoiled even expecting them to answer their email. oh well.

anyway, i am not a fan of some of the changes to the JJ os, even though i can see why you'd love it and it's certainly impressive-- it's just not for me.