[mythtv] [Experimental PATCH] BIG DVB PATCH V2.0 Released

[Taylor Jacob]

> 1) My setup is dvb0= TT Premium-T (alps),
>  dvb1= TT Budget-T (philips). When I run a scan in
> mythsetup on dvb1 it breaks my front-end and I have
> to reload the driver modules to get the tuner to
> work again. This does not happen on dvb0.
> Both cards scan OK using mythscan2. Odd!

This sounds like a driver issue to me, have you tried different drivers?  I know
there were some buggy drivers in the linux-dvb cvs that did this exact thing a
month or so ago.  Let me know if when you update/change drivers if you still
have this,  or help eliminate the drivers because it seems unlikely that
opening and closing some section filters would cuase the frontend to exhibit
that behavior.

> 2) I live in an area (Sudbury) where the local
> DVB-T transmitter is a relay to the main network
> region (Talcolneston). The main DVB-T Transport
> descriptor shows the frequency of the distribution
> network, not the local transmitter. The latter is
> shown in a "FrequencyList" descriptor (IIRC 0x62?)
> so my transports never get put into MySQL correctly.
> I can send a dvbsnoop if needed.

Support for this has been added and will be in the next patch.  Please be sure
to try it out, and let us know if it works properly since neither of us have a
way to properly test this.

> 3) In the UK, many terrestrial services are active
> only some small part of the day, and the service
> type changes depending whether it's on the air or
> not. This and the A/V PIDs need to be checked
> before attempting to set filters otherwise myth
> just dies... Is anyone working on this? Sounds like
> a myth protocol change to me.

Yes. :)  This is part of the changes being implemented.  Yes to handle livetv
properly the Frontend / Backend protocol will have to be ammended.

Taylor