(1) Something goes wrong in the last column. The value is a bit weird. E.g. if I calculate 1713*188*8 I get to 2,576,352 bit/s = 2.58 Mbit/s. Note how your result is 2[,576,]352? If I do the calculation for the video data: 965624*188*8 / 1000 / 1000 = 1452.298496, note how your result is 1452.[298]496? It seems it simply cuts out 3 chars in the middle to get to the result?
Or I don't understand this at all. Evidently I'm confused by it. 😎
(2) There's also a magical "pid 2000" which doesn't exist in the original stream. I guess it's a way to say "Totals"?
(3) The output is unaligned which makes it hard to read.
In the example "pid 0000" (PAT) and "pid 040e" (no idea) have minimal amount of packets/s, but it looks like it calculates a way higher Mbit/s than for the video stream with "pid 100e". Having 3 fractional digits adds to the confusion with a thousand separator.
(4) in the 2nd value column it uses "kb", and "mb". That's highly confusing too. "small b" always means bit, but here it seems to refer to Byte. Those units should be capitalized. (personally I also would prefer MiB and KiB (aka power of 2 units), but that's another story. 😎) Similar it also should be "Mbit", or probably "Mbit/s" even for the last column.
(5) It somehow should make more clear (e.g. in the usage output) that this is the "processing performance" of dvbtee, and not the actual stream bitrates of the input file (e.g. I do dvbtee -b < some_recording.ts)
The bitrate display is slightly confusing:
(1) Something goes wrong in the last column. The value is a bit weird. E.g. if I calculate
1713*188*8I get to 2,576,352 bit/s = 2.58 Mbit/s. Note how your result is 2[,576,]352? If I do the calculation for the video data:965624*188*8 / 1000 / 1000 = 1452.298496, note how your result is 1452.[298]496? It seems it simply cuts out 3 chars in the middle to get to the result?Or I don't understand this at all. Evidently I'm confused by it. 😎
(2) There's also a magical "pid 2000" which doesn't exist in the original stream. I guess it's a way to say "Totals"?
(3) The output is unaligned which makes it hard to read.
In the example "pid 0000" (PAT) and "pid 040e" (no idea) have minimal amount of packets/s, but it looks like it calculates a way higher Mbit/s than for the video stream with "pid 100e". Having 3 fractional digits adds to the confusion with a thousand separator.
(4) in the 2nd value column it uses "kb", and "mb". That's highly confusing too. "small b" always means bit, but here it seems to refer to Byte. Those units should be capitalized. (personally I also would prefer MiB and KiB (aka power of 2 units), but that's another story. 😎) Similar it also should be "Mbit", or probably "Mbit/s" even for the last column.
What I did expect to see:
(5) It somehow should make more clear (e.g. in the usage output) that this is the "processing performance" of dvbtee, and not the actual stream bitrates of the input file (e.g. I do
dvbtee -b < some_recording.ts)