Re: [vdr] xineliboutput and streamdev at the same time
On Mon, Apr 20, 2015 at 03:15:08PM +0200, Patrick Boettcher wrote: Is it technically possible to for example pause a live SD TV stream and copy some files over the Ethernet at the same time? Which scenario? VDR on RPI or on a remote? If VDR on a remote host, IIRC, pausing causes very few bandwidth as only a still image is displayed. VDR client+server on the same RPi. I guess it is simply too much to ask of the poor RPi. The pause is global to all connected clients to this vdr-remote. Yes, you can connect several clients to one xineliboutput-vdr-host but they will all have the same channel and OSD appearances displayed - IOW, they are not independent. I see, so it would not be a solution if you wanted to have independent clients connected to the same VDR (watching different recordings, for example). Yes. IMHO, it is better to use RPI only as client with no harddisk. It seems that vdr-fbfe could allow an inexpensive and small solution where a generic headless ARM-based NAS box acts as the server, and the RPi (attached on the back side of the TV) acts as the client. I guess that the server could simultaneously serve other clients via other plugins (such as the SmartTVweb plugin). Marko ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
On Mon, 20 Apr 2015 16:05:45 +0300 Marko Mäkelä marko.mak...@iki.fi wrote: On Mon, Apr 20, 2015 at 11:40:41AM +0200, Patrick Boettcher wrote: vdr-fbfe is connecting over network to a vdr running on a full machine. No need for streamdev. This looks interesting. Am I right assuming that the full machine will not need any video output? Yes, you are right. Vdr is running like a daemon. Can vdr-fbfe be used for editing recordings on the RPi, or is there too much latency when using 10Mb/s Ethernet to connect to an old VDR server? I'd not recommend a 10Mb/s. Fast Ethernet (100Mb/s) should be the minimum. How about using vdr-fbfe to connect on a vdr instance running on the same RPi machine? Yes. Is it technically possible to for example pause a live SD TV stream and copy some files over the Ethernet at the same time? Which scenario? VDR on RPI or on a remote? If VDR on a remote host, IIRC, pausing causes very few bandwidth as only a still image is displayed. The pause is global to all connected clients to this vdr-remote. Yes, you can connect several clients to one xineliboutput-vdr-host but they will all have the same channel and OSD appearances displayed - IOW, they are not independent. The single USB bus on the RPi would in that case need to handle the traffic of a hard disk adapter as well as the DVB dongle and the built-in Ethernet controller. Yes. IMHO, it is better to use RPI only as client with no harddisk. -- Patrick. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
On Mon, Apr 20, 2015 at 11:40:41AM +0200, Patrick Boettcher wrote: vdr-fbfe is connecting over network to a vdr running on a full machine. No need for streamdev. This looks interesting. Am I right assuming that the full machine will not need any video output? Can vdr-fbfe be used for editing recordings on the RPi, or is there too much latency when using 10Mb/s Ethernet to connect to an old VDR server? How many remote controller buttons do you typically get mapped via HDMI-CEC? How about using vdr-fbfe to connect on a vdr instance running on the same RPi machine? Is it technically possible to for example pause a live SD TV stream and copy some files over the Ethernet at the same time? The single USB bus on the RPi would in that case need to handle the traffic of a hard disk adapter as well as the DVB dongle and the built-in Ethernet controller. Marko ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
On Mon, 20 Apr 2015 11:33:02 +0200 Torgeir Veimo torgeir.ve...@gmail.com wrote: Have you tried rpihddevice plugin with VDR on the rpi? It might work even smoother than using xinelinboutput, but you'd have to find a different setup for cec i suppose. http://projects.vdr-developer.org/git/vdr-plugin-rpihddevice.git/ I think the big difference between rpihddevice and vdr-fbfe is that the vdr-fbfe does not need a local vdr-instance running on the device. vdr-fbfe is connecting over network to a vdr running on a full machine. No need for streamdev. Thank you both for your input. regards, -- Patrick. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
On pe, 2015-04-17 at 09:25 +0200, Patrick Boettcher wrote: Hi list, I'm planning to update my infrastructure according to the follow scheme: http://filter-failure.eu/wp-content/uploads/2015/01/vdr-new-backend.png The red texts are things where I'm unsure about. Especially the usage of vdr-sxfe on the RPI. I've been using xineliboutput (vdr-fbfe) with RPi for ~ year without problems. Hardware decoding and OSD work well with recent xine-lib. With RPi you want to use vdr-fbfe (not vdr-sxfe). RPi HW video decoding and video output work just well without X11. Faster startup, less stuff to configure and install. I've also used TV's remote controller to control VDR (vdr-fbfe supports HDMI-CEC with RPi). This all makes RPi quite nice VDR client; it is small, silent and requires only two or three cables (power, HDMI, optional wired network). I made this chart before finding out that there is rpihddevice and a recommended streamdev-usage. This shows that I have a need for streamdev and xineliboutput (as others on this list). Is there problem with running the xineliboutput and streamdev-server plugins at the same time on a vdr-host? No When will we start facing problems using the xineliboutput-plugin with VDR? What is most likely to break first in this case? Thanks for any comments, -- Patrick. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
Am 20.04.2015 um 15:34 schrieb Marko Mäkelä: On Mon, Apr 20, 2015 at 03:15:08PM +0200, Patrick Boettcher wrote: Is it technically possible to for example pause a live SD TV stream and copy some files over the Ethernet at the same time? Which scenario? VDR on RPI or on a remote? If VDR on a remote host, IIRC, pausing causes very few bandwidth as only a still image is displayed. VDR client+server on the same RPi. I guess it is simply too much to ask of the poor RPi. Kodi and vnsi-addon + vdr and vnsi-server-plugin are working on the same RPi, and it is a much heavier load than your setup. I can't see why this shouldn't work. Gerald !DSPAM:55352184204551113121336! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EPG Problem on vdr 2.2.0
http://www.prograss.fr/gazons/realisations/sport-9/practice-de-golf-a-st-herblain-10.html Le 18 avr. 2015 à 12:30, Risto Pajula rippe.shack...@gmail.com a écrit : Hello. For some reason I'm not able to reproduce this bug today... Both 2.0.6 and 2.2.0 work normally. I will get back with more info, if the bug reappears. BR. Risto 2015-04-18 12:32 GMT+03:00 Klaus Schmidinger klaus.schmidin...@tvdr.de: On 18.04.2015 00:45, Risto Pajula wrote: Hello. After rebuilding my HTPC I have run into a problem in the EPG data retrieval. The vdr is not able to retrieve any EPG data from DVB-T broadcast. My system consist of. Opensuse 13.2 x64 based system Linux kernel 3.16.7-7-desktop Hauppauge WinTV-NOVA-T-500 using dvb-usb-dib0700-1.20.fw firmware. vdr built from source... And I'm located in Finland (Vaasa). I have tracked this bug down to the changes between the vdr 2.0.5 and the 2.0.6, and are it still existing in the vdr 2.2.0... This exactly same issue was described in may 2014 by another user. http://www.vdr-portal.de/board79-international/board80-software/123136-epg-not-working-vdr-2-0-6/ Please activate the line //#define DEBUG_PAT_PMT in pat.c and tune to a channel that shows the problem. Do this with both version 2.0.5 and 2.0.6 and send me the debug output of both versions. In order to have proper starting conditions please start VDR in both cases with the channel already set to the one that's problematic. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
