vdr January 2011

vdr@linuxtv.org

64 participants
52 discussions

recordings not deleted in additional video-dirs (video.0x)
by Patrick Boettcher 10 Jan '11

10 Jan '11

Hi all, First let me descibe my setup: I'm using VDR from http://e-tobi.net/vdr-experimental (vdr (1.7.16/1.7.16), 1.7.16-2~ctvdr1 - vdr-abi-1.7.16-multipatch) I switched to vdr-experimental beginning of November 2010. I think the version I'm using now (above) is available only since last week (before it was 1.7.16- <something else>). I don't know what has changed and whether my problem persists with this version and I can't easily check any longer. However, I'm sure that the previous one was having the following problem: Until recently I used 2 partitions for recordings: /var/lib/video -> /var/lib/video.00 /var/lib/video.00 /var/lib/video.01 /var/lib/video.01 is what I called additional video-dir in the subject. VDR puts some files (.ts or .vdr respectively) into /var/lib/video.01 and creates symbolic links from /var/lib/video.00 . I'm not sure whether this feature is added by multipatch or included in vanilla-vdr. When now I merged the two video.0x directories onto a new partition I resolved the symbolic links with a small script and mv'd the corresponding files into the right place. When this was done I realized that there were still plenty of .ts and .vdr files which had no longer any reference in the original video.00- directory. All the files that were left are files from recordings I deleted after switching to vdr-1.7.16 . Those were recordings from before and after switching to vdr-1.7.16 . I hope what I'm writing is clear. If I'm finding the time I will take a look at the vdr-source from the package, but don't count on it... best regards, -- Patrick

2 2

howto cut recordings with vdr in daemon mode
by Gero 10 Jan '11

10 Jan '11

Hello, I'm looking for a way to cut recordings using the vdr (on a different machine), but I don't want the new recording on the same disk as the origin - normally the disk of the recording has no free space, when I like to start cutting. So I tried to fake the video-root to get the new recording to another disk. I tried to link the recordings title directory to a disk, where I do have free space and startet the vdr like this: vdr -v /path-to-disk-with-free-space --edit=/linked-directory-on-disk-with- free-space With that call I got the error message, that the recordings title directory is not a directory. So I tried to change things. I created the title-directory on the disk with free space and linked the timestamp-directory to the original recording. Trying again to cut that recording - vdr keeps on claiming, that the recordings title directory is not a directory. But this time it is a directory! So how can I cut the recording without having to copy it to a new drive? kind regards Gero

2 4

IPv6 support
by Pim Zandbergen 09 Jan '11

09 Jan '11

I own a Reelbox Avantgarde II. I know it uses IPv6 internally, but sadly none of the external services are available over IPv6. Notably SVDRP, streamdev and vdradmin. Is that a limitation of VDR, or just the Reelbox build? In vdradmin I read some comment that suggests SVDRP could talk IPv6. Strangely, I do not see any mention of IPv6 in this list or on the VDR wiki. Pim

1 0

VDR creates 2GB files when using --edit (vdr 1.7.16)
by Marco Göbenich 08 Jan '11

08 Jan '11

Hi! tried to cut a one file recording per commandline with vdr 1.7.16, but it always creates multiple files splitted after 2GB, used also "-c /etc/vdr" so that vdr knows where to find setup.conf, but it doesen't matter. Is this the expected behaviour? Regards Marco -- Needful GbR Rheinstraße 60a Telefon +49 (0) 26 24 / 95 29 301 56203 Hoehr-Grenzhausen Telefax +49 (0) 26 24 / 95 29 303 http://www.needful.de E-Mail mg(a)needful.de

3 3

How to extract HD dvb subtitles (and possibly convert to srt)?
by Luca Olivetti 08 Jan '11

08 Jan '11

I've a media player that only understand srt subtitles, so I'm looking for a way to extract the dvb subtitles from a vdr ts recording, and then use some kind of ocr to convert it to srt. I asked google and I came empty handed (many people asking the same question with no working answer). What I tried so far: - ProjectX (fails because it doesn't like hd pixel coordinates) - avidemux (it has a ts->srt option but it only allows pids up to to 255, and the lucky few that managed to make it work say that it doesn't work with hd) - mencoder -vobsubout (it just produces garbage instead of good pictures, at least according to subrip) Any other option? Bye -- Luca

4 11

Re: [vdr] vdr segfaults with glibc 2.12.2
by scott＠waye.co.uk 06 Jan '11

06 Jan '11

Funny, I tried to change my system to Archlinux last weekend and had the same problem. I gave up in the end and will try Opensuse 11.3 now. I also tried recompiling glibc from source but it gave the same error. Would be to have a test suite for pthread. Could be a 64bit problem... if I was going to pursue it I would create a test program that made the same call as vdr to submit to the Archlinux guys. Sent from my HTC ----- Reply message ----- From: "David Spicer" <azleifel(a)googlemail.com> Date: Thu, Jan 6, 2011 20:53 Subject: [vdr] vdr segfaults with glibc 2.12.2 To: <vdr(a)linuxtv.org> 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

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr January 2011