vdr February 2015

vdr@linuxtv.org

34 participants
20 discussions

xmltv2vdr.pl
by Dominic Evans 14 Aug '15

14 Aug '15

I don't know if anyone else still uses the xmltv2vdr.pl perl script for piping XMLTV data into VDR's epg, but I've been keeping a version of it updated with some additional function here: https://github.com/oldmanuk/xmltv2vdr These are the changes since the last version (1.0.9) was released on the mailing list - Add support for XMLTV episode-num. Currently gets added as EPG entry 'sub-title', if no existing subtitle has been found, in the form sXXeXX (e.g., Bones~s01e01). - Change default SVDRP port number to 6419. - Better support for ATSC/PVRINPUT EPG sources. - Allow multiple channels to have the same XMLTV channel id, useful for multi input (e.g., DVB-T, DVB-S) systems where you want to feed VDR the same info. Previously only a 1:1 mapping was permitted. I've also received a pull request from someone who rewrote the whole script to be a lot more readable and to use full XML parsing (rather than just line-by-line scraping), but I still need to investigate what the performance penalty is before accepting that in.

6 10

VDR & Multiple frontends
by Eddi 25 Jul '15

25 Jul '15

Hi, I wrote a patch to Steve Toth hvr3000 repository, so my FlyDVB Trio can use multiple frontend. So I get: /dev/dvb/adapter0/demux0 /dev/dvb/adapter0/demux1 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/dvr1 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/net1 The bus of the two frontend is shared, isn't possible to get access to both frontend simultaneously, so I get an -EBUSY error by trying accessing frontend1 if frontend0 is in use. VDR doesn't support yet the second frontend, and it try to get exclusive access on both frontend on start, so the second frontend is inusabile. Vdr should probe for multiple frontend at start, and access frontend only on channel change. Please can someone give me an help to wrote a patch for this issue? Best Regards, Eddi

4 21

sub-titles on Arte
by Peter Münster 27 Feb '15

27 Feb '15

Hi, There must be something wrong with my VDR-setup, I never see sub-titles on Arte. This is my channel.conf line: arte HD;ARD:11493:HC23M5O35P0S1:S19.2E:22000:5111=27:5112=deu@3,5113=fra@3,5117=mis@3;5116=mul@106:5114;5115=deu,5118=fra,5119=deu:0:10302:1:1019:0 How could I get sub-titles for this channel please? TIA for any hints, -- Peter P.S.: Thanks to Klaus and the other developers for the latest improvements!

3 6

"VIM syntax" for VDR channels.conf
by Zouhair 23 Feb '15

23 Feb '15

Hi, Did you know if "Vim syntax" of channels.conf is available ? is a nice to see color in the columns of channels.conf :) Thanks.

1 0

[ANNOUNCE] VDR version 2.2.0 released - Celebrating 15 years of VDR!
by Klaus Schmidinger 22 Feb '15

22 Feb '15

VDR version 2.2.0 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.2.0.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.tvdr.de/vdr/vdr-2.1.10-2.2.0.diff MD5 checksums: 8853f64c0fc3d41ffd3b4bfc6f0a14b7 vdr-2.2.0.tar.bz2 2d75806f90a4f1c8b3e30d7568891dc6 vdr-2.1.10-2.2.0.diff A summary of all the major changes since the last stable version 2.0.0 can be found at http://www.tvdr.de/changelog.htm When updating from an earlier version of VDR please make sure you read the INSTALL and MANUAL files that come with the VDR source _before_ doing so! Please make sure you have backup copies of all your configuration files, and verify carefully that your timers will be set to the correct channels after switching to this new version. Thanks to the many people who have contributed in the making, testing and debugging of this new version of VDR, and also to all users who have been enjoying VDR over the past 15 years! Please also visit the VDR homepage at http://www.tvdr.de and VDR's facebook page at https://www.facebook.com/VideoDiskRecorder Have fun! Klaus

13 16

merge 3 recordings of the same show to remove glitches?
by cedric.dewijs＠telfort.nl 19 Feb '15

19 Feb '15

Hi vdr list, I have recorded the same show 3 times. The reception was not optimal, so the are a few places where there are glitches in the recordings. When I play the files with mplayer, i see messages in the terminal as mplayer tries to conceal the errors. The glitches are not in the same place on the 3 recordings. Is there some software that can detect the errors, and then replace the damaged sections with correct data from the other 2 files? Kind regards, Cedric

4 6

Documentation and thoughts on ARGSDIR (first draft)
by Lars Hanisch 18 Feb '15

18 Feb '15

Hi, I wrote down the thoughts I had in mind when developing the conf.d patch which got integrated in vdr 2.1.7. Also I like to give some advice to distributors how I think, this feature should be used. If we can agree on a consistent naming and file-layout all users can profit. At the end there's an RFC for an interface to a not-yet-written tool "vdrctl" for managing the args-conf-files. Any comments and improvements are welcome. Regards, Lars. Using ARGSDIR ------------- The target of the "conf.d patch" is to simplify the start of vdr esp. with the newer init systems Upstart and systemd. These systems expect a single "exec" line to start a daemon. Additionally they provide mechanism for monitoring, restart on failure and controlled stopping on shutdown with defined dependencies. In the past vdr needed a long list of options, every plugin had to be mentioned, and if a plugin also needs options, the commandline gets longer and confusing. There's also the runvdr template for controlling the start and restart of vdr, which has to be adjusted to your personally needs, which makes it difficult for distributions to update these script. That is why the different distributions developed their own starting mechanisms and reading options for vdr and plugins from different files. Now with all options separated from the starting script, it will be easier to share the same configuration on different platforms and improve helping each other in adding the right options to your vdr installation. By default, the conf-files are located at /etc/vdr/conf.d, of course this can be changed via the Make.config, but not on the commandline itself, because a vdr with an option won't read the options from the conf-files to maintain backwards compatibility, so you can't choose a directory on demand. But what you can do, is to symlink different files to your conf.d-directory or even symlink the whole directory, to adjust your configuration. Additionally the directory can be retrieved by using "pkg-config --variable=argsdir vdr". To check the current configuration the vdr would use if you start it right now, you can call "vdr --showargs". Here's an example from my installation: $ vdr --showargs --video=/srv/vdr/video.00 --config=/var/lib/vdr --lib=/usr/lib/vdr/plugins --record=/usr/lib/vdr/vdr-recordingaction --shutdown=/usr/lib/vdr/vdr-shutdown.wrapper --epgfile=/var/cache/vdr/epg.data --user=vdr --grab=/tmp --port=6419 --resdir=/usr/share/vdr --cachedir=/var/cache/vdr --dirnames=,,1 --watchdog=0 --userdump --plugin=epg2vdr --plugin=channellists --plugin=sundtek --plugin=avahi4vdr --plugin=dbus2vdr --shutdown-hooks=/usr/share/vdr/shutdown-hooks --shutdown-hooks-wrapper=/usr/share/vdr-plugin-dbus2vdr/shutdown-wrapper --upstart --plugin=epgsearch -f /usr/bin/svdrpsend --plugin=live --port=8008 --ip=0.0.0.0 --log=INFO --epgimages=/var/cache/vdr/epgimages --plugin=menuorg --plugin=vnsiserver -t 10 --plugin=streamdev-server --plugin=softhddevice -D --plugin=epgsearchonly --plugin=recsearch --plugin=restfulapi --port=8002 --ip=0.0.0.0 --epgimages=/var/cache/vdr/epgimages --channellogos=/usr/share/vdr-channellogos --webapp=/var/lib/vdr/plugins/restfulapi/webapp --plugin=quickepgsearch --plugin=conflictcheckonly --plugin=skindesigner --epgimages=/var/cache/vdr/epgimages --plugin=dynamite The corresponding conf file looks like: #### /etc/vdr/conf.d/vdr.conf [vdr] --video=/srv/vdr/video.00 --config=/var/lib/vdr --lib=/usr/lib/vdr/plugins --record=/usr/lib/vdr/vdr-recordingaction --shutdown=/usr/lib/vdr/vdr-shutdown.wrapper --epgfile=/var/cache/vdr/epg.data --user=vdr --grab=/tmp --port=6419 --resdir=/usr/share/vdr --cachedir=/var/cache/vdr --dirnames=,,1 --watchdog=0 --userdump [epg2vdr] [channellists] [sundtek] [avahi4vdr] [dbus2vdr] --shutdown-hooks=/usr/share/vdr/shutdown-hooks --shutdown-hooks-wrapper=/usr/share/vdr-plugin-dbus2vdr/shutdown-wrapper --upstart [epgsearch] -f /usr/bin/svdrpsend [live] --port=8008 --ip=0.0.0.0 --log=INFO --epgimages=/var/cache/vdr/epgimages [menuorg] [vnsiserver] -t 10 [streamdev-server] [softhddevice] -D [epgsearchonly] [recsearch] [restfulapi] --port=8002 --ip=0.0.0.0 --epgimages=/var/cache/vdr/epgimages --channellogos=/usr/share/vdr-channellogos --webapp=/var/lib/vdr/plugins/restfulapi/webapp [quickepgsearch] [conflictcheckonly] [skindesigner] --epgimages=/var/cache/vdr/epgimages [dynamite] #### end of /etc/vdr/conf.d/vdr.conf "showargs" takes as an optional parameter a directory. It will read all *.conf files from the given directory and prints the corresponding configuration. This is helpful if you have various configurations and want to compare them. Distributors ------------ In the example above I use a single conf file. For a self maintained installation this may be usable, but from the perspective of a distributor the configuration should be splitted into one file per plugin and a file for vdr itself. With a package manager in mind, it has been approved, when you install a default configuration file with a plugin package, this file should be placed at /etc/vdr/conf.avail. To activate the plugin, a symlink can be placed at the conf.d directory. And with removing the symlink a plugin can easily be deactivated without removing the whole package. Keep in mind that even if a plugin doesn't need any arguments, a file with "[pluginname]" is needed, so the plugin is loaded. Just like adding "-Ppluginname" to vdr's commandline. Mostly the order of the plugins is not important, but for those small usecases, where you want to force a loading order, the following should be used: - The file with the options for vdr-core should actually be called "00-vdr.conf" so it will be read first. - An additional file "01-vdr-dbg.conf" can be used for special debugging options like "--userdump" etc. - Files for plugins which like to be loaded first, should be named "10-pluginname.conf". - Files for plugins which like to be loaded last, should be named "90-pluginname.conf". - Files for all other plugins with independend order should be named "50-pluginname.conf". vdrctl ------ What I like to see in the future is a tool "vdrctl" which will add/remove those symlinks or list the available or actived plugins etc. I would like to only specify an API for this tool, so every distribution can develop its own tool. Of course there can be a reference implementation like a simple shell-, Perl- or Python-script. In the following ARGSDIR is the configured conf.d path in your Make.config (or read by pkg-config). AVAILDIR is ARGSDIR/../conf.avail if not another directory is given. Filenames are the names of the files without their directory. Usage: vdrctl [global options] command [command options] Global options: --argsdir=<directory> read files from <directory> instead of ARGSDIR --availdir=<directory> read files from <directory> instead of ARGSDIR/../conf.avail Commands: list (without options) print a sorted list of all configuration files from AVAILDIR --enabled print a sorted list of all configuration files from ARGSDIR --disabled print a sorted list of all configuration files from AVAILDIR which are not symlinked to ARGSDIR enable <filename> create a symlink in ARGSDIR pointing to the file in AVAILDIR disable <filename> remove the symlink in ARGSDIR edit <filename> start an editor so the user can add/remove options to the file in AVAILDIR

