Closed atsushieno closed 3 years ago
It does not make sense to split predefined macros such as c
, d
, e
..., n
, CC
, B
to have another name for MIDI 2.0 primitives, therefore we would rather unify everrything in MIDI 2.0 and implement MIDI 2.0 -> 1.0 converter in ktmidi in the end.
Although, we will have to rewrite default-macro.mml
to enhance features in MIDI 2.0 mode anyways, it would suffice if we first create such updates first, switch default macros depending on --midi2(x)
option at command line, then implement converter.
Now that mugene-ng is going to generate MIDI 2.0 UMP based song files using
Midi2Music
class in ktmidi, it makes more sense to support MIDI 2.0 primitives beyond MIDI 1.0 primitive operations. It should be fairly doable.