> > So the question is what to do about the SET_TEMPO event? I think the most > reasonable at this point would be to both handle it and pass it on to the > callback, even if that would disable the callback's possibility to > override/handle the set_tempo event itself. >
Yes, but a more general question is what to do about all meta-events (EOT and SET_TEMPO included). Just because we handle these two events specially in fluid_midi.c doesn't make them any more special, as you pointed out on the ticket. So I think it only makes sense to either forward all meta-events, or none of them. (This would probably end up as a special case in the code for EOT and SET_TEMPO, but from the API standpoint those two events are not special cases.)
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
