Jason Tackaberry wrote: >> (1) This should be easy. Scan /dev/dvb and /dev/video* and we should >> get the information we need. > > Depends what information you're gathering here. If it's just discovery > of hardware, ok. But I don't think you can rely on much else.
For DVB we also know if it is DVB-T, DVB-S or DVB-C. I guess we can also find out if we have a hardware encoder, but like you ignore DVB, I ignore that :) >> (2) More tricky. We need some initial tuning data. > > Right, this will have to be asked of the user during the configuration > process. For example I would need to configure that I am capturing from > an external tuner via the svideo input, and also configure the location > to the channel changing script. (Ideally Freevo would handle changing > channels directly, and would also be a configurator for lirc, but this > is something we should defer for a future release IMHO.) Right, I forgot about channel changing scripts. >> (4) We need a mapping to match analog channel ids or dvb names to the >> channel names the grabber uses. How? > > I think this is really the crux of the problem, right? I don't know how > the DVB case should work. Won't dvb names be included in the xmltv > data? Aren't the analog channel ids stored in the xmltv data too? At least not in the normal xmltv grabber for Germany. Epgdata.com provides that information for the channels they support. > If the data is there but there's no reliable way of determining it, we > can maybe make some guesses (based on different algorithms) and then > have the user pick the right one, and then just apply that algorithm to > the rest of the channels. We do that now, but it is very hard to do right. Maybe a text file with mapping information would help. >> The only idea I have are that the epg needs to have the following >> information: >> >> o List of all channels available in all grabber. The grabber have a >> priority so we have one grabber getting us data for a channel. > > Don't you mean the list of channels that are available in the > specified/configured grabber? How could you get a list of channels from > an unconfigured grabber? You know what channels a grabber could grab but you may not be able to receive all of them. >> o A grabber needs to have an interface to tell what channels to >> get. So a basic xmltv grabber is of no use. We need support for each >> grabber so we can configure the grabber and match our channel name >> to the grabber channel name. > > What is "our channel name"? Do you mean the channel id we need for > purposes of tuning the capture card? > > I think for xmltv we can, at least for now, push the configuration onto > the user. We'll have the best support for the native kaa.epg sources. The problem is that you have a name of the channel in a dvb stream, a name in xmltv and another name in maybe other grabbers. We need to have one mapping. >> How does zaptoit work? > > I don't think it deals with DVB at all. It maps stations to channel > numbers separately. e.g. > > <station id='10036'> > <callSign>ARTSC</callSign> > <name>Arts & Entertainment Canada</name> > <affiliate>Canadian Satellite</affiliate> > </station> > > <map station='10036' channel='270' from='2005-03-30'/> > > So from our perspective you know that the tuner needs to be set to > channel 270 for this station. Question (not to you): how to get the dvb name? > I don't know, but I think xmltv is really the best show in town in terms > of coverage. So I think we should try to support the popular grabbers > natively, and fall back to xmltv for everything else. Yes Dischi -- Drugs cause amnesia and other things I can't remember...
pgpb8fqho4jZj.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
