Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-23 Thread Gerald Dachs
Am Mon, 19 Jan 2009 16:10:48 + schrieb Tony Houghton : > I noticed the bad sync too. It seemed to start off slightly out of > sync and get worse the longer I left it running, but I haven't > confirmed that. I'm using HDMI audio, you'd think the video and sound > clocks would therefore be deriv

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-22 Thread Gerald Dachs
Am Mon, 19 Jan 2009 23:28:23 +0100 schrieb Gerald Dachs : > Am Mon, 19 Jan 2009 21:39:29 + > schrieb Tony Houghton : > > > On Mon, 19 Jan 2009 18:57:51 +0100 > > Gerald Dachs wrote: > > > > > Am Mon, 19 Jan 2009 17:40:44 + > > > schrieb Tony Houghton : > > > > I'm fairly sure xvmc (whic

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-20 Thread Sascha Vogt
Hi, Gerald Dachs schrieb: >> I read something similar on the MythTV mailinglist. >> >From http://www.gossamer-threads.com/lists/mythtv/users/366684: >>> In the end I believe it was accidental code bugs when he was >>> porting the automatic letterboxing patch over to work with VDPAU >>> that caused

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Torgeir Veimo
On 20 Jan 2009, at 08:28, Gerald Dachs wrote: Am Mon, 19 Jan 2009 17:40:44 + schrieb Tony Houghton : I'm fairly sure xvmc (which xxmc is based on) isn't supported on Nvidia 8x00 and newer. 20-30% CPU usage isn't much problem, so as you aren't receiving HD anyway I'd stick with stable drive

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Gerald Dachs
Am Mon, 19 Jan 2009 21:39:29 + schrieb Tony Houghton : > On Mon, 19 Jan 2009 18:57:51 +0100 > Gerald Dachs wrote: > > > Am Mon, 19 Jan 2009 17:40:44 + > > schrieb Tony Houghton : > > > I'm fairly sure xvmc (which xxmc is based on) isn't supported on > > > Nvidia 8x00 and newer. 20-30% CP

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Tony Houghton
On Mon, 19 Jan 2009 18:57:51 +0100 Gerald Dachs wrote: > Am Mon, 19 Jan 2009 17:40:44 + > schrieb Tony Houghton : > > I'm fairly sure xvmc (which xxmc is based on) isn't supported on > > Nvidia 8x00 and newer. 20-30% CPU usage isn't much problem, so as you > > aren't receiving HD anyway I'd s

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Gerald Dachs
Am Mon, 19 Jan 2009 17:40:44 + schrieb Tony Houghton : > I'm fairly sure xvmc (which xxmc is based on) isn't supported on > Nvidia 8x00 and newer. 20-30% CPU usage isn't much problem, so as you > aren't receiving HD anyway I'd stick with stable drivers, ffmpeg and > xine etc until VDPAU is know

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Tony Houghton
On Mon, 19 Jan 2009 18:26:22 +0100 Gerald Dachs wrote: > Am Mon, 19 Jan 2009 17:03:34 + > schrieb Tony Houghton : > > > What graphics card/chip have you got? AFAIK xvmc/xxmc only works on > > NVidias up to 7x00 and VDPAU is for 8x00 and newer. If your CPU usage > > dropped significantly with

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Gerald Dachs
Am Mon, 19 Jan 2009 17:03:34 + schrieb Tony Houghton : > On Mon, 19 Jan 2009 17:40:17 +0100 > Gerald Dachs wrote: > > > Yesterday I have switched back to the use of vdpau, because I got > > now periodically hick ups with xv and xxmc, the last time I had > > this working correct I had another

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Tony Houghton
On Mon, 19 Jan 2009 17:40:17 +0100 Gerald Dachs wrote: > Yesterday I have switched back to the use of vdpau, because I got now > periodically hick ups with xv and xxmc, the last time I had this working > correct I had another CPU, mainboard and nvdida driver :(. The loss of > sync is less disturb

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Gerald Dachs
> I read something similar on the MythTV mailinglist. > >From http://www.gossamer-threads.com/lists/mythtv/users/366684: > > In the end I believe it was accidental code bugs when he was > > porting the automatic letterboxing patch over to work with VDPAU > > that caused him to end up with his OSD g

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Gerald Dachs
> I had the same problems. I didn't notice that the picture flickering > (do you get big patches of mostly green garbage?) No, not at all, always still pictures that was seen before. > was triggered by > channel changes, but that could well be the case. Only with channel changes here, and only w

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Sascha Vogt
Hi Gerald, Gerald Dachs schrieb: > [...] The biggest problem is that if I switch > channels it happens that the video starts to flicker. You can see that > between the pictures of the current channel the pictures of the previous > channel appear. Restarting vdr-sxfe fixes it till the next channel

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-19 Thread Tony Houghton
On Mon, 19 Jan 2009 00:47:17 +0100 Gerald Dachs wrote: > I have made some experiments with xineliboutput and vdpau, it looked > promising, but at least I had to give up for now. I have used vdr 1.6.0, > xineliboutput 1.0.3, nvidia driver 180.22, xine-lib-vdpau from 20090113 > and xinelib 1.1.90hg

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-18 Thread Gerald Dachs
> The biggest problem is that if I switch > channels it happens that the video starts to flicker. You can see that > between the pictures of the current channel the pictures of the > previous channel appear. I noticed now that it get worst if I use "software scaling" in the xineliboutput settings