MIKMIDISequencer stops recording almost immediately after starting if its sequence is empty.

[armadsen]

See the MIDI Files Testbed project in the 1.1 branch to reproduce this. Maybe I've screwed something up...

[armadsen]

It also plays a single piano note when you start recording. I haven't investigated at all, but perhaps that's a pre-roll problem?

[armadsen]

I pushed a fix for this. I'll let you close this if you think the fix looks OK. It's simple enough that I worry I overlooked something. I made a new issue #46 for the piano note at the beginning problem.

[armadsen]

We discussed adding a property to make this configurable. The thinking is that some apps may want recording a new track in an existing sequence to stop when the end of the sequence (ie. longest track) is reached. The default for this property would be NO (ie. doesn't stop).

I think we should also extend the length of an empty sequence to something reasonable.

[armadsen]

I hit into an issue related to this change today:

• Create an MIKMIDISequencer
• Add a track to its sequence with 20 notes, one on each beat.
• Set the sequence length to 16.
• Start recording
• When the 17th beat is played (at timestamp 16), rapid clicking is heard.

During recording, the sequencer continues processing without stopping when it hits the end of its sequence's length. The issue is that if there's a note right on the timestamp for the end of the sequence (16 in this case) it is repeatedly scheduled every time through the processing loop.

[armadsen]

Closing because I can no longer reproduce this. I believe it was fixed by
0e287cc.