From: Chris Cannam <cannam@al...> - 2003-12-17 16:48:02
Just noticed the stop() command issued from GUI to sequencer was
changed from a call to a send some while ago.
This appears to be the cause of a problem I had a while back and that
has been plagueing me again recently of the recording segment
sometimes remaining on the canvas after you stop recording, generally
resulting in a crash when you click on it. Seems that after the stop
command was sent, the sequencer continued sending data for a bit
until it had actually got around to processing it, and the GUI was
treating that as valid incoming recorded MIDI and displaying it even
though it had already finalised and shown the segment resulting from
the real record.
Anyway -- any good reason that call was changed to a send, or just one
of a parcel of similar changes attempting to avoid bogging the
sequencer down? I've changed it back now, but please speak up if
this bothers you.