[mythtv] SI/PSIP Parser

Jason Hoos jhoos at thwack.net
Wed Sep 22 12:19:43 EDT 2004


> OK I will let you know when I get it somewhere.  I was thinking of having a signal called
> something like Tune() that would allow you to hook it into the channeltype for each ATSC and DVB
> to allow the parser to change transports to get more guide which might help.. Is the PCHDTV tuning
> handled by the V4L code right now?

Yes, it is.  All of the tuning is done by the same Channel class that
the non-ATSC stuff uses.

> I was thinking you would choose one or the other per video source at least initially.  For DVB
> that works out just fine usually, but there might have to be some thought put into a mixed mode
> like you are talking about.

Going with one or the other initially until things are working is easy
enough.  I imagine that adding a "mixed mode" where the ATSC tables only
update show times and not descriptions shouldn't be too hard later on,
although handling something like a pre-emption might be a bit tricky.

> The DB strucure for ATSC is one entry per virtual channel in the channel table, and nothing
> linking the virtual channels together (i.e. another table in the DB).. With DVB there will be a
> table linking each program (virtual channel) to a transports table.  This simplifies the process
> for flagging a transport for OTA guide (EIT to be correct), or zap2it.. I think this question
> needs to be answered for a simple mixed mode method to work out OK..
>
> You could piggyback off of my new dvb_transport table structure for PCHDTV (maybe calling the
> table something more arbitrary like transports) and solve this.  It might also be a good way of
> saying "this is an analog channel, or this is a atsc channel).

We could do something like this, especially if the data structure is
going to be there for DVB anyways.  As for the "this is analog/atsc"
part, the channel table already handles that with its format field
(which contains either "NTSC", "ATSC", or "Default" which means whatever
the global setting is).  Right now Myth pretty much assumes that
anything on a pcHDTV card is ATSC and ignores that field, but I've been
playing with doing something about that so that I can have cable hooked
up to the second antenna input.  Still trying to work out whether doing
that is really worth the effort involved. :)

Jason




More information about the mythtv-dev mailing list