HDHomerun EXTEND reason reset = application watchdog

Server Version#: 1.17.0.1709
Player Version#: 4.8.1

I’ve been coming up against an issue with 2 separate HDHomerun EXTEND units recently, which I suspect is an issue with the tuner and not Plex, but it affects my DVR recordings made through Plex.

TL;DR: my HDHomerun EXTEND is resetting when it tries to transcode natively for at least one specific channel, so I would like the option to transcode OTA streams using my Plex server for DVR recordings instead of the EXTEND’s native transcoding. Is that possible? Right now, I only see the option to adjust the EXTEND’s transcode profile in my Plex Live TV settings (i.e. TRANSCODE QUALITY).

Background:

Basically, there is a local PBS channel that I record from quite frequently for my kids. The signal is pretty good (Signal Strength 95-100%, Signal Quality ~75%, Symbol Quality 100%), so I used to be able to get good captures of these shows on this channel.

Starting a few months ago, I started noticing some weird issues with my recordings from this channel. The kids show would start for a few seconds but would then jump forward a minute or two, continue for a few more seconds before jumping ahead another minute, etc. In the end, instead of a 30 minute recording of a kids show, the recording I end up with is 30 minutes of short clips from this channel recorded over the course of about 2 hours (usually 3 or 4 different shows are represented). My basic settings were as follows:

-EXTEND default transcode profile: NONE
-Plex Live TV device settings\Transcoder Quality: HIGHEST QUALITY

Note: using these settings, the EXTEND appears to use its HEAVY transcode profile.

I did some local testing, and most of the major broadcast channels work without issue when my EXTEND is using the HEAVY transcode profile. For one specific PBS channel (WHUT 32.1 in the DC area), however, my EXTEND chokes within a few seconds and resets. The EXTEND system log indicates that REASON RESET = APPLICATION WATCHDOG. This appears to be the cause of my botched DVR recordings, which all appear to be from this channel (though there may be others that I don’t regularly record from).

To work around this, I changed my Plex server Live TV device settings to request “Original Quality” instead of “Highest Quality” (the EXTEND is still set to DEFAULT TRANSCODE PROFILE = NONE). After making this change, the EXTEND displays the transcode profile as NONE when streaming to Plex, which I believe means that it is not transcoding at all. Using these settings, I have no issues with the EXTEND resetting every few seconds when watching this channel.

The problem with this workaround is DVR recording file size, which are now larger. Ideally, I would use the EXTEND to transcode, but both of the EXTEND units I have here exhibit the same problem with the same channel. Both were original plastic case w/ fan units that have now been upgraded to the metal/heat sink case by SD. I suspect this is an EXTEND firmware issue, honestly, as I never had this problem with this channel before a couple of months ago.

That said, since I can’t use the EXTEND’s native transcoding without causing my streams to die, is there a way to record streams that have been transcoded by my Plex server instead? I have plenty of disk space now, but I’d rather not burn through it unnecessarily by DVRing at full quality.

Are you updated to the latest version of the firmware on your HDHR Extend? I’m showing 20190621 as the latest version available. It may also be worth it to open a ticket with Silicon Dust. I think they can use the codes in the Extend logs to see what is causing the application watchdog to initiate a restart, so post the first few lines of an example watchdog restart.

I read a thread recently where an Extend user had to manually power down their Extend and restart it after a firmware upgrade caused some problems… they said Silicon Dust told him to do that because not everything had fully restarted after the firmware upgrade.

On the Plex side, after the show has been recorded you can have Plex create optimized versions that are smaller using the Plex transcoder. I don’t do this since my Extend is transcoding ok (knock on wood), but I found a thread that might help where people are discussing it. Make sure you backup your originals when testing whatever process you use, at least until you know the process works…

1 Like

Right on. I will definitely submit a trouble ticket, I have a draft e-mail open but will use the form you posted w/ the log outputs. Thanks for pointing me in that direction!

I’ve looked at the EXTEND logs but figured they were useless given the absence of anything from before the restart, but there are 2 lines w/ codes that might mean something SD support.

