Yes, I still have this problem and no I haven't really investigated it. The active scanner seems to pick up all the EIT data fine, however, the passive scanner seemingly only gets now/next. I haven't been bothered by it too much since active scanning works well.
<br><br>- Mark.<br><br><div><span class="gmail_quote">On 7/9/06, <b class="gmail_sendername">Torbjörn Jansson</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">(replying to a mail almost a month old)<br><br><a href="mailto:firstname.lastname@example.org">
email@example.com</a> <> wrote:<br>> I've further narrowed it down. It seems (for me anyway) that<br>> the active scanner works as expected. However, the passive<br>> scanner many times fails to pickup PID 0x12 when there's more than
<br>> now/next available.<br>><br>> - Mark.<br>><br>><br>> On 6/15/06, Torbjörn Jansson<br>> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:
<br>><br>> > One of my providers has 2day EIT available on one transport.<br>> > MythTV used to scan EIT for this provider just fine, however,<br>> > something seems to have changed in the EIT code which breaks
<br>> > it. Some times I'm able to get EIT, however the logs show ><br>many<br>> of the following: ><br>> > 2006-06-14 18:58:35.174 DVBRec(0): Unknown PID 0x12<br>> > 2006-06-14 18:58:
35.174 DVBRec(0): Unknown PID 0x12 ><br>> > Normal now+next works for all other channels on other<br>> > transports for this provider. I can provide any dvbsnoop<br>> > output requested. Could this be a table parsing problem which
<br>> > causes Myth to thing 0x12 isn't available? I've tested 10060<br>> > & 10187 and both show the problem sparadically (more<br>> often than not).<br>><br>> I'm having similar problems with eit.
<br>> Now/next works but i'm not getting the 2-3 day guide<br>> data as before.<br>> I don't know if this is a myth thing or some change my<br>> cable provider did or<br>> maybe a combination.
<br>><br>> I know the guide data is being transmitted because the<br>> guide on my dreambox<br>> works just fine.<br>><br>> I'm not seeing the unknows pid things in my backend log.<br>> I haven't tried the eit branch, is this kind of stuff
<br>> likley to have been<br>> fixed in that branch? If so, is it possibel to test<br>> that branch and then go<br>> back to trunk if things don't work any better?<br>><br>> Or maybe it will get merged soon so i should just wait a bit?
<br><br>Mark, did you find out what's wrong with eit?<br>I'm still seeing only now/next data.<br><br>Should i open a ticket for this?<br><br>I can provide logs, dvbsnoop dumps or other stuff if someone wants it.<br>This problem is with dvb-c (technotrend dvb-c
v2.1 ff card)<br>I know 2-3 days of eit is sent since i have a cablebox (dreambox) that get<br>eit data just fine when i tune in to one channel.<br><br><br>_______________________________________________<br>mythtv-dev mailing list
<br><a href="mailto:firstname.lastname@example.org">email@example.com</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</a><br></blockquote></div><br>