[MPlayer-G2-dev] vp layer and config

Arpi arpi at thot.banki.hu
Mon Dec 15 10:13:02 CET 2003


> Despite it already being somewhat ugly and complicated, I'd actually
> like to propose adding some more config-time negotiations:

Instead of hacking and adding more, i would suggest to drop g1's
vf coimpletely and re-design from scratch for g2.
Yes i know i was the one against this way, but i've changed my mind :)

some issues to solve:
- runtime re-configuration (aspect ratio, size, stride, colorspace(?) changes)
- aspect ratio negotation through the vf layer to vo
  (pass thru size & aspect to the vo layer, as some vo (directx, xv) doesnt
  like all resolutions)
- window resizing issue (user resizes vo window, then reconfigure scale
  expand etc filters to produce image in new size)
- better buffer management (get/put_buffer method)
- split mp_image to colorspace descriptor (see thread on this list)
  and buffer descriptor (stride, pointers), maybe a 3rd part containing
  frame descriptor (frame/field flags, timestamp, etc so info related to
  the visual content of the image, not the phisical buffer itself, so
  linear converters (colorspace conf, scale, expand etc) could simply
  passthru this info and change buffer desc only)
- correct support for slices (note there are 2 kind of strides: one
  when you call next filter's draw_slice after each slice rendering
  to next vf's buffer completed, and the other type is when you have
  own small buffer where one slice overwrites the previous one)
- somehow solve framedropping support
  (now its near impossible in g2, as you hav eto decode and pass a
  frame through the vf layer to get its timestamp, to be used to
  decide if you drop it, but then it's already too late to drop)

i think the new vf layer is the key of near everything.

A'rpi / Astral & ESP-team

Developer of MPlayer G2, the Movie Framework for all - http://www.MPlayerHQ.hu

More information about the MPlayer-G2-dev mailing list