vdr August 2005

vdr@linuxtv.org

146 participants
183 discussions

Re: [vdr] vdr killing its recording on symlink directory
by peter.dittmann＠freenet.de 12 Aug '05

12 Aug '05

>Von: "Emil Naepflein"<Emil.Naepflein(a)philosys.de> > On Wed, 10 Aug 2005 22:23:26 +0200, Klaus Schmidinger wrote: > > > An even better idea (IMHO) would be to drop that whole video > > directory symlinking stuff altogether and say "If you want a large disk, > > use something like RAID or whatever". I was never a friend of this > > linking, and regret the day I agreed to implement it... > > I am totally against dropping this functionality. Sound I triggered another religios war. I hope I will never regret this posting ;D > > On server systems with multiple TB of storage it would be just brain > > dead to put all recordings on one large raid filesystem. A single error > > in the filesystem could kill all the recordings. Basically the usually distribution between /videoX directories doesn't help here improving safety (doesn't matter if on RAID or single discs). A single failing disc/RAID will cause almost all recordings to fail because they are distributed. Often all recordings will miss at least one file after that. All thats left then are partial recordings, ergo useless. This was/is the reason quite a lot of people move the cutted recording completely to one /videoX , so one recording is kept on one harddrive completely. To make this work you HAVE to symlink to /video0. > The symlink functionality works fine since more than 4 years. It is easy > to use and it is easy to expand storage without doing any > reorganisation. It is one of the most important features of vdr. Agree, but for a different reason. Most people have not the money to start a RAID 5 at the beginning. I usually buy a new additional HD if needed. Ok there is LVM . . . Althought LVM works, a single disc failing in LVM crashes everything. And try one time to add a new additional disc to a RAID 5 installation . . . But thats another war . . . > Those people that have problems with it have not unterstood how it > works. Nobody is forced to use this functionality, but those that use it > intentionally appreciate it very much. See remark above. That you don't understand the intentions of others should not cause you to blaim others for not understanding vdr ;-) I was just pointing out a weekness that may be worth fixing . . . > So keep it, please. I would personnally rather vote for a round robin distribution of recordings not single files, but that a different thread. The circulating patch changing the file distribution method is not applied my vdr because I feared worse side effect. regards Peter

1 0

DVB Device in info.vdr?
by Dominique Simon 12 Aug '05

12 Aug '05

Hi! For debug purposes i wan't to know on which DVB Device a recording has been made (device 0 or 1). Anyone has a idea how this can be realised? A small line C++ Code at the right place should do it, but which and where ;) TIA, Dominique!

1 0

BBC To Open Source This Project
by edafe 12 Aug '05

12 Aug '05

'Promise.tv takes advantage of digital television technology to automatically record a full seven day's broadcasting across all selected TV channels.' http://www.promise.tv/

6 8

osdteletext and problem with OSD
by Marcel Wiesweg 12 Aug '05

12 Aug '05

Hi, I received a bug report for osdteletext which describes a way to crash the FF cards' OSD, and I am able to reproduce this. (Open teletext on a channel with colorful teletext such as RTL, press repeatedly, fast and in random order Yellow Key for half page and Green Key for zoom.) Then the OSD seems to hang a short time, then disappears, after a while some garbage appears. I tested with the in-kernel drivers from 2.6.11 and 2.6.12. Neither VDR nor the kernel driver seem to crash, but the OSD will not work again. In dmesg I read multiple times: dvb-ttpci: warning: timeout waiting in BlitBitmap: 0, 1 Reloading dvb-ttpci fixes the problem. Obviously this is some sort of driver/firmware bug. What I am concerned with is: Does osdteletext do anything wrong? Has this to be fixed somewhere in user level code, or is it just another firmware bug? Marcel

3 3

[Fwd: Re: [vdr] Mac mini + Xine plugin = perfect vdr client?]
by Reinhard Nissl 10 Aug '05

10 Aug '05

