[mythtv] Ticket #1619: DVB: backend won't tune after the first channel tune

[Mark Buechler]

I think there's something more to this. The two channels I'm going between
which effect this are 1 of two scenarios:

1. Both channels are on the same NIT, different transports (and differing
tsid)
2. Both channels on different NITs with different transports with no common
tsid in between (I use a rotor).

Given #1, I can't agree with you in that the NIT has anything to do with
this. It was #1 last night which prompted me to look into this problem
because it was very reproducable at the time.

- Mark.

On 4/11/06, Daniel Kristjansson <danielk at cuymedia.net> wrote:
>
> On Tue, 2006-04-11 at 14:03 -0400, Mark Buechler wrote:
> > BTW, when you say the zero version number is a coincidence, it's not
> > that it's 0, it's that both multiplexes have the same version number.
> > That is the cause behind the PAT never getting re-parsed after the
> > first time.
>
> See the reply I just sent to Stuart's message. The version check
> is not designed to check for transport changes. The users of the
> class, in this case tv_rec and dvbsignalmonitor, are responsible
> for resetting the class on transport changes, and resetting the
> known PAT version on a channel mismatch. It looks like it is
> doing this, but a PAT mismatch only happens when the MPEG program
> number doesn't match the expected value. But the program number
> is by no means unique across transports. Hence you need address
> ticket #1049 to address this properly, fixing it will allow
> monitoring the transportid, networkid and serviceid...
>
> -- Daniel
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20060411/d40756f9/attachment.htm