FWIW, I do have the most recent firmware updates and I’ve pulled the power source cable a while testing a couple of times during testing (to isolate one EXTEND or the other to see if I could replicate the issue on both units, which I was able to do).

Good call about optimized versions, I have done that with movies for mobile usage, not sure why it never occurred to me that I could use that for my DVR shows. I guess I had it in my head that it had to be done in real-time.

I’m beginning to wonder if the issue has anything to do w/ interlacing vs. progressive feeds, which might explain why some channels work and others don’t. Any ideas on how to test individual channels to pull things like resolution, scanning type, and frames/second?

Without getting client specific, you can see the resolution and if it is interlaced or progressive in the plex web app by going to the dashboard. Make sure show details is selected (image ). Then you can see if it is 1080p, 1080i, 720p, etc.

Frame rate - interesting, I hadn’t tried to look at this in Plex before for Live TV and I can’t find it easily for Live TV. Maybe someone else has an easier way, but I did find it in the logs - here is an example (I turned my Extend’s transcoding off so I could see if it changed for different channels. It did, I found another station where the log posted a 59.940 framerate…it also lists the resolution and if it is interlaced):

index=0&id=49&codec=mpeg2video&type=video&profile=Main&width=1920&height=1080&interlaced=1&sar=1:1&level=4&frameRate=29.970

This is from the PlexMediaServer.log file. Easiest way is to tune to a station (or two or three that you are interested in) then download the logs, open PlexMediaServer.log and search for “frameRate” back from the end of the log. Make sure you have debug logging on, and verbose logging off.

1 Like

Awesome, good call. The channel I’m having trouble with broadcasts in 1080i, so I’ll have to see if that is a recurring theme. More testing!

Checking back on this. It seems like my issue is 100% caused when trying to tune to this one channel in particular (WHUT in Washington, DC) when transcoding on the EXTEND (I typically use the heavy profile).

When I tune to the channel with EXTEND transcoding turned OFF (i.e. original quality), all channels stream without issue. When I change PMS Live TV and DVR settings so that the EXTEND is doing the transcoding (i.e. highest quality), most other channels stream without any issue (including both 720p and 1080i channels); when I try to tune to WHUT, however, the stream fails almost immediately and the EXTEND restarts (the Plex player throws a failure error message). This appears to happen with BOTH of the EXTEND units that I own.

Given the behavior I’m seeing, this does NOT appear to be an overheating issue; instead, it seems like there is something about the WHUT OTA signal is breaking the EXTEND transcoder. Is there any way to troubleshoot/identify the cause here?

If it helps, here is what I see in my HDHomerun tuner status when tuned to this channel (no EXTEND transcoding):

Virtual Channel 32.1 WHUT HD
Frequency 587.000 MHz
Program Number 1
Modulation Lock 8vsb
Signal Strength 100%
Signal Quality 81%
Symbol Quality 100%
Transcode Profile none
Streaming Rate 5.401 Mbps
Resource Lock xxx.xxx.xxx.xxx

Is the SIGNAL QUALITY too low?

For reference, here is the System Log that I see immediately after restart:

System Log
19700101-00:00:17 System: reset reason = application watchdog
19700101-00:00:17 System: E5592573 0000000E 004FE4A8 00440B88 00447DC0 00412FC8 004F942C 004F9400
19700101-00:00:17 System: 00524FAC FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
19700101-00:00:17 System: network link 100f
19700101-00:00:19 System: ip address obtained: xxx.xxx.xxx.xxx / xxx.xxx.xxx.xxx

One other thing I found on the WHUT Wikipedia page:

WHUT-TV commenced ATSC-M/H (Mobile DTV) broadcasting on February 27, 2011. WHUT-TV is the last remaining Washington-market broadcaster to broadcast an M/H signal. The signal nominally contains a feed of its main programming in standard definition on 32.1 and an audio feed of WAMU on 32.2, although neither stream contains audio or video data.

Via: WHUT-TV - Wikipedia

Does any of this stand out as possible problem? Is there anywhere else I can look for more possible leads? Is this simply a bug in the HDHomerun firmware or a poorly implemented OTA broadcast?

Thanks!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.