TVheadend using HDHomeRun ATSC continuously when idle
|Found in version:||d66746ca||Affected Versions:|
TVheadend revision d66746ca 12/15/2011 10:34 pm
HDHomeRun ATSC, using dvbhdhomerun kernel drivers
Disabled options: "Autodetect muxes", "Idle scanning", "Monitor signal quality", "Write full DVB MUX to disk", and "EIT" for all services
When TVheadend is idle (no recordings or video streams), it
(1) continuously starts and stops feeds, of PIDs 0x0, 0x1, and 0x1FFB, which I believe is a request for EIT
(2) continuously requests signal quality, as seen in dvbhdhomerun.log: "FE_READ_STATUS sym qual: 0" messages when idle or "FE_READ_STATUS sym qual: 64 FE_READ_SIGNAL_STRENGTH strength: 52 sym qual: 64 sig to noise:64" when receiving video
(3) spontaneously starts video streams to TVheadend, indicated by tuner-in-use LED on HDHomeRun and "FE_READ_STATUS sym qual: 64 FE_READ_SIGNAL_STRENGTH strength: 52 sym qual: 64 sig to noise:64" messages in dvbhdhomerun.log
As mentioned above, idle scanning, monitor signal quality, and EITs are all disabled. Is this expected behavior for TVheadend or should a bug report be opened?
For those of you familiar with dvbhdhomerun logs, http://pastebin.com/PK1bXfkD is a link to a log for about 57minutes of activity. It includes a 6min recording near the beginning, which I initiated from the TVHeadend webpage 6min prior to the end of the program; so the start was manual and the stop was automated. The recording came from adapter1, while adapter0 went unused. The light on the front of the hdhomerun showed adapter1 in use and adapter0 unused. Then 20 min after the recording successfully completed, adapter0 spontaneously fired up and outputted data to TVheadend, and continued until the end of the log, when I terminated TVheadend (I don't know of a way to stop adapter0 manually, since no recording was occurring).
#1 Updated by Adam Sutton 10 months ago
- Status changed from New to Invalid
I think this is "expected" behaviour it will generally leave the last transponder tuned even with all those settings off. However Andreas or myself will be adding a patch in coming weeks to remove this "feature".
If you still have problems though send me a message so we can discuss.
#2 Updated by m 321liftoff 4 months ago
The major problem I'm having now is that after a recording completes, TVHeadend leaves the HDHomerun tuned in on that channel (led still on, and Ethernet traffic still going). This condition remains indefinitely until a TVHeadend restart or powering cycling the HDHR. I'm running version 3.3.236~g93fe784-dirty (latest git from Jan 1, I believe). It is running on a QNAP NAS. Another QNAP & HDHR user is reporting the same problem. Let me know if you need any logs.
#4 Updated by m 321liftoff 4 months ago
Thanks Adam. I already had the "idle scan" disabled, but I didn't know about the "close device handle when idle" option. It looks like it was added Sept 13, 2012 Enabling it fixed the problem. Maybe you could change the status from of this bug from "invalid" to "fixed" and get some credit
#5 Updated by Martin Ayla 4 months ago
I have the same problem with Tvheadend and my HDHomerun, I'm using latest git version from today (I've had the problem with all versions). I have a constant network usage/traffic of ~75 Mbit/s (puts a lot of strain on my network, my HDHomerun is not on the same switch as my Tvheadend server, so the traffic has to travel over WiFi).
EIT Grabbers, idle scan and close device handle when idle are disabled.
Any ideas would be very welcome.