On Tue Feb 6 17:51:36 2024 +0000, Rémi Bernon wrote:
I didn't mean calling every single stub, as you say they indeed do nothing (and are simply there to fill the vtable). But this midi track creation function is still never called, and it's not so much work to simply reorder the changes to have the midi parser first and make it call it when it is added.
this is awkward no matter how i structure it. the best I can do is move parsing the midi header into the stub commit, so I can know # of tracks, then create corresponding number of stub midi tracks for the segment.