[confirm] EPG grabber only grabbs from first tuningdetail (1 Viewer)

[DerPat]

I don't know if it's really a bug, but I think it's worth to change.

If you have more than one tuningdetail for a channel (in my case some channels are available via dvb-s & dvb-t), the epg grabber only uses the first tuningdetail to grap. So if the first tuningdetail is a dvb-t detail and you have several dvb-s tuners with higher priority than the dvb-t ones, the epg grabber trys all the dvb-s tuners with the wrong dvb-t detail until he reaches a dvb-t card (you can watch to this play in the manual control). I confirmed this by changing the order of the tuning details in the db manually. This "bug" isn't preventing the epg grabber from doing his work, but in some kind annoing as the scan takes much longer.

I don't thing that logs are requierd as everyone can reproduce this. Never the less, the line according to this error:

2011-07-29 06:09:47.597897 [EPG Update thread(22)]: IdleEpgGrabber: no channel found for networkid:0x1 transportid:0x445 serviceid:0x6F42

Chers,
Pat

 

[elliottmc]

I don't thing that logs are requierd as everyone can reproduce this.

Oh, how many times have I heard that? How do you know that everyone can reproduce this?

 

[DerPat]

AW: EPG grabber only grabbs from first tuningdetail

It's very easy: just add some fake tuning details as the _first_ one manualy in the db and you'll notice that the epg grabber fails to get data for this channel because it will never use the second (correct) tuning detail for fetching epg data.