On Thursday 03 November 2005 14:53, Mark Adams wrote:
> > What I had done was reenable a couple of sections of commented out code.
> > I have reenabled both DLBM_TRIPLE and DLOP_DEINTERLACING, if
> > supported.
> > This is a serious improvement on what I was getting! Maybe getting
> > DLOP_FIELD_PARITY to work properly would be the icing on the cake but
> > for now it's good.
>
> Deinterlacing makes no sense in combination with field parity. So
> what happens if you enable triple buffering, disable deinterlacing and
> enable field parity?
After a couple of quick tests:
Disabling DLOP_DEINTERLACING and leaving as DLBM_TRIPLE and no
DLOP_FIELD_PARITY:
Good A-V sync and no stuttering but the field sync reverses for a few
frames
every few seconds. Less watchable than with DLOP_DEINTERLACING but I presume
this would be a better picture if field synced properly.
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.
I'll try to fiddle some more...
Cheers,
Laz
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
