2.0.2.0C, this version has introduced a new bug:
- Wrong presets are played when changing soundfonts during playback
And, heres the usual batch of bug findings I discover through my testing, originating from earlier builds:
- Pressing "x" on the "save midi file changes?" dialog box acts as a "No" button rather than "Cancel" (Since 2.0.1.1)
- Clicking "Remove surplus events (marked) during playback causes slower tempo and various other glitches when playing (Since 2.0.1.2B)
- Click and dragging the mouse up/down quickly on the pianoroll's on-screen piano right after going to the piano roll tab generates an error (Since 2.0.1.2V)
- No note off events are seen in the event viewer when note on events are hidden (Since 2.0.2.0B)
Anyway, with the undo bug, its still not fixed yet, but further investigation seems to reveal the cause for the crash is a little different than I thought (well with 2.0.1.2R+ anyway).
What I've done to reproduce this crash is, using the same autoclicking program, go to the event editor on a track with more than 4k notes, and autoclick at the same rate of 1 per 1/100sec, with the mouse positioned over the delete events button until it crashes many events later.
This time, I tried autoclicking delete about 100 times and giving 10 second breaks in between, and apparently that caused the event list to flash for several seconds, and if I kept pausing and waiting out the flashing period occasionally, I'm not getting the crashing it seems, as opposed to continuously autoclicking for a long time. Also if I slow down (underclock) my cpu, the crash seems to trigger quicker. Because of this, I'm guessing the crash is occurring due to an illegal attempt of trying to delete the next event while the previous event is still being deleted.
DLS files now have a fade out with held notes but it's miles too long and off from how it's supposed to sound.
Also as a quick suggestion, in the event editors "find and replace" section, I'd like to see a list box beside each of the three input boxes allowing the user to select between "equal to", "less than", or "more than" for the "note #", "velocity", and "length".
Edit: Oh, and along with the new "Preset not found" message, it may be helpful to have something like this: An option called "When encountering missing preset," and give the user the option to choose between "Ask me [default], "Automatically pick closest preset", "Automatically pick closest preset ..and mute percussion channels", "Automatically pick closest preset ..and use GM for percussion channels", and "Always use GM".
This, and here's
a concept of how I think the "set preset" functionality/dialog can be improved.