Quoting Mark Adams:
> > 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.
?? Why 50 frames per second ??
My understanding of setting FIELD_PARITY is, that in case of SetFieldParity(0),
the actual buffer flip is at frame boundary (top field first), whereas with
SetFieldParity(1) (bottom field first) the buffer flip happens at half frame.
> 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.
Obvious, if _in_ frame rate is higher than _out_ frame rate one has to
drop something.
But streams I've seen have 25 frames /sec (frame with to fields in interlaced).
@Laurence:
Is audio playback smooth ?
(no clicks)
Does softdevice report dropped frames ?
('+' chars written to stderr, except for start of playback)
Are there periods of '+' chars written and no chars written ?
(consider this separate for live and recording playback)
Stefan Lucke
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
