Yes, this was exactly my point of giving the responsibility to the client. If the FIFO behavior of the sequencer is documented, then the client can decide the order. If the sequencer does its own custom ordering, the client looses control.
Am Mi., 11. Dez. 2019 um 19:14 Uhr schrieb Marcus Weseloh < address@hidden>: Ah, I wasn't aware that the player doesn't use the sequencer internally. Still, the custom ordering of events might be at least surprising to sequencer users. And if I understand corrently, then it's a change of existing behaviour. I guess I still haven't understood whose problem you are actually trying to solve. If it is a problem specific to your usage of the sequencer, couldn't you ensure your preferred ordering of simultaneous events in your client application?
Just one more thought... one drawback that I see with the ordering you propose: you currently have the option to choose a different order in your client application because we currently process events in the order they were added. If we change Fluidsynth to force a different order, sequencer users would not be in complete control anymore. Is the problem you are trying to solve big enough to justify that?
Cheers Marcus
_______________________________________________ fluid-dev mailing list address@hiddenhttps://lists.nongnu.org/mailman/listinfo/fluid-dev
|