[Bug 722686] omxvideodec: integrate resize component

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=722686
  GStreamer | gst-omx | git

--- Comment #26 from Julien Isorce <julien.isorce at gmail.com> 2014-10-01 07:38:46 UTC ---
Hi Sebastian, what you have suggested is great!
I would be very interested but I don't have enough time to properly do it. (and
no rpi right now but that's a minor pb)

I can point where is the latest code:
All the commits from "omxvideodec: integrate resize component on RPI" to the
head commit :
http://cgit.collabora.com/git/raspberry-pi/gst-omx.git/log/?h=rpi-1.0.0.1

Josep already started to squash some commits, addressed some remarks from
comment #14, and more cleanup. His latest work is here:
http://cgit.collabora.com/git/user/julien/gst-omx.git/commit/?h=resize_josep_last&id=50a954824a8a7770b53961efff06886d3d6815a5

1: The first step is to start from the commit "omxvideodec: integrate resize
component on RPI" in "resize_josep_last" branch. And merge commits from branch
rpi-1.0.0.1 into branch "resize_josep_last" and squash them.

2: Second step is to apply what you suggested, i.e. some helpers to setup a
tunnel to avoid duplicating code.  If it's easier, note that the tunnel has
minimum 1 element and maximum 2 elements in our case.

- Josep do you have time to do step1 ?

- Sebastian do you think we should consider that we only have 1-2 elements, or
the general case N ? Also in our case, the decoder component is always the
first one, we just try a list of element (egl, resize)  to tunnel with the
decoder. For the resize component we add it only if the decoder cannot do it
itself. For the eglimage component it's different, we always try at the
beginning because it's more efficient.
But once the second element is decided, the code is very similar.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.