available on the system and create moer on-disk swap as needed. Additionally
Swap Extender will remove unwanted swap space when memory is freed.
WWW: http://makeapbi.sourceforge.net/
PR: ports/155955
Submitted by: Jesse Smith <jessefrgsmith@yahoo.ca>
Live, the "Live Interactive VDR Environment", is a plugin providing the
possibility to interactively control the VDR and some of it's plugins by
a web interface.
Unlike external utility programs that communicate with VDR and it's plugins
by SVDRP, Live has direct access to VDR's data structures and is thus very
fast.
WWW: http://live.vdr-developer.org/
X11 and Linux framebuffer front-end for VDR.
Plugin displays video and OSD in X/Xv/XvMC/VAAPI/VDPAU window,
Linux framebuffer/DirectFB/vidixfb or DXR3 card.
Support for local and remote frontends.
Built-in image and media player supports playback of most known
media files (avi/mp3/divx/jpeg/...), DVDs and radio/video streams
(http, rtsp, ...) directly from VDR.
FreeBSD Note: If you want to use VAAPI/VDPAU make sure the ffmpeg
and libxine ports are (re)built with the corresponding knobs turned on!
(make config in their port dirs.)
WWW: http://sourceforge.net/projects/xineliboutput/
UPnP/DLNA Plugin for Video Disk Recorder
This Plugins extends the VDR with the possibility to act as an UPnP/DLNA Media
Server (DMS). It will serve VDR's contents in the network to any UPnP-AV and
DLNA capable devices.
This still is an alpha version!
WWW: http://upnp.vdr-developer.org/
This PlugIn is a VDR implementation of the VTP (Video Transfer Protocol)
Version 0.0.3 (see file PROTOCOL) and a basic HTTP Streaming Protocol.
It consists of a server and a client part, but both parts are compiled together
with the PlugIn source, but appear as separate PlugIns to VDR.
The client part acts as a full Input Device, so it can be used in conjunction
with a DXR3-Card, XINE, SoftDevice or others to act as a working VDR
installation without any DVB-Hardware including EPG-Handling.
The server part acts as a Receiver-Device and works transparently in the
background within your running VDR. It can serve multiple clients and it can
distribute multiple input streams (i.e. from multiple DVB-cards) to multiple
clients using the native VTP protocol (for VDR-clients), or using the HTTP
protocol supporting clients such as XINE, MPlayer and so on. With XMMS or
WinAMP, you can also listen to radio channels over a HTTP connection.
WWW: http://streamdev.vdr-developer.org/
This VDR plugin is a MPEG2 decoder.
It can be used as an output device for the vdr. Possible output devices are
Xv, DirectFB, Vidix or a framebuffer.
WWW: http://softdevice.berlios.de/
This plugin extends the remote control capabilities of vdr.
The following remote control devices are supported:
(a) linux input device driver ('/dev/input/eventX', X=0,1,2,...)
(currently not supported on FreeBSD)
(b) keyboard (tty driver): /dev/console, /dev/ttyX
(c) TCP connection (telnet)
(d) LIRC
(e) some(?) FreeBSD uhid(4) devices (experimental support added by this port)
To use, add something like this to vdr_flags: '-Premote -h /dev/uhid0',
(re)start vdr, then the osd should ask you to configure the
remote by pressing the buttons you want to assign.
Note: If your remote is detected as a keyboard you'll have to
tell ukbd(4) to ignore it first by doing (as root) something like:
usbconfig add_dev_quirk_vplh 0x1241 0xe000 0 0xffff UQ_KBD_IGNORE
(and possibly unplug it for a moment or reset it via usbconfig,
0x1241 there is the vendor id, 0xe000 the product id of the
device, you can get yours by doing
usbconfig -d 1.2 dump_device_desc
and looking for idVendor and idProduct, -d 1.2 there corresponds
to ugen1.2 listed by usbconfig w/o args.)
You can check with:
usbconfig show_ifdrv
if the device is then listed as ugen...: uhid... you're good to go.
2nd note: If vdr cannot open your uhid device check it is not claimed
by xorg:
fstat |grep uhid
If it is you may need an xorg.conf(5) with manually defined
InputDevice sections for mouse and keyboard and
Option "AutoAddDevices" "False"
in the ServerFlags section.
And if for some reason you want to reassign the buttons on the
remote you can stop vdr and do:
touch /usr/local/etc/vdr/channels.conf
and/or remove uhid entries from
/usr/local/etc/vdr/remote.conf .
When you then start vdr again it should ask to configure the
remote again.
WWW: http://escape-edv.de/endriss/vdr
OSD Picture-in-Picture is a VDR PlugIn that displays the current channel
in a small box on the screen (default upper right corner). You can switch
up and down now, watching the progress of the previous channel in the box.
Quality is not too good yet, and only I-Frames are displayed.
WWW: http://projects.vdr-developer.org/projects/show/plg-osdpip
This plugin integrates multicast IPTV transport streams seamlessly into
VDR. You can use any IPTV channel like any other normal DVB channel for
live viewing, recording, etc. The plugin also features full section
filtering capabilities which allow for example EIT information to be
extracted from the incoming stream.
Currently the IPTV plugin has direct support for both multicast UDP/RTP
and unicast HTTP MPEG1/2 transport streams. Also a file input method is
supported, but a file delay must be selected individually to prevent
VDR's transfer buffer over/underflow. Therefore the file input should be
considered as a testing feature only.
IPTV plugin also features a support for external streaming applications.
With proper helper applications and configuration IPTV plugin is able to
display not only MPEG1/2 transport streams but also other formats like
MP3 radio streams, mms video streams and so on.
WWW: http://www.saunalahti.fi/~rahrenbe/vdr/iptv/
DVB Frontend Status Monitor is a VDR plugin that displays some signal
information parameters of the current tuned channel on OSD. You can zap
through all your channels and the plugin should be monitoring always the
right frontend. The transponder and stream information are also available
in advanced display modes.
WWW: http://www.saunalahti.fi/~rahrenbe/vdr/femon/
The 'control' plugin brings the ability to VDR to control
the whole OSD over a telnet client.
To reach this, 'control' listens on a network socket
(default is port 2002). If a client wants to connect, VDR
checks if that client is allowed to connect to VDR (see in
the documentation of VDR about the svdrphosts.conf file for
more info). If the connection is etablished, 'control'
sends the curent OSD state to the client. Also all key
strokes at the client side are redirected to VDR.
WWW: http://ricomp.de/vdr/down_en.html
for C++. To create webapplications Tntnet has a template-language called
ecpp similar to php, jsp or mason, where you can embed c++-code inside a
html-page to generate active content. The ecpp-files are precompiled to
c++-classes called components and compiled and linked into a shared
library. This process is done at compiletime.
WWW: http://www.tntnet.org/index.html
