Project

General

Profile

Forums » General »

why collect OTA EPG data if you're not going to use it?

Added by Rob vh over 10 years ago

I notice that tvheadend collects EPG with an epgscan for all muxes (DVB-S).
Why?
It only keeps the EPG data for services that are used in a Channel, so why both tuning to + collecting all those other muxes?
I noticed that this collection can sometimes hang-up, e.g. at
subscription: 'epggrab' subscribing to mux, weight: 3, adapter: 'STV090x Multistandard : DVB-S #0', network: '19.2E', mux: '12640V', hostname: '<N/A>', username: '<N/A>', client: '<N/A>'

I noticed the (new) option to specify the EPG Scan option for each mux, so now I disabled this for all but the useful muxes. After I changed the first Mux to Disable, I see that all other muxes suddenly show "1" instead of "Enable (auto)". Hmmm.


Replies (2)

RE: why collect OTA EPG data if you're not going to use it? - Added by Rob Rob over 10 years ago

It's a work in progress, stuff is being changed frequently with a lot of a recent builds on the EPG front. Give it some time or use an older version.
I'm not getting the bug you talk about personally though after disabling some EPG muxes with regards to a "1" appearing etc.

RE: why collect OTA EPG data if you're not going to use it? - Added by Rob vh over 10 years ago

I'm happy with the manual configuration so far, it cuts down the scanning time significantly.
The "1" showing up may be similar to the UID occasionally being shown for channel names in the Services list, when new names cannot be resolved from UIDs yet. After I wrote my initial post, the word "Enable (default)" came back.

I'm very happy with the current rush of improvements. I just wonder if there is a repository that describes the changes that were completed, including a "this is how it is supposed to work" that would allow me to get the best benefit of the improvement (and test it for your benefit too).

    (1-2/2)