vdr September 2012

vdr@linuxtv.org

36 participants
26 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-plugin-IPTV not working with vdr-plugin-xvdr and XBMC
by Paulo Louro 27 Oct '13

27 Oct '13

Hello guys/girls, I have been trying to make iptv plugin to work with xvdr and xbmc, but i haven't manage to have any success. Xvdr is a plugin that needs a 100% complete TS to work, including PAT and PMT tables. By searching and "debuging" iptv and xvdr plugins code, I found out that the problem may be related with the filtering of PIDs, but i cant manage to understand how does the filtering system works. Is there any documentation or Howto example on how to program a plugin that implements cDevice interface on the right way? Some extra comments can be found on Pipelka github: https://github.com/pipelka/xbmc-addon-xvdr/issues/64 Regards,Louro

2 1

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

[ANNOUNCE] VDR developer version 1.7.31
by Klaus Schmidinger 03 Oct '12

03 Oct '12

VDR developer version 1.7.31 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.31.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.30-1.7.31.diff MD5 checksums: a3edd18a352465dd26c97c1990f7bcfd vdr-1.7.31.tar.bz2 32ff98697d1b383478a6e1932e4afc9c vdr-1.7.30-1.7.31.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 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.30: - If regenerating an index file fails and no data is written to the file, VDR now reports this error and removes the empty index file. - The setup parameter "Recording/Instant rec. time (min)" can now be set to '0', which means to record only the currently running event (based on a patch from Matti Lehtimäki). - Decreased the ring buffer put/get trigger sizes from 1/3 to 1/10. - The script given to VDR with the '-r' option is now also called whenever a recording is deleted (thanks to Alexander Wenzel). - Improved detecting frames in MPEG 4 video (reported by Andrey Pridvorov). - cPatPmtParser::ParsePmt() now also recognizes stream type 0x81 as "AC3", so that recordings that have been converted from the old PES format to TS can be played (suggested by Jens Vogel). - Fixed a leftover frame counter in the LCARS skin's replay display after jumping to an editing mark and resuming replay. - The new class cIoThrottle is used to allow I/O intense threads to temporarily suspend their activities in case buffers run full (suggested by Torsten Lang). Currently the cutter thread is suspended if the TS or Recorder buffer use more than 50% of their capacity. Plugin authors may want to participate in this mechanism if they use intense background I/O. - Increased the size of the TS buffer to 5MB and that of the Recorder buffer to 20MB to better handle HD recordings (suggested by Torsten Lang). - Moved cleaning up the EPG data and writing the epg.data file into a separate thread to avoid sluggish response to user input on slow systems (based on a patch from Sören Moch). - Fixed sorting folders before recordings in case of UTF-8 (thanks to Sören Moch). - Reactivated stripping control characters from EPG texts and adapted it to UTF-8. - Added missing decrementing of 'len' in libsi/si.c's String::decodeText() functions. - When checking whether a video directory is empty, file names that start with a dot ('.') are no longer automatically ignored and implicitly removed if the directory contains no other files. Instead, RemoveEmptyDirectories() now has an additional parameter that can be given a list of files that shall be ignored when considering whether a directory is empty. This allows users to continue to use files such as ".keep" to prevent a directory from being deleted when it is empty. Currently the only file name that is ignored is ".sort". Have fun! Klaus

3 4

VDR on Raspberry Pi
by Morfsta 01 Oct '12

01 Oct '12

Hi, Now that Raspberry Pis are quite common, cheap (~£25) and easily acquired (I received my order within 2 days from Farnell) has anyone considered whether it might be feasible to put together an output plugin for VDR for it? It is now possible to play MPEG-2 (with a codec license costing £2.40) as well as 1080p H.264 with hardware acceleration. There is work on VOMP (previously on Hauppauge MediaMVP) to work as a VDR client on the Pi and as far as I can see quite a lot of progress has been made. I'm wondering whether it would be possible to run VDR with HDMI video / audio output on one of these too and given the work done so far on VOMP and XBMC how difficult it would be to create an output plugin? Cheers, Morfsta

5 7

Missing V4Ldevices using S2-6400 - is this normal?
by Sean Carlos 26 Sep '12

26 Sep '12

Hi list, I'm in the progress of migrating from a DVB-S / VDR 1.4.7 setup to a DVB-S2 TT-Premium S2-6400 setup using vdr 1.7.27 on Fedora 17, kernel 3.5.4-1.fc17.x86_64 . I followed these instructions here http://www.hubertus-sandmann.homepage.t-online.de/VDR.htm to install the driver & the appropriate firmware - instructions which seem to be the same on a few other wikis. /dev/dvb/ device entries appear and I can run vdr. No /dev/videoX device entries are created, which means I cannot use tvtime or similar to watch vdr. Also screen grabs which relay on /dev/videoX nodes don't work either. So two questions: 1) is lack of v4l devices a feature of the DVB-S2 driver / S2-6400 firmware, or has something gone wrong? 2) If the lack of v4l devices is a feature [or if I cannot fix the problem :-)], is it possible to view VDR output using /dev/dvb/adapter0/dvr0 using mplayer or similar? I saw many hints on accessing this node using szap -r and mplayer, but mplayer doesn't seem to provide output while vdr is running. Thanks in advance for any tips - I did try Google & searching the linux media list w/o success. Sean

