On EMGD graphics based platforms such as crownbay, the sato video player is not able to play video files. If it starts playing then the video goes bad quickly after starting the playback. On these platforms the command line gstreamer is able to play video fine. The command used to play video on command line is: gst-launch playbin2 uri="file:///home/root/myvideo.mp4" Other Intel Graphics based platforms such as Sugarbay or Chiefriver, the sato video player is able to play the video fine, but it is consuming much more cpu. It consumes 5% to 10% cpu on sugarbay & chiefriver. On the same platforms the command line gstream video player consumes 0% to 1% cpu. BTW Sample Video files for playback can be downloaded from this site: http://www.h264info.com/clips.html - Nitin
CCing Ross
So the sato video player (correctly called libowl-av) uses playbin2 but does construct a video sink directly. Can you confirm that "gst-inspect autovideosink" works for your image? My hunch is that the problem is that libav-owl is forcing a X-based sink, but as you're using VAAPI you need vaapisink. This toy application is pretty old and predates VAAPI existing IIRC. I *think* this can be solved by - as usual - deleting code in libowl-av.
There is an ancient bug related to this: Bug 615 https://bugzilla.yoctoproject.org/show_bug.cgi?id=615
libowl-av needs to let the pipeline construct a sink and use it, instead of passing the pipeline its own sink.
Merging into the master video player bug. *** This bug has been marked as a duplicate of bug 5206 ***
verified as per above comments.