vdr June 2012

vdr@linuxtv.org

35 participants
32 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

vdr-prefermenu and vdr 1.7.21
by Arturo Martinez 27 Sep '13

27 Sep '13

Is there a patch for vdr-prefermenu to work with vdr 1.7.21 ?

6 5

VDR form packages
by Marx 21 Mar '13

21 Mar '13

Hello I use Debian for years and to keep it clean I'm trying to use all software from packages. It generally works, hovewer I have problem with VDR, XBMC and drivers. Usually to have the newest driver I need to use some unstable version of VDR with the newest possible kernel. VDR in Debian is an option, hovewer it's usually behind the newest VDR, and number of plugins in repository is low. This lead to alternative repositories. I know two valuable: e-tobi and yavdr. I was using e-tobi but it lately isn't updated to the newest VDR. Yavdr is built on top of Ubuntu, and while it generally works on Debian, it's not recommended (some things doesn't work). So there is an option to build packages myself - really no option, because I have to make package manually for every plugin and for every new version of VDR. Any idea? Marx

8 31

[ANNOUNCE] vdr-xine-0.9.4 plugin
by Reinhard Nissl 15 Mar '13

15 Mar '13

Hi, I'm pleased to announce maintenance release 0.9.4. You can find it on my homepage as usual: http://home.vr-web.de/~rnissl Excerpt from HISTORY: 2011-03-16: Version 0.9.4 - The contained xine-lib-1.1 patch is outdated but might still work. The patch will get updated in 0.9.5. - A couple of xine-lib-1.2 patches is still waiting to get commited. vdr-xine-0.9.4 should be able to work without them. - Fixed a couple of things in xine-lib-1.2 and VDPAU. - Fixed compilation for VDR-1.2.x and VDR-1.6.x. - Updated Makefile to VDR-1.7.17. - Added support for VDR-1.7.17s TrueColor OSD. - Added support for VDR-1.7.12s changed PCR handling. - Added support for VDR-1.7.11s semantic of MakePrimaryDevice. - Resolved a segfault regarding VDR-1.7.x and cutting marks in radio recordings (thanks to Joachim Wilke for providing a fix). - Included Lithuanian translation (thanks to Valdemaras Pipiras). - Included Slovak translation (thanks to Milan Hrala). - Included Chinese and Taiwanese translations (thanks to NanFeng). - Fixed MANUAL about centre_cut_out_mode (thanks to Vorg on #xine-vdpau). Enjoy. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

4 6

[PATCH] Allow instant recording to record only present event
by Matti Lehtimäki 15 Sep '12

15 Sep '12

Hi I made a patch to allow special case for instant recordings to only record the present event. This is done by defining Instant rec. time to 0. There is still the question what should be done if event is non-existent or otherwise not obtained? Should the VDR default Instant rec. time be used or not? -- Matti

2 9

Filesystem hierachy standard patch needs review.
by Christopher Reimer 07 Sep '12

07 Sep '12

Hi Mailinglist, could someone please review the attached patch? It's originally posted by Maniac in this thread --> http://www.vdr-portal.de/board60-linux/board14-betriebssystem/p1054966-vdr-… The documentation and some Makefile changes are my work. The main code changes are Maniac's work. I hope the code as well as the documentation is ok, so that the patch can be added in the next VDR Version. Thanks, Christopher Reimer

14 62

[ANNOUNCE] VDR developer version 1.7.28
by Klaus Schmidinger 14 Jul '12

14 Jul '12

VDR developer version 1.7.28 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.28.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.27-1.7.28.diff MD5 checksums: 3ccff2dcc42d112e23dd64f2c39f02f1 vdr-1.7.28.tar.bz2 7249ead4aca4b24e53d49d11c67e1613 vdr-1.7.27-1.7.28.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. The new default skin "LCARS" displays the signal strengths and qualities of all devices in its main menu. For devices that have an stb0899 frontend chip (like the TT-budget S2-3200) retrieving this information from the driver is rather slow, which results in a sluggish response to user input in the main menu. To speed this up you may want to apply the patches from ftp://ftp.tvdr.de/vdr/Developer/Driver-Patches to the LinuxDVB driver source. The changes since version 1.7.27: - Fixed cPixmapMemory::DrawEllipse() for quadrants -1 and -4. - Fixed getting the maximum short channel name length in case there are no short names at all (reported by Derek Kelly). - The new function cDevice::DeviceType() returns a string identifying the type of the given device. - Now limiting the number of characters of a channel's (short) name to 16 in the schedules menus, to keep that column from getting overly wide in case there is a channel with a very long name that has no short name. - Fixed EPG scan on systems with only a single DVB device that use software output (reported by Juergen Lock). - Skins can now inquire the menu category for which their cSkinDisplayMenu is currently being used. This can be done either through a call to cSkinDisplayMenu::MenuCategory() or by reimplementing cSkinDisplayMenu::SetMenuCategory(). This information allows a skin to use special icons or decorations for the various types of menus in VDR. - The new setup option "DVB/Standard compliance" can be used to switch between different variations of the DVB standard (thanks to Rolf Ahrenberg). Currently there is "DVB" (for the original DVB standard) and "ANSI/SCTE", which is used to properly handle certain private stream types. - The disk usage is no longer automatically added to the title of the main and "Recordings" menus. This has always been a mekeshift solution and it is now up to the individual skin if, where and how it wants to display this information. A skin can use the new cVideoDiskUsage class to implement such a display. For compatibility, the default skins "Classic VDR", "ST:TNG Panels" and "Text mode" (i.e. curses) have been changed to behave like before. Other skins may want to display the disk usage in totally different ways. - A cOsdMenu can now handle skins that display different numbers of items in the various menu categories. - OSD and skin are now reinitialized after a plugin setup page has been confirmed, to have them react immediately in case any change to a plugin's setup parameter has an effect on the OSD. - The Timers list is now marked as modified whenever a recording starts or ends. - Fixed cDevice::StillPicture(), making sure it doesn't call the derived class's function if no buffer has been allocated (reported by Marcus Roscher). - Fixed the SVDRP command UPDR, which didn't update the global recordings list (reported by Lars Hanisch). - cControl::Control() now has an additional boolean parameter, which can be set to true to get the current player control even if it is hidden. - The new functions cControl::GetRecording() and cControl::GetHeader() can be used to retrieve information about what the current player is playing. - Fixed a possible high CPU load when pausing replay (thanks to Reinhard Nissl). - Fixed character comparisons in cSubtitleObject::DecodeCharacterString() (reported by Reinhard Mantey). - Renamed the function cString::sprintf(const char *fmt, va_list &ap) to vsprintf(), because it might inadvertently be called with a 'char *' as the second argument on some compilers and cause a crash (reported by Sundararaj Reel). - Removed the "bondedMasterFailed" mechanism from cDvbTuner, because it caused problems with the EPG scan in case a transponder is not receivable in a setup with bonded devices (reported by Michael Schneider). - Making sure setup strings don't contain any newline characters (thanks to Joachim Wilke). - The new member function cSkinDisplayReplay::SetRecording() allows a skin to display more information about the currently played recording. - Fixed a mismatched 'delete' in cSchedules::SetEpgDataFileName() (thanks to Reinhard Mantey). - The DrawText() functions of the OSD now accept the new alignment flag taBorder, which triggers keeping a proper distance from the edge that taLeft or taRight aligns to. - Fixed checking for UTF-8 support in cFont::Bidi() (reported by Torsten Lang). - If a recording has no info file, the 'title' of the recording's info is now set to the recording's name. - cVector::Clear() now reinitializes any previously used members. - Fixed resetting CAMs (thanks to Marco Skambraks). - The new function RgbShade() (include osd.h) can be used to generate a brighter or darker version of a given color. - The new class cSortedTimers can be used to quickly get a list of all timers, sorted by their start time. - The new skin "LCARS" is an enhanced version of the "ST:TNG" skin (which is still there in its original layout, for those who don't like the LCARS skin, or can't use it due to OSD limitations). The LCARS skin utilizes the new "menu category" feature to display additional information on the main menu page. It shows upcoming timers and the system's devices, as well as which device is recording which timers. The upper pane of the main menu displays the programme data in live and replay mode, and a progress bar. An indicator on the right side of the device list shows which device is currently used for live viewing, and whether it is in transfer mode. The individual device displays show the device number, the device type, which CAM (if any ) is currently assigned to the device, and the signal strength and quality. On the left side of the OSD there is a permanent display of the current date and time, the disk usage and the system load. "LCARS" is the new default skin of VDR. It requires at least a 4bpp (16 color) full screen OSD, but you can still operate it if your OSD can handle only fewer colors (in which case you may want to switch to the "ST:TNG" or "Classic VDR" skin). - Finally removed the code marked with __RECORDING_H_DEPRECATED_DIRECT_MEMBER_ACCESS and LEGACY_CRECEIVER. - Now making sure that the "small font" is never larger than the "osd font". - Fixed font handling with fontconfig 2.9.0 or newer (thanks to Joerg Bornkessel). - Extended the interface to the script that gets called for recordings, so that in the "edited" case it also provides the name of the original recording (thanks to Christian Richter). - Added DeleteEvent() to the EPG handler interface, so that an EPG handler can trigger deleting of an event (thanks to Christian Kaiser). - Speeded up opening menus on systems with many (several thousands) of recordings, by caching the information whether a recording is stored on the video directory file system within the cRecording data (based on a patch from Torsten Lang). Have fun! Klaus

7 15

vdr xine-lib eac3
by zaverel 10 Jul '12

10 Jul '12

hello your second patch doesn't work : no sound on eac3 channel if you want there is a sample of vdr hd-eac3 recording here: http://dl.free.fr/ew4rJddM8 103mo else , i don't know what mailing-list is the more indicate for debuging the vdr or xine-dev mailing-list ?

7 38

Please share your systemd (Upstart) service file
by Paul Menzel 03 Jul '12

03 Jul '12

Dear VDR folks, looking around for systemd service files I found three examples. One from OpenBricks [1], [Unit] Description=Video Disk Recorder After=lircd.service pvr.service ConditionPathExists=/run/geexbox/pvr/vdr [Service] ExecStart=/usr/bin/runvdr Restart=always [Install] WantedBy=multi-user.target one from a VDR-Portal forum post [2] [Unit] Description=Video Disk Recorder After=lircd.service [Service] ExecStart=/usr/local/src/VDR/vdr --lirc=/run/lirc/lircd -s /usr/local/bin/vdr-shutdown.sh -v /var/lib/vdr/video -w 90 -Plive -Pstreamdev-server -P 'epgsearch --config=/etc/vdr/plugins/epgsearch' -P 'xineliboutput --local=none --remote=37890' ExecStartPost=/usr/local/bin/svdrpsend.pl remo off Restart=on-failure [Install] WantedBy=multi-user.target and the one shipped by openSUSE [2]. [Unit] Descritpion=VDR After=lirc.service [Service] Type=once ExecStart=/usr/local/bin/runvdr TimeoutSec=0 [Install] WantedBy=multi-user.target As the comments in the VDR-Portal thread [2] suggest, it would be great to do without any shell/Bash script and more or less execute plain VDR and let systemd do everything else. heise open published an article about Upstart and as an example converted the VDR init.d script to an Upstart script [3]. Looking at that example I disagree with only starting VDR when an USB DVB device medium is plugged in, since there are use cases like IPTV or a VDR client. So how could such a generic set up look like. Do output plugins need to ship there own service files? Like xineliboutput which can also be run as a local frontend and for example sxfe needs a X server running. The current init.d script (in Debian) does not handle that either I think. So I guess it will not be possible to find a generic solution but let all plugins ship their own service files as needed or document what is needed. For the core VDR I guess we can assume it is run as a daemon and the above sample service files can be adapted and be included. Any thoughts? Thanks, Paul [1] http://hg.openbricks.org/openbricks/file/tip/packages/vdr/unit/vdr.service [2] http://www.vdr-portal.de/board16-video-disk-recorder/board8-vdr-grundlagen/… [3] http://www.heise.de/open/artikel/Init-Skripte-migrieren-844830.html

10 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2012