yep no looping so you have to put in FB 00 05 to the track header to loop from 0x05 where the track loading start then repoint all the 0x9* load layer commands by the length byte (you add 3). pretty time consuming.
it also adds a weird single tick into the whole m64's length so if you have an m64 of 4 4/4(0x300) measures for example;
instead of FD 83 00, you get FD 83 01, a tick of 1 is added to the variable timestamp for no reason and it is in all the track headers and master header so you have to subtract 1 from all the variable timestamps.
(a step = 24 ticks)
32nd - half step
16th - 1 step
8th - 2 steps
4th - 3 steps
2nd - 4 steps
whole - 8 steps
32nd note - 12 ticks 0x0c
16th note - 24 ticks 0x18
8th note - 48 ticks 0x30
4th note - 72 ticks 0x48
2nd note - 96 ticks 0x60
Whole note = 192 ticks 0xc0
4 bars = 1 4/4 measure 0x300
---------------------------------------------------
No layer utilization which means no chords, something skelux' musicxml actually did right, so you have to split it into new tracks and waste all the polyphony
instead of using 0x91 to load another layer for the chords or 92/93/94 to load more, it also does some weird transposition so things on low octaves will not play when they go below octave 2, the only good thing is the support for automation and how it optimizes the note data better and supports all note lengths.
Gone for a while.