On 6/9/07, <b class="gmail_sendername">Petri Hintukainen</b> <<a href="mailto:email@example.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">firstname.lastname@example.org</a>> wrote:
<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sat, 2007-06-09 at 18:15 +0100, Andrew Herron wrote:<br>> I have several networked vdr machines that i want to use to connect<br>> back to the 'server' vdr machine. The networked vdr machines will have<br>
> no dvb cards (they will all be located at the vdr server). How do i<br>> configure my vdr client machines to connect back to the server vdr<br>> machine and use its dvb cards/recording storage etc?<br>><br>
> Can anyone give some guidance on this type of setup or point me at a
<br>> url where I can find out about such a config?<br><br>If you don't watch different recordings / channels at the same time you<br>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><br>_______________________________________________<br>vdr mailing list<br><a href="mailto:email@example.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
firstname.lastname@example.org</a><br><a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a></blockquote><div><br><br>Hi Petri, <br></div><br></div>I have few questions after testing your suggestions above to achieve independently controlled clients with their own video
<br>and OSD;<br><br>I would like all recordings to be managed/controlled by the master vdr as this would seem to be the best solution. However if I have say a single twin tuner DVB-T card and the master vdr is controlling all recordings is it still possible for the remote clients to schedule a recording via the master vdr if the timersync plugin is used? I think that you are saying this is possible... which is great!
<br><br>I have created separate /etc/vdr2 & /etc/vdr3 directories by copying /etc/vdr Will this work ok? As both /etc/vdr3 & /etc/vdr3 are exact copies of /etc/vdr without any changes in the conf files etc. Is this what you meant or do i need to make any changes in /etc/vdr3 & /etc/vdr3 ?