-------- Original Message -------- Subject: Re: [vdr] Mac mini + Xine plugin = perfect vdr client? Date: Wed, 10 Aug 2005 21:38:33 +0200 From: Carsten Rietzschel <cr7(a)darav.de> To: Reinhard Nissl <rnissl(a)gmx.de> CC: Klaus Schmidinger's VDR <vdr(a)linuxtv.org> References: <42FA3522.9070901(a)icem.com> <42FA5383.3090908(a)gmx.de> Hello, I'm using the MacMini as my VDR since a few weeks :) configuration: - Cinergy T2 (DVB-T) - ATI remote wonder - gentoo linux with vdr 1.3.24 - xine-plugin (thanks Reinhard for OSD fix :) And it works very well! No big problems so far, except one: TV-Out doesn't work yet for me. I've tried using gatos.sf.net-drivers from Rune Petersen - but no luck yet. Maybe someone can help!!?!? Some minor problems still must be solved: - Mplayer plugin (using /usr/bin/xineplayer) doesn't work - DVD playback is sometimes choppy But currently I'm too busy to investigate - may be at the weekend. Please share your experiences too :)

1 0

[Announce] LNB-sharing patch for VDR 1.3.28
by Matthias Lötzke 10 Aug '05

10 Aug '05

Hello! A new release of the configurable LNB-sharing patch for VDR 1.3 is available at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/configurableLNBshare-VDR_… Changes: - adapted to VDR 1.3.28 The DiSEqC support still needs more testing - I do not have DiSEqC hardware myself. Please provide feedback. For general information about the LNB-sharing patch have a look at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/Description.txt http://www.vdr-wiki.de/wiki/index.php/Lnbsharing-patch (german) Matthias.

1 0

Request: periodic function called from vdr's main task
by Andreas Regel 10 Aug '05

10 Aug '05

Hello, I have a small request for vdr's cStatus class. It would be great if there were a additional method that is called every second or so from vdr's main task. That could be used in plugins that want to query objects from vdr that can only be accessed from the main task, p. e. control object of the current replay. That would be nice for the graphlcd and similar plugins. Andreas

1 0

OT: did anybody record "Taken" from Pro7 on monday 20:15 ?
by Dieter Bloms 10 Aug '05

10 Aug '05

Hi, I've recorded it with vdr-1.3.28 and every 10-15 seconds there is missing some data :( Does anybody have a recording of taken on pro7 (monday 20:15). Please drop me a private mail. Thank you! -- Gruß Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.

1 0

vdr-1.3.28: hangs while recording?
by Udo Richter 09 Aug '05

09 Aug '05

Hi list, After updating to 1.3.28 yesterday, I'm seeing strange VDR hangs today. Same machine, same plugins and patches worked flawlessly on 1.3.27 before. There were recordings running, and I was going through menus that time, when VDR suddenly did not respond to key presses any more. VDR died because of watchdog, but required an additional kill -9 to be stopped and re-started. As another hint, that time VDR was running with >50% CPU load. Next time this happens, I hope I can do some more analysis. Any one else having problems? _____________________________ Incident 1: One recording running on secondary device. 22:18:52 vdr[948]: deleting timer 16 (6 2010-2225 'Filme~Enigma - Das Geheimnis') 22:18:59 vdr[948]: switching to channel 8 22:20:40 vdr[1354]: connect from 192.168.73.1, port 2075 - accepted 22:20:43 vdr[948]: PANIC: watchdog timer expired - exiting! 22:22:36 vdr[1526]: VDR version 1.3.28 started The 'connect' is my attempt to connect via control-plugin, but control-plugin was frozen same as the remote. The recording continued (file time) until 22:22:26. Incident 2: Two recordings running, one on primary, one on secondary. Transfer mode streams another channel from secondary to primary device. 23:12:46 vdr[1526]: switching to channel 173 23:12:51 vdr[1526]: switching to channel 7 23:12:52 vdr[1657]: cDolbyRepacker: skipped 576 bytes to sync on next AC3 frame 23:14:25 vdr[1526]: PANIC: watchdog timer expired - exiting! 23:17:17 vdr[1714]: VDR version 1.3.28 started The recordings continued until 23:17:03 and 23:17:12. Cheers, Udo

2 2

RE: [vdr] Updating the list of recordings
by jori.hamalainen＠teliasonera.com 09 Aug '05

09 Aug '05

> (As a side note, a separate vdr-announce mailing list for VDR-related > announcements would be nice :-) ) Install some email client supporting folders, categories or flagging. Then make a filter for subject starting with "[vdr][announce]" and you have a virtual mailing list? Best regards, Jori

2 1

← Newer
1
...
11
12
13
14
15
16
17
18
19
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr August 2005