vdr

vdr@linuxtv.org

2 participants
6731 discussions

[ANNOUNCE] decruft plugin 0.0.1
by Dominic Morris 16 Feb '05

16 Feb '05

Hi, It's only a small plugin, but I've found it quite useful to automatically cleanup my channels lists, so maybe others might find it useful too? The decruft plugin removes undesired channels from your channel list so that you can leave "Add new channels/transponders" and find something interesting. Filtering can be performed on apid,vpid,tpid,dpid, ca, Source, Name and Provider. Possibly uses of this are: - remove radio stations - remove channels that use CAs that you don't have the CAM for - blacklist providers (if you're lucky enough to live in a country with more than one provider supplying roughly the same channels) Configuration is by a plain text config file (osd configuration may come at a later date) You can download it from: http://www.rst38.org.uk/vdr/decruft/ cheers, d.

2 5

RE: [vdr] [ADMIN] server downtime
by HGM.bg (GMX) 16 Feb '05

16 Feb '05

Johannes Stezenbach wrote: > Sorry for the inconvenience, After all the flames -> Now i have a perfect threaded view in my outlook (Initial mail and replies stay together). This is a very positive change. Just to give the feedback that not everyone is unhappy with your changes :)) > Johannes /hgm.bg

1 0

Fix for memory leak of the disableDoubleEpgEntrys patch
by Thomas Günther 16 Feb '05

16 Feb '05

Hi! The memory leak (http://www.vdrportal.de/board/thread.php?threadid=29787) of the disableDoubleEpgEntrys patch from http://www.wontorra.net/filemgmt/visit.php?lid=61 is fixed in this version: http://toms-cafe.de/vdr/download/vdr-disableDoubleEpgEntrys_0.7.1_fix-leak.… Tom

1 0

vdr-1.3.21: video data stream broken
by sn123py vdr user 16 Feb '05

16 Feb '05

Hi, i get some fatal errors when recording more than one timer. This error does not occur if recording only one timer. I use vanilla vdr-1.3.21 without any plugin dvb Version linux-dvb.2004-12-26. my DVB-Cards are two NEXUS-s Cards. The output from syslog and the strace from vdr are available at: http://tvmovie2vdr.vdr-developer.org/logs/VideoDataStreamBroken.tgz (80kb) if i can do anything that helps finding this error, let me know. regards, Friedhelm.

3 5

RE: [vdr] vdr-1.3.21: video data stream broken
by Vladimir Shved 16 Feb '05

16 Feb '05

> -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of Rainer Zocholl > Sent: Tuesday, February 15, 2005 11:40 AM > To: vdr(a)linuxtv.org > Subject: Re: [vdr] vdr-1.3.21: video data stream broken ... > >I think this bug only can be reproduced if you are using 4x1 diseqc > >switches. > >I have exact same problem on my setup > > To be exact: You have the same error messages ;-) Actually I was battling this problem since vdr1.3.9 was released. I have four DVB-S cards, two FF and two budget cards and I tried variety of hardware combinations to solve it and I think I'm getting better at it too. Since I live in US, no one makes diseqc multiswitches here which would be appropriate for my setup and I can't get one from Germany because dealers just refuse to send it. So I'm looking for other ways to solve it. > >and I traced it out to diseqc switches. > >Every time one of your cards switches one switch > >while other card is recording, the diseqc signal goes around LNB to > >another diseqc switch and moves its position too, and other card, > >which is recording, loses signal and you get VDSB. > > That sounds like the problem i have with my "single LNB" > environment: If i enabled EPG scan, after an hour the > Video stream breaks. I suggest getting latest 2.6 kernel and CVS drivers. Although I keep EPG disabled too but I never get these errors in single card setup, using 4 LNBs and I can run VDR for weeks without errors or reboots, and I do a lot of recordings. I'm still running vdr1.3.14 on my single FF card production machine and vdr1.3.21 is much better, I did not test 1.3.18-20 though. > >I don't have scope but I've put the cards in different machines > >and if I set one of the machines to record while I'm flipping channels > >on second machine, the first one would got VDSB > > >or if I'm not recording, I'd just lose signal > >on first machine. > > >If I use only one, either machine, at the time, > >stuff works without any problems. > > > >In my opinion, the only way to resolve this is to get > >diseqc-multiswitch. > > So only users with diseqc enabled have that problem? I think only users that use certain type of hardware setups like mine :) i.e. at least two 4x1 diseqc switches and as least two LNBs. I'm sure people with diseqc multiswitches don't have this problem. > >Another possibility is your hardware setup, i.e. one or all of your > >Nexus cards are using bad PCI slots or sharing IRQ with very > >incompatible devices. Try moving cards to different PCI slots to > >resolve IRQ issues. > > And why he didn't had/don't have the problem with 1.3.17? > Was diseqc handling introduced with 1.3.18ff? He'll get that problem back if I'm right and we all know when diseqc handling was introduced, and diseqc handling is out of question here. In my case VDSB does not happen every time, he just did not test it very well yet. It happened to me too, I'd make some change to my setup and all of the sudden the problem disappears and then eventually it would come back. VDR has nothing to do with it if its VDSB, its either drivers or signal loss. If you are sure the diseqc switch signal does not get through LNB back to other switches, I'd overview your hardware setup, bad RAM, CPU overheats, IRQ conflicts, PCI bandwidth bottlenecks and etc. because in my opinion, VDR just has nothing to do with this. I think there were some VDSB related problems in vdr <1.3.13 because of buffer overflows but those all fixed now. Threading has some affect but usually you can notice it very quick: the VDR responds slowly, crashes, does not exit normally and etc. In my opinion, VDSB very much causes clean exit because it detects abnormal data in the stream and does not know how to handle it. VDR can be blamed for stressing your hardware but all that should be handled by drivers and kernel? > >> hm, but with same environment, vdr-1.3.17 (with nearly all plugins > >> enabled) > >> everything works?! Is this error introduced with > 1.3.17 ? > >>> The easiest workaround is to disable the EPG scan in the EPG setup > >>> menu. Search the mailing list for details. I did disable EPG scan but I still get the problem and I think because of my hardware setup.

