Dirk Meyer wrote: > Rob Shortt wrote: >> Rob Shortt wrote: >>> Dirk Meyer wrote: >>>>Ini style? The VDR channels.conf doesn't look like an ini file to >>>>me. Do you have more docs (== not reading the source)? >>> >>> >>> This lib isn't used by VDR (yet) and is the result of several >>> discussions on the DVB and VDR lists. I think this one is ini style. >>> I'll have to go back and refresh my memory on the specifics though. >> >> Ok, I may be completely confused here. I know I saw discussions about >> an ini style conf and thought they were implimenting it... >> >> Let me just let this coffee take effect and I'll do some more poking around. > > I played around and read some source code. To summarize it all: this > whole mapping sucks! If I read the channels.conf examples in the vdr > wiki correctly, the same channel may have a different SID at different > locations in Germany. So I guess we need to think of something else. > > Proposal: read a channels.conf in a format you want. It should be easy > to detect which format is used and we can create a simple xawtv > channels.conf parser and a vdr one. When writing our own scanning, I > propose vdr 1.3.x format. > > Doing that, the freevo recorder has no idea about a unique id. It can > record "Sat.1" for analog and "SAT1" for dvb. But it doesn't have to > know more. The recordserver has an epg and can try to figure out the > correct name. E.g. the epg may contain "Sat 1". If you remove all the > whitespaces, the dot and use lower case, all three are identical. So > we can try to find a mapping that way. This doesn't work for all > channels, e.g. I have "ARD" and "Das Erste". At this point we need > the users help and he may add an epg mapping to the recordserver in a > simple text file. It's not a good solution, but I guess it will > work. For US/Canada, the recorder knows it can record S50, whatever > that means. The recordserver has the epg and the access id and can do > the mapping. > > On the other hand, a unified epg would be nice, but I don't see a nice > way to do this.
BTW, I will start a freevo-record dir for the recorder tomorrow. It will be next to freevo in the svn, not in it. The same for freevo-tv containing the recordserver. And a kaa/WIP/record with changes to fit the new needs. Since freevo-record and freevo-tv are such bad names, I'm open for suggestions. Freevo-record could be named fred (Freevo Recording Daemon or Device), but I'm not sure I like that name. Maybe we can adapt the kaa naming scheme to name the freevo parts after figures of the jungle book. But why should the recordserver be named baloo? I guess it is also a bad idea. Dischi -- Bad spellers of the world Untie!
pgphNCx7VrCSz.pgp
Description: PGP signature
