Rob Shortt wrote:
Duncan Webb wrote:
Happy New Year to you all
Happy new year. :)
I've been looking at the code and it seems to say that channels.conf has
four fields and in ignores comments starting with a #
But I'm still trying to figure out what these fields should contain.
Any examples?
In kaa SVN from trunk/record/test/channels-ivtv0.conf (v4l tv is the
same):
#
# tunerid:name:frequency Hz
# name and frequency are optional
#
4
5:BRDNEWS
6:CIHF
7:ASN
9:CJCH:187250
Does this mean that:
K32:bbc.co.uk:559250
S13:cnn.com:246250
will be okay?
I guess that there is still a way to connect a channel to the TV.xml data?
It's a rather simple format but really all that we need.
I've done what it says on the mbus page and this time it show *nothing
scheduled* and get this in the tvserver-0 log:
INFO server(514): add client <RemoteEntity type:home-theatre
id:[EMAIL PROTECTED] module:core>
But when I press OK on one of the channels in the tv menu the log main-0:
INFO [ tv] xine.py 135: recordserver found
INFO [record] tvserver.py 137: recordserver found
ERROR xine(159): FIXME: no server found
I've tried adding the route 224.255.222.240 to the eth0 and the lo
interfaces, but this doesn't change anything. It looks like I'm almost
there but could be missing one or two steps.
What is the next thing to look at?
There are two other errors in the log which may indicate a problem and
they are:
ERROR sdl(66): unable to find key code for ENTER
ERROR sdl(66): unable to find key code for ESC
Thanks
Duncan
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
