vdr

vdr@linuxtv.org

2 participants
6731 discussions

vdr segfaults with glibc 2.12.2
by David Spicer 06 Jan '11

06 Jan '11

Hi, I'm not a programmer and I'm not sure where to go with this but I thought that I'd try here first. I'm running vdr 1.6.0-2 on Arch Linux x86_64. The Arch glibc package was upgraded from 2.12.1 to 2.12.2 recently, with associated toolchain package updates. After the upgrade, vdr started segfaulting when it was run so I recompiled it with debugging symbols and got the following backtrace from gdb: (gdb) bt #0 0x0000000000000001 in ?? () #1 0x00000000004f2d06 in ?? () #2 0x00007fff1bb0269f in ?? () #3 0x00000000004c2775 in cRwLock::Lock (this=0x72bb40, Write=true, TimeoutMs=<value optimized out>) at thread.c:163 #4 0x000000000047d382 in cSchedulesLock::cSchedulesLock (this=0x7fff1bb0269f, WriteLock=<value optimized out>, TimeoutMs=<value optimized out>) at epg.c:911 #5 0x000000000047dd06 in cSchedules::Read (f=0x0) at epg.c:1014 #6 0x00000000004cc304 in main (argc=<value optimized out>, argv=<value optimized out>) at vdr.c:604 If I've done this properly then problem seems to be with the glibc, specifically pthread, functions that vdr uses to lock the epg data file for reading and writing but I have no idea whether the problem is with the vdr code or with glibc. The only workaround I have at the moment is to downgrade to glibc 2.12.1, after which vdr works again. Can anybody help please? TIA, David Spicer

1 0

ATSC plugin segfaults with channel scan
by Timothy D. Lenz 05 Jan '11

05 Jan '11

This is a old problem that went partly away for awhile (only crashed sometimes) but now is all the time again. Jan 5 13:05:39 x64VDR vdr: [22436] saved setup to /usr/local/dvb/VDR/config/setup.conf Jan 5 13:05:59 x64VDR vdr: [22575] ATSC Scanner thread started (pid=22436, tid=22575) Jan 5 13:05:59 x64VDR kernel: ATSC Scanner[22575]: segfault at 7fd8837722c0 ip 00007fd894d472b7 sp 00007fd882df38b8 error 4 in libfreetype.so.6.6.0[7fd894d01000+83000] Using vdr-1.7.15

1 0

How can I prevent that vdr deletes recordings?
by Gero 05 Jan '11

05 Jan '11

Hi, I'm using a recent 1.7.16 vdr (debian squeeze from e-tobi) and actually I realized, that recordings disappeared from recordings menue. I'm very happy, that one recording is stil on disk, but others have been removed unwanted. Diskspace is not low at all - so I don't understand the reason to start deleting. using epgsearch for most recordings, each timer sets the lifetime of the recording to 99 - which I supposed to mean "don't delete ever". Apperantly the vdr has a different understanding of lifetime 99 - so what can I do to disable deleting of recordings? I never ever want the vdr to delete a recording, which I did not marked manually as deleted. Any hint is appreciated. kind regards Gero

5 9

Re: [vdr] Replacing aging VDR for DVB-S2
by Travel Factory S.r.l. 05 Jan '11

05 Jan '11

> Those CPUs are fast enough for H.264 decoding, but in the absence > of > VDPAU, realtime 1080i deinterlacing will be difficult. You'd > probably > have to use a simple bobber. Really interesting thread... now, where can I find a updataed list of dvb-s2 cards supported "out-of-the-box" ? (I mean, no days spent recompiling kernels, modules, drivers, and a touch of abracadabra...) it's just an year now that my old vdr turns on twice each day to record a daily show... the show is going to end in a few weeks and so I will have some time to update the system... thanks Francesco

1 0

Request: E parameter in channels.conf for epg scan
by Jochen Dolze 03 Jan '11

03 Jan '11

