Re: [vdr] Vdr or driver performance dropout

2007-03-11 Thread Stefan Huelswitt
On 01 Feb 2007 Reinhard Nissl [EMAIL PROTECTED] wrote: Heikki Manninen wrote: I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at the same time. I remember there

Re: [vdr] Vdr or driver performance dropout

2007-03-11 Thread Kartsa
Stefan Huelswitt kirjoitti: On 01 Feb 2007 Reinhard Nissl [EMAIL PROTECTED] wrote: Heikki Manninen wrote: I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at

Re: [vdr] Vdr or driver performance dropout

2007-03-11 Thread Steffen Barszus
Kartsa schrieb: Stefan Huelswitt kirjoitti: On 01 Feb 2007 Reinhard Nissl [EMAIL PROTECTED] wrote: Heikki Manninen wrote: I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and

Re: [vdr] Vdr or driver performance dropout

2007-03-03 Thread Kartsa
Kartsa kirjoitti: Kartsa kirjoitti: Marko Mäkelä kirjoitti: In any case, you could profile the old and new version of vdr and see if there is any obvious difference. I'll have to take that into consideration. I'll have to download the old version and all that :) I was unsuccesfull

Re: [vdr] Vdr or driver performance dropout

2007-02-11 Thread Jouni Karvo
hi, Seppo Ingalsuo writes: Jouni Karvo wrote: Earlier I had an ATI GFX card and used XV (with xine) for playback, and had not this problem. After switching to nVidia GeForce FX 5200, it started. I wonder if this would help in xorg.conf Device section Option UseEvents

Re: [vdr] Vdr or driver performance dropout

2007-02-05 Thread Seppo Ingalsuo
Jouni Karvo wrote: Earlier I had an ATI GFX card and used XV (with xine) for playback, and had not this problem. After switching to nVidia GeForce FX 5200, it started. I wonder if this would help in xorg.conf Device section Option UseEvents True (from

Re: [vdr] Vdr or driver performance dropout

2007-02-04 Thread Jouni Karvo
hi, I have also currently the responsiveness problem. I have a P4 2.4GHz which runs at aout 20% load, so it should not be a performance problem. Currently home-made lirc, vdr-xine and 1.4.1 (and that's why I haven't reported before you started complaining, as I have not had the energy to

Re: [vdr] Vdr or driver performance dropout

2007-02-04 Thread Reinhard Nissl
Hi, Jouni Karvo wrote: I have also currently the responsiveness problem. I have a P4 2.4GHz which runs at aout 20% load, so it should not be a performance problem. Currently home-made lirc, vdr-xine and 1.4.1 (and that's why I haven't reported before you started complaining, as I have not

Re: [vdr] Vdr or driver performance dropout

2007-02-04 Thread Jouni Karvo
hi, Reinhard Nissl writes: Are you using xine's video output driver xxmc? yes, I am. I experience deadlocks with this driver on either nVidia or Via EPIA hardware. For example, when you replay a recording and press the pause button: the pause symbol (OSD) will never appear on

Re: [vdr] Vdr or driver performance dropout

2007-02-03 Thread Clemens Kirchgatterer
Marko Myllymaa [EMAIL PROTECTED] wrote: Also this newer version does some weird busylooping or whatever from time to time. Vdr gets all remote codes and buffers them, but just starts executing them after ~45s. One time it took so long, that I got ssh opened from other computer to restart vdr,

Re: [vdr] Vdr or driver performance dropout

2007-02-03 Thread Laz
On Saturday 03 February 2007 10:13, Clemens Kirchgatterer wrote: Marko Myllymaa [EMAIL PROTECTED] wrote: Also this newer version does some weird busylooping or whatever from time to time. Vdr gets all remote codes and buffers them, but just starts executing them after ~45s. One time it took

Re: [vdr] Vdr or driver performance dropout

2007-02-03 Thread Clemens Kirchgatterer
Laz [EMAIL PROTECTED] wrote: On Saturday 03 February 2007 10:13, Clemens Kirchgatterer wrote: Marko Myllymaa [EMAIL PROTECTED] wrote: Also this newer version does some weird busylooping or whatever from time to time. Vdr gets all remote codes and buffers them, but just starts

Re: [vdr] Vdr or driver performance dropout

2007-02-03 Thread Kartsa
Clemens Kirchgatterer kirjoitti: Laz [EMAIL PROTECTED] wrote: On Saturday 03 February 2007 10:13, Clemens Kirchgatterer wrote: Marko Myllymaa [EMAIL PROTECTED] wrote: Also this newer version does some weird busylooping or whatever from time to time. Vdr gets all remote codes

Re: [vdr] Vdr or driver performance dropout

2007-02-02 Thread Marko Myllymaa
On Thu, 1 Feb 2007, Kartsa wrote: Marko Mäkelä kirjoitti: On Thu, Feb 01, 2007 at 10:18:03PM +0200, Kartsa wrote: Would it really matter in this case when cpu load was that small? I was just trying to say that even though there were almost no cpu load vdr was working sluggish. Without

Re: [vdr] Vdr or driver performance dropout

2007-02-02 Thread Marko Mäkelä
On Fri, Feb 02, 2007 at 04:05:10PM +0200, Marko Myllymaa wrote: On Thu, 1 Feb 2007, Kartsa wrote: Marko Mäkelä kirjoitti: On Thu, Feb 01, 2007 at 10:18:03PM +0200, Kartsa wrote: Would it really matter in this case when cpu load was that small? I was just trying to say that even though

[vdr] Vdr or driver performance dropout

2007-02-01 Thread Kartsa
I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at the same time. I remember there seemed to be no trouble doing it. Now when I have vdr 1.4.4 after fourth recording

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Heikki Manninen
On to, 2007-02-01 at 19:29 +0200, Kartsa wrote: I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at the same time. I remember there seemed to be no trouble doing it.

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Reinhard Nissl
Hi, Heikki Manninen wrote: I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at the same time. I remember there seemed to be no trouble doing it. Now when I have vdr

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Marko Mäkelä
On Thu, Feb 01, 2007 at 09:49:55PM +0200, Kartsa wrote: Most likely, it's me who has to be blamed. Around 1.3.27, cVideoRepacker was introduced which has an impact on CPU load. This could be a reason why the menu is slow when running several recordings at the same time. Bye. I do not

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Kartsa
Reinhard Nissl kirjoitti: Hi, Heikki Manninen wrote: I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at the same time. I remember there seemed to be no trouble

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Kartsa
Marko Mäkelä kirjoitti: On Thu, Feb 01, 2007 at 09:49:55PM +0200, Kartsa wrote: Most likely, it's me who has to be blamed. Around 1.3.27, cVideoRepacker was introduced which has an impact on CPU load. This could be a reason why the menu is slow when running several recordings at the same

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Marko Mäkelä
On Thu, Feb 01, 2007 at 10:18:03PM +0200, Kartsa wrote: Marko Mäkelä kirjoitti: I do not think that it is the reason. I checked that the cpu load was less than 10% on my 3000+ AMD and even with my 550MHz PIII less than 20% when there were 5 simultaneuous recordings. You should

Re: [vdr] Vdr or driver performance dropout

2007-02-01 Thread Kartsa
Marko Mäkelä kirjoitti: On Thu, Feb 01, 2007 at 10:18:03PM +0200, Kartsa wrote: Would it really matter in this case when cpu load was that small? I was just trying to say that even though there were almost no cpu load vdr was working sluggish. Without trying it, it is hard to say.