[vdr] Any knowledge or experience in Fusion dual tuner cards
Looking for dual tuner cards and found out that Fusion has a couple of these. Anybody know if they are supported by linux? Or if they will be? http://www.fusionhdtv.co.kr/ENG/Products/DualDigital.aspx \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin and character mapping
Hi, On Tuesday 02 January 2007 19:46, Harald Milz wrote: > Andreas Mair <[EMAIL PROTECTED]> wrote: > > What language/locale do you use in VDRAdmin-AM? > > Do you use any VDR patch, that changes its character encoding? > > I'm using the UTF-8 patch (because I'm using Russian and German EPGs), > and German umlauts are displayed incorrectly unless I tell the browser > explicitly to use UTF-8. In any case, vdradmin-am should give a hint > which locale it uses, by using the appropriate META header: > > > > ... and use a portable encoding for buttons and menu entries, like ä > instead of "ä", for example, because if I set UTF-8 in the browser, > umlauted menu entries are incorrectly displayed. At the moment it appears > that for example German is tied to ISO-8859-1 in the PO file. UTF-8 > should be in the SUPPORTED_LOCALE_PREFIXES list, IMHO. There is support for UTF8 but it has to be added manually. Simply run "./make.sh utf8add" and "./make.sh po" to generate the UTF8 locales. Hope this helps... Regards, Andreas -- http://andreas.vdr-developer.org --- VDRAdmin-AM VDR user #303 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Torgeir Veimo wrote: > Every two and a half minute, my syslog gets an entry like: > > Jan 3 06:04:40 htpc kernel: cx88[1]/2: cx8802_timeout > Jan 3 06:04:49 htpc vdr: [2369] frontend 1 timed out while tuning to > channel 9, tp 578 > > About 30 seconds before i get this entry, thee's a vdr thread that eats > about 25% system cpu time. I'm wondering what it's doing with all that > processor power? As I'm using budget cards with softdevice, this has an > effect on tv playback.. It only happens when I'm using two cards at the > same time. > > top - 06:10:04 up 21 min, 2 users, load average: 2.18, 2.63, 2.10 > Tasks: 96 total, 7 running, 89 sleeping, 0 stopped, 0 zombie > Cpu(s): 50.2% us, 24.3% sy, 0.3% ni, 24.6% id, 0.3% wa, 0.0% hi, > 0.3% si, 0.0% st > Mem:515672k total, 160352k used, 355320k free,22520k buffers > Swap: 1815304k total,0k used, 1815304k free,61232k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND > 2388 root 15 0 242m 29m 4140 R 46.9 5.8 13:28.16 vdr > 2369 root 15 0 242m 29m 4140 S 17.6 5.8 1:04.57 vdr > 2368 root 15 0 000 S 3.0 0.0 0:13.46 kdvb-fe-1 It would help if you could find out which particular thread is using that CPU percentage. You can do ps -T u -C vdr to get a display like USER PID SPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND kls 27146 27146 3.7 5.8 124132 22568 pts/0Sl+ 10:49 0:08 ./vdr kls 27146 27150 0.0 5.8 124132 22568 pts/0Sl+ 10:49 0:00 ./vdr kls 27146 27151 0.0 5.8 124132 22568 pts/0Sl+ 10:49 0:00 ./vdr kls 27146 27152 1.6 5.8 124132 22568 pts/0RNl+ 10:49 0:03 ./vdr kls 27146 27154 0.0 5.8 124132 22568 pts/0Sl+ 10:49 0:00 ./vdr where the SPID number corresponds to the thread's "tid" number in VDR's log entries, as in Jan 3 10:49:19 video vdr: [27152] section handler thread started (pid=27146, tid=27152) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any knowledge or experience in Fusion dual tuner cards
On Wed, 03 Jan 2007 10:30:01 +0200 Kartsa <[EMAIL PROTECTED]> wrote: > Looking for dual tuner cards and found out that Fusion has a couple > of these. Anybody know if they are supported by linux? Or if they > will be? > > http://www.fusionhdtv.co.kr/ENG/Products/DualDigital.aspx > > \\Kartsa > There is also such card form DigitalNow: http://www.digitalnow.com.au/product_pages/QuattroS.html That could be great for a next-gen VDR. But It requires a monster pc (or some dedicated hardware) for decoding and I do not know if it is suported under linux at all. Bye, ANgelus. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
On 3 Jan 2007, at 09:58, Klaus Schmidinger wrote: It would help if you could find out which particular thread is using that CPU percentage. You can do ps -T u -C vdr Hmm, it looks like the thread 5748 (tuner on device 2 thread started). Jan 3 11:37:29 htpc vdr: [5741] loading /video/vdr/remote.conf [...] Jan 3 11:37:29 htpc vdr: [5742] video directory scanner thread started (pid=5741, tid=5742) Jan 3 11:37:29 htpc vdr: [5742] video directory scanner thread ended (pid=5741, tid=5742) Jan 3 11:37:29 htpc vdr: [5743] video directory scanner thread started (pid=5741, tid=5743) Jan 3 11:37:29 htpc vdr: [5743] video directory scanner thread ended (pid=5741, tid=5743) Jan 3 11:37:29 htpc vdr: [5741] probing /dev/dvb/adapter0/frontend0 Jan 3 11:37:29 htpc vdr: [5741] probing /dev/dvb/adapter1/frontend0 Jan 3 11:37:29 htpc vdr: [5745] tuner on device 1 thread started (pid=5741, tid=5745) Jan 3 11:37:29 htpc vdr: [5746] section handler thread started (pid=5741, tid=5746) Jan 3 11:37:29 htpc vdr: [5741] found 2 video devices Jan 3 11:37:29 htpc vdr: [5741] initializing plugin: softdevice (0.3.0): A software emulated MPEG2 device Jan 3 11:37:29 htpc vdr: [5748] tuner on device 2 thread started (pid=5741, tid=5748) Jan 3 11:37:29 htpc vdr: [5749] section handler thread started (pid=5741, tid=5749) Jan 3 11:37:29 htpc vdr: [5741] [softdevice] videoOut OK ! [...] Jan 3 11:40:59 htpc vdr: [5748] frontend 1 timed out while tuning to channel 9, tp 578 Jan 3 11:41:54 htpc kernel: cx88[1]/2: cx8802_timeout [EMAIL PROTECTED] ~]# ps -T u -C vdr USER PID SPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 5741 5741 0.2 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5745 0.3 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5746 0.5 5.4 220216 28016 ?RNLl 11:37 0:01 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5748 1.1 5.4 220216 28016 ?SLl 11:37 0:02 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5749 0.4 5.4 220216 28016 ?SNLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5752 0.0 5.4 220216 28016 ?S0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5753 0.0 5.4 220216 28016 ?S0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5754 0.0 5.4 220216 28016 ?S0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5755 0.0 5.4 220216 28016 ?S0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5756 0.0 5.4 220216 28016 ?S0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5757 0.0 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5760 0.0 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5762 0.1 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5763 0.0 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5764 0.1 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5765 0.5 5.4 220216 28016 ?SLl 11:37 0:01 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5767 71.6 5.4 220216 28016 ?SLl 11:37 2:29 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5741 5768 1.2 5.4 220216 28016 ?SLl 11:37 0:02 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo root 5759 5759 0.0 1.7 122400 9260 ?Ss 11:37 0:00 ./vdr -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice - vo dfb:mgatv -Premo [EMAIL PROTECTED] ~]# Tasks: 104 total, 5 running, 99 sleeping, 0 stopped, 0 zombie Cpu(s): 51.7% us, 24.5% sy, 0.3% ni, 22.8% id, 0.0% wa, 0.3% hi, 0.3% si, 0.0% st Mem:515672k total, 181684k used, 333988k free,40848k buffers Swap: 1815304k total,0k used, 1815304k free,61916k cached PID USER PR
Re: [vdr] background vdr thread eating cpu
> On 3 Jan 2007, at 09:58, Klaus Schmidinger wrote: > >> >> It would help if you could find out which particular thread is using >> that CPU percentage. You can do >> >> ps -T u -C vdr > > Hmm, it looks like the thread 5748 (tuner on device 2 thread started). Looks more like thread 5767 to me, see *** > > Jan 3 11:37:29 htpc vdr: [5741] loading /video/vdr/remote.conf > [...] > Jan 3 11:37:29 htpc vdr: [5742] video directory scanner thread started > (pid=5741, tid=5742) > Jan 3 11:37:29 htpc vdr: [5742] video directory scanner thread ended > (pid=5741, tid=5742) > Jan 3 11:37:29 htpc vdr: [5743] video directory scanner thread started > (pid=5741, tid=5743) > Jan 3 11:37:29 htpc vdr: [5743] video directory scanner thread ended > (pid=5741, tid=5743) > Jan 3 11:37:29 htpc vdr: [5741] probing /dev/dvb/adapter0/frontend0 > Jan 3 11:37:29 htpc vdr: [5741] probing /dev/dvb/adapter1/frontend0 > Jan 3 11:37:29 htpc vdr: [5745] tuner on device 1 thread started (pid=5741, > tid=5745) > Jan 3 11:37:29 htpc vdr: [5746] section handler thread started (pid=5741, > tid=5746) > Jan 3 11:37:29 htpc vdr: [5741] found 2 video devices > Jan 3 11:37:29 htpc vdr: [5741] initializing plugin: softdevice (0.3.0): A > software emulated MPEG2 device > Jan 3 11:37:29 htpc vdr: [5748] tuner on device 2 thread started (pid=5741, > tid=5748) > Jan 3 11:37:29 htpc vdr: [5749] section handler thread started (pid=5741, > tid=5749) > Jan 3 11:37:29 htpc vdr: [5741] [softdevice] videoOut OK ! > [...] > Jan 3 11:40:59 htpc vdr: [5748] frontend 1 timed out while tuning to channel > 9, tp 578 > Jan 3 11:41:54 htpc kernel: cx88[1]/2: cx8802_timeout > > [EMAIL PROTECTED] ~]# ps -T u -C vdr > USER PID SPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND > root 5741 5741 0.2 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5745 0.3 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5746 0.5 5.4 220216 28016 ?RNLl 11:37 0:01 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5748 1.1 5.4 220216 28016 ?SLl 11:37 0:02 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5749 0.4 5.4 220216 28016 ?SNLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5752 0.0 5.4 220216 28016 ?S -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5753 0.0 5.4 220216 28016 ?S -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5754 0.0 5.4 220216 28016 ?S -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5755 0.0 5.4 220216 28016 ?S -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5756 0.0 5.4 220216 28016 ?S -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5757 0.0 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5760 0.0 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5762 0.1 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5763 0.0 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5764 0.1 5.4 220216 28016 ?SLl 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5765 0.5 5.4 220216 28016 ?SLl 11:37 0:01 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5741 5767 71.6 5.4 220216 28016 ?SLl 11:37 2:29 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo *** thread 5767 is eating most of the CPU time. Unfortunately this one isn't listed in your log file excerpt. Klaus > root 5741 5768 1.2 5.4 220216 28016 ?SLl 11:37 0:02 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > root 5759 5759 0.0 1.7 122400 9260 ?Ss 11:37 0:00 ./vdr > -v /video/vdr -m 0 -s killall vdr;/bin/false -Psoftdevice -vo dfb:mgatv -Premo > [EMAIL PROTECTED] ~]# > > Tasks: 104 total, 5 running, 99 sleeping, 0 stopped, 0 zombie > Cpu(s): 51.7% us, 24.5% sy, 0.3% ni, 22.8% id, 0.0%
Re: [vdr] background vdr thread eating cpu
On 3 Jan 2007, at 11:59, Klaus Schmidinger wrote: *** thread 5767 is eating most of the CPU time. Unfortunately this one isn't listed in your log file excerpt. No that's the softdevice output thread. It uses about 70% which is expected with this particular setup and gfx card. -- Torgeir Veimo [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Torgeir Veimo wrote: > > On 3 Jan 2007, at 11:59, Klaus Schmidinger wrote: > >> >> *** thread 5767 is eating most of the CPU time. >> Unfortunately this one isn't listed in your log file excerpt. > > No that's the softdevice output thread. It uses about 70% which is > expected with this particular setup and gfx card. Well, the tuner thread doesn't really do that much that might eat such a lot of CPU time, one would think. Maybe you can add some debug output in cDvbTuner::Action() and cDvbTuner::SetFrontend() to find out what exactly it is doing when this happens. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Hi Klaus, On Mi, Jan 03, 2007 at 01:22:14 +0100, Klaus Schmidinger wrote: > Well, the tuner thread doesn't really do that much that might > eat such a lot of CPU time, one would think. > > Maybe you can add some debug output in cDvbTuner::Action() and > cDvbTuner::SetFrontend() to find out what exactly it is doing > when this happens. > few weeks ago I noticed a similar Problem, that vdr eats a lot of cpu power. In my HTPC there is a tt 2.3 dvb-s and a usb-dvb-t stick. I did some tests with dvb-t stick plugged in and without. The cpu load is about 20% higher with the stick. Please tell me if you need more info to find the Problem. Thanks Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Halim Sahin wrote: > Hi Klaus, > > > On Mi, Jan 03, 2007 at 01:22:14 +0100, Klaus Schmidinger wrote: >> Well, the tuner thread doesn't really do that much that might >> eat such a lot of CPU time, one would think. >> >> Maybe you can add some debug output in cDvbTuner::Action() and >> cDvbTuner::SetFrontend() to find out what exactly it is doing >> when this happens. >> > few weeks ago I noticed a similar Problem, that vdr eats a lot of cpu > power. In my HTPC there is a tt 2.3 dvb-s and a usb-dvb-t stick. > I did some tests with dvb-t stick plugged in and without. > The cpu load is about 20% higher with the stick. > Please tell me if you need more info to find the Problem. > Thanks > Halim Can you identify a particular VDR thread that consumes those 20% more CPU time? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
On 3 Jan 2007, at 15:25, Klaus Schmidinger wrote: Halim Sahin wrote: Hi Klaus, On Mi, Jan 03, 2007 at 01:22:14 +0100, Klaus Schmidinger wrote: Well, the tuner thread doesn't really do that much that might eat such a lot of CPU time, one would think. Maybe you can add some debug output in cDvbTuner::Action() and cDvbTuner::SetFrontend() to find out what exactly it is doing when this happens. few weeks ago I noticed a similar Problem, that vdr eats a lot of cpu power. In my HTPC there is a tt 2.3 dvb-s and a usb-dvb-t stick. I did some tests with dvb-t stick plugged in and without. The cpu load is about 20% higher with the stick. Please tell me if you need more info to find the Problem. Thanks Halim Can you identify a particular VDR thread that consumes those 20% more CPU time? I think in my particular case it's really kernel time being spent by the driver trying to lock onto channel 9. I guess the tuning is done to collect VPG data. -- Torgeir Veimo [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any knowledge or experience in Fusion dual tuner cards
DOm kirjoitti: On Wed, 03 Jan 2007 10:30:01 +0200 Kartsa <[EMAIL PROTECTED]> wrote: Looking for dual tuner cards and found out that Fusion has a couple of these. Anybody know if they are supported by linux? Or if they will be? http://www.fusionhdtv.co.kr/ENG/Products/DualDigital.aspx \\Kartsa There is also such card form DigitalNow: http://www.digitalnow.com.au/product_pages/QuattroS.html That could be great for a next-gen VDR. But It requires a monster pc (or some dedicated hardware) for decoding and I do not know if it is suported under linux at all. Bye, ANgelus. ___ Fusion card has a mpeg4 decoder included. \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Hi, On Mi, Jan 03, 2007 at 04:25:57 +0100, Klaus Schmidinger wrote: > Can you identify a particular VDR thread that consumes those > 20% more CPU time? > Thats very dificult. After observing this a time here is the output of ps -T u -C vdr USER PID SPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 5252 5252 0.0 1.0 31536 10628 tty1 Rl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5262 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5263 0.4 1.0 31536 10628 tty1 SNl+ 17:59 0:01 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5265 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5266 0.3 1.0 31536 10628 tty1 RNl+ 17:59 0:01 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5267 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5268 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5283 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5284 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr root 5252 5285 0.3 1.0 31536 10628 tty1 Sl+ 17:59 0:01 ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr I am not shure that you can read someting out of this. I can only tell you, that the cpuload without the dvb-t stick pluged in is lower. Thanks Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Halim Sahin wrote: > Hi, > On Mi, Jan 03, 2007 at 04:25:57 +0100, Klaus Schmidinger wrote: >> Can you identify a particular VDR thread that consumes those >> 20% more CPU time? >> > > Thats very dificult. > After observing this a time here is the output of > ps -T u -C vdr > > USER PID SPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND > root 5252 5252 0.0 1.0 31536 10628 tty1 Rl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5262 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5263 0.4 1.0 31536 10628 tty1 SNl+ 17:59 0:01 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5265 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5266 0.3 1.0 31536 10628 tty1 RNl+ 17:59 0:01 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5267 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5268 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5283 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5284 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > root 5252 5285 0.3 1.0 31536 10628 tty1 Sl+ 17:59 0:01 ./vdr > -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > I am not shure that you can read someting out of this. > I can only tell you, that the cpuload without the dvb-t stick pluged in > is lower. Maybe the CPU load is simply higher for the USB driver, as suggested by Torgeir Veimo in his posting a few hours ago. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] background vdr thread eating cpu
Hallo Klaus, On Mi, Jan 03, 2007 at 06:34:47 +0100, Klaus Schmidinger wrote: > Halim Sahin wrote: > > Hi, > > On Mi, Jan 03, 2007 at 04:25:57 +0100, Klaus Schmidinger wrote: > >> Can you identify a particular VDR thread that consumes those > >> 20% more CPU time? > >> > > > > Thats very dificult. > > After observing this a time here is the output of > > ps -T u -C vdr > > > > USER PID SPID %CPU %MEMVSZ RSS TTY STAT START TIME > > COMMAND > > root 5252 5252 0.0 1.0 31536 10628 tty1 Rl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5262 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5263 0.4 1.0 31536 10628 tty1 SNl+ 17:59 0:01 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5265 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5266 0.3 1.0 31536 10628 tty1 RNl+ 17:59 0:01 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5267 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5268 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5283 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5284 0.0 1.0 31536 10628 tty1 Sl+ 17:59 0:00 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > root 5252 5285 0.3 1.0 31536 10628 tty1 Sl+ 17:59 0:01 > > ./vdr -E /dev/shm/epg.data -w 40 -s /sbin/go_down -l 0 -c /etc/vdr > > > > I am not shure that you can read someting out of this. > > I can only tell you, that the cpuload without the dvb-t stick pluged in > > is lower. > > Maybe the CPU load is simply higher for the USB driver, > as suggested by Torgeir Veimo in his posting a few hours ago. > May be. Perhaps somebody can check the cpuload with only two pci cards? Thanks Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New VDR hardware
On Saturday 30 December 2006 19:53, Richard Scobie wrote: > Timothy D. Lenz wrote: > > Too bad it only has 1 expansion slot. That means only 1 tunner board. > > I wouldn't even concider anything with less then 2-3 slots. > > It does have 4 x USB 2.0 which seems to be becoming popular for tuners > now. Nice idea but... I've never managed to get two USB2 Nova-T devices working together for extended periods of time hanging off an Epia board. After a few hours, both of the USB boxes will randomly disconnect themselves leaving a very unhappy vdr because the DVB devices have disappeared form under its nose!! i did try various driver debugging options but never came to any conclusion about why they did this. Most of the time a reboot will restore them; other times, they need unplugging and a reboot so that they get the firmware reloaded. Maybe this is down to a buggy USB chip on the motherboard or maybe I'm just unlucky and for some reason my two USB devices won't play happily together (on their own, they can work seamlessly for weeks!), or maybe it's down to a firmware bug or something. I also have a Nova-T 500 which is a PCI card containing two USB DVB devices with an on-board USB controller: that works perfectly (in conjunction with one of the USB Nova-T devices!). Other USB devices might work well together, though... Just my experiences! My spare USB device is currently hanging off a Linksys NSLU2, a.k.a. Slug, but that's a story for another day! ;) Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New VDR hardware
Laz kirjoitti: Maybe this is down to a buggy USB chip on the motherboard or maybe I'm just unlucky and for some reason my two USB devices won't play happily together (on their own, they can work seamlessly for weeks!), or maybe it's down to a firmware bug or something. I also have a Nova-T 500 which is a PCI card containing two USB DVB devices with an on-board USB controller: that works perfectly (in conjunction with one of the USB Nova-T devices!). Now that this came up. I was wondering in my earlier post today about twin tuner cards and if I understood correctly Nova-T 500 is such a card. And if I again understood correctly it works with linux and VDR? \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New VDR hardware
On 3 Jan 2007, at 20:45, Kartsa wrote: Now that this came up. I was wondering in my earlier post today about twin tuner cards and if I understood correctly Nova-T 500 is such a card. And if I again understood correctly it works with linux and VDR? Some people including me are experiencing usb disconnection with the nova-t 500 (it has an internal usb bus), which in some cases can make your machine freeze, and in the best case causes you to loose a few seconds of playback / recording. See the linux-dvb mailing list for more details. -- Torgeir Veimo [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any knowledge or experience in Fusion dual tuner cards
>> > Fusion card has a mpeg4 decoder included. Are you sure it has hardware decoder support for mpeg4, I could not find that mentioned from that site. Could that also offer the hardware support for divx... Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