Hi, i would like to implement an parameter to disable the epg scan for (some) channels. I think an parameter in the channels.conf-file would be the best place. So, E0 means dont scan, E1 or absence of the E-parameter means scan the channel. I only start investing my time if it has an chance to be included into the VDR. Any comments welcome. Best regards, Jochen

26 78

lirc key reading to slow ? Buffer overflow ?
by Steffen Barszus 02 Jan '11

02 Jan '11

Hi ! i get these errors, once my remote is doing key repeats: Dec 3 23:33:13 vdr vdr: [24629] ERROR: unparseable lirc command: gy_Receiver-event-kbd#012b-Gyration_Gyration_RF_Technology_Receiver-event-kbd#01272 0 KEY_VOLUMEDOWN usb-Gyration_Gyration_RF_TechnoloKEY_VOLUMEDOWN Dec 3 23:34:14 vdr vdr: last message repeated 583 times especially note the usb-Gyration_Gyration_RF_TechnoloKEY_VOLUMEDOWN and ...kbd#012b-.... (this should read usb-...) is there anything forgot to reset ? A buffer to small ? Just wrong how it is read ? In irw and xbmc there seems no such issue, means the repeat just works. i increased the buffers to: private: enum { LIRC_KEY_BUF = 500, LIRC_BUFFER_SIZE = 4096 }; which seems to make the error disappear, but its still incredible slow (compared to other applications) in accept the keys. Can this be improved ?

2 2

Include Path in Makefile (VDR >=1.7.15)
by Joachim Wilke 29 Dec '10

29 Dec '10

I'm just wondering, if there has happened a mistake in updating the Makefile in VDR 1.7.15. The HISTORY file states: "Include paths are now added instead of overwriting INCLUDES in the Makefile" However, in the Makefile changes: -INCLUDES = -I/usr/include/freetype2 +INCLUDES ?= -I/usr/include/freetype2 Shouldn't that be += instead of ?=. In my case, my IDE sets INCLUDES with some custom stuff. Therefore the Makefile does not touch INCLUDES any more and I get an error. -- Best Regards, Joachim.

4 6

Recordings starting with B-Frame?
by Tobias Grimm 28 Dec '10

28 Dec '10

I don't known how much I can trust avidemux, but it tells me, that my HD-VDR recordings (1.7.16) start with a B-Frame. Shouldn't all *.ts Files start with an I-Frame? Tobias

3 2

Architecture difference between recording and viewing?
by Torsten Kunkel 28 Dec '10

28 Dec '10

Hello, I still have problems with my Tevii S470 with DVB-S2-channels. The problem (as already posted long ago at http://www.vdr-portal.de/board/thread.php?threadid=93713) is: The buffer runs full buffer usage: 70% (tid=12493) buffer usage: 60% (tid=12493) buffer usage: 70% (tid=12493) buffer usage: 60% (tid=12493) buffer usage: 70% (tid=12493) buffer usage: 60% (tid=12493) buffer usage: 70% (tid=12493) buffer usage: 60% (tid=12493) buffer usage: 100% (tid=12493) ERROR: driver buffer overflow on device 2 ERROR: skipped 11 bytes to sync on TS packet on device 2 This repeats over and over again in a timeloop of about 2mins. Remarkable for me is the fact, I can record any HD-channel without any problems and I even can watch this recording at once. In my oppinion this cannot be a problem with the S470, because I wouldn't be able to record anything. I'm running vdr vdr-1.7.16 with latest xineliboutput (git) and latest xine-sources (hg). The system load is low (<5%) and the menue is smooth and this only happens with DVB-S2-channels. This brings me to the question where is the difference between watching a channel and recording it? Greetings Torsten -- Gerade weil wir alle in einem Boot sitzen, sollten wir heilfroh darüber sein, dass nicht alle auf unserer Seite stehen.

2 1

Framerates
by Tobias Grimm 28 Dec '10

28 Dec '10

Hi! I have tiny question: When recording from a HD channel (720p50), the *.rec/info -file tells me the recording has a framerate of 25 fps. mediainfo or ffmpeg detect 50 fps. Why such a difference? And what's the framerate the frame number in the *.rec/marks -file is based on? Tobias

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr