miditrack stepedit DANGER!

when i edit midinotes in stepedit weird things happen.
example: i wanted to move a note from 04.00.05 to 04.00.01.
the list looked like this after moving:
004.01.01
001.01.01
001.01.51
001.02.01
001.02.51
001.03.51
.
.
instead of starting on the "one" (should have looked like this:)
001.01.01
001.01.51
.
.
04.01.01

a few minutes ago i moved a midi note (track6)in step edit and the whole sequence was f.... up. several tracks didnt play back anymore. only first basedrum on my drumtrack was played back e.g. the rest was muted.
then i saved the entire memory. while saving, the mpc froze. had a lot of samples in memory and didnt purge before to avoid more problems.
so i turned it off after a while and on again. fortunately only some samples were missing and i had the sequence + progs saved. the tracks still didnt play back.so trying to find the reason for this i deleted one track after another and found track 5 causing all this!?but i edited the note on track 6 !
i checked all events on track 5 but couldnt figure out what was causing the mutes (no track mutes recorded).
something went wrong there..

So be careful with the stepedit function and save your work frequently.

anyone else experienced strange things with stepediting?

os v1.21?

v1.20

Yeah, I rarely use StepEdit at all so am not the best person to answer this question. The reason I don't use it is because I have problems with it....


Any reason why you're not on the latest OS? May solve some problems???

im still on os 1.20 because my daw is synced to mpc by MidiTimeCode,
and i read about problems on vers.1.21 with mtc.
i hope this issue will be fixed with the next update.
i can live with some small bugs but this one really destroys the
workflow and could destroy the whole sequence. saving and restarting the mpc doesnt work here.