RENDER: ATSC 3.0 Analysis Software

[Trip]

All,

I'm very pleased to announce a public release of RENDER, the RabbitEars NextGen Data Evaluator and Reporter. Most of the relevant information can be found here:

RENDER [RabbitEars Knowledge Base]

I've written the software for the Linux command line, but it's open source (GPLv3) and should be possible to compile on other platforms as well. Note that this is a very early experimental release. I can make no guarantees about the accuracy or functionality at this time.

I've also provided a link to view the output from all those files that folks have heard me chasing down over the past few weeks. As I continue develop the code, I'll periodically update and replace those files with versions using the newer code. Note that the heaviest testing I've done has been on the three DC-area signals and the one Baltimore-area signal, as they're local to me, but WHUT is the only station that I believe I have seen with BPS, which makes it particularly interesting.

By the way, I'm still looking for data from a number of stations to help with my testing and validation. The complete current list is now found below the instructions on this page here:

Capturing 3.0 Data [RabbitEars Knowledge Base]

Looking forward to feedback and opinions. Hope folks find it interesting and/or useful!

- Trip

 

[Trip]

For folks with no local 3.0 signals, or who want to test out the Dev-level functions, or who want to see a signal with BPS in it, I've added a folder of test data from three of my four local 3.0 signals that can be downloaded and run through it.

- Trip

 

[zippyfrog]

Thank you for working on this project! I love the data side of things. The current RabbitEars website never showed the breakdown of how much data each ATSC 3.0 channel was using for WGN, WBBM, WMAQ, WFLD, and WGBO. I am curious though - is the data I see there an average over time or some other calculation? I see the total as being 41.48MB. I didn't think a single frequency could handle that much data.