On Thu, 28 May 2015, Fabio Fantoni wrote: [...] > Thanks for reply, I'm preparing spice-gtk with vp8 patches armhf for > test it on arm thin client (for example raspberry 2), I want try to use > gst-omx for hardware decoding of mjpeg and vp8, can I simply build and > install gst-omx instead of gst-ffmpeg or a change in spice-gtk is needed > for use gst-omx? I have patches that could probably be useful to you for this: a simplification of the pipeline creation, optionally the use of decoebin, and for the performance aspects zero-copy for both the input buffer and the ouput frame. So I have created some github repositories to make it easier to get these: https://github.com/fgouget/spice-gtk.git * gst branch All the above except for decodebin. * decodebin branch Uses decodebin instead of manually picking the decoders. However on my machine decodebin tries to use vaapi which, given my test configuration, immediately triggers an assert, thus killing the process. Uninstalling vaapi fixes that but it's annoying. So I don't really like the decodebin approach though it's probably more a vaapi bug than a decodebin issue. https://github.com/fgouget/spice.git * gst branch The patches adding GStreamer and VP8 support. * gst-1.0 branch Experimental branch with non-functional GStreamer 1.0 and h264 code. Note that GStreamer 1.0 support can be disabled using './configure --disable-gstreamer-1.0' so H264 support can be tested too. https://github.com/fgouget/xf86-video-qxl.git * gst branch Has the patch to make it possible to specify the encoder:codec pairs in either SpiceVideoCodecs or XSPICE_VIDEO_CODECS. There are also spice-common and spice-protocol repositories but these should get pulled automatically. -- Francois Gouget <fgouget@xxxxxxxxxxxxxxx> _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel