Channels DVR Beta for HDHomeRun Premium TV

Hmm, that’s coming directly from the HDHR so it might be a question for SD support.

Just submitted a tech support request on it to SD

Do the premium channels show up on all your EXTENDs? Frm the log it looks like the DVR only tried to record from 1053D4DE and none of your other EXTENDs.

There is a new pre-release build available (v2018.08.22.0107) which fixes the HISTORY and PARAMOUNT channel guide data.

1 Like

When I check both the my.hdhomerun page with the extends I see the full channel line up on all three of them, as well as when I check from the Channels DVR settings page (channels under each of the extends).

so yes.

Seems like it should have tried the other devices then. Can you reproduce any time you try to record more than 2 premium channels? Does the Log show it trying to connect to another device ID after it gets the “tuners in use” error?

Does the commercial skip feature work on the premiums in the same way as it does on the antenna channels ?

The USA ‘On Now’ and ‘Guide’ are still showing different things as playing right now.

Yes it does.

Recordings don’t seem to work with the new update. Ever time I try and record I get this. I can see on my HDHomeRun that the tunner is in use and turned to the correct channel. Same thing happens with OTA channel. . Any thoughts.

2018/08/22 05:00:00 [DVR] Starting job 1534932000-1 Steven Universe on ch=[1734]
2018/08/22 05:00:00 [TNR] Opened connection to 10633093 for ch1734
2018/08/22 05:00:00 [DVR] Error running job 1534932000-1 Steven Universe: could not find tuner for channels=[1734]
2018/08/22 05:00:30 [DVR] Starting job 1534932000-1 Steven Universe on ch=[1734]
2018/08/22 05:00:30 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=2, len=8469776)
2018/08/22 05:00:30 [DVR] Error running job 1534932000-1 Steven Universe: could not find tuner for channels=[1734]
2018/08/22 05:01:00 [WRN] Buffer for 10633093 ch1734 is more than 50% full (clients=2, len=16777684)
2018/08/22 05:01:00 [DVR] Starting job 1534932000-1 Steven Universe on ch=[1734]
2018/08/22 05:01:00 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=3, len=16797424)
2018/08/22 05:01:00 [DVR] Error running job 1534932000-1 Steven Universe: could not find tuner for channels=[1734]
2018/08/22 05:01:30 [WRN] Buffer for 10633093 ch1734 is more than 75% full (clients=3, len=25166000)
2018/08/22 05:01:30 [DVR] Starting job 1534932000-1 Steven Universe on ch=[1734]
2018/08/22 05:01:30 [TNR] Sharing existing connection to 1043F497 for ch1734 (clients=4, len=25281676)
2018/08/22 05:01:30 [DVR] Error running job 1534932000-1 Steven Universe: could not find tuner for channels=[1734]
2018/08/22 05:01:54 [WRN] Buffer for 10633093 ch1734 is more than 95% full (clients=4, len=31878916)
2018/08/22 05:01:59 [WRN] Buffer for 10633093 ch1734 is more than 99% full (clients=4, len=33221236)
2018/08/22 05:02:00 [DVR] Starting job 1534932000-1 Steven Universe on ch=[1734]
2018/08/22 05:02:00 [DVR] Waiting 23h57m59.020113541s until next job 1535018400-1 Steven Universe
2018/08/22 05:02:00 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=5, len=33554432)
2018/08/22 05:02:00 [DVR] Error running job 1534932000-1 Steven Universe: could not find tuner for channels=[1734]
2018/08/22 05:02:30 [DVR] Starting job 1534932000-1 Steven Universe on ch=[1734]
2018/08/22 05:02:30 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=6, len=33554432)
2018/08/22 05:02:30 [DVR] Error running job 1534932000-1 Steven Universe: could not find tuner for channels=[1734]
2018/08/22 05:03:00 [DVR] Skipping job because program already started 1534932000-1 Steven Universe
2018/08/22 05:16:00 [TNR] Closed connection to 10633093 for ch1734

Here is another example with just clicking record on a channel…

2018/08/22 06:01:08 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:01:09 [TNR] Opened connection to 10633093 for ch1734
2018/08/22 06:01:09 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]
2018/08/22 06:01:39 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:01:39 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=2, len=8475040)
2018/08/22 06:01:39 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]
2018/08/22 06:02:09 [WRN] Buffer for 10633093 ch1734 is more than 50% full (clients=2, len=16777684)
2018/08/22 06:02:09 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:02:09 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=3, len=16838220)
2018/08/22 06:02:09 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]
2018/08/22 06:02:39 [WRN] Buffer for 10633093 ch1734 is more than 75% full (clients=3, len=25166000)
2018/08/22 06:02:39 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:02:39 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=4, len=25227720)
2018/08/22 06:02:39 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]
2018/08/22 06:03:03 [WRN] Buffer for 10633093 ch1734 is more than 95% full (clients=4, len=31877600)
2018/08/22 06:03:08 [WRN] Buffer for 10633093 ch1734 is more than 99% full (clients=4, len=33219788)
2018/08/22 06:03:09 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:03:09 [TNR] Sharing existing connection to 1043F497 for ch1734 (clients=5, len=33554432)
2018/08/22 06:03:09 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]
2018/08/22 06:03:39 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:03:39 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=6, len=33554432)
2018/08/22 06:03:39 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]
2018/08/22 06:04:09 [DVR] Starting job 1534935600-ch1734 The Amazing World of Gumball on ch=[1734]
2018/08/22 06:04:09 [TNR] Sharing existing connection to 10633093 for ch1734 (clients=7, len=33554432)
2018/08/22 06:04:09 [DVR] Error running job 1534935600-ch1734 The Amazing World of Gumball: could not find tuner for channels=[1734]

The HDHomeRun turner is tuned to channel 1734. It also stays tuned to that channel after I cancel the recording. The only way for it to give up the tuner after cancelling was to reboot the HDHomeRun.

Thanks,

  1. I was able to repeat it. Was watching 1 stream and scheduled 3 more for recording. Got the following for all attempts to record: could not find tuner for channels=[1412].

  2. I don’t remember how to submit diagnostics, or if you want to drop in and look, but it does seem to be repeatable.

Not sure if this is a channels issue or an SD issue but running the latest DVR build 2018.08.22.0107 the guide data for the History channel is in Spanish. All others appear to be correct and in English.

Ok, 15 minutes later it’s now in English…

Channels is the best app I have experienced on the Apple tv. Thank you for your response to Premium tv’s release. Very nice work :wink:

3 Likes

Nothing seems to be recording with the latest beta for me (Premium TV channels or OTA channels). Looking at the HDHomeRun tuner status page, it shows them being tuned to the correct channels, but the streaming rate is listed as none, and the recordings themselves never show up in channels and there are no files on my hard drive.

1 Like

I had the same thing happen. Seems to be on OTA and the Premium Channels. Impost my DVR log above with two examples. Glad I am not the only one.

Same here, DVR can not find a tuner (2018.08.22.0107)

Oops looks like I broke recoding. New beta build coming soon…

2 Likes

Yep, same here. I am not getting any new shows recording.

Not seeing this here…

Both tabs use the same data so they should be exactly the same. Does it happen after a force quit and relaunch of the app?