Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
vdr [2013/05/13 19:37] – Quote final install steps at the end of quick install so it doesn't get overlooked JuergenLockvdr [2022/09/19 01:31] (current) – Remove unecessary ACL and spurious horizontal rule KubilayKocak
Line 1: Line 1:
----- 
- 
 ===== What is VDR? ===== ===== What is VDR? =====
  
Line 28: Line 26:
  
 And finally, if you want to compare vdr to other existing ports, And finally, if you want to compare vdr to other existing ports,
-it's a bit like [[MythTV|MythTV]] - only most Linux users _I_ know prefer vdr+it's a bit like [[Ports/multimedia/mythtv|MythTV]] - only most Linux users _I_ know prefer vdr
 over mythtv. :)  (and vdr also doesn't use a rdbms so you don't over mythtv. :)  (and vdr also doesn't use a rdbms so you don't
 have to worry about mysql etc.) have to worry about mysql etc.)
Line 64: Line 62:
      -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol \      -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol \
      -Pinfosatepg -Piptv -Pwirbelscan -Preelchannelscan -Pttxtsubs \      -Pinfosatepg -Piptv -Pwirbelscan -Preelchannelscan -Pttxtsubs \
-     -Pxvdr -Pextrecmenu"+     -Pvnsiserver -Pextrecmenu"
 </code> </code>
  
Line 82: Line 80:
  
 <code> <code>
-vdr '-Pxineliboutput --local=none --remote=127.1:37890' -Pskinenigmang -Pfemon -Posdpip '-Posdteletext --cache-system=packed --max-cache=128' -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol -Pinfosatepg -Piptv -Pwirbelscan -Preelchannelscan -Pttxtsubs -Pxvdr -Pextrecmenu+vdr '-Pxineliboutput --local=none --remote=127.1:37890' -Pskinenigmang -Pfemon -Posdpip '-Posdteletext --cache-system=packed --max-cache=128' -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol -Pinfosatepg -Piptv -Pwirbelscan -Preelchannelscan -Pttxtsubs -Pvnsiserver -Pextrecmenu
 </code> </code>
  
Line 238: Line 236:
  
 and you can put a custom one in ~/.xbmc/userdata/Lircmap.xml . and you can put a custom one in ~/.xbmc/userdata/Lircmap.xml .
 +
 +  * Update: The main multimedia/xbmc port now supports pvr too via multimedia/xbmc-addon-pvr and multimedia/vdr-plugin-vnsiserver (-Pvnsiserver instead of -Pxvdr), since this is a newer xbmc version than the xbmc-pvr port it's probably preferred.
  
 ==== Controlling the OSD: Keyboard (not for XBMC-PVR) ==== ==== Controlling the OSD: Keyboard (not for XBMC-PVR) ====
  
-  * Unless you want to get lirc or the (experimental) %%FreeBSD%% uhid(4) patches in the vdr remote plugin working first (and your remote has enough buttons for vdr, some of those coming with dvb tuners are really quite `minimal', see below), you probably will at least initially want to use keyboard control.  I have included an example remote.conf for vdr-sxfe and the multimedia/vdr-plugin-control plugin that you can access by telnet (default port is 2002), I have put the menu button on the tab and insert keys and OK on the return key, see /usr/local/etc/vdr/remote.conf for the full keybindings list.  (If you start vdr in the foreground and keep that shell open you should be able to use that for keyboard control also, the control plugin just gives you an osd too over telnet.)+  * Unless you want to get lirc or the (experimental) %%FreeBSD%% uhid(4) patches in the vdr remote plugin working first (and your remote has enough buttons for vdr, some of those coming with dvb tuners are really quite `minimal', see below), you probably will at least initially want to use keyboard control.  I have included an example remote.conf for vdr-sxfe and the multimedia/vdr-plugin-control plugin that you can access by telnet (default port is 2002) 
 + 
 +  * I have put the menu button on the tab and insert keys and OK on the return key, see /usr/local/etc/vdr/remote.conf for the full keybindings list.  (If you start vdr in the foreground and keep that shell open you should be able to use that for keyboard control also, the control plugin just gives you an osd too over telnet.)
  
 And if you use xine And if you use xine
Line 438: Line 440:
      -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol \      -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol \
      -Pinfosatepg -Piptv -Pwirbelscan -Preelchannelscan -Pttxtsubs \      -Pinfosatepg -Piptv -Pwirbelscan -Preelchannelscan -Pttxtsubs \
-     -Pxvdr -Pextrecmenu"+     -Pvnsiserver -Pextrecmenu"
 </code> </code>
 +
 +(in general plugin vdr-plugin-foo is loaded by -Pfoo and may take args explained in /usr/local/share/doc/vdr-plugin-foo/README, like '-Pfoo -bar -baz' - so if you want to use, say, vdr-plugin-vdrmanager also then add -Pvdrmanager.)
  
   * Now make sure the tuner is plugged in and working: (assuming you want to use a tuner and not iptv or the streamdev-client plugin)   * Now make sure the tuner is plugged in and working: (assuming you want to use a tuner and not iptv or the streamdev-client plugin)
Line 447: Line 451:
 </code> </code>
  
-(there should be at least one adapterX dir with demux0, dvr0, and frontend0 device nodes)  See also this forum thread for hints about drivers providing /dev/dvb nodes: http://forums.freebsd.org/showthread.php?p=193811+(there should be at least one adapterX dir with demux0, dvr0, and frontend0 device nodes)  See also this forum thread for hints about drivers providing /dev/dvb nodes: http://forums.freebsd.org/viewtopic.php?t=35179
  
   * If you don't have a tuner you probably want to tell the vdr rc.d script not to wait for the tuner(s) to appear at vdr start:   * If you don't have a tuner you probably want to tell the vdr rc.d script not to wait for the tuner(s) to appear at vdr start:
Line 492: Line 496:
 </code> </code>
  
-You can get more fancy like by adding a login class to vdr's passwd(5) entry (or a giving it a homedir and then +You can get more fancy like by adding a login class to vdr's passwd(5) entry (or a giving it a homedir, 
-putting a ~/.login_conf file there like this:+ 
 +<code> 
 +pw usermod vdr -d /video 
 +</code> 
 + 
 +and then putting a ~vdr/.login_conf file there like this:
  
 <code> <code>
Line 534: Line 543:
  
   * Port more plugins that people might want to use...   * Port more plugins that people might want to use...
 +
 +----
 +
 +{{tag>Ports}}
  
  • vdr.1368473847.txt.gz
  • Last modified: 2013/05/13 19:37
  • by JuergenLock