[meta-freescale] imxipuvideosink in 3.10.53 on Nitrogex6xlite

Nikolay Dimitrov picmaster at mail.bg
Tue May 19 08:28:03 PDT 2015


Hi Gary,

On 05/19/2015 06:13 PM, Gary Thomas wrote:
> On 2015-05-19 09:09, Carlos Rafael Giani wrote:
>> It is strange that gtk-play isn't picking this one. Anyway, if you
>> explicitely pick it, you should have windowed output.
>
> Do you know how I can force that?

Hehe, one ugly way to do this is to delete the overlay plugin, thus
gtk-play won't have a big choice ;).

>> Am 2015-05-19 um 13:54 schrieb Gary Thomas:
>>> On 2015-05-19 05:23, Carlos Rafael Giani wrote:
>>>>
>>>>
>>>> Am 2015-05-19 um 13:17 schrieb Gary Thomas:
>>>>> On 2015-05-19 05:11, Carlos Rafael Giani wrote:
>>>>>>
>>>>>>>>> Thanks for the explanation, perhaps it can help someone fix
>>>>>>>>> this.  My
>>>>>>>>> guess is that the FSL plugin doesn't handle those dynamic
>>>>>>>>> elements and
>>>>>>>>> thus is not equipped to set up the render in the appropriate
>>>>>>>>> window on
>>>>>>>>> the screen.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Also the full-screen behavior depends the videosink
>>>>>>>>>>>> configuration, so
>>>>>>>>>>>> hard to give universal answer, as none will fit all cases.
>>>>>>>>
>>>>>>>> I doubt that the issue is caused exactly by the GstImxVpuDec or
>>>>>>>> GstOverlaySink, as by looking at your pipeline they seem to have
>>>>>>>> static pads. So it's more of how the
>>>>>>>> playbin/decodebin bins handle the pipeline creation process...
>>>>>>>
>>>>>>> All I know is that it does work correctly on other platforms, e.g. a
>>>>>>> native x86 (intel-corei7-64), as well as when there are no i.MX
>>>>>>> plugins
>>>>>>> installed, so it's definitely tied to the FSL plugin.
>>>>>>
>>>>>> The issue here is that the IPU sink does not know anything about
>>>>>> windows. It directly overwrites the framebuffer's pixels. One way
>>>>>> I am trying out is to create an empty window in
>>>>>> the sink and let the IPU overwrite its pixels, but this is not
>>>>>> exactly clean, and can cause artifacts. If you want to render to a
>>>>>> window, I recommend using the imxeglvivsink
>>>>>> instead. In fact, this should be the default one. How did you get
>>>>>> the plugins?
>>>>>
>>>>> Nothing special, I simply included gst1.0-fsl-plugin in my image.
>>>>> I'm building my own X based image, which includes these packages:
>>>>>           gst-player-bin
>>>>>           gstreamer1.0-libav
>>>>>           gst1.0-fsl-plugin
>>>>>           gstreamer1.0-plugins-imx
>>>>>
>>>>
>>>> What do you get when you run "gst-inspect-1.0 imxeglvivsink" ?
>>>
>>> Output attached.
>>>
>>> Note: based on my capture of the gstreamer info (.dot), that plugin
>>> is not what is being used by gtk-play/gst-play.  You can find the .dot
>>> file in a previous reply on this thread (yesterday) or I'll send it
>>> again if you need.

Regards,
Nikolay


More information about the meta-freescale mailing list