2 3

Coordinating translations for VDR 2.2.0
by Klaus Schmidinger 17 Feb '15

17 Feb '15

In order to help translators coordinate their work (and avoid duplicate work) for the upcoming VDR 2.2.0, I have set up the directory ftp://ftp.tvdr.de/vdr/Developer/Translations which contains the latest version of all VDR core *.po files. The file "Untranslated" in this directory contains a list of all the *.po files that still contain untranslated texts, each followed by the number of missing translations. These are currently ar.po: 54 ca_ES.po: 54 cs_CZ.po: 54 da_DK.po: 187 el_GR.po: 250 es_ES.po: 54 hr_HR.po: 187 nn_NO.po: 315 pt_PT.po: 82 ru_RU.po: 54 sk_SK.po: 54 sl_SI.po: 55 sr_RS.po: 54 tr_TR.po: 187 uk_UA.po: 3 zh_CN.po: 54 I will update these files as translations come in. If you are considering to contribute translations, please use these files as your starting point. The countdown for VDR version 2.2.0 is running, so translations can only be adopted until next Wednesday, February 19. Thanks to all translators for their support! Klaus

4 6

Restart of frontend
by René 16 Feb '15

16 Feb '15

Hi, First of all i want to thank Klaus for VDR. Vdr has been now "part of my life" for roughly 10 years, and i can't imagine myself changing it to anything else! I have finally got time to migrate xineliboutput to softhddevice, but this has not been working 100% stable. I have had a couple of screen-freezes and screen-blackouts, and the only way to get this fixed was by restarting vdr. When using xineliboutput i have solved this by simply restarting my windowmanager (lightdm) by using an external command that reloads lightdm.. Is there a way that this could be done from vdr itself, eg by reloading the softhddevice-plugin with either an external command without stopping VDR? Best Regards, René

10 13

looking for workingvaapi config for xineliboutput
by Halim Sahin 14 Feb '15

14 Feb '15

Hi, I am trying to setup my new vdr using an intel hd graphic device. Could you please post a working config for xineliboutput? MfG. Halim

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr February 2015