Quoting Ville Syrj?l? ([EMAIL PROTECTED]):
> I'm sure everyone remembers Brian's CRTC2 troubles. Well I think we
> managed to fix it off list some time ago. The problem was caused by
> displaying the fields in the wrong order.
>
> Here's a patch with the solution I came up with. It adds a new method
> IDirectFBDisplayLayer::SetFieldParity() to select which field is displayed
> first after a Flip(). This behaviour isn't always the best choice so I
> added {DLCAPS,DLOP}_FIELD_PARITY flags.
I applied your patch, thanks ;)
> Is the term "field parity" correctly used here? I'm not very well informed
> on video terminology.
Sounds good. But I don't know the official term either.
> My first implementation used IDirectFBSurface::SetField() for this but I
> think it's better to have a private method for this. Or is it?
The extra method is good. SetField() just sets the current output field
for deinterlacing. For software deinterlacing it sets which field is blitted
from next. For hardware deinterlacing (e.g. BES) it sets the field that is
displayed. But I don't know if the BES switches the field immediately.
So the SetField() method has nothing to do with flipping. It's mainly used
on single buffered surfaces.
> Should IDirectFBDisplayLayer::WaitForSync respect this too?
Does it sync on each field?
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
Convergence GmbH
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-dev" as subject.
