From: Chris Tapp <opensource@keylevel.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Gstreamer pipeline problem
Date: Wed, 10 Jul 2013 20:53:58 +0100 [thread overview]
Message-ID: <CC208FFA-C689-4892-8764-4F5CCCACB2E0@keylevel.com> (raw)
In-Reply-To: <D775EFAA-7E4F-42C0-84D0-7A8D0A85A401@keylevel.com>
On 10 Jul 2013, at 20:19, Chris Tapp wrote:
> I've got an application which uses playbin2 to capture video. The pipeline is of the form:
>
> playbin2 uri=... video-sink="queue2 ! videoscale ! video/x-raw-rgb, pixel-aspect-ratio=1/1, width=<capture-width>, height=<capture-height> ! fakesink"
>
> I then get the "frame" property from the pipeline and use this to grab the latest frame.
>
> This works on my development system (Ubuntu 11.10) and a Cedar Trail / Yocto system, but the pipeline fails on the Wandboard Quad. I think this is related to:
>
> 0:00:13.028151336 1349 0x4442d520 WARN basetransform /media/SSD-RAID/build-danny-wandboard/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/libs/gst/base/gstbasetransform.c:1304:gst_base_transform_setcaps:<videoscale0x2ab820> transform could not transform video/x-raw-yuv, width=(int)854, height=(int)480, framerate=(fraction)24/1, format=(fourcc)I420, interlaced=(boolean)false in anything we support
>
> I added an ffmpegcolorspace element betwween the queue2 and the videoscale to get round this and the pipeline now builds, but only a few frames are captured. There are different diagnostics showing:
>
> 0:00:02.881403000 1361 0x28da60 WARN vpudec vpudec.c:914:gst_vpudec_core_create_and_register_frames: Allocate Internal framebuffers!!!!
> Message Callback : Element playbin0x250b68 changed state from READY to PAUSED.
> 0:00:03.237675000 1361 0x28da60 WARN vpudec vpudec.c:1578:gst_vpudec_chain: Got no frame buffer message, return 0x89, 8 frames in displaying queue!!
> 0:00:03.242324334 1361 0x28da60 WARN vpudec vpudec.c:1578:gst_vpudec_chain: Got no frame buffer message, return 0x89, 8 frames in displaying queue!!
>
> <lots of repeats>
>
> 0:00:08.499914334 1382 0x28d860 WARN vpudec vpudec.c:1655:gst_vpudec_chain: Retry too many times, maybe BUG!!
> 0:00:08.500784667 1382 0x28d860 WARN vpudec vpudec.c:1578:gst_vpudec_chain: Got no frame buffer message, return 0x88, 8 frames in displaying queue!!
>
> <lots of repeats>
>
> Message Callback : Element playbin0x250aa0 changed state from PAUSED to PLAYING.
> 0:00:09.253202667 1382 0x28d860 WARN vpudec vpudec.c:1578:gst_vpudec_chain: Got no frame buffer message, return 0x88, 8 frames in displaying queue!!
>
> 0:00:13.364523335 1460 0x142ec0 WARN mfw_v4lsink mfw_gst_v4l_buffer.c:435:mfw_gst_v4l2_new_buffer: Try new buffer failed, ret 2 No such file or directory queued 0
>
>
> The "Message Callback" events are my own logging to try and see what's happening in my app.
>
> Is this something I'm doing wrong, or are these messages a real issue somewhere?
This is when playing a .webm. The results for an .flv are as expected.
Chris Tapp
opensource@keylevel.com
www.keylevel.com
next prev parent reply other threads:[~2013-07-10 19:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 19:19 Gstreamer pipeline problem Chris Tapp
2013-07-10 19:53 ` Chris Tapp [this message]
2013-07-11 8:39 ` Thomas Senyk
2013-07-11 23:22 ` Chris Tapp
2013-07-12 0:22 ` John Weber
2013-07-12 7:50 ` Chris Tapp
2013-07-12 8:03 ` Philip Craig
2013-07-12 8:19 ` Chris Tapp
2013-07-12 14:12 ` John Weber
2013-07-12 16:44 ` Chris Tapp
2013-07-15 8:02 ` Thomas Senyk
2013-07-15 16:42 ` Chris Tapp
2013-07-12 16:35 ` Chris Tapp
2013-07-15 8:24 ` Thomas Senyk
2013-07-15 16:41 ` Chris Tapp
2013-07-15 17:11 ` Thomas Senyk
2013-07-15 20:58 ` Chris Tapp
2013-07-16 19:15 ` vpudec doe not like "queue(2)" - Was: " Chris Tapp
2013-07-16 20:18 ` John Weber
2013-07-17 19:57 ` Chris Tapp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CC208FFA-C689-4892-8764-4F5CCCACB2E0@keylevel.com \
--to=opensource@keylevel.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.