Anyone using mfw_h264decoder on i.MX53?

kartiknatarajan — Mon, 25 Feb 2013 12:08:48 GMT

Hi,

I tested the mfw_h264decoder for the first time and I have run into some issues. Please find below the (second) pipeline that is being tested. When I run that pipeline it waits for the input with the line “New clock: GstSystemClock..”

When I start an h264 stream on the other end using another imx53 device(pipeline below):

1) gst-launch mfw_v4lsrc device=/dev/video0 ! mfw_vpuencoder ! rtph264pay ! udpsink host=192.168.0.179 port=9020 sync=false

The pipeline being tested crashes

2) root@imx53qsb:~# gst-launch -v udpsrc port=9020 ! "application/x-rtp, payload=96" ! rtph264depay ! mfw_h264decoder ! "video/x-raw-yuv, height=640, width=480, framerate=25/1" ! mfw_v4lsink sync=false

H264D_ARM11_02.06.01 build on Jul 12 2011 13:38:27.

MFW_GST_H264_DECODER_PLUGIN build on Jan 13 2013 10:36:16.

MFW_GST_V4LSINK_PLUGIN build on Jan 13 2013 10:36:03.

Setting pipeline to PAUSED ...

Pipeline is live and does not need PREROLL ...

Setting pipeline to PLAYING ...

New clock: GstSystemClock

/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = application/x-rtp, payload=(int)96, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264

/GstPipeline:pipeline0/GstRtpH264Depay:rtph264depay0.GstPad:src: caps = video/x-h264, stream-format=(string)byte-stream, alignment=(string)nal

/GstPipeline:pipeline0/GstRtpH264Depay:rtph264depay0.GstPad:sink: caps = application/x-rtp, payload=(int)96, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264

/GstPipeline:pipeline0/MFW_GST_H264DEC_INFO_T:mfw_gst_h264dec_info_t0.GstPad:sink: caps = video/x-h264, stream-format=(string)byte-stream, alignment=(string)nal

/GstPipeline:pipeline0/MFW_GST_H264DEC_INFO_T:mfw_gst_h264dec_info_t0.GstPad:src: caps = video/x-raw-yuv, format=(fourcc)I420, width=(int)0, height=(int)0, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)25/1, crop-left-by-pixel=(int)16, crop-top-by-pixel=(int)16, crop-right-by-pixel=(int)16, crop-bottom-by-pixel=(int)16, num-buffers-required=(int)21, sfd=(int)1

Caught SIGSEGV accessing address 0x2b785228

Spinning. Please run 'gdb gst-launch 1669' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

My observation is that the decoder sets the height and width to 0, even though I set its caps to certain values.

Please advice

Re: Anyone using mfw_h264decoder on i.MX53?

fabio_estevam — Mon, 25 Feb 2013 16:35:25 GMT

mfw_h264decoder is a software decoder. mx53 has a hardware decoder (VPU) and you should use mfw_vpudecoder instead.

i.MX ProcessorsのトピックRe: Anyone using mfw_h264decoder on i.MX53?

Anyone using mfw_h264decoder on i.MX53?

Re: Anyone using mfw_h264decoder on i.MX53?