vdr

vdr@linuxtv.org

2 participants
6731 discussions

Cleanup Thread (like .update)
by hgm.bg 05 Oct '05

05 Oct '05

Hi Klaus, Is there a possibility to implement the same way .update works a way to start the cleanup thread which is deleting the deleted recordings ? I'm usually low an diskspace and when try to free space for new recordings it takes mostly more than 5 minutes of an idle VDR to delete the recordings on the system. Sometimes 5 Minutes is too long :). Is this harcoded anywhere in the code ? Than it would be enough for me to shorten this amount of time. /hgm.bg

4 8

RE: [vdr] lagged responce on Nexus 2.2
by Vladimir Shved 05 Oct '05

05 Oct '05

Yes, dma is enabled. > -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of Stefan Taferner > Sent: Wednesday, October 05, 2005 5:04 AM > To: Klaus Schmidinger's VDR > Subject: Re: [vdr] lagged responce on Nexus 2.2 >

1 0

Alphacrypt Light doesn't work...
by Christian Stangier 05 Oct '05

05 Oct '05

Hello, I'm running vdr 1.3.31 with a Cinery DVB-C 1200 card. Everything has been working fine: I've been able to watch FTA channels with no problems. Last week I was subscribing to PayTV and therefore I installed the CineView CI (http://www.knc1.com/gb.htm) with the CAM AlphaCrypt Light. Free To All television is working until I plug in the CAM. After that I don't get any more data and I can't watch anything until the next reboot. The smartcard that I'm using has not been activated yet (wanted to do this but didn't work as everything else :-() BTW: Accessing the CAM menu and viewing informations about the smartcard is possible so I don't think the CAM is damaged. This what the kernel says: Linux video capture interface: v1.00 saa7146: register extension 'budget dvb /w video in'. PCI: Found IRQ 5 for device 0000:00:0a.0 saa7146: found saa7146 @ mem f0920000 (revision 1, irq 5) (0x153b,0x1156). DVB: registering new adapter (Terratec Cinergy 1200 DVB-C). adapter failed MAC signature check encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff Obudget-av: ci interface initialised. KNC1-0: MAC addr = 00:0a:ac:01:e0:fc DVB: registering frontend 0 (Philips TDA10021 DVB-C)... ...vdr's output: VDR version 1.3.31 started vdr[2682]: loading plugins [..skipped..] kernel: budget-av: cam inserted kernel: dvb_ca adapter 0: DVB CAM detected and initialised successfully vdr[2682]: found 1 video device vdr[2682]: setting primary device to 2 vdr[2682]: SVDRP listening on port 2001 CAM: AlphaCrypt Light, 01, 4A20, 4A20 switching to channel 46 switching to channel 44 thanks in advance, chris.

1 0

Easy TV and VDR
by Robert Schneider 05 Oct '05

05 Oct '05

2 3

RE: [vdr] lagged responce on Nexus 2.2
by Vladimir Shved 05 Oct '05

05 Oct '05

> -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of Jon Burgess > Sent: Tuesday, October 04, 2005 3:22 PM > To: Klaus Schmidinger's VDR > Subject: Re: [vdr] lagged responce on Nexus 2.2 .... > > I think it would be worth noting which processes are high in the 'top' > list, is it VDR? > > I've seen VDR occasionally switch the system time backwards and forwards > repeatadly which can upset some of VDR's internal time() based loops > causing spikes of CPU usage. Are there any messages like these in > /var/log/messages? Thank you for pointing those out, I've checked my system and ruled out all your mentioned causes. The vdr is on top all the time, top shows 0-0.5% cpu utilization, even when I do 2-3 recordings at the same time. I've disabled time setting in VDR from sat stream, the system is set to sync time using ntp. So those are not the problems here. I'm trying to figure out why starting recording on budget card would fix this lagged behavior on FF card. Its like something flushes/clears the data pipe to FF card when I start recording on budget card, the FF card starts to respond very fast and without pauses. I guess the issue is specific to my setup only, possibly an issue with PCI bus transfers. I'm going to try to move my FF card to another system and see how it behaves there.

2 1

Wanted: Filesize of recordings available in skins
by Christoph Hermanns 05 Oct '05

05 Oct '05

Hello @all, when showing the details of a recording, i'd like to know how much diskspace in MB is needed on my HD (e.g. sum of .vdr files). This size in MB is very useful when archiving some recordings on dvd or copying the data to another limited storage place. My questions to Klaus and Sascha or others that can be of help: 1. Is this size information already available for a plugin ? If not, i would highly welcome that this size information can be accessed from a plugin. 2. Because i used the text2skin plugin this size information has to be implemented into the text2skin plugin. Due this plugin has been not changed in the last months i'd like to know if the development is going on in the next time and if such a new feature can be implemented. Best regards, Christoph

4 3

[ANNOUNCE] LoadEPG version 0.1.6
by lukkinosat 05 Oct '05

05 Oct '05

Hi 2005-10-05: Version 0.1.6 - Improved the source code for better preformances - Add Finnish translation (by Rolf Ahrenberg) - Add provider Canal Digital on S1W satellite (by Rolf Ahrenberg) http://www.kikko77.altervista.org/index.php Lukkino ___________________________________ Yahoo! Messenger: chiamate gratuite in tutto il mondo http://it.messenger.yahoo.com

1 0

lagged responce on Nexus 2.2
by Vladimir Shved 05 Oct '05

05 Oct '05

On my system I get lagged response from VDR until I start recording on budget card. The system just responds very slow, or kind of jumpy, its like if system is busy with something but CPU usage is 0%. The recordings seem to pause for millisecond from time to time. The only work around I found is to start and stop recording on budget card, then it starts to respond smooth and nice. Any suggestions how to solve it, things to try? So far I've tried pulling all cards out, left only single FF card in the system. Tried moving FF card to different slots, starting/stopping recording on FF card does not make the problem to go away. I tried different kernels, 2.6.8 through 2.6.14-rc3 and firmwares 261f to 2621. Tried vanilla VDR sources and heavy patched VDR, versions 1.3.15 to 1.3.33. If VDR restarts the problem comes back right away, I have to record something again using budget card for the problem to go away. Newest drivers do not produce any error messages of any kind, all loads fine and tried running it for over 48 hours without restart. When using single FF card in the system, I can't find a way to get rid of the problem. I just ran out of ideas on what to try next. Thanks in advance. --Vlad My system specs: Nexus-S 2.3 SkyStar 2 (2.6c) Technotrend budget, (like Nova-S S1102) Athlon-XP 2200+ cpu Asus A7V880 via KT880 motherboard 1Gig of RAM(x2 512Mb sticks) running in dual channel config.

3 2

RE: [vdr] lagged responce on Nexus 2.2
by Vladimir Shved 04 Oct '05

04 Oct '05

That does not seem to be an issue here, output should be attached with this message. --Vlad > -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of Jon Burgess > Sent: Tuesday, October 04, 2005 11:49 AM > To: Klaus Schmidinger's VDR > Subject: Re: [vdr] lagged responce on Nexus 2.2 > > Vladimir Shved wrote: > > On my system I get lagged response from VDR until I start recording on > > budget card. The system just responds very slow, or kind of jumpy, its > like > > if system is busy with something but CPU usage is 0%. The recordings > seem to > > I saw something similar before when a SATA controller was spamming the > system with 100,000+ interrupts per second. Could you run "vmstat 1" for > a few seconds when you find the slugish behaviour? >

2 1

Re: [vdr] Allocating Channels to Specific Devices
by Morfsta 04 Oct '05

04 Oct '05

> The problem with hdtv is afaik the mpeg2decoder of the tt-premium cards. > So I think your can't do anything to get it work with a skysta and a > tt-premium. > > Halim I am using xine output plugin, not the mpeg2decoder on the TT premium. However, the TT premium is attached to a CAM so I would prefer to still use it. Morf

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr