On 8.11.2011 22:45, Chris Rankin wrote:
# netstat -napt |grep xine
tcp0 0 127.0.0.1:49124 127.0.0.1:37890
ESTABLISHED 5058/xine
It all looks reasonable. I can even (sometimes) persuade elements of the OSD to
appear in the xine-ui window by pressing
Le 09/11/2011 00:39, Mika Laitio a écrit :
What am I missing ? Thanks for helping.
Have you configured file:
plugins/xineliboutput/allowed_hosts.conf
Yes I put 127.0.0.1 in /video/plugins/xineliboutput/allowed_hosts.conf
with no result.
Here are the strace output for both
Your vdr-xineliboutput might not be the primary output device, you must
first change that before you see live video/audio.
On 9 November 2011 12:02, Damien Bally bir...@free.fr wrote:
Le 09/11/2011 00:39, Mika Laitio a écrit :
What am I missing ? Thanks for helping.
Have you configured
Tue, 8 Nov 2011 12:45:16 -0800 (PST)
Chris Rankin ranki...@yahoo.com wrote:
can you give output of this command's please?
lsmod |grep dvb
$ lsmod |grep dvb
em28xx_dvb 16720 11
cxd2820r 22613 3 em28xx_dvb
dvb_core 67728 2 em28xx_dvb,cxd2820r
Le 09/11/2011 11:19, Theunis Potgieter a écrit :
Your vdr-xineliboutput might not be the primary output device, you must
first change that before you see live video/audio.
I tried the following command line : vdr-Pxineliboutput --local=none
--primary --remote=37890
No success.
Damien
Am 09.11.2011 13:49, schrieb Damien Bally:
Le 09/11/2011 11:19, Theunis Potgieter a écrit :
Your vdr-xineliboutput might not be the primary output device, you must
first change that before you see live video/audio.
I tried the following command line : vdr-Pxineliboutput --local=none
Le 09/11/2011 13:58, Joerg Riechardt a écrit :
Am 09.11.2011 13:49, schrieb Damien Bally:
Le 09/11/2011 11:19, Theunis Potgieter a écrit :
Your vdr-xineliboutput might not be the primary output device, you must
first change that before you see live video/audio.
I tried the following
Am Mittwoch, 9. November 2011, 15:09:16 schrieb Damien Bally:
The output of vdr-sxfe is in the attached file.
[1163] [input_vdr] Server not replying
[1163] [input_vdr] Can't connect to tcp://127.0.0.1:37890
so
netstat -tulpn | grep 37890
probably does not show anything either - it should be
Le 09/11/2011 15:48, Wolfgang Rohdewald a écrit :
netstat -tulpn | grep 37890
probably does not show anything either - it should be something
like
tcp0 0 0.0.0.0:37890 0.0.0.0:*
LISTEN 3592/vdr
udp0 0 255.255.255.255:37890 0.0.0.0:*
vdr -Pxineliboutput --local=none --remote=37890 --primary
try: vdr -P'xineliboutput --local=none --remote=37890 --primary'
Using double-quotes is problematic.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Le 09/11/2011 18:56, VDR User a écrit :
vdr -Pxineliboutput --local=none --remote=37890 --primary
try: vdr -P'xineliboutput --local=none --remote=37890 --primary'
I gave it a try. Doesn't work :-(
___
vdr mailing list
vdr@linuxtv.org
Hi,
Since the driver doesn't allow to create only the frontend of the desired delivery type, here's a patch for
cDvbDevice. If there's no demux/dvr device with the frontend number it looks for one with a lower number.
Now it's possible to use -D 0 for DVB-C or -D 1 for DVB-T (change device
you must have an output xineplug_inp_xvdr.so then, you can play using
xine cmd line:
xine xvdr://127.0.0.1:37890
FYI, I have been successfully using xineliboutput *for years* with VDR 1.6.x.
The *only reason* I felt this worth reporting to the mailing list is because it
has all stopped
13 matches
Mail list logo
