Lucian Muresan wrote: > 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.
I didn't know that. > I don't know if you guys followed the linuxdvb ML, not anymore > 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. Sounds like a good idea. But libdvbcfg has way to much lines. You can write it much smaller in Python, so I guess we will write a Python parser for the same config style. We will take a look at it. Dischi -- The world is full of willing people -- some willing to work and some willing to let them. - Robert Frost.
pgpePezjojjXy.pgp
Description: PGP signature
