Result is :
-------------------------------
1 current frame + 0 field 0 flipping on field 0
1 current frame + 2 field 0 flipping on field 0
1 current frame + 40 field 0 flipping on field 0
1 current frame + 1 field 0 flipping on field 0
2 current frame + 1 field 1 flipping on field 0
12 current frame + 1 field 0 flipping on field 0
2 current frame + 1 field 1 flipping on field 0
1 current frame + 2 field 0 flipping on field 0
2 current frame + 1 field 0 flipping on field 0
... etc...
OK then, it appears that you're simply not able to generate frames fast
enough, with the effect that frames will be repeated. If that happens and
the frames are interlaced, you will see nasty judder because you get to see
something like field 1, field 2, field 3, field 4, field 3, field 4, field
7, field 8 etc.
Wherever you see '+2' in the output, that means that more than 1 frame
period has elapsed since the last frame was flipped.
You can see that often the flips occur first during field 0 of a frame, then
after a few frames, they've slipped into field 1, then you skip a frame and
go back to field 0.
I suspect that the DirectFB gfxdriver and the framebuffer are working
perfectly but your hardware is just not able to keep up with generating
frames.
307 current frame + 1 field 0 flipping on field 0
792 current frame + 1 field 0 flipping on field 0
Those bits probably displayed properly, yes?
I presume that output you quoted was for the software decode case? How does
it look when you use the hardware decoder?
M.
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
