My instrument (an organ) produces MIDI files which use multiple channels within a single track to hold the data of each keyboard and the pedalboard. For example, the pedalboard is always channel zero, and the keyboards go up from there.Since this software supports color-coding by track and not channel, I've been looking into using a MIDI Editor to move the data from channels to tracks. When I do and I open the resulting file in SeeMusic, it reads the data in each track sequentially, not simultaneously. For example, a performance lasting one minute, if I modified it to use two tracks, will take two minutes afterward. First, it will play one track, followed by the other (it's seeing the tracks fine, as the color-coding is correct). I can confirm that it is correct by opening in a third application, like Audacity, and the file is read fine, but in SeeMusic the same file is read incorrectly (see video for evidence of this)I've produced a short video below demonstrating the issue on a very minimal MIDI file of just a few seconds.I'm using SeeMusic 1.16 and MIDIEditor 3.3.0 (the newest, as of when I checked today).Video: https://drive.google.com/file/d/126DnGd-Kr_lHzAaxZMj0GV-vi46yVMW2/view?usp=sharingI am really excited about the possibilities of this software, and I understand the challenges in a new piece of software. As a developer myself (for work) I'm impressed with this app already and can see immense potential here! So I'm submit this in hopes of helping improve things.If you have any further questions or need clarification or another sample, feel free to ask.