Hi,<br><br>yesterday evening i followed your setup to create 1 client.<br>Server : VDR & VDR2 server<br>Client : vdr-sxfe<br><br>When i run the second VDR server i can't switch channels. It's bloked on channels attached to the first transponder (hope you understand what i mean). plz help...
<br><br>cheers,<br>'Z<br><br><div><span class="gmail_quote">2007/6/28, Alasdair Campbell <<a href="mailto:ragawu@gmail.com">ragawu@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 18/06/07, Alasdair Campbell <<a href="mailto:ragawu@gmail.com">ragawu@gmail.com</a>> wrote:<br>> On 16/06/07, Petri Hintukainen <<a href="mailto:phintuka@users.sourceforge.net">phintuka@users.sourceforge.net
</a>> wrote:<br>> > On Wed, 2007-06-13 at 19:16 +0100, Alasdair Campbell wrote:<br>> > > Is it possible to have one of the VDR 'servers/instances' to be<br>> > > running on one of the clients rather than the main server pc?
<br>> ><br>> > Yes. Then you don't need the -D option.<br>> ><br>> > > The exact same setup except Client2 has an instance of VDR running in the<br>> > > background with 1 dvb card saving files to the server's /video mounted
<br>> > > over nfs.<br>> > > Ideally all Clients + Master VDR Server will see channels on Client<br>> > > 2's satellite feed and be able to register timers on that server.<br>> ><br>> > This is more complicated :)
<br>> ><br>> > I think you need to set every timer manually to the system where it is<br>> > supposed to be recorded. Timersync won't work as it disables all<br>> > recording at client(s). Using timersync and enabling recording at the
<br>> > client won't work if you use streamdev: both systems will see the same<br>> > channels and would record the same timers in paraller.<br>> ><br>> > Maybe something like this might work:<br>
> > VDR1: (2x DVB-?):<br>> > streamdev-server, streamdev-client connected to VDR2<br>> > VDR2: (1x DVB-S):<br>> > streamdev-server, streamdev-client connected to VDR1<br>> > VDR3: (no DVB):
<br>> > 2 instances of streamdev-client: one connected to VDR1 and another to<br>> > VDR2.<br>> ><br>> > Note that circular streamdev setup doesn't work without patching<br>> > ( <a href="http://www.vdr-developer.org/mantisbt/view.php?id=198">
http://www.vdr-developer.org/mantisbt/view.php?id=198</a> )<br>> ><br>> > > If there was a way for PCI buses to traverse networks, then the<br>> > > location of the 3rd card wouldn't be an issue, but I don't believe
<br>> > > that's possible...<br>> ><br>> > No, but transferring the device interface (/dev/dvb/...) over network is<br>> > possible with something like nbd (network block device). I think I saw
<br>> > similar redirector for DVB devices few years ago:<br>> > <a href="http://linuxtv.org/mailinglists/linux-dvb/2004/08-2004/msg00326.html">http://linuxtv.org/mailinglists/linux-dvb/2004/08-2004/msg00326.html
</a><br>> > But it seems quite old and unmaintained.<br>><br>> I remember reading about this years ago, if it could work then it<br>> would be ideal for my situation - maybe for others too. Vadim Epmak's
<br>> address is bouncing so I'll ask on the DVB mailing list and see if<br>> anyone else ever got it up and running.<br>><br>> I'm keen on trying it out myself, and have started reading about<br>> porting drivers to
2.6 kernels. Could be an interesting way to learn<br>> more C ;-)<br><br>In hindsight, I believe learning C on my own by porting a driver to<br>the 2.6 kernel was a tad optimistic..<br><br>Sill won't compile, and I haven't got to grips with the changes in the
<br>dvb api from when this was written.<br><br>No response yet on the linuxtv list. I'll keep working at the code -<br>it could be a fun way to learn, and the principle seems quite<br>straight-forward.<br><br>_______________________________________________
<br>vdr mailing list<br><a href="mailto:vdr@linuxtv.org">vdr@linuxtv.org</a><br><a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr">http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a><br></blockquote></div><br>