Re: Any hope of vblank-synchronized rendering (from vivante) on i.MX6 soon?

[Carlos Rafael Giani <dv@pseudoterminal.org>]

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

This is probably because v4l somehow uses vsync directly. Keep in mind 
that v4l bypasses X11.
Also, you can use qt5 with pure framebuffer output. There, vsync works.

On 2014-09-23 19:19, Alfonso Tamés wrote:
>
>
> Yes, the attached test video is tearing in EGL FB without X11/wayland.
>
> This tears:
>
> gst-launch-1.0 -v filesrc location=vttest.mp4 typefind=true ! qtdemux 
> ! h264parse ! imxvpudec ! imxeglvivsink
>
> This does not tear:
>
> gst-launch -v filesrc location=vttest.mp4 typefind=true ! aiurdemux ! 
> queue ! vpudec ! mfw_v4lsink
>
> I was jut starting a project using qt-gst gl video sink. I guess it 
> will be a dead end
>
> :(
>
>
>
>
>
> On Sep 23, 2014, at 11:48 AM, Prabhu S <prabhusundar@gmail.com 
> <mailto:prabhusundar@gmail.com>> wrote:
>
>> i.MX6 X11 EGL is single buffered and there is no support for VSYNC. 
>> The tearing with X11 is a known issue. We did investigate to fix 
>> this, but the solution becomes too hacky and cannot be used in 
>> production systems.
>>
>> We are adding VSYNC support in Wayland. eglSwapInterval will be 
>> supported for FBDEV and Wayland backends in the upcoming release(in 
>> january). So Ozone-wayland can take advantage of this.
>>
>> On Tue, Sep 23, 2014 at 9:55 AM, Carlos Rafael Giani 
>> <dv@pseudoterminal.org <mailto:dv@pseudoterminal.org>> wrote:
>>
>>     On 09/23/2014 04:50 PM, Daiane Angolini wrote:
>>
>>         On Tue, Sep 23, 2014 at 11:31 AM, Gerard Bucas
>>         <gerard.b@tekmagic.net <mailto:gerard.b@tekmagic.net>> wrote:
>>
>>             I agree Carlos!
>>
>>             This is a show-stopper for applications in markets like
>>             the Digital Signage market - which could be huge for the
>>             i.MX6. The i.MX6 could be the best "media player" out
>>             there but the problems related to video playback in a
>>             browser (like Chrome/Chromium) needs to be solved wih the
>>             highest priority and at the highest level.
>>
>>             There seem to be TWO main issues:
>>
>>         Do you have only 2 issues? Have you double checked if they
>>         are/are not
>>         reported in bugzilla?
>>
>>         Do you have the detailed step-by-step? I want to reproduce them.
>>
>>         Daiane
>>
>>
>>     Daiane,
>>
>>     try out the attached HTML example. It draws a white vertical bar
>>     on a black background, and moves that bar horizontally. Run this
>>     on an imx6 in Chromium in X11, and you will see how severe the
>>     tearing is.
>>
>>     --
>>     _______________________________________________
>>     meta-freescale mailing list
>>     meta-freescale@yoctoproject.org
>>     <mailto:meta-freescale@yoctoproject.org>
>>     https://lists.yoctoproject.org/listinfo/meta-freescale
>>
>>
>> -- 
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org <mailto:meta-freescale@yoctoproject.org>
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>


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