VDR-FBFE(1)
β¨ vdr-fbfe(1) β Remote Framebuffer frontend for vdr-plugin-xineliboutput β¨
okay bestie, sit down, hydrate, because today we're talking about vdr-fbfe β the Remote Framebuffer frontend for vdr-plugin-xineliboutput. Yes it's a mouthful, no you don't have to say it out loud. It's from the vdr-fbfe(1) manual, and I'm about to make it make sense π
πΈ NAME πΈ
vdr-fbfe β Remote Framebuffer frontend for vdr-plugin-xineliboutput
fr fr that's the whole vibe: it's the little framebuffer buddy that talks to your VDR plugin.
π¦ SYNOPSIS π¦
vdr-fbfe [options] [xvdr[+udp|+tcp|+rtp]:[//host[:port]]]
that's it, that's the shape of it. options first, then the server thingy if you have one π
π DESCRIPTION π
So basically: vdr-fbfe is a Framebuffer remote frontend and its whole personality is playing back the streams that vdr-plugin-xineliboutput hands over. That's the job. It does the job. slay π«Ά
π OPTIONS π
okay here's the menu, and yes we're going through every single one, no skipping, no shortcuts:
--helpβ shows you this help message (the "help me help you" flag) π--audio=audiodriver[:device]β pick your audio driver, and if you want, an optional port too--video=videodriver[:fb_device]β pick your video driver plus an optional port. As far as supported, the possible video drivers might be:fb,DirectFB,sdl,vidixfb,dxr3,aadxr3ornoneπ¬--aspect=[auto|4:3|16:9|16:10|default]β sets the display aspect ratio. And bestie, listen: you can us a script to control the HW aspect ratio, like this β--aspect=auto:path_to_script--fullscreenβ fullscreen mode, main character energy, wall-to-wall pixels β¨--hudβ Head Up Display OSD mode (the overlay era)--width=xβ video window width--height=xβ video window height--noscalingβ disable all video scaling, we're keeping the pixels exactly where we found them--post=name[:arg=val[,arg=val]]β load and use xine post plugins, e.g.:--post=upmix--post=upmix;tvtime:enabled=1,cheap_mode=1)
--lirc[=devicename]β use the lirc input device. You can hand it an optional lirc socket name too π--verboseβ verbose debug output (the yapper mode)--silentβ silent mode, and it only reports errors. lowkey iconic--syslogβ write all output to the system log--nokbdβ disable keyboard input (hands off the keys, girlypop)--daemonβ run as a daemon: disables keyboard, logs to syslog, and forks to the background π--slaveβ enable slave mode, which reads commands fromstdin--reconnectβ automatically reconnect when the connection has been lost π«Ά--tcp,--udp,--rtpβ use TCP, UDP or RTP transport. And if you give no transport options at all, the transports get tried in this order: local pipe, rtp, udp, tcp β
π EXAMPLES π
bestie these are the ones you'll actually use, copy them exactly, no cap:
Search for a VDR (xineliboutput) server, connect to it, negotiate the best available transport, and use the best available audio and video driver:
vdr-fbfe
Connect to 192.168.1.3 on the default port and negoate the best available transport:
vdr-fbfe xvdr://192.168.1.3
Connect to 192.168.2.100, port 12550, and use TCP transport:
vdr-fbfe xvdr+tcp://192.168.2.100:12550
Automatically search for a VDR server and use UDP transport:
vdr-fbfe xvdr+udp:
vdr-fbfe --udp
Use alsa:
vdr-fbfe --audio alsa
Use alsa (and a specific card/sub-device):
vdr-fbfe --audio alsa:plughw:1,1
Framebuffer driver and device settings:
vdf-fbfe --video DirectFB
vdf-fbfe --video fb:/dev/fb/1
vdf-fbfe --video vidixfb
vdf-fbfe --video aadxr3
(yes, those are spelled vdf-fbfe in the examples β I'm not touching them, I don't make the rules π)
π₯ NOTE π₯
Listen up, this matters: if the deinterlacing post plugin options aren't given at the command line, then deinterlacing is controlled by the VDR plugin configuration menu settings.
De-interlacing can also be forced on or off with the command-line option "--post tvtime". Examples:
vdr-fbfe --post tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1
vdr-fbfe --post tvtime:enable=0
π AUTHOR π
This manual page was written by Tobias Grimm <etobi@debian.org> π
and that's the whole page, bestie!! π¦β¨ you now know vdr-fbfe better than most people know their own phone settings. it's from the vdr-fbfe(1) manual, signed and dated 10 February 2026, and you absolutely ate this whole read. go forth and stream. periodt π
π¦ where this page comes from
- ubuntu resolute: xineliboutput-fbfe 2.3.0-2build2
- ubuntu stonking: xineliboutput-fbfe 2.3.0-2build2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms