Hi,

I started messing around with freevo last week, and I am really impressed
with where it's at! I'd like to help out with the effort if I can find a
spot to apply myself.

I have a question, but first - some info on my setup:
Freevo version: 3.5
video card: ATI TV-Wonder VE (Actually, it works pretty good considering
the $$)
OS: RH 9
Kernel: 2.4.20-23

I've installed from rpm's.

On to the question: The recording server is looking for a file called
record_schedule.xml. The local_conf.py file (and of course the
corresponding  freevo_config.py file * see note below) has the following
setting:
REC_SCHEDULE_FILE = '/tmp/freevo_record.lst'

Even if they (freevo and the recording server) are pointed to the same
file, they are different formats. Which means that when one selects a
program and "F6's" to record it from freevo, the two entites will not meet
in the middle - meaning the recording server never gets notification that
there is something to record (a snippet from the recording server's log
file):

2003/09/01 21:16 MDT [*RecordServer*] in checkToRecord
2003/09/01 21:16 MDT [*RecordServer*] GET: reading cached file
(/var/cache/freevo/record_schedule.xml)
2003/09/01 21:16 MDT [*RecordServer*] Got ScheduledRecordings (version 2).
2003/09/01 21:16 MDT [*RecordServer*] ScheduledRecordings has 0 items.

I've searched around quite a bit in the news group and documentation for
the answer to this, and I'm hoping I will not look like the twit who is
asking this question for the n'th time... But, here it goes:

It doesn't seem like the linkage between freevo and the recording server
can work at all. I'm somehow missing a big piece of the puzzle - how to
either tell freevo to save the recording schedule in an XML format that
the recording server will understand, or vice versa.

The documentation on this is a little light. From subtle comments on the
email list, there might be a large piece of documentation on the recording
server that I've missed (including the setup of the web interface).

I would love to help out on some of this. If you can help me understand
the linkage, I can document it in a fuller fashion for the web based
docs... Perhaps this is already fully explained in a web based doc that I
am missing?

Thanks for any help you can provide.

cheers,
Greg

Note:
- the subtle name difference in the freevo_config.py file vs.
local_conf.py (which one is suppose to create to make the local
modifications) hung me up for several minutes... It might be wise to
highlight the "config" vs "conf" difference better on the web page. Maybe
I'm the only one who missed this, so it's just my $0.02 worth.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to