You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing implementations of CPacketStream and CPacketQueue don't care about probabilistic reordering of UDP packets. Normally it should care about sequence numbers to process audio frames on the right order.
The text was updated successfully, but these errors were encountered:
This is actually the job of the repeaters/hotspot.
Indeed, even if xlx reorder udp packet before forwaring them to clients, there are no
garanties that they will not be scrambled again on their way to the final destination.
I cannot be agree with your point. In case when xlxd does transcoding it changes sequence numbers from D-STAR’s resolution of 21 numbers per sequence to at least MMDVM’s resolution of 256 numbers per sequence. In this case you breake a sequence. Also AMBE has a statefull algorithm and you have to provide frames to it in a proper sequence.
Existing implementations of CPacketStream and CPacketQueue don't care about probabilistic reordering of UDP packets. Normally it should care about sequence numbers to process audio frames on the right order.
The text was updated successfully, but these errors were encountered: