vdr October 2013

vdr@linuxtv.org

27 participants
18 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

no image with TeVii S464
by Peter Münster 11 Nov '13

11 Nov '13

Hi, This is probably not a VDR problem, but I guess that here are people who could help perhaps. I use the femon plugin to check the signal, and there is only some 20% of the first line (red), when I test my brand new TeVii S464, and no image. When I replace the card with my old "Technotrend/Hauppauge WinTV Nexus-S rev2.X", I get green signals and an image, so it seems that everything is fine with my dish. Is there some configuration issue, or is this new card just broken? Or do I need another LNB? TIA for any hints, -- Peter

3 4

VDR and folders
by Thomas Maass 04 Nov '13

04 Nov '13

Hi! I like the new editing functions coming with version 2.1.2. Thank you for that Klaus! It would be nice, if VDR could recognize existing subfolders and add them to folders.conf automatically. Sometimes I edited my videodir manually, created some subfolders to sort some recordings. VDR does not know about these folders. Thomas -- gpg-id: D31AAEEA https://www.setho.org/people

2 1

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

searching a HW problem
by Torsten Mohr 27 Oct '13

27 Oct '13

Hello, i have a VDR up and running, the SW works fine so far (at least i think so). Some recordings are half-corrupted, have breaks inbetween, bad sound, etc. The bad-quality problem is not related to a certain channel, i wonder how i can track this down. My hardware: 2 (TWO !) Terratec Cinergy PCI cards. <-- two cards MSI C847 MS-E33 board I use DVB-C. The cable goes into me set-top-box, out to PCI card 1, from there out to PCI card 2. I wonder if i can detect somehow which card did which recording? Is there a way to force a recording to happen on a certain card? Thanks for any hints Torsten

6 10

[Patch] reconnect to lirc socket even if it doesn't exist on startup
by Lars Hanisch 26 Oct '13

26 Oct '13

Hi, The reconnect loop of cLircRemote will not be started if the socket does not exist at the time, vdr starts. In "fast boot" environments this may be true. The attached patch fixes this. Regards, Lars.

1 0

[ANNOUNCE] VDR developer version 2.0.3
by Klaus Schmidinger 23 Oct '13

23 Oct '13

VDR version 2.0.3 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.0.3.tar.bz2 A 'diff' against the previous stable version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.0.2-2.0.3.diff MD5 checksums: dd8fb1642bdfa7feb0e9a8ae41e9ef2f vdr-2.0.3.tar.bz2 77b4785029926e2be2103f9a995ca879 vdr-2.0.2-2.0.3.diff This version fixes a few minor bugs that came up after the release of version 2.0.2. The changes since version 2.0.2: - Fixed asserting free disk space in the cutter. - No longer trying to delete old recordings in AssertFreeDiskSpace() if the given Priority is less than 1. - Fixed handling LIRC events in case repeated events are lost. - Fixed a possible crash when shutting down VDR while subtitles are being displayed (reported by Ville Skyttä). - cDevice::IsPrimaryDevice() now also checks whether the primary device actually has a decoder and returns false otherwise. This should improve device allocation on systems that are only used as a receiver and don't actually display anything. - Increased the value of MAXRETRIES to 20 to reduce the probability of disturbances in transfer mode. - All bonded devices (except for the master) now turn off their LNB power completely to avoid problems when receiving vertically polarized transponders (suggested by Manfred Völkel and Oliver Endriss). - Fixed cleaning up old EPG events in case no epg data file is given (reported by Dave Pickles). Have fun! Klaus

1 2

xineliboutput buffer problems, dropouts and skipped frames
by Milos Kapoun 21 Oct '13

21 Oct '13

