Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: kvdr-0.61 and xv?



On Saturday 05 June 2004 11:18, Guido Fiala wrote:
> On Saturday 05 June 2004 10:33, Gregoire Favre wrote:
> > Well, I don't know exactly... The problem I have with kvdr is that I
> > have perfect video, than a small glitch, then perfect video, then a
> > glitch... which is just annoying.
>
> Now it's more clear - it has something to do with the synchronising between
> video and Monitor. I will try using select() and see if that makes it any
> better. But there is another effect - see below.

Maybe i found something - can not remember having that problem at my old system, 
but here i had the problem, that the framerate drops almost to zero if PiP/MP was activated in Xv.

You might try the following patch:

--- kvdr.cpp.orig       2004-06-05 11:49:12.262083952 +0200
+++ kvdr.cpp    2004-06-05 11:44:44.988715680 +0200
@@ -1525,7 +1525,7 @@
            if( !stopXv && ( -1!=(my_ismv?multivideo_fd[i].handle():video_fd.handle()) ) )
            {
             vm[i].frame=vm[i].frame?0:1;
-            ioctl(my_ismv?multivideo_fd[i].handle():video_fd.handle(), VIDIOCSYNC, &(vm[i].frame));
+            if(i==my_viddev) ioctl(my_ismv?multivideo_fd[i].handle():video_fd.handle(), VIDIOCSYNC, &(vm[i].frame));
             ioctl(my_ismv?multivideo_fd[i].handle():video_fd.handle(), VIDIOCMCAPTURE, &(vm[i]));
            fstat[vm[0].frame]=0;//not exactly true, but very likely :-)
            nograb=false;

---
This is just one line changed to avoid that the SYNC is called for every device which is not intended.
To sync only at the first video device. That is not exactly correct but i don't see any easy solution to this problem.
It might now happen, that the content of the PiP is composed of 2 subsequent frames.




Home | Main Index | Thread Index