On 6/9/07, <b class="gmail_sendername">Petri Hintukainen</b> <<a href="mailto:phintuka@users.sourceforge.net">phintuka@users.sourceforge.net</a>> wrote:<div><span class="gmail_quote"></span>If you don't watch different recordings / channels at the same time you
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">can just run vdr-sxfe at each client and connect to the single VDR<br>server. You'll get same video + OSD mirrored to all locations.
<br><br>But, if you need to have independently controlled clients with own video<br>and OSD, you need to run several instances of VDR - it doesn't matter if<br>you run all VDR instances on server or at each client. I run several VDR
<br>instances on the server:<br> - less maintenance, only one installation of VDR and<br> plugins required<br> - allows using diskless clients (and with less memory)<br> - Faster cutting / DVD burning / ... as there is no
<br> network between VDR and disks<br> - no need to export/mount /video to every client<br> - ...<br><br>Here's how I do it:<br><br> master VDR: DVB cards, recordings, server for client 1:<br> vdr -c /etc/vdr \<br>
-P"xineliboutput --local=none --remote=37890" \<br> -Pstreamdev-server<br> server for client 2:<br> vdr -c /etc/vdr2 \<br> -D 10 \<br> -P"xineliboutput --local=none --remote=37892" \
<br> -Pstreamdev-client<br> server for client 3:<br> vdr -c /etc/vdr3 \<br> -D 10 \<br> -P"xineliboutput --local=none --remote=37894" \<br> -Pstreamdev-client<br><br>+ other options / plugins you normally use.
<br><br>Using -D 10 option for client VDR instances "forces" all DVB cards for<br>master VDR. Streamdev plugin is used to provide live view for client<br>VDR's, it is not required to just watch recordings.<br>
You must use separate configuration directory for each VDR (-c option).<br>Without it you'll most likely break all recordings (all VDRs record all<br>timers in paraller to same recording directory).<br><br>And at clients:
<br> Client 1:<br> vdr-sxfe<br> Client 2:<br> vdr-sxfe xvdr://<server ip>:37892<br> Client 3:<br> vdr-sxfe xvdr://<server ip>:37894<br><br>If you use RTP between vdr and vdr-sxfe, using separate RTP address or
<br>port for each xineliboutput server instance might be good idea.<br><br>Also it might be good idea to disable recording at all but the "master"<br>vdr. Recording the same timer on two VDR instances will most likely
<br>corrupt whole recording. Besides that, doing all recordings directly<br>from DVB card (no streamdev in middle) makes things simpler and less<br>error prone. It is probably even impossible to do several recordings<br>from different transponders using single streamdev instance.
<br>I use timersync plugin to disables recording on client VDRs. All timers<br>are still visible at each client and you can create/modify timers at any<br>client just as before. Plugin synchronizes all modifications to timers
<br>between VDR instances and takes care that all recordings are made only<br>by "master" vdr. Still, if you have some kind of autotimer plugins etc.<br>that generate timers automatically it might be better to run those only
<br>at server vdr...<br><br><br>- Petri<br><br></blockquote></div><br>Hi Petri,<br>
<br>
Thanks for providing exactly the info I needed. Much appreciated indeed :-)<br>
<br>
Andrew<br>