Hello, I did a lot of trouble shooting two new DVB-T multiplexes in Prague (Czech republic). Problems are dropouts and errors in the picture. After approximately 10 minutes xine crash : "floating point error" and VDR do reload. It is occurring only on that two multiplexes. I did checks for signal and stream quality and it is good, details attached. In the log is: 200 frames delivered, 17 frames skipped, 0 frames discarded 200 frames delivered, 10 frames skipped, 0 frames discarded 200 frames delivered, 20 frames skipped, 0 frames discarded This is there for MPEG2 streams, for h264 streams it is different. I think it is buffer underrun, all (my) problems with buffer overflow is due to xine playing incomplete/corrupted data. I did tests on 1.7.38, 2.0.0 and 2.1.1. Ffmpeg and xine are now on latest versions. DVB drivers are from kernel 3.7.1. Two different dvb-t cards. Behavior had been same. Could you suggest, what next to test? Thank you Milos Debug outputs: VDRPRG="./vdr -p 2001 -P"remote -i /dev/my_remote" -P femon -P dvbhddevice -P"xineliboutput --local=sxfe --video=xv --audio=alsa:hw:0,3 --remote=none" -v /video0 " Lspci 04:02.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 02) Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card Flags: bus master, slow devsel, latency 32, IRQ 18 Memory at fbde0000 (32-bit, non-prefetchable) [size=64K] I/O ports at cf00 [size=32] Kernel driver in use: b2c2_flexcop_pci 04:03.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend-Budget/Hauppauge WinTV-NOVA-T DVB card Flags: bus master, medium devsel, latency 32, IRQ 16 Memory at fbdff000 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_ci dvb channels.conf: TELKA;Digital Broadcasting s.r.o.:642000000:B8C34D12G8M64S0T8Y0:T:0:3611=2:3612=cze@3:3615:0:518:8395:1025:0 Stream check VDR2:/usr/src/VDR# dvbsnoop -ph 0 -adapter 0 -crc -n 100000 -s bandwidth 0x0e1b dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ --------------------------------------------------------- PID bandwidth statistics... PID: 3611 (0x0e1b) - max packet count: 100000 --------------------------------------------------------- packets read: 28/(28) d_time: 0.004 s = 10528.000 kbit/s (Avrg: 10528.000 kbit/s) [bad: 0] packets read: 34/(62) d_time: 0.021 s = 2435.048 kbit/s (Avrg: 3729.920 kbit/s) [bad: 0] ... packets read: 29/(99977) d_time: 0.019 s = 2295.579 kbit/s (Avrg: 2580.893 kbit/s) [bad: 0] packets read: 30/(100007) d_time: 0.021 s = 2148.571 kbit/s (Avrg: 2580.737 kbit/s) [bad: 0] ## PID: 3611 (0x0e1b) bad/total packets: 0/100007 (= 0.0%) Avrg: 2580.737 kbit/s VDR2:/usr/src/VDR# dvbsnoop -ph 0 -adapter 1 -crc -n 1000 -s signal 0x0e1b | grep -v "SIG CARR VIT SYNC LOCK" dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ Signal check --------------------------------------------------------- Transponder/Frequency signal strength statistics... max cycle count: 1000 --------------------------------------------------------- VDR2:/usr/src/VDR# dvbsnoop -ph 0 -adapter 1 -crc -n 100000 -s signal 0x0e1b | grep -v "SIG CARR VIT SYNC LOCK" dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ --------------------------------------------------------- Transponder/Frequency signal strength statistics... max cycle count: 100000 --------------------------------------------------------- VDR2:/usr/src/VDR# dvbsnoop -ph 0 -adapter 0 -crc -n 100000 -s signal 0x0e1b | grep -v "SIG CARR VIT SYNC LOCK" dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ --------------------------------------------------------- Transponder/Frequency signal strength statistics... max cycle count: 100000 --------------------------------------------------------- VDR signal debug, it is same for both cards. FE 1/0: 13D02103 Q = FFFF D8D8 1 0 0 84% FE 1/0: 13D02103 S = FFFF EC5F 92% FE 1/0: 13D02103 Q = FFFF DDDD 1 0 0 86% FE 1/0: 13D02103 S = FFFF EE1F 93% FE 1/0: 13D02103 Q = FFFF DADA 1 0 0 85% FE 1/0: 13D02103 S = FFFF ECCF 92% FE 1/0: 13D02103 Q = FFFF DADA 1 0 0 85% FE 1/0: 13D02103 S = FFFF EE5F 93% FE 1/0: 13D02103 Q = FFFF D8D8 1 0 0 84% FE 1/0: 13D02103 S = FFFF ED7F 92%

1 0

Re: [vdr] Fix SIGNALSTRENGTH in vdr 2.0.3 TechniSat SkyStar 2 DVB-S rev 2.3P - dvbdevice.c
by guido.cordaro＠tiscali.it 21 Oct '13

21 Oct '13

Il 13/10/2013 10:51, guido.cordaro(a)tiscali.it ha scritto: > Thanks Klaus Schmidinger > > For having responded to my e-mail > > This' modified code that you send as an attachment ... > > Files created with " diff -urN <orig> <mod>> new.diff " > > Guido Cordaro > > > > > Il 12/10/2013 23:08, Klaus Schmidinger ha scritto: >> On 12.10.2013 21:21, knap.home wrote: >>> With this change to the source I was able to run properly "SIGNAL >>> STRENGTH." >>> >>> Using the device Netsystem TechniSat SkyStar 2 DVB-S rev 2.3P. >>> >>> Great as a solution ... >>> >>> Modified Source -> /usr/local/src/vdr-2.0.3/dvbdevice.c >> >> Please send just the differences (diff -u) between the original and the >> modified code. I'm afraid even though I tried I can't seem to generate >> a proper diff from what you've posted. And please send it as an >> attachment, >> not inline (lines get wrapped). >> >> Klaus >> >> _______________________________________________ >> vdr mailing list >> vdr(a)linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr October 2013