Situation (hypotetical). I have (besides the other) two MIDI-devices: sequencer (file reader) and display. Reader reads the text from SMF, the song lyrics. But it can't display it, it can't send it to display, there no exist such messages.
Actually, here is a tricky way to do that, according to MIDI Specifications. We can map meta event "FF 07 ll text (Cue Point)" to MTC RT Cueing message "F0 7F id 05 0E el em nibblized_text F7 (Event Name) F0 7F id 05 0B el em F7 (Cue Point)" (ll - text length, id - device identifier, el, em - event number. Wow!)
Simple map exists for meta "FF 58 (Time Signature)" = SysEx "F0 7F 7F 03 02 (Time Signature)".
But how about the lyrics?
So there is the question: why meta-events are not SysEx-MIDI-events? What is the philosophy?
Actually, here is a tricky way to do that, according to MIDI Specifications. We can map meta event "FF 07 ll text (Cue Point)" to MTC RT Cueing message "F0 7F id 05 0E el em nibblized_text F7 (Event Name) F0 7F id 05 0B el em F7 (Cue Point)" (ll - text length, id - device identifier, el, em - event number. Wow!)
Simple map exists for meta "FF 58 (Time Signature)" = SysEx "F0 7F 7F 03 02 (Time Signature)".
But how about the lyrics?
So there is the question: why meta-events are not SysEx-MIDI-events? What is the philosophy?
0
Undo
Votes
I think it was originally assumed that the device playing the SMF would be the device displaying or otherwise using the meta-events, so there would be no need to transmit them via MIDI. Obviously, that assumption has turned out to be wrong, at least sometimes. And the fact that there exist universal sysex messages for a few of them suggests that this problem has been noticed. Perhaps a single universal sysex that could wrap any meta-event would have been a better solution.
- Page :
- 1
There are no replies made for this post yet.
