Thierry Lelégard

> Maybe I'd just pre-process them all and remap the PIDs to a common scheme? Probably, yes. There are all necessary plugins to rename TS, services, remap PID's, etc. If...

This is the intended behaviour, the same for all tables, not only the NIT. The textual dump and the XML/JSON representations work are different levels of abstraction. You may see...

This is not a matter of NIT, this is a matter of level of abstraction for all tables. The XML/JSON representation targets the table logical level, not the binary implementation...

> offer a view of the tables as they are generated. That exists, this is the default textual description from `tstables`. You can also save the binary sections in section...

> what is the end char of the binary data sent over udp There is none. For two reasons: 1) binary data, 2) UDP. There can be no "end char"...

Hi @AmaralVini A transport stream is a suite of 188-byte packets, nothing else. The input plugin is in charge of extracting the 188-byte packets from the input data, depending on...

OK, but this still does not make sense, technically speaking. The 16-byte Reed Solomon trailer is the outer FEC layer of a broadcast modulation system such as DVB-T/S/C, ISDB, ATSC...

> > This IP output format could be an enhancement for tsduck? > > Everything is possible and, over the years, TSDuck integrated supports for multiple bugs or insane usages...

> Option --rs204 has been added in the ip output plugin. Version 3.31 is just out. This feature was the last one to make its way in 3.31.

The 16-byte trailers in the input file are, in your case, part of the ISDB-T modulation layer and are not part of the transport stream layer. `tsp` is a transport...