2 2

Two instances but only one epg.data ?
by Tilo Renkl 15 Feb '05

15 Feb '05

Hi list, since a few month I use two instaces of VDR for two TV's on one machine (with two remotes). I have two separate config-folders, but I want to use only ONE epg.data-file. This is because I user tvmovie2vdr and loadepg-Plug to fill parts of my epg-data. The problem is that even if I explicitly define one file for both VDR's and then start the loadepg-Plugin or tvmovie2vdr-skript, only one of the instances get's updated. The other one will never be updated till the next restart. Is there any solution for that problem (yes I think this is a bug) ? Thanx in advance. Tilo

2 3

[ANNOUNCE] Official launch of the english VDR wiki
by Thomas Wehrspann 15 Feb '05

15 Feb '05

Hi all, finally, I can announce the official launch of the english VDR wiki: http://www.linuxtv.org/vdrwiki/index.php/Main_Page the english counterpart of the german VDR wiki at http://www.vdr-wiki.de. Thanks to the Wiki-conzept, everybody can contribute information to the knowledge base and work as an author, even without registration. This way, everybody can help to create a complete and freely available reference book for VDR and related topics. http://www.linuxtv.org also has ist own DVB related wiki. Greetings, Thomas

4 5

Null titles and cSchedule::GetFollowingEvent
by Chris Warren 14 Feb '05

14 Feb '05

Hi all, I notice that quite often EPG data contains events with null or empty titles. These tend to be 'gaps' between programs (especially on movie channels.) Would it be sensible to skip over these when showing the "Whats on Next?" screen? Looking at the code, the place that needs changed is cSchedule::GetFollowingEvent in epg.c. Apart from cMenuWhatsOn::cMenuWhatsOn in menu.c, the only other place place this is called from is cSchedule::Dump - would the following patch (attached and included below) cause any problems? I've been running it for a few days and it seems ok. Or would it be better to make the change to cMenuWhatsOn::cMenuWhatsOn? Chris --- vdr-1.3.20/epg.c 2005-01-02 11:25:25.000000000 +0000 +++ vdr-1.3.20-modified/epg.c 2005-02-11 20:26:10.000000000 +0000 @@ -672,8 +672,14 @@ const cEvent *cSchedule::GetPresentEvent const cEvent *cSchedule::GetFollowingEvent(bool CheckRunningStatus) const { const cEvent *p = GetPresentEvent(CheckRunningStatus); - if (p) + if (p) { p = events.Next(p); + + const cEvent *tempp = p; + while(tempp && ((tempp->Title() == NULL) || (strlen(tempp->Title())==0))) tempp = events.Next(tempp); + if(tempp) + return tempp; + } return p; }

3 2

problem with DVB-S in Debian
by Eduardo 14 Feb '05

14 Feb '05

I've got a sat reciver: > Technotrend DVB-S 1.3 Premium into K7 700Mhz 768Mb: > Debian GNU/Linux 2.6.8-2-k7 i686 driver: > Incluidos en el kernel-image. firmware: > dvb-ttpci-01.fw Version 261d software: > VDR version 1.2.6 that I can not make it work. Loading the driver module, an it load ther firmware: > modprobe dvb_ttpci log in /var/log/syslog: kernel: Linux video capture interface: v1.00 kernel: saa7146: register extension 'dvb'. kernel: PCI: Found IRQ 9 for device 0000:00:09.0 << - Technotrend DVB-S 1.3 Premium kernel: PCI: Sharing IRQ 9 with 0000:00:04.2 kernel: PCI: Sharing IRQ 9 with 0000:00:04.3 kernel: saa7146: found saa7146 @ mem f09a5000 (revision 1, irq 9) (0x13c2,0x0000). kernel: DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3). kernel: Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 0 has MAC addr = 00:d0:5c:00:90:15 kernel: gpioirq unknown type=0 len=0 kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d << - firmware kernel: DVB: AV7111(0) - firmware supports CI link layer interface kernel: av7110(0): adac type set to 0 kernel: videodev: "av7110" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ << - this's warning no error kernel: saa7146_vv: saa7146 (0): registered device video0 [v4l2] kernel: av7110: found av7110-0. input.agent[3111]: evbug: blacklisted input.agent[3102]: evbug: blacklisted input.agent[3102]: evdev: already loaded input.agent[3111]: evdev: already loaded lsmod: dvb_ttpci 85644 0 dvb_core 88168 1 dvb_ttpci saa7146_vv 50560 1 dvb_ttpci video_buf 22212 1 saa7146_vv saa7146 19236 2 dvb_ttpci,saa7146_vv v4l1_compat 14404 1 saa7146_vv v4l2_common 6208 1 saa7146_vv videodev 9984 1 saa7146_vv firmware_class 10368 1 dvb_ttpci ttpci_eeprom 2880 1 dvb_ttpci info in sysfs: /sys/devices/pci0000:00/0000:00:09.0 << - Technotrend DVB-S 1.3 Premium class config detach_state device irq - >> irq 9 power/ resource subsystem_device subsystem_vendor vendor here's not entry for 0000:00:09.0 !!!! /sys/class/firmware timeout the devices here is it: ls -laF /dev/dvb/adapter0 total 8 drwxr-xr-x 2 root root 4096 2005-02-10 06:10 ./ drwxr-xr-x 6 root root 4096 2005-02-10 06:10 ../ crw-rw---- 1 root video 250, 1 2005-02-10 06:10 audio0 crw-rw---- 1 root video 250, 6 2005-02-10 06:10 ca0 crw-rw---- 1 root video 250, 4 2005-02-10 06:10 demux0 crw-rw---- 1 root video 250, 5 2005-02-10 06:10 dvr0 crw-rw---- 1 root video 250, 3 2005-02-10 06:10 frontend0 crw-rw---- 1 root video 250, 7 2005-02-10 06:10 net0 crw-rw---- 1 root video 250, 8 2005-02-10 06:10 osd0 crw-rw---- 1 root video 250, 0 2005-02-10 06:10 video0 the firmwares here is it: ls /lib/firmware dvb-fe-nxt2002.fw dvb-fe-tda10045.fw dvb-fe-tdlb7.fw dvb-fe-sp8870.fw dvb-fe-tda10046.fw dvb-ttpci-01.fw << - Version 261d Starting vdr: /etc/init.d/vdr start vdr[3324]: VDR version 1.2.6 started vdr[3324]: loading /var/lib/vdr/sources.conf vdr[3324]: loading /var/lib/vdr/diseqc.conf vdr[3324]: loading /var/lib/vdr/channels.conf vdr[3324]: loading /var/lib/vdr/commands.conf vdr[3324]: loading /var/lib/vdr/reccmds.conf vdr[3324]: loading /var/lib/vdr/svdrphosts.conf vdr[3324]: loading /var/lib/vdr/ca.conf vdr[3324]: loading /var/lib/vdr/keymacros.conf vdr[3324]: probing /dev/dvb/adapter0/frontend0 !!! The devece is not found ¡¡¡ vdr[3324]: ERROR: /dev/dvb/adapter0/frontend0: No existe tal dispositivo o dirección vdr[3324]: no DVB device found vdr[3324]: ERROR: invalid primary device number: 1 vdr[3324]: ERROR: no primary device found - using first device! vdr[3324]: ERROR: invalid primary device number: 1 logger: restarting VDR kernel: saa7146: unregister extension 'dvb'. << kernel: saa7146: register extension 'dvb'. kernel: PCI: Found IRQ 9 for device 0000:00:09.0 kernel: PCI: Sharing IRQ 9 with 0000:00:04.2 kernel: PCI: Sharing IRQ 9 with 0000:00:04.3 kernel: saa7146: found saa7146 @ mem f09a5000 (revision 1, irq 9) (0x13c2,0x0000). kernel: DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3). kernel: Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 0 has MAC addr = 00:d0:5c:00:90:15 kernel: gpioirq unknown type=0 len=0 kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d kernel: DVB: AV7111(0) - firmware supports CI link layer interface kernel: av7110(0): adac type set to 0 kernel: videodev: "av7110" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ kernel: saa7146_vv: saa7146 (0): registered device video0 [v4l2] kernel: av7110: found av7110-0. input.agent[3383]: evbug: blacklisted vdr[3422]: VDR version 1.2.6 started vdr[3422]: loading /var/lib/vdr/sources.conf vdr[3422]: loading /var/lib/vdr/diseqc.conf vdr[3422]: loading /var/lib/vdr/channels.conf vdr[3422]: loading /var/lib/vdr/commands.conf vdr[3422]: loading /var/lib/vdr/reccmds.conf vdr[3422]: loading /var/lib/vdr/svdrphosts.conf vdr[3422]: loading /var/lib/vdr/ca.conf vdr[3422]: loading /var/lib/vdr/keymacros.conf vdr[3422]: probing /dev/dvb/adapter0/frontend0 vdr[3422]: ERROR: /dev/dvb/adapter0/frontend0: No existe tal dispositivo o dirección vdr[3422]: no DVB device found vdr[3422]: ERROR: invalid primary device number: 1 vdr[3422]: ERROR: no primary device found - using first device! vdr[3422]: ERROR: invalid primary device number: 1 logger: restarting VDR input.agent[3383]: evdev: already loaded input.agent[3407]: evbug: blacklisted input.agent[3407]: evdev: already loaded Is any body can help me? Thanks a lot. Eduardo. PD: I'm sorry by my English.

2 6

Re: [vdr] [ANNOUNCE] vdr-xine-0.7.1 plugin
by Anssi Hannula 13 Feb '05

13 Feb '05

Reinhard Nissl wrote: > Hi, > > Anssi Hannula wrote: > >>> I'm pleased to announce bugfix release 0.7.1: >>> >>> http://home.vr-web.de/~rnissl/vdr-xine-0.7.1.tgz >> >> >> Are you planning to add support for socket connections as proposed by >> Patrick Boettcher anytime soon? > > > We already had a discussion about that. He is currently working on a > "cleaner" approach (just one server side socket and only two sockets at > client side) and that one will be integrated into vdr-xine-0.8.0. By the way, your message didn't go to mailinglist. VDR ml configuration has changed so if you want to send message to mailinglist also, use the "reply to all" function of your email reader. This kind of configuration is commonly used in mailinglists. -- Anssi Hannula

5 11

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr