The status.json number is not an instant at all. Read the message from Claude. It displays a seesaw pattern because of the counter reset about every second.

$ while :; do rate=$(curl -sS $TUNERIP/status.json |
jq -r '.[] | select(.Resource == "tuner3") | .NetworkRate') && printf '%s %s\n' "$(date ...

It seems the NetworkRate as reported by /status.json is very different from /tuner<n>/debug in net: bps=

Shouldn't they be the same?

Quoting Claude:
NetworkRate should be a rate (bytes/sec since last poll, or over a rolling window), not a counter that resets on an internal ~1s tick independent of ...

The problem is ATSC holding back modern codecs on ATSC 1.0 for the purpose of selling us ATSC 3.0.
Is seems they've never heard of the OSI model.

I can guarantee you that people at the FCC read everything that gets filed and there are subject matter experts across the entire range of things they need to deal with from engineering to law. If there is something they need additional information on, they will arrange to get it.


If this were ...

It might have been a good time to point out lack of familiarity with the OSI model by ATSC 3.0 proponents.

I hope the plan is not to go with ATSC 3.0 which is DOA.

I am surprised seeing ATSC 3.0 infrastructure being build - AVSend. How did Silicon Dust end up on the wrong side? Advertising?

Thanks for writing the app. Super useful.

It would be nice if we could get some history in addition to the instantaneous values in order to better catch momentary drop outs.

Maybe a histogram or a lighter color for the current bar above the minimum in the last few seconds ...

Anybody using this functionality or just pulling streams via http?