From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id EEC84E009DA; Tue, 19 May 2015 04:16:23 -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 95ADDE009B6 for ; Tue, 19 May 2015 04:16:20 -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 29E3160006F3; Tue, 19 May 2015 14:16:19 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1432034179; bh=V8PJh7qOPi65G6zf0HKCMMFgUfKenVJTtMwPgNCV5Xk=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=UK2A7qGkTVyCeKGcOJXs2tN7JjKSRz0VqPWjvhVzHO24qHxB67W6IGWizslO9tOeN sonUJqSuRX9QBsBkPugUISbYuMFbM8KXSBgDJEg5BPXZKqsJzSJNUBGI9vu/mY0I2t Ne20e4SJCnf7+gRLVaV2cxgftW7v+6ahyZSrCrqE= Message-ID: <555B1B82.6050308@mail.bg> Date: Tue, 19 May 2015 14:16:18 +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: Carlos Rafael Giani , 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> In-Reply-To: <555B1A48.9030303@pseudoterminal.org> 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 11:16:24 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Carlos, On 05/19/2015 02:11 PM, 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? You're talking about X11 overlay, is it correct? Regards, Nikolay