japanhas.blogg.se - Open source transport stream ccerrors

Indeed, that's also what I believe based on my findings. The way you explain the problem, it looks like the two streams from 239.1.1.1:4001 and 239.1.1.1:4002 are getting mixed while they are in fact two different transport streams. I'm measuring the CC errors at the output of each TSP processes: * continuity: packet index: 31,472, PID: 0x02D0, missing 12 packets * continuity: packet index: 31,460, PID: 0x02D0, missing 13 packets * continuity: packet index: 31,459, PID: 0x026C, missing 13 packets * continuity: packet index: 31,438, PID: 0x02D0, missing 9 packets * continuity: packet index: 31,437, PID: 0x026C, missing 9 packets * continuity: packet index: 31,403, PID: 0x02D0, missing 7 packets * continuity: packet index: 31,402, PID: 0x026C, missing 6 packets * continuity: packet index: 31,346, PID: 0x026C, missing 15 packets

* continuity: packet index: 31,292, PID: 0x02D0, missing 6 packets * continuity: packet index: 31,291, PID: 0x026C, missing 6 packets * continuity: packet index: 31,249, PID: 0x026C, missing 6 packets * continuity: packet index: 31,248, PID: 0x02D0, missing 5 packets * continuity: packet index: 31,221, PID: 0x02D0, missing 13 packets * continuity: packet index: 31,220, PID: 0x026C, missing 12 packets * continuity: packet index: 31,200, PID: 0x02D0, missing 9 packets * continuity: packet index: 31,199, PID: 0x026C, missing 10 packets * continuity: packet index: 31,167, PID: 0x026C, missing 7 packets Switch to TSDuck-NIC1, and Switch to TSDuck-NIC2. We will call them NIC1 and NIC2.Ĭonnection will involve a switch: Playout-NIC1 to Switch.

One Linux server with two different physical Ethernet ports used as TS inputs/outputs.

One MPEG2-TS playout/streamer, aka "sender", with one physical Ethernet ports used as TS output.

However, as soon as both TSP1 and TSP2 are running at the same time, the Continuity Errors Count skyrocket like crazy, from the very first second the two TSP process run concurrently.Įquipment involved to easily reproduce the problem:.

Likewise, if only TS2 is launched, not a single CC error is detected either.

If only TS1 is launched, not a single CC error is detected.

We will call these instances TSP1 and TSP2.

When two TSP instances with the same multicast output (but different ports obviously) are running on the same network, the number of Continuity Errors are skyrocketing.

Bug description:Ĭontinuity Errors Count skyrocketing when two TSP instances with same multicast address output (but different ports) are running on same network Hi thought I opened a bug ticket mistakenly earlier on today, therefore I closed it.īut it seems I actually have found a bug, so I am re-opening one.