Morty Yocto Release wayland sink issue

Morty Yocto Release wayland sink issue

[sanjeev sharma]

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

Hi,

On Morty Yocto Release, we unable to play/decode H264 video on nitrogen6x
using gsteamer pipeline for wayland sink. This only happens with wayland
sink.

Gstreamer Pipeline:

# 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=/usr/share/early-data/xse_splash_1280x480.h264 ! h264parse !
imxvpudec ! imxipuvideotransform ! imxipuvideosik

I know there is recently* Libimxvpuapi library* has been introduced in
this release which may creating this issue.

Any pointer would be appreciated.

Regards

Sanjeev Sharma

[-- Attachment #2: Type: text/html, Size: 1762 bytes --]

Re: Morty Yocto Release wayland sink issue

[sanjeev sharma]

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Adding Carlos,

Regards
Sanjeev Sharma

On Tue, Feb 28, 2017 at 11:21 AM, sanjeev sharma <
sanjeevsharmaengg@gmail.com> wrote:

> Hi,
>
> On Morty Yocto Release, we unable to play/decode H264 video on nitrogen6x
> using gsteamer pipeline for wayland sink. This only happens with wayland
> sink.
>
> Gstreamer Pipeline:
>
> # 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=/usr/share/early-data/xse_splash_1280x480.h264 ! h264parse ! imxvpudec ! imxipuvideotransform ! imxipuvideosik
>
> I know there is recently* Libimxvpuapi library* has been introduced in this release which may creating this issue.
>
> Any pointer would be appreciated.
>
> Regards
>
> Sanjeev Sharma
>
>

[-- Attachment #2: Type: text/html, Size: 2487 bytes --]