[Bug 747297] gl: live rpicamsrc/omxh264dec/glimagesink pipeline fails

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=747297

--- Comment #19 from Julien Isorce <julien.isorce at gmail.com> ---
(In reply to Nicolas Dufresne (stormer) from comment #15)
> Note, I never seem video playback working at 128 mb on the Pi, shall we
> close this bug ?

It rings some bells, I remember that it required to set 256 mb for the gpu. The
default (128) was not working for 1080p but I have been always surprised of
this.


(In reply to Florent Thiéry from comment #16)
> gst-launch-1.0 videotestsrc pattern=2 ! video/x-raw\,\
> format\=\(string\)YUY2\,\ width\=\(int\)1920\,\ height\=\(int\)1080\,\
> framerate\=\(fraction\)30/1 ! fakesink sync=false silent=false -v
> 
> Well, it does work, quite slowly at 1080p (~3.2 fps), but it does. What do
> you mean by "working" ? ;)

You get 3 fps with this above pipeline ? That's due do videotestsrc not using
SIMD through orc since by default it is disabled on arm, see
http://cgit.freedesktop.org/gstreamer/orc/tree/configure.ac#n169 . The distro
you are using would have to enable it manually. (It was enabled there
https://git.collabora.com/cgit/raspberry-pi/ sometime ago but I could not find
it anymore)

I remember I could have +25fps with videotestsrc ! ximagesink for 720p when
liborc is enabled on arm. Same with omxh264dec ! ximagesink with 720p with
gst-omx from https://git.collabora.com/cgit/raspberry-pi/gst-omx.git/.


(In reply to Florent Thiéry from comment #18)
> (In reply to Julien Isorce from comment #14)
> > That's huge!  We should avoid using useless Frame Buffer Objects in the
> > glimagesink bin: gluploadelement ! glcolorconvert ! glimagesinkelement
> > (Indeed a FBO by itself uses memory in addition to the pool of
> > textures/eglimages)
> 
> After checking, the large memory amount does not seem to be allocated by
> gstgl alone (at least not in 1.6.2), because with a small amount of reserved
> memory (gpu_mem=64) i can display upto 2049x1000 YUY2 (glvideoconvert used)
> or 10000x1000 RGBA (glvideoconvert apparently in passthrough).

omxh264dec will also use a lot of gpu mem since this mem is used by the HW
decoder.

How much gpu mem is used if you only do omxh264dec ! .. ! ximagesink (no gl)
with 1080p ?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.