vdr

vdr@linuxtv.org

2 participants
6731 discussions

xineliboutput cvs won't compile
by Marco Göbenich 28 Oct '11

28 Oct '11

Hi! I tried to compile xineliboutput from CVS, but I get an error message: xine_frontend_main.o: In function `main': xine_frontend_main.c:(.text+0x867): undefined reference to `EXIT' xine_frontend_main.c:(.text+0x895): undefined reference to `EXIT' xine_frontend_main.c:(.text+0x909): undefined reference to `EXIT' I looked at the source code but the EXIT macro is not defined. Regards Marco -- Needful GbR Rheinstraße 60a Telefon +49 (0) 26 24 / 95 29 301 56203 Höhr-Grenzhausen Telefax +49 (0) 26 24 / 95 29 303 http://www.needful.de E-Mail mg(a)needful.de

2 1

VDR segfault with cable provider Unitymedia (DE)
by Juergen Judt 25 Oct '11

25 Oct '11

vdr-1.7.21 segfault by cable provider unitymedia (DE) Hi, I have problems with the VDR because I get segfaults every ~5-10 minutes. Similar problems are also reported in the VDR-Portal --> www.vdr-portal.de/board60-linux/board14-betriebssystem/board69-c-t-vdr/p102… . The failure / segfault must have something to do with the EPG scan...... When I limit the channels.conf and set in the DVB menu --> Update Channels to "Names and PIDs" it works without segfaults. In case that the cable provider Unitymedia send wrong data, I assume the vdr should not make a segfault. I make some test with different (unpatched=vanilla VDR) VDR version, but all with the same result --> segfault (see attachment). So it seems that the cable provider send something what let the VDR crash :( . Do you have any idea or patch? Can I test something with special syslog information? Bye, Juergen

2 2

VDR segfault with cable provider Unitymedia (DE)
by OppTupacShakur 25 Oct '11

25 Oct '11

I have the same problems on vdr 1.6.0 and 1.7.21 with unitymedia. Here is my backtrace: (gdb) bt #0 cHashBase::Get (this=0xc4ba414, Id=1319943600) at tools.c:1992 #1 0x080be6db in cEIT (this=0xb4112240, Schedules=0x818fa40, Source=1124073472, Tid=81 'Q', Data=0xb4112338 "Q\361\345e\373툸 \001\005'\017\210Q\003\037\332\070\003", OnlyRunningStatus=false) at eit.c:68 #2 0x080bf97c in cEitFilter::Process (this=0xc4176c0, Pid=18, Tid=81 'Q', Data=0xb4112338 "Q\361\345e\373툸\001\005'\017\210Q\003\037\332\070\003", Length=488) at eit.c:382 #3 0x0810c763 in cSectionHandler::Action (this=0xc417790) at sections.c:212 #4 0x08128ab0 in cThread::StartThread (Thread=0xc417790) at thread.c:257 #5 0xb7f8a955 in start_thread (arg=0xb4113b70) at pthread_create.c:300 #6 0xb7d03e7e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

1 0

FreeviewHD compressed EPG
by Stuart Morris 25 Oct '11

25 Oct '11

In the absence of a modification to the Eepg plugin to decompress the FreeviewHD EPG, I have applied the original Freesat.diff to my installation of VDR 1.7.21 and have achieved some success accessing the FreeviewHD EPG. The patch is here: http://www.rst38.org.uk/vdr/freesat.diff The first hunk fails to apply but this is ok because that part of the patch is relevant to freesat only. The decompressed EPG has many 'holes' in it due to incomplete Huffman lookup tables in the freesat.diff. I did manage to port the Freesat lookup tables from the Eepg plugin to the freesat.diff and I can now receive what appears to be the complete FreeviewHD EPG :-)))))

5 9

vdr-sxfe and compositing
by Tony Houghton 24 Oct '11

24 Oct '11

I'm having some problems with vdr-sxfe under GNOME3/mutter. If I start it with --fullscreen it doesn't go fullscreen properly; I can still see the gnome shell panel at the top of the screen and there's no vsync so I get tearing. If I toggle fullscreen off and on again by double-clicking it does cover up the panel correctly but I still get tearing. If I start it without --fullscreen and double click it works correctly without tearing. I would have thought it would be a good idea to have an output backend especially for compositors because AIUI compositing provides features like scaling and YUV-RGB conversion and it would probably be more efficient to work directly with the compositor instead of xv. Is there such a thing for xine? Or would it make sense to use opengl? I've just been watching a recording of Nasa's Greatest Missions from the Quest channel. It was quite jerky, but I think it may have been because the US source was badly converted to PAL; it was one big jerk every second and other programmes don't suffer from this, but I still think it's maybe more jerky than it was with GNOME 2. Could be my imagination. But after watching the NASA thing I noticed that vdr-sxfe had printed loads of copies of this message: [21326] [input_vdr] vdr_adjust_realtime_speed: assertion failed: this->is_trickspeed is true !

1 0

Segfault in vdr-sxfe
by Vidar Tyldum 24 Oct '11

24 Oct '11

Evening lads, In dmesg: vdr-sxfe[2926]: segfault at 1 ip 00000001 sp b4a1918c error 14 in vdr-sxfe[8048000+20000] Doing a quick gdb session on the coredump: > Core was generated by `/usr/bin/vdr-sxfe --hud -f -v -l --syslog xvdr://127.0.0.1'. > Program terminated with signal 11, Segmentation fault. > #0 0x00000001 in ?? () > (gdb) bt > #0 0x00000001 in ?? () > #1 0x0805c443 in ?? () > #2 0xb727636d in ?? () from /usr/lib/libxine.so.2 > #3 0xb7276908 in ?? () from /usr/lib/libxine.so.2 > #4 0xb7596bc7 in ?? () from /usr/lib/nvidia-current/libGL.so.1 > #5 0xb71a969e in clone () from /lib/libc.so.6 > (gdb) My interpretation is that it is most likely an issue between lib-xine and the nvidia driver? I have a bunch of these segfaults, but only recently enabled core dumps. Have similar segfaults with vdr itself too, but I guess it is pointless to post those without a core-file? [190166.409612] vdr[16514]: segfault at b6359bcc ip 08139352 sp bfd73480 error 4 in vdr[8048000+14e000] [192021.947521] vdr[14006]: segfault at b63f9bcc ip 08139352 sp bff6a160 error 4 in vdr[8048000+14e000] -- Vidar Tyldum vidar(a)tyldum.com PGP: 0x3110AA98

1 0

eepg plugin with UK freeview (not freesat!) EPG
by Laz 24 Oct '11

24 Oct '11

Does anyone know whether the eepg plugin should "just work" with the Huffman encoded EPG broadcast on Freeview (DVB-T) HD channels in the UK? (Someone mentioned it on here a week or so back.) I'm pretty sure the EPG data is encoded in exactly the same way as it is on Freesat, i.e. DVB-S, and eepg can decode that EPG. I'm trying to work out whether it should currently be able to do it (and I need to configure something before it'll work), or whether I should try to add support for it. A quick scan of the source code looks like the terms "freesat" and "freeview" are used interchangably in it. Currently, I have completely garbled EPG on HD channels! I can add decoded EPG grabbed via xmltv but the EPG gets overwritten with the garbled version. (What's vdr's policy on EPG data added through SVDRP, etc., being overwritten by data from the EIT?) Cheers, Laz

5 7

delete no event timers
by Lou 23 Oct '11

23 Oct '11

Sun Oct 23 11:08:23, Klaus Schmidinger wrote: > A "hook" is definitely the wrong approach! > > What you need to do is find out exactly *why* VDR doesn't delete these > timers as soon as you would expect it to. Then we can see what can > be done about that. I agree, here's what I noticed with a more thorough look at yesterday's syslog. I attached the relevant parts of the log to avoid line wrapping. The timer enumeration of the problematic timers all changed from their respective value to 1 after being "set to no event" - please note that the actual recording happened as expected. Any thoughts on how to debug the issue?

2 1

delete no event timers
by Lou 23 Oct '11

23 Oct '11

I noticed vdr 1.7.16 sometimes waits unusually long until a VPS timer set to "no event" is getting deleted. Mostly it works fine, meaning: vdr will delete no event timers after a few seconds or minutes. But there are the occassional oddities, where it takes more than an hour, which in return will cause the media center to stay on longer than necessary during overnight recordings. This also would not encourage me much to leave vdr unmaintained for a few days during holidays. Does somebody have a solution for this problem (e.g. a "recording-hook AFTER" checking timers, removing those dirty ones using svdrpsend) ?

2 1

old recordings are not deleted
by cedric.dewijs＠telfort.nl 22 Oct '11

22 Oct '11

Am 21.10.2011 20:47, schrieb cedric.dewijs(a)telfort.nl: > I have installed VDR. It runs great, but it has one problem. It does not > delete my old recordings. I have a lot of recordings, and they all have a > lifetime of 0. See also the following info file: VDR deletes old recordings if - Disk space on the root video directory is less than 1Gb (39 min) - The recording is on the file system(s) of the root video directory - The recording is not edited (does not start with %) - The guaranteed lifetime has expired (99 never expires) - In case of lifetime=0, the current recording needs higher priority than the old recording The first two rules about the root video directory do account for everything within the usual /video.00, /video.01, etc. folders, but not any directory trees mounted to sub-directories. So if you mount a disk to /video/archive, disk space will not count there, and nothing will be deleted. Cheers, Udo I see. I have 2 partitions, a / partition and a /storage partition. I would like to record to /storage/video/video.00. I have edited /etc/default/vdr so it reads: # /etc/default/vdr # # See also /usr/share/doc/README.Debian # # Change to 1 to enable vdr's init-script ENABLED=1 # Change this to 1 if you want vdr to be able to shutdown the # computer ENABLE_SHUTDOWN=0 # Options that will be passed to vdr's commandline # for example: OPTIONS="-w 15" OPTIONS="-v /storage/video/video.00 -w 60" # Set this to load only plugins with the correct patch level PLUGIN_CHECK_PATCHLEVEL="no" PLUGIN_CHECK_STARTABLE="no" # Locale which is used when running vdr VDR_LANG=de_DE.UTF-8 VDR_CHARSET_OVERRIDE="ISO8859-15" Still I get the error: Oct 22 07:51:24 localhost vdr: [1579] low disk space while recording, trying to remove a deleted recording... Oct 22 07:51:24 localhost vdr: [1579] ...no deleted recording found, trying to delete an old recording... Oct 22 07:51:24 localhost vdr: [1579] ...no old recording found, giving up What can I do? Best reards, Cedric

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr