First, thank you for building this! Due to Comcast's TS/MP4 migration, I'm moving from tivodecode to this version, and had a problem with error output. Currently, in one mode, I use the stderr output to determine how complete the processing is. Verbose mode (-v) puts out a progress line per packet:
where the first block is the number of bytes processed, so I can easily compute how far processing is complete.
When I use -v with tivodecode-ng, it puts out a much longer stream for each packet in both TS and PS, resulting in multi-gigabyte files. So in this pull request, I demoted the Packet debug info to VVerbose and added the same reporting <FilePosition> : stream_id: xx block_no: dd to the TS reporting.
If you prefer the packet info to be in Verbose mode, I could instead create an independent Progress option that would just report the data above. Let me know.
First, thank you for building this! Due to Comcast's TS/MP4 migration, I'm moving from tivodecode to this version, and had a problem with error output. Currently, in one mode, I use the stderr output to determine how complete the processing is. Verbose mode (-v) puts out a progress line per packet:
where the first block is the number of bytes processed, so I can easily compute how far processing is complete.
When I use -v with tivodecode-ng, it puts out a much longer stream for each packet in both TS and PS, resulting in multi-gigabyte files. So in this pull request, I demoted the Packet debug info to VVerbose and added the same reporting
<FilePosition> : stream_id: xx block_no: ddto the TS reporting.If you prefer the packet info to be in Verbose mode, I could instead create an independent Progress option that would just report the data above. Let me know.