i.MX ProcessorsのトピックRe: libimxvpuapi wayland sink issue

libimxvpuapi wayland sink issue

sanjeevsharma — Mon, 27 Feb 2017 07:58:03 GMT

On Latest Freescale Yocto Release for i.MX6, we unable to play/decode H264 video using gsteamer pipeline for wayland sink. This only happens with wayland sink.

Gstreamer Pipeline being used.

# gst-launch-1.0 filesrc location=/XXX_1280x480.h264 ! h264parse ! imxvpudec ! imxipuvideotransform ! waylandsink

Error Observed.

gst-launch-1.0: ../imxvpuapi/imxvpuapi_vpulib.c:2349: imx_vpu_dec_mark_framebuffer_as_displayed: Assertion `framebuffer != NULL' failed. *Aborted (core dumped)*

On other hand, it works fine with imxipuvideosink.

gst-launch-1.0 filesrc location=/XXX_ 1280x480.h264 ! h264parse ! imxvpudec ! imxipuvideotransform ! imxipuvideosik 

I know there is recently Libimxvpuapi library has been introduced in this release which can create this issue but I am not 
sure about this.

Any pointer would be appreciated.

Re: libimxvpuapi wayland sink issue

igorpadykov — Tue, 28 Feb 2017 00:57:19 GMT

Hi sanjeev

for gstreamer-imx one can look at

trac.gateworks.com/wiki/Yocto/gstreamer

and post question on meta-fsl-arm mailing list, so that someone familiar

with it could try to assist you.
https://lists.yoctoproject.org/listinfo/meta-freescale

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: libimxvpuapi wayland sink issue

sanjeevsharma — Wed, 01 Mar 2017 08:58:54 GMT

Thanks igor.

We follow-up with Carlos dv@pseudoterminal.org, who is the maintainer of gstreamer-imx plugin for freescale regarding this issue and here is his reply.

Ah yes, I think this issue was fixed recently by this pull request: https://github.com/Freescale/gstreamer-imx/commit/678f823d9ec30921192ba08d1a0a119176730f86

We integrated suggested patch and now we don't see this issue anymore.