On Fri, 2005-11-04 at 10:14 +0000, Mark Adams wrote: > > Enabling my DLOP_FIELD_PARITY stuff with DLBM_TRIPLE (no > > DLOP_DEINTERLACING): > > I'm back at my weird stuttering/timing as before. > > > > Triple buffering is definitely helping me but there is just something about > > DLOP_FIELD_PARITY it doesn't like at the moment. > > OK, I think you need to look up-stream. With field parity enabled, > you need to be supplying _frames_, 25 times a second. Without it, you > need to supply fields or frames 50 times a second. If the up-stream > code is generating 50 pictures per second, it's certainly going to > stutter if they only go out 25 times a second.
That sounds about right like it could be the problem and would make sense with what I'm seeing. Should DLOP_FIELD_PARITY work exactly the same as with a Matrox card? In my changes to softdevice, I pretty much copied the code which was there for Matrox TV-out (unless I missed a bit, of course!) and I believe that is meant to work well (not that I could get anything out of the Matrox card I got a few weeks back!). I.e. I don't think that enabling Matrox TV-out does anything like switching from 50 fields per second to 25 full, interlaced frames per second. I'll delve deeper... Cheers, Laz _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
