Hello Jeffrey, i wonder if you or "someone" have interest in helping me finish "bug out" my online midisequenser.
It is very "homerolled" coding going on.
But i think it has the right ideas going for it, sure i would like to finish it, and most of all somekind of interface to read and write midifiles.
For now i just hogged into someone else code to import midi but have it read and write midifiles would of course be a mainfeature, i know from doing in pascal eons ago how akward the format is to handle and not that keen on doing it again.
I have a layout of an editor but it is not finished and riddled with bugs.
I just do not have the gist/inclination to finish it and work it thru, without someones further input..
WARNING, it is riddled global variables, but the code is divided into rather small functions and files for good or worse.
Should probably make a structural file that tells in what files each function are and what they do.
"Even a list on what bugs and features to fix first would be helpful" implementing to many parts without really locking them bugfree and it get problematic with what to finish..."
Your project is what one would hoped for would be part of products, midi specs.
Do you have possibility to write in "a message" add a comment "for nonedocumented messaging outside midi standard" can't remember what they are called.
Can you chose separator, that is a nice feature because every programming language use different.
Of course timing for such a project of listing messages if of no use, if you could come up with a standard for midi documentattion would be nice.
Because reading those old manuals totally drive me nuts their vv ww xx .....
Range is a nice word.... and looks better in decimal....
Manuals should not be about deciphering....
So messages grouped within headers that describe the functionality.
Then we could have the messages for devices specified in a database....