On Sun, April 12, 2009 4:52 am, Matthew Job wrote:
>
> I spent a bit of time on this and it seems that the livepause plugin
> fails.  I cannot get a consist result as to why the livepause plugin
> fails.  Sometimes it is when freevo starts, other times it lasts hours.
>

I've been meaning to answer this thread but didn't mean to find the time
over the weekend and I see Jonathan has done a fine job of answering most
of the questions :-)

>
> THe error is as follows.
>
>
>
> 2009-04-12 12:08:34,742 INFO     encodingclient.py (109): ('localhost',
> 18002) i
> s up
> Freevo 1.8.3 ready
> Exception in thread Slave Server:
> Traceback (most recent call last):
>   File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
>     self.run()
>   File "/usr/lib/python2.5/threading.py", line 446, in run
>     self.__target(*self.__args, **self.__kwargs)
>   File
> "/usr/lib/python2.5/site-packages/freevo/tv/plugins/livepause/__init__.py
> ", line 777, in run
>     connection, addr = self.socket.accept()
>   File "/usr/lib/python2.5/socket.py", line 167, in accept
>     sock, addr = self._sock.accept()
> timeout: timed out

Eh, this shouldn't happen there is no timeout on the accept!? I've never
seen this before and I've run livepause at home for, well before it was
released. Not a helpful answer I know but see the end of the email for
some hope.

> WHen this fails, I am still able to record using the record serer.

That's as expected as the record server is in a separate process. On that
note I'll answer a question that was asked earlier wrt does the record
button send the recording to the server or use the buffer? It uses the
contents of the stream buffer so in theory you should be able to watch a
program decided you want to keep it to show the misses and then hit record
and the whole thing get dumped into the recordings directory. I say in
theory as it was one area that didn't get enough testing due to not being
used at home.

And now one of those annoying it'll be fixed in the next release messages,
yes most of the issues raised should be fixed in the next release of
freevo (they are currently in svn if people want to test them, hint hint).
The current svn and the next release will need you to download and install
a new program, livepause from http://sf.net/projects/dvbstreamer, that
moves a lot of the code out of python into C. As a result there is now
only a 1 second delay before mplayer/xine/vlc is started and CPU usage (on
my system anyway) has dropped massively.

One thing I forgot to mention was you can select which player is used by
livepause by setting the LIVE_PAUSE2_PREFERRED_PLAYER variable to mplayer,
xine or vlc. A bit nicer than having to uninstall xine/vlc :-).

cheers

Adam


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to