From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 2A534E009ED; Tue, 19 May 2015 08:28:20 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1318DE009F6 for ; Tue, 19 May 2015 08:28:04 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id E66BF60008B2; Tue, 19 May 2015 18:28:03 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1432049284; bh=NRxl8ALjnAsGtAnkb8sNmr1gOnZeQYVX4vMDpKKuNuQ=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ZEI9Wo17uBpXotxqlc0HXVVID2y3ZMjfjSGaUxgjJ8z+ghYE8fRthbepmLh2q9kEc 0jhj68j6Jpghrjl4+YhgW0piYPZNd9jkaLn88+tiNPllJFPjHVLFB5SGCESrqASyaL xArCTBFDse6eOdyN64mgQygBU1PMwLvRQuzgIFac= Message-ID: <555B5683.20004@mail.bg> Date: Tue, 19 May 2015 18:28:03 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Gary Thomas , meta-freescale@yoctoproject.org References: <555979FE.50306@satel.pl> <5559A04D.5080500@mail.bg> <5559D536.5030206@mlbassoc.com> <555A0B81.3090905@mail.bg> <555A130C.9060605@mlbassoc.com> <555A7B5B.90906@mail.bg> <555B1634.9050003@gmail.com> <555B18AB.4080403@mail.bg> <555B19AA.4010309@gmail.com> <555B1A48.9030303@pseudoterminal.org> <555B1BD6.7090704@mlbassoc.com> <555B1D37.4040300@pseudoterminal.org> <555B248D.2070401@mlbassoc.com> <555B5234.9060104@pseudoterminal.org> <555B5307.1030108@mlbassoc.com> In-Reply-To: <555B5307.1030108@mlbassoc.com> Subject: Re: imxipuvideosink in 3.10.53 on Nitrogex6xlite X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 15:28:20 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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