Live Tuning Failover Logic

Had an issue tonight that I thought I should report. Tuner sharing is on. Tried to tune live to my local NBC affiliate via HDHomeRun quadro. 18.1. Turns out all tuners on the HDHomeRun were in use, so it moved on to my HDHomeRun prime. However, instead of tuning the Hd version of the channel, it went to the SD version of the channel. I assumed this failover logic would prefer HD channels over SD ones, but that does not seem to be the case. Let me know if this is expected behavior, or if you need diagnostics to track it down.

Edit: went ahead and submitted logs just in case. af801d2f-7489-42b7-938c-b914bffffa5d

Which client

Apple TV

Here are the relevant lines from the log to help correlate timestamps, it if helps. It tries the HD version via the quadro first, then TVE via Spectrum (which was having problems at the time), then to channel 8 on the Prime, which is SD. The tune to 906 at the end was me manually picking it from the guide. I would have expected it to go to 906 before 8, since 906 is HD. The client is set not to stack channels I believe, if it matters.

2021/11/21 20:04:15.313732 [ERR] Could not start stream for 1074FE32 ch18.1 WLEX-TV: HDHomeRun: 805 All Tuners In Use
2021/11/21 20:04:25.799199 [ERR] Could not start stream for TVE-Spectrum ch6000 WLEX: TVE: Post "https://sp.auth.adobe.com/adobe-services/authorize": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    2021/11/21 20:04:26.375614 [TNR] Opened connection to 13139C75/0 for ch8 WLEX
    2021/11/21 20:05:37.770079 [SNR] Statistics for ch8 WLEX: ss=100% snq=100% seq=97%,0%-100% bps=2640564,0-2880160 pps=227,0-246
    2021/11/21 20:05:37.772285 [TNR] Closed connection to 13139C75/0 for ch8 WLEX
    2021/11/21 20:05:49.698804 [TNR] Opened connection to 13139C75/0 for ch906 HD WLEX

I also just checked and verified that no Channels are favorited in the client on the prime.

Are channels 8 (WLEX) and 906 (HD WLEX) actually mapped to the same guide data? If the "HD WLEX" is named/mapped differently, that could be why it was not tried as a replacement for the other two attempts.

Yes, they are both mapped to 18.1:


Could you submit the logs from the Apple TV after this happens? It will give more details as to what happened.

Just reproduced and submitted from the client menu.

Looks like this is totally an oversight on our part in the channel selection logic on iOS/tvOS. We thought it worked the way you expected. We're working on a fix for this.

2 Likes