Bug 5202

Summary: distorted images from gstreamer
Product: [Build System, Metadata & Runtime] BSPs Reporter: Dennia Han <jshan>
Component: bsps-meta-fsl-armAssignee: Otavio Salvador <otavio>
Status: RESOLVED NOTABUG QA Contact:
Severity: critical    
Priority: Medium CC: angolini, otavio, picmaster, sgw
Version: 1.4.2   
Target Milestone: Future   
Hardware: Other   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
1280x720, H264 none

Description Dennia Han 2013-09-16 08:38:28 UTC
Created attachment 1498 [details]
1280x720, H264

display images in fullscreen are distorted in gstreamer while the resized are fine.

attached sample video clip reproduces the result.

tested env:
display: HDMI 720P ( uboot: video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24 )
media: 1280x720 resolution media file.
app: qmediaplayer
Comment 1 Saul Wold 2014-05-12 16:17:11 UTC
Please update status
Comment 2 Daiane 2014-05-27 13:14:19 UTC
What is the backend used? Can you share the DISTRO_FEATURE to reproduce the issue?

Or even better, can you, please, test it again in daisy?

Thanks
Comment 3 Nikolay Dimitrov 2014-11-05 19:05:27 UTC
The reason for this issue is that mfw_isink doesn't have the option "force-aspect-ratio", so the described behavior of "distorted video" is expected (it generally means changed aspect-ratio).

One possible work-around for the issue is to use apply properly calculated scaling when using mfw_isink. Another option is to use mfw_v4lsink plugin instead, which supports "force-aspect-ratio" option. Here's an example media pipeline, that can be used to observe the proper behavior:

gst-launch playbin2 uri=file:///video.mp4 video-sink="mfw_v4lsink force-aspect-ratio=true"

It's possible that this solution is not appropriate for all use cases, as the mfw_v4lsink plugin doesn't support the IPU FG/BG layers alpha-blending.

I can also confirm that the described behaviors of both mfw_isink and mfw_v4lsink can be observed with the current "daisy" code.
Comment 4 Otavio Salvador 2014-11-05 20:54:24 UTC
Hello,

First, thank you for the detailed answer.

(In reply to comment #3)
> I can also confirm that the described behaviors of both mfw_isink and
> mfw_v4lsink can be observed with the current "daisy" code.

Is it possible for you to try the Dizzy branch? It has updated codecs and might offer better results (or not).
Comment 5 Nikolay Dimitrov 2014-11-13 22:41:36 UTC
Hi Otavio. Just tested the gstreamer behavior on Dizzy branch, and it's exactly the same as reported previously.
Comment 6 Stephen K Jolley 2014-12-01 18:20:10 UTC
It appears the NEEDINFO request has been answered
Comment 7 Nikolay Dimitrov 2014-12-01 18:39:25 UTC
The way I see this issue is that mfw_isink plugins needs the "force-aspect-ratio" property to be implemented. After this is done, mfw_isink will behave as well as mfw_v4lsink, which means that all media streams containing proper metadata (width/height/pixel-aspect-ratio) will be displayed with correct aspect-ratio.

In all other cases the image will be displayed with geometric distortion, but this wouldn't be a defect in neither Gstreamer nor fsl-gstreamer-plugins. In such cases the end-user will need to manually specify the video width/height.
Comment 8 Daiane 2015-10-21 16:46:49 UTC
I'm closing this bug as "resolved" and "notabug" after one year of latest comment.

In last one year, FSL Community BSP has adopted gstreamer 1.0 and 'gst-fsl-plugin' was replaced by 'gst1.0-fsl-plugin', and 'gstreamer-imx' has been used and maintained by community (in github) very responsiveness.

In case this is still something still to be discussed, we can reopen this bug, although I think it was stressed enough now.