From: "Paweł Żabiełowicz" <pawel.zabielowicz@satel.pl>
To: meta-freescale@yoctoproject.org
Subject: Re: imxipuvideosink in 3.10.53 on Nitrogex6xlite
Date: Tue, 19 May 2015 08:48:09 +0200 [thread overview]
Message-ID: <555ADCA9.8080302@satel.pl> (raw)
In-Reply-To: <5559D536.5030206@mlbassoc.com>
Indeed the problem was with the pipeline. The 'h264parse' was missing
after depay plugin. Test with 'videotestsrc' was successful and using
either 'imxeglvivsink' or 'imxipuvideosink' I was able to see the
rendered video.
Thank you for the tip.
Pawel
On 18.05.2015 14:04, Gary Thomas wrote:
> On 2015-05-18 02:18, Nikolay Dimitrov wrote:
>> Hi Pawel,
>>
>> On 05/18/2015 08:34 AM, Paweł Żabiełowicz wrote:
>>> Hi all,
>>>
>>> I'm having some problems running video playback on Nitrogen6x-Lite. I'm
>>> using fido with 3.10.53 kernel. Display is running properly as I see a
>>> console after start, but starting any simple video with Gstreamer1.0 +
>>> gstreamer-imx plugins does not give any video output, even though the
>>> decoding looks like it's working.
>>>
>>> Gstreamer log:
>>> gst-launch-1.0 rtspsrc location=rtsp://watch:watch13579
>>> 192.168.7.24:554/profile3/media.smp ! rtph264depay ! imxvpudec !
>>> imxipuvideosink
>>> [INFO] Product Info: i.MX6Q/D/S
>>> Pipeline is live and does not need PREROLL ...
>>> Progress: (open) Opening Stream
>>> Progress: (connect) Connecting to
>>> rtsp://192.168.7.24:554/profile3/media.smp
>>> Progress: (open) Retrieving server options
>>> Progress: (open) Retrieving media info
>>> Progress: (request) SETUP stream 0
>>> Progress: (request) SETUP stream 1
>>> Progress: (open) Opened Stream
>>> Setting pipeline to PLAYING ...
>>> New clock: GstSystemClock
>>> Progress: (request) Sending PLAY request
>>> Progress: (request) Sending PLAY request
>>> Progress: (request) Sent PLAY request
>>> ^Chandling interrupt.
>>> Interrupt: Stopping pipeline ...
>>> Execution ended after 0:00:15.125067669
>>> Setting pipeline to PAUSED ...
>>> Setting pipeline to READY ...
>>> Setting pipeline to NULL ...
>>> Freeing pipeline ...
>>>
>>> Plugins installed:
>>>
>>> gst-inspect-1.0 | grep imx
>>> imxipu: imxipuvideotransform: Freescale IPU video transform
>>> imxipu: imxipuvideosink: Freescale IPU video sink
>>> imxvpu: imxvpudec: Freescale VPU video decoder
>>> imxvpu: imxvpuenc_h263: Freescale VPU h.263 video encoder
>>> imxvpu: imxvpuenc_h264: Freescale VPU h.264 video encoder
>>> imxvpu: imxvpuenc_mpeg4: Freescale VPU MPEG-4 video encoder
>>> imxvpu: imxvpuenc_mjpeg: Freescale VPU motion JPEG video encoder
>>> imxg2d: imxg2dvideosink: Freescale G2D video sink
>>> imxg2d: imxg2dvideotransform: Freescale G2D video transform
>>> imxaudio: imxuniaudiodec: Freescale i.MX uniaudio decoder
>>> imxv4l2src: imxv4l2src: V4L2 CSI Video Source
>>> imxpxp: imxpxpvideosink: Freescale PxP video sink
>>> imxpxp: imxpxpvideotransform: Freescale PxP video transform
>>> imxeglvivsink: imxeglvivsink: Freescale EGL video sink
>>>
>>> While using imxeglvivsink I'm seeing red flash for few milliseconds over
>>> the console and that's it.
>>> Any advices will be helpful.
>>
>> Please download this file and try a local file playback, to eliminate
>> possible networking issues:
>>
>> https://download.blender.org/durian/trailer/sintel_trailer-1080p.mp4
>>
>> Also, please check whether an automatically constructed pipeline is
>> able to play the file above:
>>
>> gst-launch-1.0 playbin uri=file:///sintel_trailer-1080p.mp4
>>
>> You can try same tests with Xorg running.
>
> What would that pipeline look like (to force the result into a window
> on the screen)? As is, this simple command takes over the entire screen.
>
>
prev parent reply other threads:[~2015-05-19 6:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 5:34 imxipuvideosink in 3.10.53 on Nitrogex6xlite Paweł Żabiełowicz
2015-05-18 7:48 ` Carlos Rafael Giani
2015-05-18 8:18 ` Nikolay Dimitrov
2015-05-18 12:04 ` Gary Thomas
2015-05-18 12:26 ` Carlos Rafael Giani
2015-05-18 12:33 ` Gary Thomas
2015-05-18 15:55 ` Nikolay Dimitrov
2015-05-18 16:27 ` Gary Thomas
2015-05-18 23:52 ` Nikolay Dimitrov
2015-05-19 10:53 ` Gary Thomas
2015-05-19 11:04 ` Nikolay Dimitrov
2015-05-19 11:08 ` Gary Thomas
2015-05-19 11:11 ` Carlos Rafael Giani
2015-05-19 11:16 ` Nikolay Dimitrov
2015-05-19 11:17 ` Gary Thomas
2015-05-19 11:23 ` Carlos Rafael Giani
2015-05-19 11:54 ` Gary Thomas
2015-05-19 15:09 ` Carlos Rafael Giani
2015-05-19 15:13 ` Gary Thomas
2015-05-19 15:28 ` Nikolay Dimitrov
2015-05-21 13:53 ` Gary Thomas
2015-05-21 14:13 ` Gary Thomas
2015-05-21 14:40 ` Nikolay Dimitrov
2015-05-21 14:49 ` Nikolay Dimitrov
2015-05-21 14:46 ` Carlos Rafael Giani
2015-05-21 14:52 ` Gary Thomas
2015-05-26 13:50 ` Gary Thomas
2015-05-26 13:59 ` Carlos Rafael Giani
2015-05-26 14:04 ` Gary Thomas
2015-05-26 18:53 ` Carlos Rafael Giani
2015-05-27 12:05 ` Gary Thomas
2015-05-28 6:33 ` Carlos Rafael Giani
2015-05-28 12:11 ` Gary Thomas
2015-05-29 7:06 ` Carlos Rafael Giani
2015-05-29 7:25 ` Carlos Rafael Giani
2015-05-29 13:00 ` Gary Thomas
2015-06-02 15:34 ` Carlos Rafael Giani
2015-06-02 17:11 ` Carlos Rafael Giani
2015-06-02 17:16 ` Gary Thomas
2015-06-02 21:05 ` Carlos Rafael Giani
2015-06-02 21:19 ` Nikolay Dimitrov
2015-06-02 22:10 ` Gary Thomas
2015-06-02 22:17 ` Pushpal Sidhu
2015-06-02 22:33 ` Gary Thomas
2015-06-02 22:42 ` Pushpal Sidhu
2015-05-19 11:10 ` Nikolay Dimitrov
2015-05-19 11:19 ` Gary Thomas
2015-05-19 6:48 ` Paweł Żabiełowicz [this message]
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=555ADCA9.8080302@satel.pl \
--to=pawel.zabielowicz@satel.pl \
--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.