bug in editing / saving sequence

Has anyone else encountered a bug where
-you edit a sequence by moving some events in time
-you save it to the disk
-when you reload it, it is different (there are small errors around the places you edited)?

I have a piano performance that I recorded in real-time, and it has a lot of long notes in it because I recorded it with the "convert sustain pedal to duration" option turned on (see the MISC page).

I edited it in the STEP EDIT window, by grabbing say three notes in a row and moving them 10 or so ticks later in time. I played it back to verify that the edit was good. I then saved the sequence out. When I load it back in, the notes I edited have been cut into two pieces and the second piece is a very short note (say duration 50 ticks or less). It sounds very different when played back -- the note cuts off abruptly.

At first I thought I did something wrong, so I tried this again starting from the raw realtime track I recorded. I did the edit again, played it back to be sure it was right. I then saved it and loaded it to another sequence in memory. I compare the two in the STEP EDIT window and they are different, right at the edit points.

Anyone else seen this?

-illiac

I beta tested some of the earlier OS's and several bugs in the sequencing section was noted, some very similar to your own i.e. sustained notes being chopped anywhere from value >600 down to <60. Also notes duplicating themselves at the same edit point. These were only two of several bugs I came across while beta-testing. All my reports were either ignored or deemed too incidental for any fix by the OS boffins. Needless to say I felt any input I had given had just been a waste of time and decided not to continue with the beta testing.
Hopefully, there maybe a new OS on the horizon that will eradicate ALL bugs that have surfaced since OS 1.71 but I wouldn't hold my breath.

Thanks for yours response.

I run into this bug a lot these days and I can replicate it easily. I sent a bug report to the support email address at akai but no response... I'll probably give them a call because it's making it hard for me to work at the moment. If I could just find a workaround...

-illiac

illiac wrote:Thanks for yours response.

I run into this bug a lot these days and I can replicate it easily. I sent a bug report to the support email address at akai but no response... I'll probably give them a call because it's making it hard for me to work at the moment. If I could just find a workaround...

-illiac

Bug reports go to a different address then the support address. You'll want to send them to

[email protected]

illiac wrote:Thanks for yours response.

I run into this bug a lot these days and I can replicate it easily. I sent a bug report to the support email address at akai but no response... I'll probably give them a call because it's making it hard for me to work at the moment. If I could just find a workaround...

-illiac

Again when I noted that some bugs were hard to replicate and only seemed to be very intermittent and random, Akai informed me that if they could not be replicated or were random, then that would not constitute as being bugged(??!!). Therefore they could not act if the evidence was not in front of them.
I'm afraid that's computers and technology for you. An imperfect science.

well, in this case I can put evidence in front of them. I've got a sequence that does this on cue with a certain edit. I'll try to get it to them.
thx,
-illiac

OK, I sent a bug report to them. In case anyone else feels like verifying this, I've created a simple test case that shows the bug. Well, it shows a bug anyhow, I think it's the same as the one affecting my piano edits.

Go to an empty sequence.

Change the number of bars to something big, say 100. This eliminates the possibility that the truncation is due to the sequence length.

In STEP EDIT (any track), create two notes for the same pad, say 37/A01. The first note at time 001.01.000 and the second at 002.01.000.

Using the keypad, change their durations to 9000 each. I do this for the first note (001.01.000) first, then for the second note.

SAVE the sequence.

LOAD the saved sequence.

The durations of the notes are now 3840 and 5160 respectively.

--

long duration notes like that don't come up in a drum sequence, but in piano stuff where you're holding the sustain pedal for a long time (and using the "Convert sustain pedal to duration" option) it can happen. Anyhow the bug also shows up with much shorter durations -- less than 1000.

-illiac

Yip. Exactly as I pointed out to Akai during my beta testing! Still hasn't been fixed.

[tried to draw some pictures but they are f*cked up. oops.]

-illiac