4 4

Re: [vdr] Vdr server on Sheevaplug, channel listing corrupt with xvdr/vnsi plugins.
by Kent Nielsen 22 Sep '12

22 Sep '12

I can confirm the same problem. Unfortunately I can't pinpoint if it's related to VDR, VNSI/XVDR plugins or their XBMC addons. In backend for testing I used empty recording directory, empty timers.conf and only one channel in channels.conf. If I have more than one channels, then XBMC restarts and from the logs I see that they are really corrupt. I have also tried to use XVDR addon, but it doesnt work either. Additonally I have same setup (same software version), but with x64 backend. Everything works OK, both with VNSI and other addons. Backend info and logs: http://pastebin.com/xcWBNjzc Linux 3.3.2-kirkwood-dg #1 Mon Apr 23 17:09:27 CDT 2012 armv5tel GNU/Linux vdr (1.7.28/1.7.28) - The Video Disk Recorder vnsiserver (0.9.0) - VDR-Network-Streaming-Interface (VNSI) Server (latest git) VDR log from syslog: Sep 22 19:45:08 vana user.err vdr: [4868] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf Sep 22 19:45:08 vana user.err vdr: [4868] VNSI: Client with ID 1 connected: 192.168.16.6:56945 Sep 22 19:45:08 vana user.err vdr: [4876] VNSI: Welcome client 'XBMC Media Center' with protocol version '2' Sep 22 19:45:08 vana user.err vdr: [4876] VNSI: Creating new live Receiver Sep 22 19:45:08 vana user.err vdr: [4876] VNSI: Successfully switched to channel 1 - ETV Sep 22 19:45:08 vana user.err vdr: [4876] VNSI: Started streaming of channel ETV (timeout 10 seconds) Sep 22 19:45:08 vana user.err vdr: [4878] receiver on device 1 thread started (pid=4855, tid=4878) Sep 22 19:45:08 vana user.err vdr: [4877] cLiveStreamer stream processor thread started (pid=4855, tid=4877) Sep 22 19:45:08 vana user.err vdr: [4879] TS buffer on device 1 thread started (pid=4855, tid=4879) Sep 22 19:45:08 vana user.err vdr: [4877] VNSI: streaming of channel started Sep 22 19:45:08 vana user.err vdr: [4877] VNSI: sending 8 buffered packets Sep 22 19:46:21 vana user.err vdr: [4876] VNSI-Error: cxSocket::read: read() error at 0/4 Sep 22 19:46:21 vana user.err vdr: [4877] VNSI: exit streamer thread Sep 22 19:46:21 vana user.err vdr: [4877] cLiveStreamer stream processor thread ended (pid=4855, tid=4877) Sep 22 19:46:21 vana user.err vdr: [4876] buffer stats: 151152 (4%) used Sep 22 19:46:21 vana user.err vdr: [4879] TS buffer on device 1 thread ended (pid=4855, tid=4879) Sep 22 19:46:21 vana user.err vdr: [4878] buffer stats: 84412 (4%) used Sep 22 19:46:21 vana user.err vdr: [4878] receiver on device 1 thread ended (pid=4855, tid=4878) Sep 22 19:46:21 vana user.err vdr: [4868] VNSI: Client with ID 1 seems to be disconnected, removing from client list Frontend info and logs: http://pastebin.com/F3RJeA6H Linux 3.2.0-2-amd64 #1 SMP Mon Jun 11 17:24:18 UTC 2012 x86_64 GNU/Linux XBMC Media Center 12.0-ALPHA6 Git:20120921-ad94545 xbmc-pvr-addons commit ff729c0 cat xbmc.log | grep ERROR 19:44:22 T:139639212595136 ERROR: HAL: seems that Hal daemon is not running: The name org.freedesktop.Hal was not provided by any .service files 19:44:22 T:139639212595136 ERROR: HAL: no Hal context 19:44:22 T:139639212595136 ERROR: GLX: Same window as before, refreshing context 19:44:23 T:139639212595136 ERROR: JSONRPC Server: Failed to connect to sdpd 19:45:08 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:45:18 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:45:28 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:45:38 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:45:48 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:45:58 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:46:08 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id 19:46:18 T:139638525974272 ERROR: AddOnLog: VDR VNSI Client: StreamContentInfo - unknown stream id

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr September 2012