Analyzing Program Details with Power Query

[NickBurns]

I've suddenly started getting signal impacted shows and I'd like to analyze the details of the recordings to see if I can determine a pattern (below is a screenshot of the info I'm referring to).

The information is presented in JSON, which Power Query is very good at reading.
I can copy and create a JSON file for each recording but that's a bit cumbersome.
A couple of questions:

1. How do I connect Power Query to get this information?
2. How can I do it remotely?
3. From the image below, the warning states that the show was 100% impacted by signal issues. - How is this calculated/determined?
4. From my USMC captain motto: ITABWODI - Is there a better way of doing it?

[NickBurns]

Any help at all?

[chDVRuser]

@NickBurns

From the image below, the warning states that the show was 100% impacted by signal issues. - How is this calculated/determined?

Improvements to recording statistics

Understanding why a recording is pixelated or has strange artifacts is an ongoing issue that has caused a lot of frustration for users over the years. Figuring out why this is happening has always been difficult and has involved guessing and fiddling. We've been logging [SNR] log messages for every HDHomerun-based recording for a while as we experimented with different ways to quantify if a recording had issues or not and how bad it was. We recently had a breakthrough that has allowed us to rep…

[NickBurns]

Thanks, that is helpful, though those entries are in the log files and not those json files that the individual shows have.

the DVR is producing these json messages. somehow I think I should be able to access them.

[chDVRuser]

You can view them in the recording file json.

and view the recorded file json

or view it in your browser at http://127.0.0.1:8089/dvr/files/7282
or retrieve it using a curl command curl http://127.0.0.1:8089/dvr/files/7282

  "SignalStats": {
    "SS": {
      "Initial": 97,
      "Last": 97,
      "Min": 97,
      "Max": 97,
      "Sum": 90016,
      "GoodCount": 928,
      "BadCount": 0
    },
    "SNQ": {
      "Initial": 100,
      "Last": 100,
      "Min": 100,
      "Max": 100,
      "Sum": 92800,
      "GoodCount": 928,
      "BadCount": 0
    },
    "SEQ": {
      "Initial": 0,
      "Last": 100,
      "Min": 0,
      "Max": 100,
      "Sum": 92700,
      "GoodCount": 927,
      "BadCount": 1
    },
    "BPS": {
      "Initial": 0,
      "Last": 3836704,
      "Min": 0,
      "Max": 3990112,
      "Sum": 3486463008,
      "GoodCount": 927,
      "BadCount": 1
    },
    "PPS": {
      "Initial": 0,
      "Last": 328,
      "Min": 0,
      "Max": 342,
      "Sum": 298515,
      "GoodCount": 927,
      "BadCount": 1
    },
    "TSERR": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 928,
      "BadCount": 0
    },
    "NETERR": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 928,
      "BadCount": 0
    },
    "DVRBUF": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 0,
      "BadCount": 0
    },
    "DVRDROP": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 0,
      "BadCount": 0
    },
    "STREAMTIMEOUT": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 0,
      "BadCount": 0
    },
    "Grade": {
      "GoodCount": 928,
      "BadCount": 0
    },
    "NetworkGrade": {
      "GoodCount": 928,
      "BadCount": 0
    },
    "SignalGrade": {
      "GoodCount": 928,
      "BadCount": 0
    },
    "StreamGrade": {
      "GoodCount": 928,
      "BadCount": 0
    }
  },
  "BufferStats": {
    "BufferPct": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 0,
      "BadCount": 929
    },
    "BufferDrop": {
      "Initial": 0,
      "Last": 0,
      "Min": 0,
      "Max": 0,
      "Sum": 0,
      "GoodCount": 929,
      "BadCount": 0
    }
  },

[NickBurns]

That's definitely getting closer. Isn't there a web api I can access as well?

[chDVRuser]

Official, but more limited in what you get.

BETA: API & Feeds

Hey everyone, we just launched our first dabble into providing a stable, documented, read-only API for Channels DVR Server. This is early still, but provides a lot of coverage for your library. It's currently read-only for now. Eventually the API will evolve to provide ways to mutate the data in your library like marking things as favorites, or editing metadata. But for now, we're looking to nail down the data we're providing you and also making sure everything is running smoothly. Feeds? T…

And this Support doc is linked to in there

Server API

[NickBurns]

Yup, that's what I was looking for, but unfortunately, as they state, it's very limited. The shows and jobs do not provide the Device ID for the recording.

[chDVRuser]

A few lines above the Signal Stats in the recorded file json it displays the ChannelNumber and DeviceID, but not the tuner# within the DeviceID. That would have to be grepped from the DVR log.