This is best demonstrated using an example:
export GST_DEBUG="*:2"
1) gst-launch playbin2 uri=http://media.w3.org/2010/05/sintel/trailer.webm
2) gst-launch playbin2 uri=http://media.w3.org/2010/05/sintel/trailer.webm video-sink="multiqueue ! mfw_v4lsink"
3) gst-launch playbin2 uri=http://media.w3.org/2010/05/sintel/trailer.webm video-sink="queue ! mfw_v4lsink"
4) gst-launch playbin2 uri=http://media.w3.org/2010/05/sintel/trailer.webm video-sink="queue2 ! mfw_v4lsink"
Playback for 1) and 2) is good, where as playback for 3) and 4) starts of choppy, stalls and gets lots of messages of the form:
0:00:00.472157023 7566 0x40d60150 WARN vpudec vpudec.c:1578:gst_vpudec_chain: Got no frame buffer message, return 0x89, 10 frames in displaying queue!!
GST_DEBUG=GST_ELEMENT_FACTORY:3 shows that playbin2 without the video-sink property uses 'multiqueue'.
So, it looks as if something is going on with 'vpudec' when the pipeline includes a 'queue' or 'queue2' element.
This was running on a Wandboard Quad using an image built using Yocto.
Can anyone explain what's going on here?