Bug #3748
EIT EPG grabber not scanning all muxes
0%
Description
Since Tvheadend version 4.1-1942~g4244439 (or maybe more?) EIT EPG seems not to be auto-scanning the muxes anymore for EPG updates as it did before.
I have about 5 channels without EPG data (most channels use xmltv), but if I tune to one of these "empty" channels then the EPG data is loaded. So it seems that TVH does not auto-tune for EIT EPG updates.
In fact I don't see anymore epggrabber in the status->subscriptions tab, and I don't see anymore tuning for EPG grabbing in TVH log like the following (from version 4.1-1931~gc3eefc6):
Apr 27 10:13:45 raspberrypi tvheadend[898]: mpegts: 594MHz in DVB-T Italy - tuning on DiBcom 7000PC : DVB-T #0 Apr 27 10:13:45 raspberrypi tvheadend[898]: subscription: 002E: "epggrab" subscribing to mux "594MHz", weight: 4, adapter: "DiBcom 7000PC : DVB-T #0", network: "DVB-T Italy", service: "Raw PID Subscription" Apr 27 10:13:45 raspberrypi tvheadend[898]: mpegts: 658MHz in DVB-T Italy - tuning on DiBcom 7000PC : DVB-T #0 Apr 27 10:13:45 raspberrypi tvheadend[898]: subscription: 002F: "epggrab" subscribing to mux "658MHz", weight: 4, adapter: "DiBcom 7000PC : DVB-T #0", network: "DVB-T Italy", service: "Raw PID Subscription" Apr 27 10:13:54 raspberrypi tvheadend[898]: subscription: 0029: "epggrab" unsubscribing Apr 27 10:13:55 raspberrypi tvheadend[898]: mpegts: 514MHz in DVB-T Italy - tuning on DiBcom 7000PC : DVB-T #0 Apr 27 10:13:55 raspberrypi tvheadend[898]: subscription: 0031: "epggrab" subscribing to mux "514MHz", weight: 4, adapter: "DiBcom 7000PC : DVB-T #0", network: "DVB-T Italy", service: "Raw PID Subscription" Apr 27 10:13:56 raspberrypi tvheadend[898]: subscription: 002F: "epggrab" unsubscribing Apr 27 10:13:57 raspberrypi tvheadend[898]: mpegts: 546MHz in DVB-T Italy - tuning on DiBcom 7000PC : DVB-T #0 Apr 27 10:13:57 raspberrypi tvheadend[898]: subscription: 0033: "epggrab" subscribing to mux "546MHz", weight: 4, adapter: "DiBcom 7000PC : DVB-T #0", network: "DVB-T Italy", service: "Raw PID Subscription"
Do I miss a new config feature that I have to enable, or is this a bug introduced in one of the latest releases?
With 4.1-1931~gc3eefc6 I did not notice anything strange, EPG was loaded as usual.
History
Updated by Jaroslav Kysela over 8 years ago
- Status changed from New to Fixed
It was fixed in v4.1-1943-g10f1326 .