barhom

I tried to reproduce your example but instead of using udp://:1100 as input for the caller I used a multicast address which has mpeg-ts data on it. After a minute...

Trying to do what you suggested generated the following, In console output of receiver ``` * continuity: packet index: 776,713, PID: 0x0200, missing 6 packets * continuity: packet index: 776,725,...

here is some more debug; f1.ts ``` tsp -v -I file f1.ts -P continuity -O drop * file: initial input bitrate is 3,000,000 b/s * continuity: packet index: 7, PID:...

The two files can be downloaded from google drive [here](https://drive.google.com/drive/u/0/folders/1EDOQ-ftYAAhSK3cP4hAZfwnxrwfJV6Xe). Please remember that the input srt source could have the CC errors coming from the upstream encoder (I'm not sure)....

@lelegard Thank you for going through all of this! > Out of curiosity, which operating system do you use and which version? Debian 11 running in PXE booted environment (all...

I tried something which is at least interesting, On the same host run the following, ``` iperf3 -s ``` and ``` iperf3 -c 127.0.0.1 -u -b 100000000 -R -l 1316...

> I thought that it was just a test to replicate a specific issue on lo interface for simplicity but when you mention 1 Gb/s of "lo" interface multicast traffic,...

@lelegard since you debugged that there was no packet loss, but only packet-reordering issue, would sending it via RTP on localhost help? Does tsduck rtp input have a buffer where...

> I suggest to try to use unicast on lo (ie. `-O ip localhost:NNNN` and `-I ip NNNN`). The processing of multicast has always exhibited strange behaviours on different operating...

#65 same issue?