diff mbox

Xine - with network support?

Message ID 424614EA.2020809@syphir.sytes.net
State New
Headers

Commit Message

C.Y.M March 27, 2005, 2:05 a.m. UTC 
  norm@dressler.ca wrote:
> Hi all,
> 
> I'm currently using the xine plugin with network support.  Works fine for the 
> most part but I'm getting the occasional drop or freeze on my 1Ghz Pentium 
> notebook with 10meg wireless.
> 
> Is there an updated version available yet or is this it?  
> 

Does this patch help? It was posted on vdrportal.

Comments

norm@dressler.ca March 28, 2005, 10:50 p.m. UTC | #1 
I tried this patch but it makes no difference.  It takes a long time for xine 
on my notebook to buffer or sync it seems.  Then it will drop frames on 
occasion.  Sometimes its worse then others.  My notebook is the only wireless 
device on the network.  The desktop with vdr is directly connected to the 
wireless router.

Vdr shows me this:
vdr-xine: incoming requests on 15
vdr-xine: successful request on 15 (client: 21)
vdr-xine: polling for connection on 16...
vdr-xine: incoming requests on 16
vdr-xine: successful request on 16 (client: 22)
vdr-xine: polling for connection on 17...
vdr-xine: incoming requests on 17
vdr-xine: successful request on 17 (client: 26)
vdr-xine: polling for connection on 18...
vdr-xine: incoming requests on 18
vdr-xine: successful request on 18 (client: 27)
Pvdr-xine: Client connected!
[vVMaA+19+20+23+26]
PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP

The P's come up when everything is messed up.  Sometimes if I change channels 
then return it fixes itself a bit quicker.  Using the same setup but with 
xine locally on the same machine as vdr, everything works great.

Norm

On March 26, 2005 09:05 pm, C.Y.M wrote:
> norm@dressler.ca wrote:
> > Hi all,
> >
> > I'm currently using the xine plugin with network support.  Works fine for
> > the most part but I'm getting the occasional drop or freeze on my 1Ghz
> > Pentium notebook with 10meg wireless.
> >
> > Is there an updated version available yet or is this it?
>
> Does this patch help? It was posted on vdrportal.
Stefan Taferner March 29, 2005, 10:15 a.m. UTC | #2 
On Tuesday 29 March 2005 00:50, norm@dressler.ca wrote:
> I tried this patch but it makes no difference.  It takes a long time for
> xine on my notebook to buffer or sync it seems.  Then it will drop frames
> on occasion.  Sometimes its worse then others.  My notebook is the only
> wireless device on the network.  The desktop with vdr is directly connected
> to the wireless router.

You could do some network tests to ensure that it is the xine plugin which
has the problems.

E.g. have a look at "netstat -i" and see if there are errors (RX-ERR, TX-ERR),
or try a flood ping, or do a bulk transfer of some large file.

Kind regards,
Stefan
syrius.ml@no-log.org March 29, 2005, 10:31 a.m. UTC | #3 
Stefan Taferner <taferner@kde.org> writes:

>> I tried this patch but it makes no difference.  It takes a long time for
>> xine on my notebook to buffer or sync it seems.  Then it will drop frames
>> on occasion.  Sometimes its worse then others.  My notebook is the only
>> wireless device on the network.  The desktop with vdr is directly connected
>> to the wireless router.
>
> You could do some network tests to ensure that it is the xine plugin which
> has the problems.
>
> E.g. have a look at "netstat -i" and see if there are errors (RX-ERR, TX-ERR),
> or try a flood ping, or do a bulk transfer of some large file.

Or better, try to reproduce it on a wired network !

--
diff mbox

Patch

diff -u --recursive xine-0.7.2.orig/xineLib.c xine-0.7.2/xineLib.c
--- xine-0.7.2.orig/xineLib.c	2005-03-09 09:26:19.000000000 +0200
+++ xine-0.7.2/xineLib.c	2005-03-10 15:03:02.000000000 +0200
@@ -2007,6 +2007,13 @@ 
       
       ::signal(SIGPIPE, sigPipeHandler);
       
+      if (r == 0)
+      {
+	  fprintf(stderr, "deadlock! (no more)\n");
+	  disconnect();
+	  return -1;
+      }
+
       if (r < 0)
       {
         if (EAGAIN == myErrno)