Hi folks! Dirk Meyer wrote: > Damit, my mail yesterday got lost :( > > Rob Shortt wrote: [...] >>Also, have you looked at using a different channels.conf format? The >>one you're using now relies on the DVB name as the defining factor which >>isn't that reliable IMO. The VDR 1.3.x format is consistent accross >>DVB-C/S/T I think, and exposes the channels Service ID (SID). > > > I was thinking about creating our own channels.conf format, including > dvb and analog settings.
This is getting in the same old direction, re-invent everything. You're not to blame for this, as there isn't any universal format for TV channels yet, every application has it's own (xawtv, tvtime, xine, mplayer, freevo, etc...), and that's a pity. VDR's channel.conf also support analogue channels (just by the usge of the present fields, VDR itself isn't aware of analog channels), as described in the analogtv plugin's documentation. http://www.linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf http://www.vdr-wiki.de/wiki/index.php/Syntax_der_channels.conf http://www.vdr-wiki.de/wiki/index.php/Channels.conf_analog I couldn't setup analogtv myself, but there is another similar plugin only targeted at Hauppauge PVR and compatible cards, pvrinput, which was a snap to install and use, as it just takes the MPEG2 stream from the PVR's hardware encoder and feeds VDR's MPEG2 decoder, whatever that is, hardware or software. Pvrinput also uses the same format as analogtv does, for VDR's channels.conf analogue channels entries. So VDR's channel.conf basically has all this. I have to agree, it lacks information about the language of the EPG for a specific channel for example, which is not necessarily the same like the language of audio pids, but Freevo is using UTF-8 already anyway and maybe will deal with this better. > > >>Now, in the past, it is this SID (just like a numeric tuner ID) that >>made the correlation to my XMLTV data, for example channel 203 in my >>XMLTV data was the same as the DVB channel defined by SID 203 - and in >>almost every case the XMLTV display name and the DVB name were different. > > > Right, the name is different very often. That's why I wanted a > mapping. But maybe the SIDs may help. We (Soenke and I) will try to > find a nice solution tomorrow at our 'Freevo TV Hacking Day 2' about > tuners and autodetection (BTW, 'Hacking Day 3' could be about adding > teletext support) > > >>>Comments / better suggestions / help ??? >> >>Can you check if your DVB provider broadcasts a Service ID for your >>channels? Also, have you looked into the VDR 1.3.x channels.conf format? > > > We will do that. I don't know if you guys followed the linuxdvb ML, but there where efforts to unify channel configuration data in a library (I guess at the moment it's just in CVS): libdvbcfg, just ahave a look http://www.linuxtv.org/cgi-bin/viewcvs.cgi/dvb-apps/libs/ . They enherited lots of things from VDR 1.3.x. Maybe it is a good moment to try to unify all this channel format chaos, then applications could just use libdvbcfg and then channel configs may be shared between such frameworks of more apps like freevo is, easier. I think libdvbcfg might even be able to accomodate analog channels the way it's done in VDR, because it's just up to the application (like in VDR's case, to the anlogplugin or pvrinput) to use those channels masked by a special CA-ID which normal DVB-targeted apps ignore due to the fact that those look "encrypted" to them. Just my 0.02 €uros... Lucian ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
